HP mt20 Maintenance and Service Guide - Page 90

Diskless (No-Flash) unit troubleshooting

Get HP mt20 PDF manuals and user guides View all HP mt20 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 90 highlights

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 9-6 Diskless unit troubleshooting Item Information Action MAC Address NIC portion of the system board is OK If no MAC Address, the system board is at fault. Contact the Call Center for service. GUID General system board information If no GUID information, the system board is at fault and should be replaced. Client ID Information from server 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. MASK Information from server 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. DHCP IP Information from server 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. If you are running in a 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 F12 key to activate the network 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. 80 Chapter 9 Diagnostics and troubleshooting

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
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 9-6
Diskless unit troubleshooting
Item
Information
Action
MAC Address
NIC portion of the system board is OK
If no MAC Address, the system board is at fault. Contact the
Call Center for service.
GUID
General system board information
If no GUID information, the system board is at fault and
should be replaced.
Client ID
Information from server
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.
MASK
Information from server
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.
DHCP IP
Information from server
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.
If you are running in a 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
F12
key to activate the network 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.
80
Chapter 9
Diagnostics and troubleshooting