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

Interpreting Chassis Logs Using the chassis_code.codes File, Step 1.

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 112 highlights

Troubleshooting Chassis Code to FRU Decode 2. The problem is with fan #4. 3. The problem is a fan failure. 4. The fan failed on April 15, 1999 at 9:29 PM. In this example, fan #4 should be replaced to correct the problem. Interpreting Chassis Logs Using the chassis_code.codes File For chassis logs generated by system firmware (Reporting Entity Type 0), use the chassis_code.codes file for chassis code definitions. Each revision of system firmware (AKA Processor Dependent Code or PDC) has a unique chassis_code.codes file. This file is not part of either the PF_Cxxxxx or PHSS_xxxxx server firmware patches. The chassis_code.codes files appear in the appendices of the Interpreting Chassis Logs in Detail guide. The definition of a PDC reported chassis code is determined by locating either the last four digits of a chassis log or the last three digits of a selftest chassis code in the appropriate chassis_code.codes file. Refer to the Interpreting Chassis Logs in Detail guide for definition and examples of selftest chassis codes. NOTE Be sure to use the appropriate appendix as the PDC for rp5400/rp5450 is different than PDC for rp5470. Using the wrong appendix may result in a mis-interpretation of the chassis code. To quickly learn the definition of a PDC reported chassis code, follow these four steps: Step 1. Determine either the last 4 digits of the hex chassis code or the last 3 digits of the selftest chassis code. Step 2. Go to the appropriate appendix in the Interpreting Chassis Logs in Detail guide. Step 3. Locate the chassis code that matches the last 3 or 4 digits. If viewing via web browser or Adobe Acrobat, use the FIND feature to locate the chassis code. Step 4. Take action as appropriate. 98 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
98
2. The problem is with fan #4.
3. The problem is a fan failure.
4. The fan failed on April 15, 1999 at 9:29 PM.
In this example, fan #4 should be replaced to correct the problem.
Interpreting Chassis Logs Using the chassis_code.codes File
For chassis logs generated by system firmware (Reporting Entity Type 0), use the chassis_code.codes file for
chassis code definitions. Each revision of system firmware (AKA Processor Dependent Code or PDC) has a
unique chassis_code.codes file. This file is not part of either the PF_Cxxxxx or PHSS_xxxxx server firmware
patches. The chassis_code.codes files appear in the appendices of the
Interpreting Chassis Logs in Detail
guide.
The definition of a PDC reported chassis code is determined by locating either the last four digits of a chassis
log or the last three digits of a selftest chassis code in the appropriate chassis_code.codes file. Refer to the
Interpreting Chassis Logs in Detail
guide for definition and examples of selftest chassis codes.
NOTE
Be sure to use the appropriate appendix as the PDC for rp5400/rp5450 is different than PDC
for rp5470. Using the wrong appendix may result in a mis-interpretation of the chassis code.
To quickly learn the definition of a PDC reported chassis code, follow these four steps:
Step 1.
Determine either the last 4 digits of the hex chassis code or the last 3 digits of the selftest chassis
code.
Step 2.
Go to the appropriate appendix in the
Interpreting Chassis Logs in Detail
guide.
Step 3.
Locate the chassis code that matches the last 3 or 4 digits. If viewing via web browser or Adobe
Acrobat, use the FIND feature to locate the chassis code.
Step 4.
Take action as appropriate.