Troubleshooting, Option rom not shown during post, Using a diagnostic monitor for troubleshooting – HP SmartStart-Software User Manual
Page 22: Target connection problems
Troubleshooting 22
Troubleshooting
ProLiant BL685c servers fail to finish boot sequence
Symptom
On some ProLiant BL685c servers with more than 4 GB of memory, the system fails to finish the boot
sequence after a SLES10 install.
Resolution
Add the parameter "numa=off" to the list of parameters given for boot options or in the PXE configuration
file depending on the type of install.
Option ROM not shown during POST
Symptom
When installing iSCSI boot targets using PXE and when using Port 1 on an NC373m to iSCSI boot, PXE
option ROM may not show during POST after the iSCSI target is found and logged into the system.
Resolution
First disable the array controller in RBSU and then reboot to see the PXE screen post during POST.
Using a diagnostic monitor for troubleshooting
If the client is not able to boot from the target server and the problem is not discernable from the
immediately available information, you may need to use a network monitor that is capable of parsing the
iSCSI protocol to troubleshoot the information.
If the iSCSI target is software running on a server, you may be able to run a software network monitor
such as Ethereal directly on the target system. Otherwise, you may need to configure a network switch
with port mirroring and direct the mirrored packets to a port where either a hardware or software network
monitor can be attached.
Target connection problems
Symptoms:
The initiator is unable to make a connection to the target.
Possible causes:
•
The initiator and target are not connected to the same network
•
The initiator and target are not in the same VLAN (if any)
•
The IP configurations for the initiator and target are not correct