IBM 88614RX Maintenance Manual - Page 147

Problem-determination tips, Are the exact machine type and model

Get IBM 88614RX - Eserver xSeries 365 PDF manuals and user guides
UPC - 000435172662
View all IBM 88614RX manuals
Add to My Manuals
Save this manual to your list of manuals

Page 147 highlights

Problem-determination tips Because of 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 - Does the server fail the diagnostic programs? - What, when, where, single, or multiple servers? - Is the failure repeatable? - Has this configuration ever worked? - If it has been working, what changes were made before it failed? - Is this the original reported failure? v Diagnostics version - Type and version level v Hardware configuration - Print (print screen) configuration currently in use - BIOS code level v Operating-system software - Type and version level Note: To eliminate confusion, servers are considered identical only if they: v Are the exact machine type and model v Have the same BIOS level v Have the same adapters and attachments in the same locations v Have the same address jumpers, terminators, and cabling v Have the same software versions and levels v Have the same diagnostics code (version) v Have the same configuration options set v Have the same setup for the operating-system control files Comparing the configuration and software setup between working and non-working servers will often lead to problem resolution. Chapter 6. Symptom-to-FRU index 137

  • 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
Problem-determination tips
Because of 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
–
Does the server fail the diagnostic programs?
–
What, when, where, single, or multiple servers?
–
Is the failure repeatable?
–
Has this configuration ever worked?
–
If it has been working, what changes were made before it failed?
–
Is this the original reported failure?
v
Diagnostics version
–
Type and version level
v
Hardware configuration
–
Print (print screen) configuration currently in use
–
BIOS code level
v
Operating-system software
–
Type and version level
Note:
To eliminate confusion, servers are considered identical only if they:
v
Are the exact machine type and model
v
Have the same BIOS level
v
Have the same adapters and attachments in the same locations
v
Have the same address jumpers, terminators, and cabling
v
Have the same software versions and levels
v
Have the same diagnostics code (version)
v
Have the same configuration options set
v
Have the same setup for the operating-system control files
Comparing the configuration and software setup between working and
non-working servers will often lead to problem resolution.
Chapter 6. Symptom-to-FRU index
137