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

Example 6-1, Chassis Log: Reporting Entity Type = System Firmware, 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 113 highlights

Troubleshooting Chassis Code to FRU Decode Example 6-1 Chassis Log: Reporting Entity Type = System Firmware Log Entry # 0 :SYSTEM NAME: fesrhapgspDATE: 12/08/2000 TIME: 23:46:22ALERT LEVEL: 6 = Boot possible, pending failure - action requiredSOURCE: 3 = PDHSOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: 3PROBLEM DETAIL: 0 = no problem detailCALLER ACTIVITY: 1 = test STATUS: 0CALLER SUBACTIVITY: 71 = implementation dependentREPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 030x0000306030031710 00000000 000000FE type 0 = Data Field Unused0x5800386030031710 0000640B 08172E16 type 11 = Timestamp 12/08/2000 23:46:22Type CR for next entry, Q CR to quit. Using the example above: Step 1. The last 4 digits are 1710. Step 2. This is an rp5450 so use Appendix B in the Interpreting Chassis Logs in Detail guide. Step 3. Using the FIND feature to look up 1710 in Appendix B, we learn the definition is CC_BOOT_INVALID_SPHYR_SETTINGS. Step 4. The appropriate action in this example would be to verify the switch settings on the system board are set correctly for the installed CPU's. Chapter 6 99

  • 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
99
Example 6-1
Chassis Log: Reporting Entity Type = System Firmware
Log Entry #
0 :SYSTEM NAME: fesrhapgspDATE: 12/08/2000 TIME: 23:46:22ALERT LEVEL: 6
= Boot possible, pending failure - action requiredSOURCE: 3 = PDHSOURCE DETAIL: 0 =
unknown, no source stated
SOURCE ID: 3PROBLEM DETAIL: 0 = no problem detailCALLER
ACTIVITY: 1 = test
STATUS: 0CALLER SUBACTIVITY: 71 = implementation
dependentREPORTING ENTITY TYPE: 0 = system firmware
REPORTING ENTITY ID:
030x000030603003
1710
00000000 000000FE type
0 = Data Field Unused0x5800386030031710
0000640B 08172E16 type 11 = Timestamp 12/08/2000 23:46:22Type CR for next entry, Q CR
to quit.
Using the example above:
Step 1.
The last 4 digits are 1710.
Step 2.
This is an rp5450 so use Appendix B in the
Interpreting Chassis Logs in Detail
guide.
Step 3.
Using the FIND feature to look up 1710 in Appendix B, we learn the definition is
CC_BOOT_INVALID_SPHYR_SETTINGS.
Step 4.
The appropriate action in this example would be to verify the switch settings on the system board
are set correctly for the installed CPU’s.