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

IBM JS20 Hardware Maintenance Manual - Page 64

Recovering, system, firmware

UPC - 000435230263

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

Page 64 highlights

UPDATE AND MANAGE FLASH The current permanent system firmware image is 2b204_310 The current temporary system firmware image is 2b204_310 The system is currently booted from the temporary firmware image. Move cursor to selection, then press 'Enter'. Validate and Update System Firmware Validate System Firmware Commit the Temporary Image 802810 F1=Help F10=Exit F3=Previous Menu If the system was booted using the permanent image instead of the temporary image (as shown in the above example), the screen example would show: The system is currently booted from the permanent firmware image. and the last selection option is changed to: Reject the Temporary Image The firmware version information displayed by the AIX diagnostics (2b204_310 in the example shown above) may be different than the information displayed by the management module (see"Determination of current server firmware levels" on page 51). Cross reference information is given in the firmware information ("Blade Server Firmware - IBM BladeCenter JS20") on the IBM Support Web site at http://www.ibm.com/support/, as well as in the README file for the firmware image. Recovering the system firmware code If the system firmware code has become damaged, such as from a power failure during a flash update, the blade server might appear to be nonfunctional (no progress codes or firmware codes). You can recover the system firmware code by using the system firmware code page jumper (J14). Note: To obtain a system firmware flash image, download a system firmware file from http://www.ibm.com/support/. The system firmware is contained in two separate images in the flash memory of the blade server (primary and backup). Note: The primary image is also known as the TEMP side of the flash module. The backup image is also known as the PERM side of the flash module. If the primary image becomes damaged, such as from a power failure during a flash update, you can recover the primary image from the backup image. If this occurs, you can see one of two symptoms: v The system automatically starts up from backup. This is indicated by the error code 20D00902. v The system automatically starts up from backup. This is indicated by an event log message "OS Watchdog Triggered". v The system hangs or is non-responsive after the system is started with no checkpoints. 54 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

UPDATE

AND

MANAGE

FLASH

802810

The

current

permanent

system

firmware

image

2b204_310

The

current

temporary

system

firmware

image

2b204_310

The

system

currently

booted

from

the

temporary

firmware

image.

Move

cursor

selection,

then

press

’Enter’.

Validate

and

Update

System

Firmware

Validate

System

Firmware

Commit

the

Temporary

Image

F1=Help

F10=Exit

F3=Previous

the

system

was

booted

using

the

permanent

image

instead

the

temporary

image

(as

shown

the

above

example),

the

screen

example

would

show:

The

system

currently

booted

from

the

permanent

firmware

image.

and

the

last

selection

option

changed

to:

Reject

the

Temporary

Image

The

firmware

version

information

displayed

the

AIX

diagnostics

(2b204_310

the

example

shown

above)

may

different

than

the

information

displayed

the

management

module

(see“Determination

current

server

firmware

levels”

page

51).

Cross

reference

information

given

the

firmware

information

(“Blade

Server

Firmware

IBM

BladeCenter

JS20”)

the

IBM

Support

Web

site

http://www.ibm.com/support/,

well

the

README

file

for

the

firmware

image.

Recovering

the

system

firmware

code

the

system

firmware

code

has

become

damaged,

such

from

power

failure

during

flash

update,

the

blade

server

might

appear

nonfunctional

(no

progress

codes

firmware

codes).

You

can

recover

the

system

firmware

code

using

the

system

firmware

code

page

jumper

(J14).

Note:

obtain

system

firmware

flash

image,

download

system

firmware

file

from

http://www.ibm.com/support/.

The

system

firmware

contained

two

separate

images

the

flash

memory

the

blade

server

(primary

and

backup).

Note:

The

primary

image

also

known

the

TEMP

side

the

flash

module.

The

backup

image

also

known

the

PERM

side

the

flash

module.

the

primary

image

becomes

damaged,

such

from

power

failure

during

flash

update,

you

can

recover

the

primary

image

from

the

backup

image.

this

occurs,

you

can

see

one

two

symptoms:

The

system

automatically

starts

from

backup.

This

indicated

the

error

code

20D00902.

The

system

automatically

starts

from

backup.

This

indicated

event

log

message

“OS

Watchdog

Triggered”.

The

system

hangs

non-responsive

after

the

system

started

with

checkpoints.

BladeCenter

JS20

Type

8842:

Hardware

Maintenance

Manual

and

Troubleshooting

Guide