Diskless (No-Flash) Unit Troubleshooting - HP t620 Troubleshooting Manual

Diskless (No-Flash) Unit Troubleshooting

This section is only for those units that do not have ATA Flash capability. Because there is no ATA Flash
in this model the boot priority sequence is:
USB device
PXE
1. When the unit boots, the monitor should display the following information:
Table B-6
Item
MAC Address
GUID
Client ID
MASK
DHCP IP
If you are running in an Microsoft RIS PXE environment go to step 2.
If you are running in a Linux environment go to step 3.
2.
If you are running in a Microsoft RIS PXE environment press the
service boot as soon as the DHCP IP information appears on the screen.
If the unit does not boot to the network the server is not configured to PXE.
If you missed the F12 cue, the system will try to boot to the ATA flash that is not present. The
message on the screen will read: ERROR: Non-system disk or disk error. Replace and
press any key when ready.
Pressing any key will restart the boot cycle.
3. If you are running in a Linux environment an error message will appear on the screen if there is no
Client IP. ERROR: Non-system disk or disk error. Replace and press any key when
ready.
52 Appendix B Diagnostics and Troubleshooting
Diskless Unit Troubleshooting
Information
NIC portion of the system board is
OK
General system board information
Information from server
Information from server
Information from server
Action
If no MAC Address, the system board is at fault. Contact
the Call Center for service.
If no GUID information, the system board is at fault and
should be replaced.
If no Client ID information there is no network
connection. This may be caused by a bad cable, the
server is down, or a bad system board. Contact the Call
Center for service for the bad system board.
If no MASK information there is no network connection.
This may be caused by a bad cable, the server is down,
or a bad system board. Contact the Call Center for
service for the bad system board.
If no DHCP IP information there is no network
connection. This may be caused by a bad cable, the
server is down, or a bad system board. Contact the Call
Center for service for the bad system board.
F12 key to activate the network