HP Integrity rx2800 rx2800 i2 User Service Guide - Page 73

continued, Action, Condition

Page 73 highlights

Table 25 Basic low end troubleshooting (continued) Step 4a (cont.) Condition Still no iLO 3 MP prompt on system console. Action Nothing may be logged for this condition (note: if the iLO 3 MP is off, the system health is off as well). Front panel LEDs indicate that the server is either booting or running the OS. 1. Verify that the proper terminal type is set: Supported settings are hpterm, VT100+ (default), and VTUTF8. 2. Verify that the RS-232C configuration matches between the server and the local console or modem (See "Supported configurations" (page 82) for details). 3. Look for loose, damaged, or disconnected power and signal cables on the I/O backplane. The preceding problem is fixed when iLO 3 MP menu appears on the system console, and the system health is steady green. 4b Cannot see UEFI prompt on system console. Nothing may be logged for this condition (system health is off, internal health is steady green, external health is steady green, and power is steady green). Front panel LEDs indicate that the server is either booting or running the OS. 1. Examine the state (flashing or solid on) of the three LEDs, located in the back left corner of the server, visible through the perforations in the server. Server (logic and system firmware) stages are tracked by the PDH FPGA, using these three LEDs (see "Troubleshooting tools" (page 75) for more LED info). 2. Examine the iLO 3 MP logs for entries related to CPUs, CPU power modules (PPMs), shared memory, and core I/O devices (see "Errors and reading error logs" (page 80) for details). The preceding problem is fixed when UEFI menu appears on the system console, and system firmware booting completes. 4c Cannot find a boot disk or removable media drive. Nothing may be logged for this condition (system health is off, internal health is steady green, external health is steady green, and power is steady green). 1. Examine the boot device, to determine if it is plugged into its drive bay properly. 2. Examine the drive cabling for any problems. 3. Examine the boot path settings. 4. Examine the iLO 3 MP logs for entries related to CPUs, CPU power modules (PPMs), shared memory, and core I/O devices (see "Errors and reading error logs" (page 80) for more details). The preceding problem is fixed, when all boot devices are found. Methodology 73

  • 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
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151

Table 25 Basic low end troubleshooting
(continued)
Action
Condition
Step
Nothing may be logged for this condition (note:
if the iLO 3 MP is off, the system health is off as
well). Front panel LEDs indicate that the server is
either booting or running the OS. 1. Verify that
the proper terminal type is set: Supported settings
are hpterm, VT100+ (default), and VTUTF8. 2.
Verify that the RS-232C configuration matches
between the server and the local console or
modem (See
“Supported configurations” (page 82)
for details). 3. Look for loose, damaged, or
disconnected power and signal cables on the I/O
backplane.
The preceding problem is fixed when iLO 3 MP
menu appears on the system console, and the
system health is steady green.
Still no iLO 3 MP prompt on system console.
4a (cont.)
Nothing may be logged for this condition (system
health is off, internal health is steady green,
external health is steady green, and power is
steady green). Front panel LEDs indicate that the
server is either booting or running the OS. 1.
Examine the state (flashing or solid on) of the three
LEDs, located in the back left corner of the server,
visible through the perforations in the server. Server
(logic and system firmware) stages are tracked by
the PDH FPGA, using these three LEDs (see
“Troubleshooting tools” (page 75)
for more LED
info). 2. Examine the iLO 3 MP logs for entries
related to CPUs, CPU power modules (PPMs),
shared memory, and core I/O devices (see
“Errors
and reading error logs” (page 80)
for details).
The preceding problem is fixed when UEFI menu
appears on the system console, and system
firmware booting completes.
Cannot see UEFI prompt on system console.
4b
Nothing may be logged for this condition (system
health is off, internal health is steady green,
external health is steady green, and power is
steady green). 1. Examine the boot device, to
determine if it is plugged into its drive bay
properly. 2. Examine the drive cabling for any
problems. 3. Examine the boot path settings. 4.
Examine the iLO 3 MP logs for entries related to
CPUs, CPU power modules (PPMs), shared
memory, and core I/O devices (see
“Errors and
reading error logs” (page 80)
for more details).
The preceding problem is fixed, when all boot
devices are found.
Cannot find a boot disk or removable media drive.
4c
Methodology
73