Bug ID 591776: Unable to exit or quit AOM menu when AOM DHCP configuration is in process and DHCP server is unavailable

Last Modified: Apr 10, 2019

Bug Tracker

Affected Product:  See more info
Discovery AOM(all modules)

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1

Opened: May 06, 2016
Severity: 3-Major
Related AskF5 Article:
K11503028

Symptoms

When you use the AOM menu at the serial console (ESC shift 9) and select to configure the BMC's management IP address using DHCP, the AOM menu operation does not correctly timeout and return to the AOM menu if the DHCP server is unavailable. In this state, neither the AOM menu, nor the host CPU's serial console can be accessed. When using DHCP to configure the BMC's management address information, the AOM menu normally waits for up to 45 seconds to configure the network using the DHCP option. During that time, a series of '........' displays to indicate progress. At the end of 45 seconds, if DHCP has not completed, the configuration process times out and returns to the AOM menu list (and shows a DHCP configuration error).

Impact

The AOM menu will remain stuck indefinitely in the DHCP configuration process, continually printing "......." In this state, neither the AOM menu, nor the host CPU's serial console can be accessed. The DHCP server must become available again, or the device power cycled.

Conditions

Establish a serial console connection to the device, then bring up the AOM menu using by pressing ESC shift 9. Select 'n' to configuration the network. Select 'y' to use DHCP. If DHCP is not accessible, the process will fail to timeout.

Workaround

To work around this issue, you must make the DHCP server accessible again to the network. Try these solutions to make the server available: * Ensure DHCP is running and accessible on the network * Verify that the network cable is connected properly * Check intermediate cables, devices, etc. * Power cycle the device

Fix Information

None

Behavior Change