Home » IBM Manuals » Desktops » IBM JS20 » Manual Viewer

IBM JS20 Hardware Maintenance Manual - Page 158

Memory, problems, Microprocessor, Monitor

UPC - 000435230263

Add to My Manuals
Save this manual to your list of manuals

Page 158 highlights

Memory problems Symptom FRU/action Degraded memory performance 1. Verify that: or amount of memory displayed v All installed memory is recognized in the Display Vital Product Data of lscfg is less than the amount of -vp physical memory installed v The memory modules are seated correctly. v You have installed the correct type of memory. v All banks of memory on the DIMMs are enabled. The server might have automatically disabled a DIMM bank when it detected a problem or a DIMM bank could have been manually disabled. Look at the BladeCenter management module event log for error message (checkpoint or firmware error codes). a. If the DIMM was disabled by a system management interrupt (SMI), replace the DIMM. b. If the DIMM was disabled by POST, obtain the eight-digit error code and replace the failing DIMM. v The DIMMs are not defective. If a DIMM is defective, replace it; then, restart the server. v The memory has been recognized, if you changed the memory (restart the server). 2. DIMM. 3. System board. Suspected memory problem See the management module error log. Microprocessor problems Symptom FRU/action The blade server will not boot or 1. If a checkpoint or firmware error was logged in the BladeCenter a checkpoint or firmware error management module event log, correct that error. code is logged in the BladeCenter management module event log (the startup 2. If no error was logged, restart the blade server and check the management error log again for error codes. microprocessor is not working 3. System board. correctly) Monitor problems Symptom Testing the monitor. The screen is blank. FRU/action v See the information that comes with the monitor for adjusting and testing instructions. (Some IBM monitors have their own self-tests.) 1. Verify that: v The system power cord is connected to the BladeCenter power module and a working electrical outlet. v The monitor cables are connected correctly. v The monitor is turned on and the brightness and contrast controls are adjusted correctly. 2. If you have verified these items and the screen remains blank, replace: a. Monitor b. Management module on the BladeCenter (see the Hardware Maintenance Manual and Troubleshooting Guide for your BladeCenter unit). 148 BladeCenter JS20 Type 8842: Hardware Maintenance Manual and Troubleshooting Guide

Section	Page
About this manual	5
Important safety information	5
Online support	5
Contents	7
Chapter 1. Introduction	11
Related documentation	13
The IBM BladeCenter Documentation CD	14
Hardware and software requirements	14
Using the Documentation Browser	14
Notices and statements used in this document	15
Features and specifications	16
BladeCenter JS20 specifications for non-NEBS/ETSI environments	16
BladeCenter JS20 specifications for NEBS/ETSI environments	17
Preinstallation checklist	19
Checking the status of the media tray	20
Chapter 2. Blade server power, controls, and indicators	23
Turning on the blade server	23
Turning off the blade server	24
Blade server controls and LEDs	24
Chapter 3. Configuration	27
Using the command-line interface	28
Configuring the Gigabit Ethernet controller	28
Blade server Ethernet controller enumeration	29
Chapter 4. Problem determination procedures for AIX and Linux	31
Problem determination	31
Obtaining an SRN/SRC or error code	32
Chapter 5. AIX online, standalone and verification procedures	35
Performing AIX online concurrent mode diagnostics for problem determination	35
Running the standalone diagnostics from CD-ROM	35
Performing AIX online concurrent mode diagnostics for previous diagnostic results: service aids	38
Performing AIX online concurrent mode diagnostics for system verification	39
Verifying the replacement part using AIX diagnostics	40
Chapter 6. Running a Serial Over LAN session	43
Selecting the command target	44
Starting the command-line interface	44
Establishing a Telnet connection	45
Establishing a Secure Shell (SSH) connection	45
Starting an SOL session	45
Ending an SOL session	46
Chapter 7. Diagnostics	47
General checkout	47
Checkout procedure	48
Diagnostic tools overview	49
POST	50
Checkpoints	50
Accessing the Linux system error log	50
Service aids and the Linux system error log	50
FRU/CRU isolation	56
Error symptom charts	56
Light path diagnostics	56
Memory errors	57
Recovering the system firmware code	58
Recovery of system firmware code using service aids	58
Starting the TEMP image	58
Recovering the TEMP image from the PERM image	59
Updating the blade server firmware	60
Determination of current server firmware levels	61
Updating the blade server service processor	61
Update and manage system flash using Linux service aids	61
Updating the system flash using Linux	61
Verifying the system firmware levels using Linux	62
Update and manage system flash using AIX diagnostics	62
Updating the system flash using AIX	62
Committing the temporary firmware image using AIX	63
Verifying the system firmware levels using AIX	63
Recovering the system firmware code	64
Recovery of system firmware code using service aids	65
Starting the backup image	65
Recovering the primary image	66
Chapter 8. General AIX and xSeries standalone diagnostic information	69
Information for general diagnostic systems running the AIX operating system	69
AIX operating system message files	69
CE login	69
Missing resources	70
Automatic diagnostic tests	70
Configuration program	70
Diagnostic programs	71
Error log analysis	71
Introducing tasks and service aids	72
Task and service aid functions	72
AIX automatic error log analysis (diagela)	72
Error log analysis	73
Log repair action	73
Tasks (service aids)	73
Download microcode	74
Update and manage system flash	75
Using the standalone CD-ROM and online current diagnostics	77
Standalone and online diagnostics operating considerations	77
Running online diagnostics	77
Running the online diagnostics in concurrent mode	78
Running standalone diagnostics from a management (NIM) server	78
NIM server configuration	79
Client configuration and booting eServer standalone diagnostics from the NIM server	79
Chapter 9. Installing options	81
Installation guidelines	81
System reliability guidelines	81
Handling static-sensitive devices	81
Removing the blade server from the BladeCenter unit	83
Opening the blade server cover	84
Removing the blade server bezel assembly	85
Installing IDE hard disk drives	85
Installing memory modules	87
Installing an I/O expansion card	89
Ethernet controller, switch module, and cabling requirements	92
Replacing the battery	93
System board	96
System board component locations	96
System-board LED locations	97
Replacing the system board	97
Completing the installation	100
Installing the blade-server bezel assembly	100
Closing the blade server cover	102
Input/output connectors and devices	102
Chapter 10. Symptom-to-FRU index	103
Firmware checkpoint (progress) codes	104
Firmware error codes	112
Service request numbers	118
Linux service aid \	119
Using the SRN list	119
Service request number	119
Source of SRN	119
Failing Function Codes	119
Description and action	120
Using the SRN list	120
SRN tables	120
AIX SRNs 101-711 through 2D02	120
SRNs A00-(x)xxx through A1D-(x)xxx	131
Failing Function Codes (FFCs)	151
FFC table	152
Light path diagnostics LEDs	155
Error symptoms	155
CD drive problems	156
Diskette drive problems	157
General problems	157
Hard disk drive problems	157
Memory problems	158
Microprocessor problems	158
Monitor problems	158
Mouse problems	159
Network connection problems	160
Option problems	160
Power problems	161
Service processor problems	161
Software problems	162
Startup problems	162
Service processor error codes	162
Boot problem resolution	163
Physical location codes	164
Undetermined problems	166
Problem determination tips	168
Chapter 11. Parts listing, Type 8842	169
Appendix A. Getting help and technical assistance	171
Before you call	171
Using the documentation	171
Getting help and information from the World Wide Web	172
Software service and support	172
Hardware service and support	172
Appendix B. Safety information	173
General safety	173
Electrical safety	174
Safety inspection guide	175
Grounding requirements	176
Safety notices (multi-lingual translations)	176
Notices	207
Edition notice	207
Trademarks	208
Important notes	208
Product recycling and disposal	209
Battery return program	209
Electronic emission notices	210
Federal Communications Commission (FCC) statement	210
Industry Canada Class A emission compliance statement	210
Australia and New Zealand Class A statement	210
United Kingdom telecommunications safety requirement	210
European Union EMC Directive conformance statement	211
Taiwanese Class A warning statement	211
Chinese Class A warning statement	211
Japanese Voluntary Control Council for Interference (VCCI) statement	211

Match case Limit results 1 per page

Memory

problems

Symptom

FRU/action

Degraded

memory

performance

amount

memory

displayed

less

than

the

amount

physical

memory

installed

Verify

that:

All

installed

memory

recognized

the

Display

Vital

Product

Data

lscfg

-vp

The

memory

modules

are

seated

correctly.

You

have

installed

the

correct

type

memory.

All

banks

memory

the

DIMMs

are

enabled.

The

server

might

have

automatically

disabled

DIMM

bank

when

detected

problem

DIMM

bank

could

have

been

manually

disabled.

Look

the

BladeCenter

management

module

event

log

for

error

message

(checkpoint

firmware

error

codes).

the

DIMM

was

disabled

system

management

interrupt

(SMI),

replace

the

DIMM.

the

DIMM

was

disabled

POST,

obtain

the

eight-digit

error

code

and

replace

the

failing

DIMM.

The

DIMMs

are

not

defective.

DIMM

defective,

replace

it;

then,

restart

the

server.

The

memory

has

been

recognized,

you

changed

the

memory

(restart

the

server).

DIMM.

System

board.

Suspected

memory

problem

See

the

management

module

error

log.

Microprocessor

problems

Symptom

FRU/action

The

blade

server

will

not

boot

checkpoint

firmware

error

code

logged

the

BladeCenter

management

module

event

log

(the

startup

microprocessor

not

working

correctly)

checkpoint

firmware

error

was

logged

the

BladeCenter

management

module

event

log,

correct

that

error.

error

was

logged,

restart

the

blade

server

and

check

the

management

error

log

again

for

error

codes.

System

board.

Monitor

problems

Symptom

FRU/action

Testing

the

monitor.

See

the

information

that

comes

with

the

monitor

for

adjusting

and

testing

instructions.

(Some

IBM

monitors

have

their

own

self-tests.)

The

screen

blank.

Verify

that:

The

system

power

cord

connected

the

BladeCenter

power

module

and

working

electrical

outlet.

The

monitor

cables

are

connected

correctly.

The

monitor

turned

and

the

brightness

and

contrast

controls

are

adjusted

correctly.

you

have

verified

these

items

and

the

screen

remains

blank,

replace:

Monitor

Management

module

the

BladeCenter

(see

the

Hardware

Maintenance

Manual

and

Troubleshooting

Guide

for

your

BladeCenter

unit).

148

BladeCenter

JS20

Type

8842:

Hardware

Maintenance

Manual

and

Troubleshooting

Guide