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

IBM JS20 Hardware Maintenance Manual - Page 46

Ending, session

UPC - 000435230263

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

Page 46 highlights

BladeCenter and BladeCenter T Management Module Command Line Eserver Interface Reference Guide for information about SOL commands. See the operating-system documentation for information about SOL commands that you can enter using the command-line interface. Additional information about setting up and enabling SOL, and configuring a blade server for SOL, is available in the BladeCenter JS20 Installation and User's Guide on the IBM BladeCenter Documentation CD. 2. The BladeCenter management module automatically stores the previous 8 KB of serial data that was transmitted by each blade server, even when SOL sessions are not active. When an SOL session is established, all of the previous serial data, up to 8 KB, is automatically displayed. If no previous data is available when the SOL session starts, the cursor will remain on the command line until new serial data is transmitted. After you start a Telnet or SSL session to the BladeCenter management module, you can start an SOL session to any individual blade server that supports SOL using the console command. Therefore, you can have simultaneous SOL sessions active for each blade server installed in the BladeCenter unit. Use the console command from the command line, indicating the target blade server, where x is the corresponding blade server bay number: console -T system:blade[x] For example, to start an SOL connection to the blade server in blade bay 14, type console -T system:blade[14] A blade server that occupies more than one blade server bay is identified by the lowest bay number that it occupies. After an SOL session is started, all commands are sent to the blade server that is specified by the console command until the SOL session is ended, regardless of the persistent command target that was in effect before the SOL session. To restart the blade server through an SOL session, use the following key sequence: Esc R Esc r Esc R Complete the following steps to start a BladeCenter management module Telnet CLI session: 1. From a command prompt, type telnet location Where location is the host name or IP address of the BladeCenter management module 2. Log on to the BladeCenter management module. The default user name is USERID, and the default password is PASSW0RD (note the number zero, not the letter O, in PASSW0RD). Ending an SOL session To end an SOL session, use the following key sequence: Press the Esc and shift-9 keys. The command-line interface will return to the persistent command target that was in effect before the SOL session. To exit a BladeCenter management-module Telnet CLI session, type exit at the BladeCenter management-module Telnet CLI prompt after ending an SOL session. 36 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

Eserver

BladeCenter

and

BladeCenter

Management

Module

Command

Line

Interface

Reference

Guide

for

information

about

SOL

commands.

See

the

operating-system

documentation

for

information

about

SOL

commands

that

you

can

enter

using

the

command-line

interface.

Additional

information

about

setting

and

enabling

SOL,

and

configuring

blade

server

for

SOL,

available

the

BladeCenter

JS20

Installation

and

User’s

Guide

the

IBM

BladeCenter

Documentation

CD.

The

BladeCenter

management

module

automatically

stores

the

serial

data

that

was

transmitted

each

blade

server,

even

when

SOL

sessions

are

not

active.

When

SOL

session

established,

all

the

serial

data,

KB,

automatically

displayed.

data

available

when

the

SOL

session

starts,

the

cursor

will

remain

the

command

line

until

new

serial

data

transmitted.

After

you

start

Telnet

SSL

session

the

BladeCenter

management

module,

you

can

start

SOL

session

any

individual

blade

server

that

supports

SOL

using

the

console

command.

Therefore,

you

can

have

simultaneous

SOL

sessions

active

for

each

blade

server

installed

the

BladeCenter

unit.

Use

the

console

command

from

the

command

line,

indicating

the

target

blade

server,

where

the

corresponding

blade

server

bay

number:

console

-T

system:blade[

]

For

example,

start

SOL

connection

the

blade

server

blade

bay

14,

type

console

-T

system:blade[14]

blade

server

that

occupies

than

one

blade

server

bay

identified

the

lowest

bay

number

that

occupies.

After

SOL

session

started,

all

commands

are

sent

the

blade

server

that

specified

the

console

command

until

the

SOL

session

ended,

regardless

the

persistent

command

target

that

was

effect

before

the

SOL

session.

restart

the

blade

server

through

SOL

session,

use

the

following

key

sequence:

Esc

Complete

the

following

steps

start

BladeCenter

management

module

Telnet

CLI

session:

From

command

prompt,

type

telnet

location

Where

location

the

host

name

address

the

BladeCenter

management

module

Log

the

BladeCenter

management

module.

The

default

user

name

USERID,

and

the

default

password

PASSW0RD

(note

the

number

zero,

not

the

letter

PASSW0RD).

Ending

SOL

session

end

SOL

session,

use

the

following

key

sequence:

Press

the

Esc

and

shift-9

keys.

The

command-line

interface

will

return

the

persistent

command

target

that

was

effect

before

the

SOL

session.

exit

BladeCenter

management-module

Telnet

CLI

session,

type

exit

the

BladeCenter

management-module

Telnet

CLI

prompt

after

ending

SOL

session.

BladeCenter

JS20

Type

8842:

Hardware

Maintenance

Manual

and

Troubleshooting

Guide