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

Interpreting System Alerts, Sample System Alert, Key FRU Identification Fields for System Alerts

Page 109 highlights

Troubleshooting Chassis Code to FRU Decode Interpreting System Alerts Do one of the following: 1. No response: the alert will time out and the system will continue operating. 2. A - Responding with the letter A will inform the Service Processor that you have seen the entry. The system will continue to operate. 3. X - Responding with the letter X will inform the Service Processor to disable all future alert messages. This can be re-enabled with a Service Processor command. Sample System Alert SYSTEM ALERT ALERT LEVEL: 6=Boot possible, pending failure or environmental problem - action required PROBLEM DETAIL: 4=fan failure - SOURCE ID: 04 SYSTEM NAME: fesrhapgsp MODEL NAME: MODEL STRING: S/N: SPU POWER: ON ACTIVITY/COMPLETION LEVEL: 0% SYSTEM BOOT IS PENDING LEDs: RUN FLASH ATTENTION OFF FAULT OFF REMOTE ON CALLER ACTIVITY: 4=monitor - CALLER SUBACTIVITY: 05=fan REPORTING ENTITY TYPE: 2=power monitor - REPORTING ENTITY ID: 00 SOURCE: 6=platform - SOURCE DETAIL: 3=cabinet fan 0x002008646304405F 00000000 00000000 - type 0 = Data Field Unused 0x582008646304405F 00006303 0F151D08 - type 11 = Timestamp 04/15/1999 21:29:08 A: ack read of this entry - X: Disable all future alert messages Anything else skip redisplay the log entry ->Choice:a Key FRU Identification Fields for System Alerts The following fields are used for FRU identification. Alert Level: Source: Source Detail: Source ID: How the problem has affected the system operation. What major part of the system the alert is referring to (i.e, platform, memory, processor, etc...). What sub-part of the system the alert is referring to (i.e, cabinet fan, DIMM, high voltage DC power, etc...). Specific FRU referred to in Source and Source Detail (i.e, cabinet fan #4). Problem Detail: Timestamp: Specific problem information (i.e, power off, functional failure, etc...). When the problem occurred. The above sample system alert shows the following: 1. The problem does not affect system boot. 2. The problem is with platform cabinet fan #4. 3. The problem is a fan failure. Replace fan #4 to correct the problem. 4. The fan failed on April 15, 1999 at 9:29 PM. Chapter 6 95

  • 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
95
Interpreting System Alerts
Do one of the following:
1. No response: the alert will time out and the system will continue operating.
2.
A
- Responding with the letter
A
will inform the Service Processor that you have seen the entry. The
system will continue to operate.
3.
X
- Responding with the letter
X
will inform the Service Processor to disable all future alert messages.
This can be re-enabled with a Service Processor command.
Sample System Alert
*************************SYSTEM ALERT***************************************
ALERT LEVEL: 6=Boot possible, pending failure or environmental problem - action required
PROBLEM DETAIL: 4=fan failure - SOURCE ID: 04
SYSTEM NAME: fesrhapgsp
MODEL NAME:
MODEL STRING:
S/N:
SPU POWER: ON
ACTIVITY/COMPLETION LEVEL:
0%
SYSTEM BOOT IS PENDING
LEDs:
RUN
ATTENTION
FAULT
REMOTE
FLASH
OFF
OFF
ON
CALLER ACTIVITY: 4=monitor - CALLER SUBACTIVITY: 05=fan
REPORTING ENTITY TYPE: 2=power monitor - REPORTING ENTITY ID: 00
SOURCE: 6=platform - SOURCE DETAIL: 3=cabinet fan
0x002008646304405F 00000000 00000000 - type
0 = Data Field Unused
0x582008646304405F 00006303 0F151D08 - type 11 =
Timestamp 04/15/1999 21:29:08
A: ack read of this entry - X: Disable all future alert messages
Anything else skip redisplay the log entry
->Choice:a
Key FRU Identification Fields for System Alerts
The following fields are used for FRU identification.
Alert Level:
How the problem has affected the system operation.
Source:
What major part of the system the alert is referring to (i.e, platform,
memory, processor, etc...).
Source Detail:
What sub-part of the system the alert is referring to (i.e, cabinet fan,
DIMM, high voltage DC power, etc...).
Source ID:
Specific FRU referred to in Source and Source Detail (i.e, cabinet fan #4).
Problem Detail:
Specific problem information (i.e, power off, functional failure, etc...).
Timestamp:
When the problem occurred.
The above sample system alert shows the following:
1. The problem does not affect system boot.
2. The problem is with platform cabinet fan #4.
3. The problem is a fan failure. Replace fan #4 to correct the problem.
4. The fan failed on April 15, 1999 at 9:29 PM.