HP A4500A Hardware Manual - rp24xx, Customer Viewable - Page 147

Chassis Code to Customer Replaceable Unit (CRU) Decode, Accessing Error Chassis Logs

Page 147 highlights

Chassis Code to Customer Replaceable Unit (CRU) Decode Chassis Code to Customer Replaceable Unit (CRU) Decode This is a guide to identify failing CRU's from the Error Chassis Logs. The guide includes the following information: • "Accessing Error Chassis Logs" • "Key Identification Fields for Error Chassis Logs" • "Cross-Referencing Chassis Log Errors to A400/500 CRU's." Accessing Error Chassis Logs Execute the following steps to access the Error Chassis Logs. 1. At the system console prompt, type CTRL B (this will bring up the gsp login screen) 2. Type in the Service Processor Login and Password (this will give you a GSP prompt) 3. At the prompt, GSP>, type SL (this will take you to the support logs) 4. At the prompt, Which buffer are you interested in: Incoming, Error, Current boot, Last boot? (I/A/E/C/L), type E (for error logs) 5. At the prompt, Do you want to set up filter options on this buffer? (Y/[N]), type N 6. At this point, the most recent Error Log Entry (Log Entry #0) will be displayed. A carriage return after this will display the next log entry. Type Q to stop displaying the log entries. 7. At the prompt, GSP>, type CO to return to the console Key CRU Identification Fields for Error Chassis Logs The following fields (bold in the sample error log entry) are useful 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 CRU referred to in Source and Source Detail (i.e., fan #1). Problem Detail: Specific problem information (i.e, power off, functional failure, etc.). Timestamp: When the problem occurred. Cross-Referencing Chassis Log Errors to A400/A500 CRU's Use the following table to identify the failing CRU from the Chassis Log information. Chapter 1

  • 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

Chapter
Chassis Code to Customer Replaceable Unit (CRU) Decode
1
Chassis Code to Customer Replaceable Unit (CRU) Decode
This is a guide to identify failing CRU’s from the Error Chassis Logs. The guide includes the following
information:
“Accessing Error Chassis Logs”
“Key Identification Fields for Error Chassis Logs”
“Cross-Referencing Chassis Log Errors to A400/500 CRU’s.”
Accessing Error Chassis Logs
Execute the following steps to access the Error Chassis Logs.
1. At the system console prompt, type
CTRL B
(this will bring up the gsp login screen)
2. Type in the Service Processor Login and Password (this will give you a GSP prompt)
3. At the prompt,
GSP>
, type
SL
(this will take you to the support logs)
4. At the prompt,
Which buffer are you interested in:
Incoming, Error, Current boot, Last boot? (I/A/E/C/L),
type
E
(for error logs)
5. At the prompt,
Do you want to set up filter options on this buffer? (Y/[N]), type
N
6. At this point, the most recent Error Log Entry (Log Entry #0) will be displayed. A carriage return after
this will display the next log entry. Type Q to stop displaying the log entries.
7. At the prompt,
GSP>
, type
CO
to return to the console
Key CRU Identification Fields for Error Chassis Logs
The following fields (bold in the sample error log entry) are useful 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 CRU referred to in Source and Source Detail (i.e., fan #1).
Problem Detail:
Specific problem information (i.e, power off, functional failure, etc.).
Timestamp:
When the problem occurred.
Cross-Referencing Chassis Log Errors to A400/A500 CRU’s
Use the following table to identify the failing CRU from the Chassis Log information.