BIG IP appliance is not booting when AOM interface is attachned to the switch
Hello Everyone. I work as a system engineer at IT Integrator company. Unfortunately I don't have much experience with f5 devices so I need your help. Couple days ago, we have installed two i4600 devices in customer's datacenter. The datacenter is also new, customer plans to migrate existing infrastructure to this new one, that's why there is no network infrastructure yet in new DC. I mean, there is network hardware installed, but they're not configured yet. That's why, when we've installed BIG IPs into racks, I've just connected Console interfaces into TOR switch with standard RJ45 patch cord, but didn't configured AOM itself, as there's no VLANs yet. I've had startup of both devices (customer gave me only MGMT network), activated them, upgraded TMOS versions and when I've restarted them, the devices didn't booted. I've been waiting for more than 10 minutes, after I connected to the Console port via standard (serial) console cable and as soon, as I connected and pushed on Enter, the system started to Boot. As if it was waiting to some actions from Console. I've disconnected cables from Console ports (which were connected into switches) and tried to restart devices 2 times, both were successful. Then I've connected the cables back (console port to switches) and again, after restarting appliances, they refuse to boot, unless I connect serial console cable to console port and TMOS is starting booting immediately. Is that some kind of pre-configured feature which I can disable from tmsh, is that due to the not configured AOM, or is that bug? Did anyone faced that behavior? The devices came with two versions of software 13 and 15. I tried on both of them and the result is the same. I really appreciate your suggestions, do you even configure/use that Console port with AOM IP configured and should it be constantly connected to network, or should I treat it as an ordinary Out-of-Management/LOM/IPMI port which will be used only in emergency situations, physically connecting serial cable. I didn't manage to find much information about f5's AOM management and as it has feature to assign IP address to that port, I thought that it will be good idea, to connect it to the switch permanently, so that Administrator will be able to connect to it remotely via AOM IP. Thanks in advance and sorry for long text :-)
Power cycle using AOM?
Hello, I could not find a definitive answer or article describing the AOM option P. My question is - can I use the AOM option P to power cycle a VCMP host that got stuck during reboot? Meaning, if I use the AOM option P to power off, will I be able to also use AOM to power ON the system afterwards? Or is it only meant to be used after halting the system from bash.. Thanks a lot for any advice. Michal
Active serial console on Viprion chassis with two blades
Hi there, I got a Viprion 2400 chassis with two 2150 blades in slots 1 and 2. I've connected the console ports of both blades to my console server but I'm getting confused with how the consoles are working. I'd expect to get login (or AOM access) on both consoles or at least in the console of the blade that has the role of master in the cluster, but I only get the blade 2 console even the blade in slot 1 is the master. I've tried to disable slot 2 and I'm still getting console on this physical connection and the console of blade in slot 1 is completely dead. I can't get login nor AOM access through it. I don't understand how console access works when you have a cluster with more than a blade in a chassis. Which console is active? Can't I have both consoles actives? Thanks.
Running EUD from CLI or AOM
Hi All, I need to run an EUD on one of our F5 units that is housed in a remote datacenter. I've updated EUD to v12.12.0.4.0, but as I don't have direct access to the unit I need to run the EUD remotely. Does anyone happen to know what steps I need to take to action this? Many thanks, AnthonyCannot run configuration utility through serial console port
Hi all, I am trying to set the management IP address to a 2100 blade through the serial console port. The blade is part of a BigIP VIPRIOM 2400 platform and it consists on just one 2100 blade. I connect to the COM1 successfully and the blade shows me the AOM menu (blade baud setting, blade info, blade reseting, ...) if I press ESC (. The problem is the configuration utility doesn't run when I introduce config on the terminal (putty in my case). I don't even get anything when I press a button. The F5 just replies to ESC ( and nothing else. My department got this VIPRIOM from another department that made use of it. I am wondering if they could removed the config utility. In this case, is there a way to reinstall the config utility to my F5 again or anyone suggest something else? thanks in advance!Error starting 8900
Hi, i have 3 8900 with the same trouble. All don't start the TMOS. I try use the AOM but when i try any option says that the host is unreachable. Anyone have any idea what can i do? I try a clean install with USB but the USB don't start until the stop screen Or all them dont have more solution? Thanks
Viprion 2250 AOM Network Access
After reviewing SOL9403 it would appear that their is no support for setting an IP address to access AOM via the MGMT Interface and that the only way to access AOM is via the console port. Can someone confirm that this is true? Are their any other Lights Out Management Options available on the Viprion 2400 platform? Our primary use case is to monitor chassis/blade upgrades, reboots and run EUD if required. I should also mention that we currently only have one 2250 blade. Thanks.Is AOM available in BigIP VE (Running in ESX)?
Hi there, I am setting up my first pair of virtual edition (VE) BigIPs currently and struggle to get AOM network access running. When using physical BigIPs ESC-( does the trick, but when trying to enter this via the ESX console, as soon as I type ESC I get ^[ so I won't be able to access the AOM menu. Looking at K14594: Accessing the AOM Command Menu I am not seing VEs listed anywhere. So am I right that VEs generally do not offer any AOM at all and the idea is to do all the maintenance/troubleshooting via the ESX console? If not - how do you configure network access to the AOM for VEs? Cheers, Torsten
AOM configuration on 3900
Hi, I have an disk issue with one bigip that I'm working on. The recommended action for this is to reboot the divice and run a fsck. https://support.f5.com/kb/en-us/solutions/public/10000/300/sol10328.html The solution guid asks me to have direct access to the device when doing this. Is AOM good enough? Then I got the next issue. Is it not possible to configure AOM through SSH for the 3900 platform? http://support.f5.com/kb/en-us/solutions/public/9000/600/sol9608.html Regards Andréas
