IBM HS20 Hardware Maintenance Manual - Page 101

Problem determination tips, A functioning BladeCenter

Get IBM HS20 - BladeCenter - 8832 PDF manuals and user guides
UPC - 087944983033
View all IBM HS20 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 101 highlights

5. Remove or disconnect the following devices (one at a time) until you find the failure (reinstall, turn on and reconfigure the blade server each time): v I/O adapter v Drives v Memory modules (minimum requirement = two 256 MB DIMMs) Note: Minimum operating requirements are: a. System board b. One microprocessor c. Memory (with a minimum of two 256 MB DIMMs) d. A functioning BladeCenter 6. Install and turn on the blade server. If the problem remains, suspect the following FRUs in the order listed: v DIMM v System board v Microprocessor Notes: 1. If the problem goes away when you remove an I/O adapter from the system and replacing that I/O adapter does not correct the problem, suspect the system board. 2. If you suspect a networking problem and all the system tests pass, suspect a network cabling problem external to the system. Problem determination tips Due to the variety of hardware and software combinations that can be encountered, use the following information to assist you in problem determination. If possible, have this information available when requesting assistance from Service Support and Engineering functions. v Machine type and model v Microprocessor or hard disk upgrades v Failure symptom - Do diagnostics fail? - What, when, where, single, or multiple systems? - Is the failure repeatable? - Has this configuration ever worked? - If it has been working, what changes were made prior to it failing? - Is this the original reported failure? v Diagnostics version - Type and version level v Hardware configuration - Print (print screen) configuration currently in use - BIOS level v Operating system software - Type and version level Chapter 8. Symptom-to-FRU index 91

  • 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
5.
Remove or disconnect the following devices (one at a time) until you find the
failure (reinstall, turn on and reconfigure the blade server each time):
v
I/O adapter
v
Drives
v
Memory modules (minimum requirement = two 256 MB DIMMs)
Note:
Minimum operating requirements are:
a.
System board
b.
One microprocessor
c.
Memory (with a minimum of two 256 MB DIMMs)
d.
A functioning BladeCenter
6.
Install and turn on the blade server. If the problem remains, suspect the
following FRUs in the order listed:
v
DIMM
v
System board
v
Microprocessor
Notes:
1.
If the problem goes away when you remove an I/O adapter from the system and
replacing that I/O adapter does not correct the problem, suspect the system
board.
2.
If you suspect a networking problem and all the system tests pass, suspect a
network cabling problem external to the system.
Problem determination tips
Due to the variety of hardware and software combinations that can be encountered,
use the following information to assist you in problem determination. If possible,
have this information available when requesting assistance from Service Support
and Engineering functions.
v
Machine type and model
v
Microprocessor or hard disk upgrades
v
Failure symptom
–
Do diagnostics fail?
–
What, when, where, single, or multiple systems?
–
Is the failure repeatable?
–
Has this configuration ever worked?
–
If it has been working, what changes were made prior to it failing?
–
Is this the original reported failure?
v
Diagnostics version
–
Type and version level
v
Hardware configuration
–
Print (print screen) configuration currently in use
–
BIOS level
v
Operating system software
–
Type and version level
Chapter 8. Symptom-to-FRU index
91