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

IBM JS20 Hardware Maintenance Manual - Page 62

Update, manage, system, flash, using, diagnostics

UPC - 000435230263

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

Page 62 highlights

This will copy your new image from the temp side to perm side of flash. Verifying the system firmware levels using Linux To verify the system firmware levels on the Perm and Temp side, enter the following command at the Linux prompt (the entire command must be entered on one line): for file in `ls /proc/device-tree/openprom/*bank*`; do echo $file; cat $file; echo; echo; done For Example: This command will return information similar to the following: /proc/device-tree/openprom/ibm,fw-bank P /proc/device-tree/openprom/ibm,fw-perm-bank FW04310120, 17:16:09, 07/26/2004 /proc/device-tree/openprom/ibm,fw-temp-bank FW04310120, 17:16:09, 07/26/2004 v The value for ibm,fw-bank indicates what side you booted from (T for TEMP, P for PERM). v The value for ibm,fw-perm-bank identifies the firmware version, date and time stamp of firmware on the PERM side. v The value for ibm,fw-temp-bank indicates the firmware version, date and time stamp of firmware on the TEMP side. Notes: 1. If you have to recover the system firmware code, see "Recovering the system firmware code" on page 54. 2. The IBM Remote Deployment Manager (RDM) program does not support the BladeCenter JS20 Type 8842. 3. A reboot of the system must be done after using update_flash -c for the firmware level shown in ibm,fw-perm-bank to be current. Update and manage system flash using AIX diagnostics This section describes how to update, commit and verify the system flash using AIX diagnostics. Updating the system flash using AIX Attention: Do not power off the system while performing this task! Complete the following steps: 1. Obtain the flash image you want to update from the IBM Support Web site at http://www.ibm.com/support/ (look for the flash image for Type 8842, under ″AIX Diagnostics Version Number″, this is the version used by the AIX diagnostics service aid). v If you want to update the image from the local file system, put the image into the /etc/microcode directory on the system prior to running this service aid. v If you want to update the image from media (diskette or optical media), put the image on the media of choice prior to running this service aid. 2. Run diagnostics. v If you have booted AIX, login as ″root″ or use the CE login; then, at the command line, enter: diag v Otherwise, boot standalone diagnostics; then press Enter. 52 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

This

will

copy

your

new

image

from

the

temp

side

perm

side

flash.

Verifying

the

system

firmware

levels

using

Linux

verify

the

system

firmware

levels

the

Perm

and

Temp

side,

enter

the

following

command

the

Linux

prompt

(the

entire

command

must

entered

one

line):

for

file

`ls

/proc/device-tree/openprom/*bank*`;

echo

$file;

cat

$file;

echo;

done

For

Example:

This

command

will

return

information

similar

the

following:

/proc/device-tree/openprom/ibm,fw-bank

/proc/device-tree/openprom/ibm,fw-perm-bank

FW04310120,

17:16:09,

07/26/2004

/proc/device-tree/openprom/ibm,fw-temp-bank

FW04310120,

17:16:09,

07/26/2004

The

value

for

ibm,fw-bank

indicates

what

side

you

booted

from

for

TEMP,

for

PERM).

The

value

for

ibm,fw-perm-bank

identifies

the

firmware

version,

date

and

time

stamp

firmware

the

PERM

side.

The

value

for

ibm,fw-temp-bank

indicates

the

firmware

version,

date

and

time

stamp

firmware

the

TEMP

side.

Notes:

you

have

recover

the

system

firmware

code,

see

“Recovering

the

system

firmware

code”

page

54.

The

IBM

Remote

Deployment

Manager

(RDM)

program

does

not

support

the

BladeCenter

JS20

Type

8842.

reboot

the

system

must

done

after

using

update_flash

-c

for

the

firmware

level

shown

ibm,fw-perm-bank

current.

Update

and

manage

system

flash

using

AIX

diagnostics

This

section

describes

how

update,

commit

and

verify

the

system

flash

using

AIX

diagnostics.

Updating

the

system

flash

using

AIX

Attention:

not

power

off

the

system

while

performing

this

task!

Complete

the

following

steps:

Obtain

the

flash

image

you

want

update

from

the

IBM

Support

Web

site

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

(look

for

the

flash

image

for

Type

8842,

under

″

AIX

Diagnostics

Version

Number

″

this

the

version

used

the

AIX

diagnostics

service

aid).

you

want

update

the

image

from

the

local

file

system,

put

the

image

into

the

/etc/microcode