Step Condition Action
3a Cannot see UEFI prompt on
system console. UEFI is
running.
Nothing can be logged for this condition.
1. If the blade was able to join the partition but didn't reach
the UEFI prompt, then the issue might be I/O related.
Check the CAE for any issues with PCIe card drivers.
2. If the blade was not able to join the partition, then open the
Health Repository from the OA CLI using show hr
followed by the show indict and show deconf
commands to check for entries related to processors,
processor power modules, shared memory, and core I/O
devices.
3. If this is a console issue and no other hardware problems
are indicated, replace the Monarch blade.
The issue is fixed when the UEFI menu appears on the
system console.
3b Cannot find a boot disk. UEFI
is running.
Nothing might be logged for this condition.
1. Search for the boot disk path using the UEFI shell
(reconnect –r and map -r) command.
2. Check the I/O card driver settings in the UEFI Device
Manager Menu.
3. Examine the OA CLI logs for entries related to processors,
processor power modules, shared memory, and core I/O
devices. See Using event logs on page 72.
4. Review the OA SHOW ALL section for the SHOW SERVER
PORT MAP{bay} to verify that the SAN port is connected.
Then check the SAN switch for failures and verify the
correct configuration.
3c PXE fails to find the boot file
on the network. UEFI is
running.
Nothing can be logged for this condition.
1. Verify that the network interface is connected (ifconfig
—l). Verify that the Media State: is Media present.
2. If the network interface is connected, configure an IP
address using DHCP (ifconfig —s eth0 dhcp),
check the network interface again (ifconfig —l), and
ping the PXE server (ping <PXE IP> ).
If you are able to ping the PXE server, then the PXE boot
failure is probably a software issue and not related to the
system hardware.
4 Cannot see OS prompt on
system console. OA CLI is
running.
Nothing can be logged for this condition.
Examine the OA CLI logs for entries related to OA modules,
processors, processor power modules, shared memory, and
core I/O devices. See Using event logs on page 72.
IRC or KVM can also be used.
The issue is fixed when the OS prompt appears on the
system console.
Troubleshooting 53
To Next Page
Loading...
