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

IBM JS20 Hardware Maintenance Manual - Page 55

management-module

UPC - 000435230263

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

Page 55 highlights

Step 006 Step 007 Step 008 RTAS daemon started RTAS: -------- event-scan begin -------RTAS: Location Code: U0.1-P1-C2 RTAS: Log Debug: 04 4b2726fb04a00011702c0014000000000000000000000000f1800001001801d3ffffffff0100000 00000000042343138 20202020383030343236464238454134303030303 030303030303030 RTAS: Log Debug: D2 5046413405020d0a000001000271400100000033434d502044415441000001000000000000010000 f180000153595320444154410000000000000000200216271501050920021627150105092002063 7150105095352432044415441702c001400000000000000020018820201d3820000000000000000 0000000000000000000000000000000000000000000000000000000000000000000000000000000 00000000000000000000000000280048ea400000000000000000000000000000000000000004350 542044415441702cff08000000001c000000702cf0080000000080000000702cf100702cf200702 c000400000800702c01040bf2002e702c02040c1fffbf702c0300702c1000702c11040bf2002e70 2c12040c1fffbf702c1300702ca000702ca108000000000000a03c702ca208000000000000effc7 02cb000702cb108000000000000a03c702cb208000000000000effc702cc000702cc10800000000 0000a03c702cc208000000000000effc702c3000702c31080000000000000003702c32080000000 00000007b702c8000702c81080000000020e27a39702c820800000000fffeffff702cd000702cd1 080000000010004010702cd208000000007777f3fffffffffffffffffffffffffffffffffffffff fffffffffffffffffffffffffff RTAS: WARNING: (FULLY RECOVERED) type: INTERN_DEV_FAIL RTAS: initiator: UNKNOWN target: UNKNOWN RTAS: Status: unrecoverable new RTAS: Date/Time: 20020905 15372200 RTAS: CPU Failure RTAS: Internal error (not cache) RTAS: CPU id: 0 RTAS: Failing element: 0x0000 RTAS: -------- event-scan end -------- Record any extended data found in the Linux Syslog (platform log) in Step 001 or the Linux boot (IPL) log in Step 003 . Be sure to record word 13. Note: The lines in the Linux extended data that begin with RTAS: Log Debug: 04 contain the error code listed in the next 8 hex characters. In the previous example, 4b27 26fb is an error code. The error code is also known as word 11. Each 4 bytes after the error code in the Linux extended data is another word (for example, 04a0 0011 is word 12, and 702c 0014 is word 13, and so on). Were any error codes or checkpoints recorded in Steps 001 , 002 , 003 , 004 , 005 , or 006 ? NO. Go to Step 008 . YES. Go to "Firmware checkpoint (progress) codes" on page 94 and "Firmware error codes" on page 102 for each recorded error code or symptom. Perform the indicated actions one at a time for each error code until the problem has been corrected. If all recorded error codes have been processed and the problem has not been corrected, go to Step 008 . If no additional error information is available and the problem has not been corrected, shut down the blade server. 1. Are there any event-logged entries in the BladeCenter management-module event log? 2. Replace the system board. Chapter 7. Diagnostics 45

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

RTAS

daemon

started

RTAS:

--------

event-scan

begin

--------

RTAS:

Location

Code:

U0.1-P1-C2

RTAS:

Log

Debug:

4b2726fb04a00011702c0014000000000000000000000000f1800001001801d3ffffffff0100000

00000000042343138

20202020383030343236464238454134303030303

030303030303030

RTAS:

Log

Debug:

5046413405020d0a000001000271400100000033434d502044415441000001000000000000010000

f180000153595320444154410000000000000000200216271501050920021627150105092002063

7150105095352432044415441702c001400000000000000020018820201d3820000000000000000

0000000000000000000000000000000000000000000000000000000000000000000000000000000

00000000000000000000000000280048ea400000000000000000000000000000000000000004350

542044415441702cff08000000001c000000702cf0080000000080000000702cf100702cf200702

c000400000800702c01040bf2002e702c02040c1fffbf702c0300702c1000702c11040bf2002e70

2c12040c1fffbf702c1300702ca000702ca108000000000000a03c702ca208000000000000effc7

02cb000702cb108000000000000a03c702cb208000000000000effc702cc000702cc10800000000

0000a03c702cc208000000000000effc702c3000702c31080000000000000003702c32080000000

00000007b702c8000702c81080000000020e27a39702c820800000000fffeffff702cd000702cd1

080000000010004010702cd208000000007777f3fffffffffffffffffffffffffffffffffffffff

fffffffffffffffffffffffffff

RTAS:

WARNING:

(FULLY

RECOVERED)

type:

INTERN_DEV_FAIL

RTAS:

initiator:

UNKNOWN

target:

UNKNOWN

RTAS:

Status:

unrecoverable

new

RTAS:

Date/Time:

20020905

15372200

RTAS:

CPU

Failure

RTAS:

Internal

error

(not

cache)

RTAS:

CPU

id:

RTAS:

Failing

element:

0x0000

RTAS:

--------

event-scan

end

--------

Step

±006²

Record

any

extended

data

found

the

Linux

Syslog

(platform

log)

Step

±001²

the

Linux

boot

(IPL)

log

Step

±003²

sure

record

word

13.

Note:

The

lines

the

Linux

extended

data

that

begin

with

RTAS:

Log

Debug:

contain

the

error

code

listed

the

hex

characters.

the

example,

4b27

26fb

error

code.

The

error

code

also

known

word

11.

Each

bytes

after

the

error

code

the

Linux

extended

data

another

word

(for

example,

04a0

0011

word

12,

and

702c

0014

word

13,

and

on).

Step

±007²

Were

any

error

codes

checkpoints

recorded

Steps

±001²

±002²

±003²

±004²

±005²

±006²

NO.

Step

±008²

YES.

“Firmware

checkpoint

(progress)

codes”

page

and

“Firmware

error

codes”

page

102

for

each

recorded

error

code

symptom.

Perform

the

indicated

actions

one

time

for

each

error

code

until

the

problem

has

been

corrected.

all

recorded

error

codes

have

been

processed

and

the

problem

has

not

been

corrected,

Step

±008²

Step

±008²

additional

error

information

available

and

the

problem

has

not

been

corrected,

shut

down

the

blade

server.

Are

there

any

event-logged

entries

the

BladeCenter

management-module

event

log?

Replace

the

system

board.

Chapter

Diagnostics