HP rp5400 User Guide - HP rp5400 Family of Servers - Page 108

Interpreting System Alerts, Step 2.

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

Page 108 highlights

Troubleshooting Chassis Code to FRU Decode Step 2. The Source Detail, the Source ID, and the Problem Detail values are all not applicable for the Processor row of the table. Step 3. The FRU column of the table identifies the FRU as a failing processor. Step 4. The Action column of the table instructs us to use the Info Menu and PR command of the BCH Main Menu to identify the failing processor. Here is the output of Step 4 in our example: Main Menu: Enter command or menu > in ---- Information Menu Command ------ALL BootINfo CAche ChipRevisions COprocessor FRU FwrVersion IO LanAddress MEmory PRocessor WArnings Description ----------Display all system information Display boot-related information Display cache information Display revisions of major VLSI Display coprocessor information Display FRU information Display firmware version Display I/O interface information Display Core LAN station address Display memory information Display processor information Display selftest warning messages ---Information Menu: Enter command > pr PROCESSOR INFORMATION Processor --------- 1 3 Speed -------440 MHz 440 MHz HVERSION Model -------0x05c4 0x05c4 SVERSION Model/Op -------- 0x0491 0x0491 CVERSION -------- 2. 0 2. 0 Processor State ------------Active Stopped:Nonresponding Central Bus Speed (in MHz) Software ID (dec) Software ID (hex) Software Capability : 82 : 1635329341 : 0x6179253d : 0x01100000f0 Information Menu: Enter command > Processor #3 is Stopped:Nonresponding. Replace Processor #3. Interpreting System Alerts System Alerts are reported to the system console when a problem is detected by the Service Processor. These alerts are stored in the Service Processor Error Logs. When this new alert is added to the log file, it will cause the front panel ATTENTION LED to blink. 94 Chapter 6

  • 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
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
Chapter 6
Troubleshooting
Chassis Code to FRU Decode
94
Step 2.
The Source Detail, the Source ID, and the Problem Detail values are all not applicable for the
Processor row of the table.
Step 3.
The FRU column of the table identifies the FRU as a failing processor.
Step 4.
The Action column of the table instructs us to use the Info Menu and PR command of the BCH
Main Menu to identify the failing processor.
Here is the output of Step 4 in our example:
Main Menu: Enter command or menu > in
---- Information Menu ----------------------------------------------
Command
Description
-------
-----------
ALL
Display all system information
BootINfo
Display boot-related information
CAche
Display cache information
ChipRevisions
Display revisions of major VLSI
COprocessor
Display coprocessor information
FRU
Display FRU information
FwrVersion
Display firmware version
IO
Display I/O interface information
LanAddress
Display Core LAN station address
MEmory
Display memory information
PRocessor
Display processor information
WArnings
Display selftest warning messages
----
Information Menu: Enter command > pr
PROCESSOR INFORMATION
HVERSION
SVERSION
Processor
Processor
Speed
Model
Model/Op
CVERSION
State
---------
--------
--------
--------
--------
-------------
1
440
MHz
0x05c4
0x0491
2.
0
Active
3
440
MHz
0x05c4
0x0491
2.
0
Stopped:Nonresponding
Central Bus Speed (in MHz)
:
82
Software ID (dec)
: 1635329341
Software ID (hex)
: 0x6179253d
Software Capability
: 0x01100000f0
Information Menu: Enter command >
Processor #3 is
Stopped:Nonresponding
. Replace Processor #3.
Interpreting System Alerts
System Alerts are reported to the system console when a problem is detected by the Service Processor. These
alerts are stored in the Service Processor Error Logs. When this new alert is added to the log file, it will cause
the front panel ATTENTION LED to blink.