IBM HS20 Hardware Maintenance Manual - Page 79

System Management: Failed - firmware update

Page 79 highlights

Note: See "System" on page 94 to determine which components should be replaced by a field service technician. Error code/symptom FRU/action 005-XXX-000 (Failed video test) v System board 030-XXX-000 (Failed internal SCSI interface test) 1. SCSI storage expansion unit 2. System board 035-XXX-099 1. No adapters were found. 2. If adapter is installed re-check connection. 075-XXX-000 (Failed power supply test) v Power supply 089-XXX-001 (Failed microprocessor test) 1. Microprocessor 1 2. System board 089-XXX-002 (Failed optional microprocessor test) 1. Optional microprocessor 2 2. System board 165-060-000 (Service Processor: ASM may 1. Rerun the diagnostic test. be busy) 2. Fix other error conditions that may be keeping ASM busy. Refer to the error log and diagnostic panel. 3. Power down blade server and reseat it in chassis. 4. System board. 165-198-000 (Service Processor: Aborted) 1. Rerun the diagnostic test 2. Fix other error conditions that may be keeping ASM busy. Refer to the error log and diagnostic panel. 3. Power down blade server and reseat it in chassis. 4. System board. 165-201-000 (Service Processor: Failed) 1. Power down blade server and reseat it in chassis. 2. System board. 165-330-000 (Service Processor: Failed) v Update to the latest ROM diagnostic level and retry. 165-342-000 (Service Processor: Failed) 1. Ensure latest firmware levels for ASM and BIOS are installed. 2. Power down blade server and reseat it in chassis. 3. System board. 166-198-000 System Management: Aborted (Unable to communicate with ASM. It may be busy. Run the test again.) 1. Run the diagnostic test again. 2. Correct other error conditions and retry. These include other failed system management tests and items logged in the System Error Log of the management module. 3. Power down blade server and reseat it in chassis. 4. System board. 166-201-001 System Management: Failed 1. DIMMs (I2C bus error(s) See SERVPROC and DIAGS entries in event log.) 2. System board 166-201-002 System Management: Failed 1. Reseat I2C cable between the operator information card and (I2C bus error(s) See SERVPROC and the system board. DIAGS entries in event log.) 2. Operator information card. 3. System board. Chapter 8. Symptom-to-FRU index 69

  • 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

Note:
See “System” on page 94 to determine which components should be replaced by a field service technician.
Error code/symptom
FRU/action
005-XXX-000
(Failed video test)
v
System board
030-XXX-000
(Failed internal SCSI interface test)
1.
SCSI storage expansion unit
2.
System board
035-XXX-099
1.
No adapters were found.
2.
If adapter is installed re-check connection.
075-XXX-000
(Failed power supply test)
v
Power supply
089-XXX-001
(Failed microprocessor test)
1.
Microprocessor 1
2.
System board
089-XXX-002
(Failed optional microprocessor test)
1.
Optional microprocessor 2
2.
System board
165-060-000
(Service Processor: ASM may
be busy)
1.
Rerun the diagnostic test.
2.
Fix other error conditions that may be keeping ASM busy. Refer to
the error log and diagnostic panel.
3.
Power down blade server and reseat it in chassis.
4.
System board.
165-198-000
(Service Processor: Aborted)
1.
Rerun the diagnostic test
2.
Fix other error conditions that may be keeping ASM busy. Refer to
the error log and diagnostic panel.
3.
Power down blade server and reseat it in chassis.
4.
System board.
165-201-000
(Service Processor: Failed)
1.
Power down blade server and reseat it in chassis.
2.
System board.
165-330-000
(Service Processor: Failed)
v
Update to the latest ROM diagnostic level and retry.
165-342-000
(Service Processor: Failed)
1.
Ensure latest firmware levels for ASM and BIOS are installed.
2.
Power down blade server and reseat it in chassis.
3.
System board.
166-198-000 System Management:
Aborted
(Unable to communicate with ASM. It may
be busy. Run the test again.)
1.
Run the diagnostic test again.
2.
Correct other error conditions and retry. These include other failed
system management tests and items logged in the System Error
Log of the management module.
3.
Power down blade server and reseat it in chassis.
4.
System board.
166-201-001 System Management: Failed
(I2C bus error(s) See SERVPROC and
DIAGS entries in event log.)
1.
DIMMs
2.
System board
166-201-002 System Management: Failed
(I2C bus error(s) See SERVPROC and
DIAGS entries in event log.)
1.
Reseat I2C cable between the operator information card and
the system board.
2.
Operator information card.
3.
System board.
Chapter 8. Symptom-to-FRU index
69