IBM JS20, BladeCenter JS20Type 8842 Maintenance And Troubleshooting Manual
BladeCenter JS20
Ty pe 8842
Hardw are Maintenance Manual and
Troubleshooting Guid e
BladeCenter JS20
Ty pe 8842
Hardw are Maintenance Manual and
Troubleshooting Guid e
Notes
v Before using this information and the product it supports, read Appendix B, “Safety information,” on page 163 and
“Notices” on page 197
v The most recent version of this document is available at http://www.ibm.com/pc/support/.
16th Edition (June 2006)
© Copyright International Business Machines Corporation 2003. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
About this manual
This manual contains diagnostic information, a symptom-to-FRU index, service
information, error codes, error messages, and configuration information for the IBM
BladeCenter
®
JS20 Type 8842 blade server.
Important safety information
Be sure to read all caution and danger statements in this book before performing
any of the instructions; see Appendix B, “Safety information,” on page 163.
Leia todas as instruções de cuidado e perigo antes de executar qualquer operação.
Prenez connaissance de toutes les consignes de type Attention et Danger avant de
procéder aux opérations décrites par les instructions.
Lesen Sie alle Sicherheitshinweise, bevor Sie eine Anweisung ausführen.
Accertarsi di leggere tutti gli avvisi di attenzione e di pericolo prima di effettuare
qualsiasi operazione.
Lea atentamente todas las declaraciones de precaución y peligro ante de llevar a
cabo cualquier operación.
®
WARNING: Handling the cord on this product or cords associated with accessories
sold with this product, will expose you to lead, a chemical known to the State of
California to cause cancer, and birth defects or other reproductive harm. Wash
hands after handling.
ADVERTENCIA: El contacto con el cable de este producto o con cables de
accesorios que se venden junto con este producto, pueden exponerle al plomo, un
elemento químico que en el estado de California de los Estados Unidos está
considerado como un causante de cancer y de defectos congénitos, además de
otros riesgos reproductivos. Lávese las manos después de usar el producto.
Online support
You can download the most current firmware update and device driver files from
http://www.ibm.com/pc/support.
© Copyright IBM Corp. 2003 iii
iv BladeCenter JS20 Type 8842: Hardware Maintenance Manual and Troubleshooting Guide
Contents
About this manual . . . . . . . . . . . . . . . . . . . . . . . iii
Important safety information . . . . . . . . . . . . . . . . . . . . iii
Online support . . . . . . . . . . . . . . . . . . . . . . . . . iii
Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . .1
Related documentation . . . . . . . . . . . . . . . . . . . . . .3
The IBM BladeCenter Documentation CD . . . . . . . . . . . . . . .4
Hardware and software requirements . . . . . . . . . . . . . . . .4
Using the Documentation Browser . . . . . . . . . . . . . . . . .4
Notices and statements used in this document . . . . . . . . . . . . . .5
Features and specifications . . . . . . . . . . . . . . . . . . . . .6
BladeCenter JS20 specifications for non-NEBS/ETSI environments . . . . .6
BladeCenter JS20 specifications for NEBS/ETSI environments . . . . . . .7
Preinstallation checklist . . . . . . . . . . . . . . . . . . . . . .9
Checking the status of the media tray . . . . . . . . . . . . . . . .10
Chapter 2. Blade server power, controls, and indicators . . . . . . . .13
Turning on the blade server . . . . . . . . . . . . . . . . . . . .13
Turning off the blade server . . . . . . . . . . . . . . . . . . . .14
Blade server controls and LEDs . . . . . . . . . . . . . . . . . .14
Chapter 3. Configuration . . . . . . . . . . . . . . . . . . . . .17
Using the command-line interface . . . . . . . . . . . . . . . . . .18
Configuring the Gigabit Ethernet controller . . . . . . . . . . . . . . .18
Blade server Ethernet controller enumeration . . . . . . . . . . . . . .19
Chapter 4. Problem determination procedures for AIX and Linux . . . . .21
Problem determination . . . . . . . . . . . . . . . . . . . . . .21
Obtaining an SRN/SRC or error code . . . . . . . . . . . . . . . .22
Chapter 5. AIX online, standalone and verification procedures . . . . . .25
Performing AIX online concurrent mode diagnostics for problem determination 25
Running the standalone diagnostics from CD-ROM . . . . . . . . . . .25
Performing AIX online concurrent mode diagnostics for previous diagnostic
results: service aids . . . . . . . . . . . . . . . . . . . . . .28
Performing AIX online concurrent mode diagnostics for system verification . . .29
Verifying the replacement part using AIX diagnostics . . . . . . . . . . .30
Chapter 6. Running a Serial Over LAN session . . . . . . . . . . . .33
Selecting the command target . . . . . . . . . . . . . . . . . . .34
Starting the command-line interface . . . . . . . . . . . . . . . . .34
Establishing a Telnet connection . . . . . . . . . . . . . . . . .35
Establishing a Secure Shell (SSH) connection . . . . . . . . . . . .35
Starting an SOL session . . . . . . . . . . . . . . . . . . . . .35
Ending an SOL session . . . . . . . . . . . . . . . . . . . . . .36
Chapter 7. Diagnostics . . . . . . . . . . . . . . . . . . . . .37
General checkout . . . . . . . . . . . . . . . . . . . . . . . .37
Checkout procedure . . . . . . . . . . . . . . . . . . . . . . .38
Diagnostic tools overview . . . . . . . . . . . . . . . . . . . . .39
POST . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
Checkpoints . . . . . . . . . . . . . . . . . . . . . . . . .40
Accessing the Linux system error log . . . . . . . . . . . . . . . .40
© Copyright IBM Corp. 2003 v
Service aids and the Linux system error log . . . . . . . . . . . . .40
FRU/CRU isolation . . . . . . . . . . . . . . . . . . . . . . .46
Error symptom charts . . . . . . . . . . . . . . . . . . . . . .46
Light path diagnostics . . . . . . . . . . . . . . . . . . . . . .46
Memory errors . . . . . . . . . . . . . . . . . . . . . . . . .47
Recovering the system firmware code . . . . . . . . . . . . . . . .48
Recovery of system firmware code using service aids . . . . . . . . .48
Starting the TEMP image . . . . . . . . . . . . . . . . . . . .48
Recovering the TEMP image from the PERM image . . . . . . . . . .49
Updating the blade server firmware . . . . . . . . . . . . . . . . .50
Determination of current server firmware levels . . . . . . . . . . . .51
Updating the blade server service processor . . . . . . . . . . . . .51
Update and manage system flash using Linux service aids . . . . . . . .51
Updating the system flash using Linux . . . . . . . . . . . . . .51
Verifying the system firmware levels using Linux . . . . . . . . . .52
Update and manage system flash using AIX diagnostics . . . . . . . . .52
Updating the system flash using AIX . . . . . . . . . . . . . . .52
Committing the temporary firmware image using AIX . . . . . . . . .53
Verifying the system firmware levels using AIX . . . . . . . . . . .53
Recovering the system firmware code . . . . . . . . . . . . . . . .54
Recovery of system firmware code using service aids . . . . . . . . .55
Starting the backup image . . . . . . . . . . . . . . . . . . . .55
Recovering the primary image . . . . . . . . . . . . . . . . . .56
Chapter 8. General AIX and xSeries standalone diagnostic information 59
Information for general diagnostic systems running the AIX operating system 59
AIX operating system message files . . . . . . . . . . . . . . . .59
CE login . . . . . . . . . . . . . . . . . . . . . . . . . . .59
Missing resources . . . . . . . . . . . . . . . . . . . . . . . .60
Automatic diagnostic tests . . . . . . . . . . . . . . . . . . . . .60
Configuration program . . . . . . . . . . . . . . . . . . . . .60
Diagnostic programs . . . . . . . . . . . . . . . . . . . . . .61
Error log analysis . . . . . . . . . . . . . . . . . . . . . . . .61
Introducing tasks and service aids . . . . . . . . . . . . . . . . . .62
Task and service aid functions . . . . . . . . . . . . . . . . . .62
AIX automatic error log analysis (diagela) . . . . . . . . . . . . . .62
Error log analysis . . . . . . . . . . . . . . . . . . . . . . .63
Log repair action . . . . . . . . . . . . . . . . . . . . . . .63
Tasks (service aids) . . . . . . . . . . . . . . . . . . . . . .63
Download microcode . . . . . . . . . . . . . . . . . . . . .64
Update and manage system flash . . . . . . . . . . . . . . . .65
Using the standalone CD-ROM and online current diagnostics . . . . . .67
Standalone and online diagnostics operating considerations . . . . . . .67
Running online diagnostics . . . . . . . . . . . . . . . . . . .67
Running the online diagnostics in concurrent mode . . . . . . . . . .68
Running standalone diagnostics from a management (NIM) server . . . . . .68
NIM server configuration . . . . . . . . . . . . . . . . . . . .69
Client configuration and booting ERserver standalone diagnostics from the
NIM server . . . . . . . . . . . . . . . . . . . . . . . .69
Chapter 9. Installing options . . . . . . . . . . . . . . . . . . .71
Installation guidelines . . . . . . . . . . . . . . . . . . . . . .71
System reliability guidelines . . . . . . . . . . . . . . . . . . .71
Handling static-sensitive devices . . . . . . . . . . . . . . . . .71
Removing the blade server from the BladeCenter unit . . . . . . . . . .73
Opening the blade server cover . . . . . . . . . . . . . . . . . . .74
vi BladeCenter JS20 Type 8842: Hardware Maintenance Manual and Troubleshooting Guide
Removing the blade server bezel assembly . . . . . . . . . . . . . .75
Installing IDE hard disk drives . . . . . . . . . . . . . . . . . . .75
Installing memory modules . . . . . . . . . . . . . . . . . . . .77
Installing an I/O expansion card . . . . . . . . . . . . . . . . . . .79
Ethernet controller, switch module, and cabling requirements . . . . . . . .82
Replacing the battery . . . . . . . . . . . . . . . . . . . . . .83
System board . . . . . . . . . . . . . . . . . . . . . . . . .86
System board component locations . . . . . . . . . . . . . . . .86
System-board LED locations . . . . . . . . . . . . . . . . . . .87
Replacing the system board . . . . . . . . . . . . . . . . . . .87
Completing the installation . . . . . . . . . . . . . . . . . . . . .90
Installing the blade-server bezel assembly . . . . . . . . . . . . . .90
Closing the blade server cover . . . . . . . . . . . . . . . . . .92
Input/output connectors and devices . . . . . . . . . . . . . . . . .92
Chapter 10. Symptom-to-FRU index . . . . . . . . . . . . . . . .93
Firmware checkpoint (progress) codes . . . . . . . . . . . . . . . .94
Firmware error codes . . . . . . . . . . . . . . . . . . . . . . 102
Service request numbers . . . . . . . . . . . . . . . . . . . . . 108
Linux service aid ″diagela″ . . . . . . . . . . . . . . . . . . . 109
Using the SRN list . . . . . . . . . . . . . . . . . . . . . . 109
Service request number . . . . . . . . . . . . . . . . . . . 109
Source of SRN . . . . . . . . . . . . . . . . . . . . . . 109
Failing Function Codes . . . . . . . . . . . . . . . . . . . 109
Description and action . . . . . . . . . . . . . . . . . . . .110
Using the SRN list . . . . . . . . . . . . . . . . . . . . .110
SRN tables . . . . . . . . . . . . . . . . . . . . . . . . .110
AIX SRNs 101-711 through 2D02 . . . . . . . . . . . . . . . .110
SRNs A00-(x)xxx through A1D-(x)xxx . . . . . . . . . . . . . . 121
Failing Function Codes (FFCs) . . . . . . . . . . . . . . . . 141
FFC table . . . . . . . . . . . . . . . . . . . . . . . . 142
Light path diagnostics LEDs . . . . . . . . . . . . . . . . . . . 145
Error symptoms . . . . . . . . . . . . . . . . . . . . . . . . 145
CD drive problems . . . . . . . . . . . . . . . . . . . . . . 146
Diskette drive problems . . . . . . . . . . . . . . . . . . . . 147
General problems . . . . . . . . . . . . . . . . . . . . . . 147
Hard disk drive problems . . . . . . . . . . . . . . . . . . . . 147
Memory problems . . . . . . . . . . . . . . . . . . . . . . 148
Microprocessor problems . . . . . . . . . . . . . . . . . . . . 148
Monitor problems . . . . . . . . . . . . . . . . . . . . . . 148
Mouse problems . . . . . . . . . . . . . . . . . . . . . . . 149
Network connection problems . . . . . . . . . . . . . . . . . . 150
Option problems . . . . . . . . . . . . . . . . . . . . . . . 150
Power problems . . . . . . . . . . . . . . . . . . . . . . . 151
Service processor problems . . . . . . . . . . . . . . . . . . . 151
Software problems . . . . . . . . . . . . . . . . . . . . . . 152
Startup problems . . . . . . . . . . . . . . . . . . . . . . . 152
Service processor error codes . . . . . . . . . . . . . . . . . . . 152
Boot problem resolution . . . . . . . . . . . . . . . . . . . . . 153
Physical location codes . . . . . . . . . . . . . . . . . . . . . 154
Undetermined problems . . . . . . . . . . . . . . . . . . . . . 156
Problem determination tips . . . . . . . . . . . . . . . . . . . . 158
Chapter 11. Parts listing, Type 8842 . . . . . . . . . . . . . . . . 159
Appendix A. Getting help and technical assistance . . . . . . . . . . 161
Contents vii
Before you call . . . . . . . . . . . . . . . . . . . . . . . . 161
Using the documentation . . . . . . . . . . . . . . . . . . . . . 161
Getting help and information from the World Wide Web . . . . . . . . . 162
Software service and support . . . . . . . . . . . . . . . . . . . 162
Hardware service and support . . . . . . . . . . . . . . . . . . . 162
Appendix B. Safety information . . . . . . . . . . . . . . . . . 163
General safety . . . . . . . . . . . . . . . . . . . . . . . . 163
Electrical safety . . . . . . . . . . . . . . . . . . . . . . . . 164
Safety inspection guide . . . . . . . . . . . . . . . . . . . . . 165
Grounding requirements . . . . . . . . . . . . . . . . . . . . . 166
Safety notices (multi-lingual translations) . . . . . . . . . . . . . . . 166
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Edition notice . . . . . . . . . . . . . . . . . . . . . . . . . 197
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Important notes . . . . . . . . . . . . . . . . . . . . . . . . 198
Product recycling and disposal . . . . . . . . . . . . . . . . . . 199
Battery return program . . . . . . . . . . . . . . . . . . . . . 199
Electronic emission notices . . . . . . . . . . . . . . . . . . . . 200
Federal Communications Commission (FCC) statement . . . . . . . . 200
Industry Canada Class A emission compliance statement . . . . . . . . 200
Australia and New Zealand Class A statement . . . . . . . . . . . . 200
United Kingdom telecommunications safety requirement . . . . . . . . 200
European Union EMC Directive conformance statement . . . . . . . . 201
Taiwanese Class A warning statement . . . . . . . . . . . . . . . 201
Chinese Class A warning statement . . . . . . . . . . . . . . . . 201
Japanese Voluntary Control Council for Interference (VCCI) statement 201
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
viii BladeCenter JS20 Type 8842: Hardware Maintenance Manual and Troubleshooting Guide
Chapter 1. Introduction
The IBM BladeCenter JS20 Type 8842, also known as the blade server, is based
on the IBM Power Architecture
™
technologies.
The BladeCenter JS20 Type 8842 is compatible with IBM BladeCenter units. This
high-performance blade server is well-suited for networking environments that
require outstanding microprocessor performance, efficient memory management,
flexibility, and reliable data storage.
Notes:
1. In this document, the term BladeCenter unit refers to any IBM BladeCenter,
BladeCenter T, or other BladeCenter-class chassis model, except where
specifically indicated otherwise.
2. The number of blade servers your BladeCenter unit supports depends on the
type of BladeCenter unit. For example, the IBM Eserver BladeCenter Type
8677 supports up to 14 hot-swap blade servers; the BladeCenter T Types 8720
and 8730 support up to 8 hot-swap blade servers. See the documentation that
comes with the BladeCenter unit for more information. For more information
about determining the power requirements for the blade server, see the IBM
Eserver BladeCenter Power Module Upgrade Guidelines Technical Update on
the IBM BladeCenter Documentation CD.
3. The types and capacities of power modules your BladeCenter unit supports,
which affects the number of blade servers you can install in the BladeCenter
unit, depends on the type of BladeCenter unit. See the documentation that
comes with the BladeCenter unit for more information.
© Copyright IBM Corp. 2003 1
Release
levers
Release
button
Notes:
v In a BladeCenter unit that supports multiple types of power modules with different
capacities, such as the BladeCenter Type 8677, the maximum number of blade
servers that the BladeCenter unit supports varies by the wattage of the power
modules that are installed in the BladeCenter unit. For more information about
determining the power requirements for the blade server, see the IBM Eserver
BladeCenter Power Module Upgrade Guidelines Technical Update on the World
Wide Web at http://www.ibm.com/support/.
v Two power modules are required to support the blade servers in power domain A
in the BladeCenter unit. The following blade bays are in power domain A:
– Blade bays 1 through 6 in a BladeCenter Type 8677 or similar unit
– Blade bays 1 through 5 in a BladeCenter T unit
If you install blade servers in these blade bays, you must install power modules
in power-module bays 1 and 2 in the BladeCenter unit.
v Two additional power modules are required to support the blade servers in power
domain B in the BladeCenter unit. The following blade bays are in power domain
B:
– Blade bays 7 through 14 in a Type 8677 or similar BladeCenter unit
– Blade bays 6 through 8 in a BladeCenter T unit
you install blade servers in these blade bays, you must install power modules
If
in power-module bays 3 and 4 in the BladeCenter unit.
v Make sure that you review and understand the design of the BladeCenter unit.
Use this information to help you determine your system configuration
requirements and the bays and connectors where you will install or remove
2 BladeCenter JS20 Type 8842: Hardware Maintenance Manual and Troubleshooting Guide
components. For additional information, see the BladeCenter unit Installation and
User’s Guide on the Documentation CD for your BladeCenter unit, or go to
http://www.ibm.com/support/ on the World Wide Web.
Related documentation
This Hardware Maintenance Manual and Troubleshooting Guide is provided in
Portable Document Format (PDF) on the IBM BladeCenter JS20 Documentation CD
that comes with the IBM BladeCenter JS20 Type 8842. It contains information to
help you solve problems yourself or to provide helpful information to a service
technician.
In addition to this Hardware Maintenance Manual and Troubleshooting Guide, the
following information is provided in PDF on the IBM BladeCenter Documentation
CD that comes with the IBM BladeCenter JS20 Type 8842:
v Safety Information: This document contains translated caution and danger
statements. Each caution and danger statement that appears in the
documentation has a number that you can use to locate the corresponding
statement in your language in the Safety Information document.
v BladeCenter JS20 Type 8842 Installation and User’s Guide: This document
contains instructions for setting up the server, contains basic instructions for
installing some options; and provides general information about the server,
including information about features and how to configure the server.
v BladeCenter and BladeCenter T Management Module User’s Guide: This
document contains instructions for installing, starting, configuring, and using the
BladeCenter unit management module. This document also provides general
information about the management module and contains a description of the
management module features.
v BladeCenter and BladeCenter T Management Module Command-Line Interface
Reference Guide: This document contains instructions for installing, starting,
configuring, and using the IBM Eserver BladeCenter management-module
command-line interface. This document also provides general information about
the BladeCenter management-module command-line interface and contains a
description of its features.
v BladeCenter or BladeCenter T Management Module Installation Guide: This
document contains instructions for installing, setting up, starting, and configuring
the BladeCenter unit management module.
v BladeCenter unit Installation and User’s Guide: This document contains
instructions for setting up and configuring the BladeCenter unit and basic
instructions for installing some options in the BladeCenter unit. It also contains
general information about the BladeCenter unit.
v BladeCenter unit Hardware Maintenance Manual and Troubleshooting Guide:
This document contains the information to help you solve BladeCenter unit
problems yourself, and it contains information for service technicians.
v BladeCenter unit Rack Installation Instructions: This document contains
instructions for installing the BladeCenter unit in a rack.
v IBM 4-Port Gb Ethernet Switch Module for BladeCenter Installation and User’s
Guide: This document contains instructions for setting up, installing, and
configuring the IBM 4-Port Gb Ethernet Switch Module for BladeCenter and a
description of the switch-module features.
v Nortel Networks Layer 2-7 GbE Switch Module for IBM BladeCenter Installation
Guide: This document contains instructions for setting up, installing, and
Chapter 1. Introduction 3
configuring the Nortel Networks Layer 2-7 GbE Switch Module for IBM Eserver
BladeCenter and a description of the switch-module features.
v IBM BladeCenter 2-Port Fibre Channel Switch Module Installation Guide: This
document contains instructions for setting up, installing, and configuring the IBM
Eserver BladeCenter 2-Port Fibre Channel Switch Module, and a description of
the switch module features.
v Technical Update for IBM BladeCenter Fiber Channel Switch Module version
1.00: This document contains updated information about the IBM Eserver
BladeCenter 2-Port Fibre Channel Switch Module.
v IBM Eserver BladeCenter and BladeCenter T Serial Over LAN Setup Guide:
This document contains instructions for establishing a Serial Over LAN (SOL)
connection, enabling the SOL feature, and configuring the blade server so that
you can run SOL sessions and use the BladeCenter management-module
command-line interface. This document also contains instructions for updating
and configuring BladeCenter components for SOL operation using the
management-module Web-based management and configuration program.
v IBM Eserver BladeCenter Power Module Upgrade Guidelines Technical Update:
This document contains information that helps you determine the power
requirements for the blade server.
Additional documentation might be included on the IBM BladeCenter Documentation
CD.
The IBM BladeCenter Documentation CD
The IBM BladeCenter JS20 blade server Documentation CD contains
documentation for the blade server in Portable Document Format (PDF) and
includes the IBM Documentation Browser to help you find information quickly.
Hardware and software requirements
The IBM Documentation CD requires the following minimum hardware and
software:
v Microsoft
Red Hat
Windows NT
®
®
Linux
®
4.0 (with Service Pack 3 or later), Windows
®
v 100 MHz microprocessor
v 32 MB of RAM
v Adobe Acrobat Reader 3.0 (or later) or xpdf, which comes with Linux operating
systems
Note: Acrobat Reader software is included on the CD, and you can install it
when you run the Documentation Browser.
Using the Documentation Browser
Use the Documentation Browser to browse the contents of the CD, read brief
descriptions of the documents, and view documents using Adobe Acrobat Reader or
xpdf. The Documentation Browser automatically detects the regional settings in use
in the system and displays the documents in the language for that region (if
available). If a document is not available in the language for that region, the English
version is displayed.
®
2000, or
Use one of the following procedures to start the Documentation Browser:
v If Autostart is enabled, insert the CD into the CD drive. The Documentation
Browser starts automatically.
4 BladeCenter JS20 Type 8842: Hardware Maintenance Manual and Troubleshooting Guide
v If Autostart is disabled or is not enabled for all users:
– If you are using a Windows operating system, insert the CD into the CD drive
and click Start --> Run. In the Open field, type
x:\win32.bat
(where x is the drive letter of the CD drive), and click OK.
– If you are using a Linux operating system, insert the CD into the CD drive;
then, run the following command from the /mnt/cdrom directory:
sh runlinux.sh
Select the server from the Product menu. The Available Topics list displays all the
documents for the server. Some documents might be in folders. A plus sign (+)
indicates each folder or document that has additional documents under it. Click the
plus sign to display the additional documents.
When you select a document, a description of the document appears under Topic
Description. To select more than one document, press and hold the Ctrl key while
you select the documents. Click View Book to view the selected document or
documents in Acrobat Reader or xpdf. If you selected more than one document, all
the selected documents are opened in Acrobat Reader or xpdf.
To search all the documents, type a word or word string in the Search field and
click Search. The documents in which the word or word string appears are listed in
order of the most occurrences. Click a document to view it, and press Crtl+F to use
the Acrobat search function or Alt+F to use the xpdf search function within the
document.
Click Help for detailed information about using the Documentation Browser.
Notices and statements used in this document
The caution and danger statements that appear in this document are also in the
multilingual Safety Information document, which is on the IBM BladeCenter unit or
blade server Documentation CD. Each statement is numbered for reference to the
corresponding statement in the Safety Information document.
The following notices and statements are used in the documentation:
v Notes: These notices provide important tips, guidance, or advice.
v Important: These notices provide information or advice that might help you avoid
inconvenient or problem situations.
v Attention: These notices indicate potential damage to programs, devices, or
data. An attention notice is placed just before the instruction or situation in which
damage could occur.
v Caution: These statements indicate situations that can be potentially hazardous
to you. A caution statement is placed just before the description of a potentially
hazardous procedure step or situation.
v Danger: These statements indicate situations that can be potentially lethal or
extremely hazardous to you. A danger statement is placed just before the
description of a potentially lethal or extremely hazardous procedure step or
situation.
Chapter 1. Introduction 5
Features and specifications
This section provides a summary of the features and specifications of your blade
server. Through the BladeCenter unit management module, you can view the blade
server firmware code and other hardware configuration information.
Note: Power, cooling, removable-media drives, external ports, and advanced
system management are provided by the IBM Eserver BladeCenter unit.
For more information, see the Installation and User’s Guide for your
BladeCenter unit.
BladeCenter JS20 specifications for non-NEBS/ETSI environments
The following table provides a summary of the features and specifications of the
BladeCenter JS20 Type 8842 in a non-NEBS/ETSI environment. This includes
model-specific information.
®
Microprocessor:
®
Two IBM PowerPC
microprocessors
with 512 KB ECC L2 cache
Memory:
v Four double-data rate (DDR)
PC2700 sockets
v Minimum: 512 MB
v Maximum: 4 or 8 GB (depends on
the blade server model) *
IDE
devices:
v Support for up to two internal
integrated drive electronics (IDE)
2.5-inch hard disk drives
or
v Support for one internal IDE
2.5-inch hard disk drive in IDE
connector 1 and one optional I/O
expansion card in IDE connector 2
Note: Installing an I/O expansion
Size:
v Height: 24.5 cm (9.7 inches)
v Depth: 44.6 cm (17.6 inches)
v Width: 2.9 cm (1.14 inches)
v Maximum weight: 5.4 kg (12 lb)
Integrated
functions:
v One dual-port Gigabit Ethernet
controller
v Light path diagnostics
v Local service processor
v One IDE hard disk drive controller
with two channels
v RS-485 interface for
communication with BladeCenter
management module
v Serial Over LAN (SOL)
Predictive Failure Analysis
alerts:
v Microprocessors
v Memory
v Hard disk drives
Environment:
v Air temperature:
– Blade server on: 10° to 35°C
(50° to 95°F). Altitude: 0 to 914
m (0 to 3000 ft)
– Blade server on: 10° to 32°C
(50° to 90°F). Altitude: 914 m to
2133 m (3000 ft to 7000 ft)
– Blade server off: -40° to 60°C
(40° to 140° F)
v
Humidity:
– Blade server on: 8% to 80%
– Blade server off: 5% to 80%
Electrical input:
v Input voltage: 12 V dc
card increases network
connections.
* For information about dual inline memory module (DIMM) type and supported DIMM size, see “Installing memory
modules” on page 77.
(PFA)
Note: The operating system in the blade server must provide USB support for the
blade server to recognize and use the CD drive and diskette drive. The
BladeCenter unit uses USB for internal communications with these devices.
6 BladeCenter JS20 Type 8842: Hardware Maintenance Manual and Troubleshooting Guide
BladeCenter JS20 specifications for NEBS/ETSI environments
The following table provides a summary of the features and specifications of the
BladeCenter JS20 Type 8842 in a NEBS/ETSI environment. This includes
model-specific information.
Microprocessor:
®
v Two IBM Power PC
microprocessors with 512 KB ECC
L2 cache
Memory:
v Four DDR PC2700 sockets
v Minimum: 1 GB
v Maximum: 4 or 8 GB (depends on
the blade server model)
IDE
devices:
v NEBS application does not support
internal drives
Size:
v Height: 24.5 cm (9.7 inches)
v Depth: 44.6 cm (17.6 inches)
v Width: 2.9 cm (1.14 inches)
v Maximum weight: 5.4 kg (12 lb)
Integrated
functions:
v One dual-port Gigabit Ethernet
controller
v Light path diagnostics
v Local service processor
v One IDE hard disk drive controller
with two channels
v RS-485 interface for
communication with BladeCenter
management module
v Serial over LAN
Predictive
Failure Analysis (PFA)
alerts:
v Microprocessors
v Memory
Environment (NEBS):
v Air temperature:
– Blade server on: 5° to 40°C (41°
to 104°F). Altitude: -60 to 1800 m
(-197 to 6000 ft)
– Blade server on (short term): -5°
to 55°C (23° to 131°F) Altitude:
-60 to 1800 m (-197 to 6000 ft)
– Blade server on: 5° to 30°C (41°
to 86°F). Altitude: 1800 to 4000
m (6000 to 13 000 ft)
– Blade server on (short term): -5°
to 45°C (23° to 113°F). Altitude:
1800 to 4000 m (6000 to 13 000
ft)
– Blade server off: -40° to 70°C
(-40° to 158°F)
v
Humidity:
– Blade server on: 5% to 80%
– Blade server on (short term): 5%
to 90% but not to exceed 0.024
kg water/kg of dry air
– Blade server off: uncontrolled
"Short term" refers to a period
Note:
of not more than 96 consecutive hours
and a total of not more than 15 days in
1 year. (This refers to a total of 360
hours in any year, but no more than 15
occurrences during that 1-year period.)
Electrical input:
v Input voltage: 12 V dc
* For information about DIMM type and supported DIMM size, see “Installing memory modules” on page 77.
Notes:
1. The operating system in the blade server must provide USB support for the
blade server to recognize and use the CD drive and an external diskette drive.
The BladeCenter T unit uses USB for internal communication with these
devices.
Chapter 1. Introduction 7
2. BladeCenter JS20 models that are designed for the NEBS environment contain
a power-management capability that provides the maximum possible operating
time for your system. Power management is invoked only when the blade server
is installed in a BladeCenter T unit and only under the short term extended
thermal conditions that are described in the preceding table as "short term" in
the high end of the NEBS extended temperature range, 40° to 55°C (104° to
131°F). Instead of shutting down or failing in short term extended thermal
conditions, the JS20 blade server automatically reduces the frequency of the
processor to maintain acceptable thermal levels. The processor frequency
automatically returns to normal as thermal conditions improve. The BladeCenter
management module is notified when power management starts and again
when it stops.
The following entries are made in the event log:
v Frequency throttling process is now active.
(This message indicates that power reduction is in effect.)
v Frequency throttling process is now idling.
(This message indicates that power reduction was previously invoked but is
no longer in effect.)
not restart the blade server when power reduction is in effect.
Do
3. Some applications are sensitive to processor frequency changes. Check with
your application vendors to determine if there are any possible impacts to your
applications from the effects of the JS20 blade server power-management
capability in the short term extended thermal conditions of the NEBS
environment.
8 BladeCenter JS20 Type 8842: Hardware Maintenance Manual and Troubleshooting Guide
Preinstallation checklist
Before you can use the BladeCenter unit with the blade server, you must correctly
set up and configure the BladeCenter unit, and install and configure the required
components in the BladeCenter unit. Read Appendix B, “Safety information,” on
page 163, and the information in “Installation guidelines” on page 71, and review
the documentation that comes with each device and any applicable information in
the “Related documentation” on page 3.
If you have not already done so, perform the activities on the following checklist:
__ 1. Set up the rack in which you will install the BladeCenter unit.
__ 2. Install the BladeCenter unit in a rack. For additional information, see the
Rack Installation Instructions that come with the BladeCenter unit.
__ 3. Install and configure the required BladeCenter unit components:
__ a. Make sure that the BladeCenter unit has adequate power to support
__ b. Install and configure one or two management modules in the
__ c. Install and configure one or two Ethernet switch modules in the
all the installed devices. The BladeCenter unit must contain either two
or four power modules. If necessary, on BladeCenter units that
support it, upgrade the power modules in the BladeCenter unit to
higher-capacity power modules. For additional information, see the
IBM Eserver BladeCenter Power Module Upgrade Guidelines
Technical Update.
BladeCenter unit.
BladeCenter unit.
To support the Serial Over LAN (SOL) feature on any blade server
that is installed in the BladeCenter unit:
v A SOL-compatible Ethernet switch module must be installed in I/O
bay 1 of the BladeCenter unit.
v Both the BladeCenter unit and the Ethernet switch module must be
configured so that the SOL feature is enabled and set to operate on
the same virtual local area network (VLAN).
If you plan to install the operating system through the Ethernet
network, you also must install and configure a second Ethernet switch
module in I/O bay 2 of the BladeCenter unit.
__ d. Configure the BladeCenter unit for SOL operation as described in the
__ 4. If the BladeCenter unit was shipped to you before June 2003, make sure
that:
Note: If you install other Ethernet switch modules, they do not have
to be the same type that you installed in I/O bay 1 of the
BladeCenter unit.
IBM Eserver BladeCenter and BladeCenter T Serial Over LAN Setup
Guide.
Verify that the firmware code for the BladeCenter unit, management
module, and Ethernet switch modules supports the SOL feature. If you
are not sure whether these devices come with this feature, see the
IBM Eserver BladeCenter and BladeCenter T Serial Over LAN Setup
Guide for additional information.
The SOL feature is required and must remain enabled for all
applicable devices, including the BladeCenter unit, management
module, and Ethernet switch modules.
Chapter 1. Introduction 9
__ a. The hardware and firmware in the BladeCenter unit are at the
supported levels for the blade server. Go to the IBM Support Web
site, http://www.ibm.com/support/, for additional information.
__ b. The BladeCenter unit has the correct customer interface card (CIC)
(see “Checking the status of the media tray”).
For illustrations and additional information, see the following related documentation
on the World Wide Web at http://www.ibm.com/support/:
v BladeCenter Type 8677 Rack Installation Instructions
v BladeCenter Type 8677 Installation and User ’s Guide
v BladeCenter T Types 8720 and 8730 Installation and User’s Guide
v BladeCenter T 2-Post Rack Mount Kit Installation Instructions
v BladeCenter T 4-Post and Universal Telco Frame (UTF) Rack Mount Kit
Installation Instructions
v IBM Eserver BladeCenter Power Module Upgrade Guidelines Technical Update
v BladeCenter Management Module Installation Guide
v BladeCenter T Management Module Installation Guide
v BladeCenter and BladeCenter T Management Module Command-Line Interface
Reference Guide
v IBM Eserver BladeCenter and BladeCenter T Serial Over LAN Setup Guide
v The documentation that comes with the Ethernet switch module that you are
using; for example:
– IBM 4-Port Gb Ethernet Switch Module for BladeCenter Installation and User’s
Guide
– Nortel Networks Layer 2-7 GbE Switch Module for IBM BladeCenter
Installation Guide
For more information, see “Related documentation” on page 3.
Note:
Checking the status of the media tray
If you received a BladeCenter unit other than a Type 8677, this topic does not
apply.
Important: If you received a Type 8677 BladeCenter unit before June 2003, the
customer interface card (CIC) in the media tray of the BladeCenter unit might need
to be replaced before the CD drive will work correctly with a BladeCenter JS20
Type 8842.
If you received a Type 8677 BladeCenter unit before June 2003, start the
management-module Web interface and perform these steps to determine if the
CIC in your BladeCenter unit needs to be replaced:
1. In the navigation pane on the left side, select Monitors; then, select Hardware
VPD.
2. While looking at the “BladeCenter Hardware VPD” table in the right pane, find
the row for module name “Media Tray”.
3. Check the “FRU Number” column for the “Media Tray”.
4. If you see 59P6629, have the CIC replaced before installing a BladeCenter
JS20 Type 8842 in the BladeCenter unit.
10 BladeCenter JS20 Type 8842: Hardware Maintenance Manual and Troubleshooting Guide
To have the CIC replaced, call the IBM Support Center and report the CIC as a
failed part and request replacement with the latest CIC field replaceable unit (FRU).
Chapter 1. Introduction 11
12 BladeCenter JS20 Type 8842: Hardware Maintenance Manual and Troubleshooting Guide
Chapter 2. Blade server power, controls, and indicators
This chapter describes the power features, how to turn on and turn off the blade
server, and what the controls and indicators mean.
Turning on the blade server
Important: To generate faster blade-server startups from the network, connect the
dynamic host configuration protocol (DHCP) server to the Ethernet switch module in
I/O bay 2 in the BladeCenter unit. The system firmware code in the blade server
detects this Ethernet controller first. The Ethernet controller in each blade server is
then associated with the switch module in I/O bay 2.
Notes:
v After you connect the power cords of the BladeCenter unit to the electrical
outlets, wait until the power-on LED on the blade server flashes slowly before
pressing the blade server power-control button. Before the LED flashes, the
service processor in the BladeCenter management module is initializing, and the
power-control button on the blade server will not respond.
v While the blade server is powering up, the power-on LED on the front of the
server is lit. See “Blade server controls and LEDs” on page 14 for the power-on
LED states.
v After an orderly shutdown of the operating system occurs, the Wake on LAN
feature is permanently enabled in the blade server system firmware. Therefore,
Enabled is the default setting. The Wake on LAN setting for each blade server is
stored in the management-module nonvolatile random-access memory (NVRAM).
To disable the Wake on LAN feature for one or more blade servers, use the
BladeCenter management-module Web interface. For more information about the
BladeCenter management-module Web interface, see the BladeCenter and
BladeCenter T Management Module User’s Guide on the IBM BladeCenter
Documentation CD.
v Throughout this document, the management-module Web-based user interface is
also known as the BladeCenter management-module Web interface.
®
you connect the BladeCenter unit to power, the blade server can start in any
After
of the following ways:
v You can press the power-control button on the front of the blade server (behind
the control panel door) to start the server.
v If a power failure occurs, the BladeCenter unit and then the blade server can
start automatically when power is restored (if the blade server is configured
through the BladeCenter management module to do so).
v You can turn on the blade server remotely by means of the service processor in
the BladeCenter management module.
v If the operating system supports the Wake on LAN feature and it has not been
disabled through the BladeCenter management-module Web interface, the blade
server power-on LED is flashing slowly, and the Wake on LAN feature can turn
on the blade server.
© Copyright IBM Corp. 2003 13
Turning off the blade server
When you turn off the blade server, it is still connected to power through the
BladeCenter unit. The blade server can respond to requests from the service
processor, such as a remote request to turn on the blade server. To remove all
power from the blade server, you must remove it from the BladeCenter unit.
Shut down the operating system before you turn off the blade server. See the
operating-system documentation for information about shutting down the operating
system.
If the blade server has not been turned off, it can be turned off in any of the
following ways:
v You can press the power-control button on the blade server (behind the control
panel door). This starts an orderly shutdown of the operating system, if this
feature is supported by the operating system.
Note: After turning off the blade server, wait at least 5 seconds before you press
the power-control button to turn on the blade server again.
v If the operating system stops functioning, you can press and hold the
power-control button for more than 4 seconds to turn off the blade server.
v The management module can turn off the blade server.
After turning off the blade server, wait at least 30 seconds for its hard disk
Note:
drives to stop spinning before you remove the blade server from the
BladeCenter unit.
Blade server controls and LEDs
This section describes the controls and LEDs on the blade server.
Power-control button: This button is behind the control panel door. Press this
button to manually turn the blade server on or off.
Note: The power-control button has effect only if local power control is enabled for
the blade server. Local power control is enabled and disabled through the
BladeCenter management-module Web interface.
14 BladeCenter JS20 Type 8842: Hardware Maintenance Manual and Troubleshooting Guide
Power control button
Notes:
1. The blade-error LED, information LED, and location LED can be turned off
through the BladeCenter management-module Web interface.
2. For additional information about errors, see “Light path diagnostics” on page 46.
3. This blade server does not have a keyboard/mouse/video select button.
Blade-error
LED
Information
LED
Location
LED
Activity
LED
Power-on
LED
CD/diskette/USB
select button
CD
Blade-error LED: When this amber LED is lit, it indicates that a system error has
occurred in the blade server.
Information LED: When this amber LED is lit, it indicates that information about a
system error for this blade server has been placed in the BladeCenter system-error
log.
Location LED: When this blue LED is lit, it has been turned on remotely by the
system administrator to aid in visually locating the blade server. The location LED
on the BladeCenter unit will be lit also.
Chapter 2. Blade server power, controls, and indicators 15
Activity LED: When this green LED is lit, it indicates that there is hard disk drive or
network activity.
Power-on LED: This green LED indicates the power status of the blade server in
the following manner:
v Flashing rapidly – The service processor on the blade server is communicating
with the BladeCenter management module.
v Flashing slowly – The blade server has power but is not turned on.
v Lit continuously (steady) – The blade server has power and is turned on.
16 BladeCenter JS20 Type 8842: Hardware Maintenance Manual and Troubleshooting Guide
Chapter 3. Configuration
The firmware in the blade server uses auto-configuration; therefore, additional
blade-server configuration programs are not required for the blade server. However,
if you have attached other devices to the blade server or the BladeCenter unit, you
must configure those devices as described in the applicable documentation that
comes with those devices or the BladeCenter unit. You do not have to set any
passwords to use the blade server. If you change the battery or replace the system
board, you must reset the date and time through the operating system.
You must establish a Serial Over LAN (SOL) connection and start an SOL session
on the blade server:
v To establish a communications channel between the blade server and a
compatible monitor (or video console), keyboard, and mouse
v To install the operating system on the blade server
v To configure the SOL feature
v To run diagnostics programs
v To have the blade server serviced
information relating to establishing an SOL connection, enabling the SOL
For
feature, and configuring the blade server so that you can run SOL sessions and use
the BladeCenter management-module command-line interface, see the following
documents on the IBM BladeCenter Documentation CD:
v IBM Eserver BladeCenter JS20 Installation and User’s Guide
v IBM Eserver BladeCenter and BladeCenter T Management Module
Command-Line Interface Reference Guide
Other documents on the IBM BladeCenter Documentation CD that you might find
useful in the configuration process are:
v IBM 4-Port Gb Ethernet Switch Module for BladeCenter Installation and User’s
Guide
v Nortel Networks Layer 2-7 GbE Switch Module for IBM BladeCenter Installation
Guide
For information about setting up the network configuration for remote management,
see the IBM Eserver BladeCenter Planning and Installation Guide or the IBM
Eserver BladeCenter T Planning and Installation Guide. Yo u can obtain the
planning guide from the Web site at http://www.ibm.com/pc/support.
To support the SOL feature and to configure the blade server, you must install a
compatible Ethernet switch module in I/O bay 1 of the BladeCenter unit. Examples
of compatible Ethernet switch modules are the IBM 4-Port Gb Ethernet Switch
Module for BladeCenter and the Nortel Networks Layer 2-7 GbE Switch Module for
IBM BladeCenter. For more information about these switch modules, see the IBM
4-Port Gb Ethernet Switch Module for BladeCenter Installation and User’s Guide or
Nortel Networks Layer 2-7 GbE Switch Module for IBM BladeCenter Installation
Guide on the IBM BladeCenter Documentation CD. Information is also available in:
v Chapter 6, “Running a Serial Over LAN session,” on page 33
v The IBM Eserver BladeCenter and BladeCenter T Management Module
Command Line Interface Reference Guide on the IBM BladeCenter
Documentation CD
© Copyright IBM Corp. 2003 17
Note: The BladeCenter unit supports up to four Ethernet switch modules.
The SOL feature is accessed through the Management Module Command-Line
Interface. For information about using the command-line interface, see “Using the
command-line interface” and the IBM Eserver BladeCenter and BladeCenter T
Management Module Command Line Interface Reference Guide on the IBM
BladeCenter Documentation CD.
Using the command-line interface
The IBM Eserver BladeCenter Management Module Command-Line Interface
provides direct access to BladeCenter management functions as an alternative to
using the Web interface. Using the command-line interface, you can issue
commands to control the power and configuration of the blade server and other
components installed in the BladeCenter unit. The command-line interface also
provides access to the text-console command prompt for the blade server through
an SOL connection. See the IBM Eserver BladeCenter and BladeCenter T
Management Module Command Line Interface Reference Guide on the IBM
BladeCenter Documentation CD for information and instructions.
Configuring the Gigabit Ethernet controller
One dual-port Gigabit Ethernet controller is integrated on the blade server system
board. Each controller port provides a 1000-Mbps full-duplex interface for
connecting to one of the Ethernet-compatible switch modules in I/O bays 1 and 2,
which enables simultaneous transmission and reception of data on the Ethernet
local area network (LAN). Each Ethernet controller port on the system board is
routed to a different switch module in I/O bay 1 or bay 2. The routing from the
Ethernet controller port to the I/O bay will vary based on blade server type and the
operating system that is installed. See “Blade server Ethernet controller
enumeration” on page 19 for information about how to determine the routing from
the Ethernet controller ports to I/O bays for the blade server.
Note: Other types of blade servers, such as the BladeCenter HS20 Type 8678, that
are installed in the same BladeCenter unit as this BladeCenter JS20 Type
8842 might have different requirements for Ethernet controller routing. See
the documentation that comes with the other blade servers for detailed
information.
You do not need to set any jumpers or configure the controllers for the blade server
operating system. However, you must install a device driver to enable the blade
server operating system to address the Ethernet controller ports. For device drivers
and information about configuring the Ethernet controller ports, see the Ethernet
software documentation that comes with the blade server, or contact your reseller or
IBM marketing representative. For updated information about configuring the
controllers, go to the IBM Support Web site at http://www.ibm.com/support/.
The Ethernet controller supports failover, which provides automatic redundancy for
the Ethernet controller ports. Without failover you can have only one Ethernet
controller port from each server attached to each virtual LAN or subnet. With
failover you can configure more than one Ethernet controller port from each server
to attach to the same virtual LAN or subnet. Either one of the integrated Ethernet
controller ports can be configured as the primary Ethernet controller port. If you
have configured the controller ports for failover and the primary link fails, the
secondary controller port takes over. When the primary link is restored, the Ethernet
18 BladeCenter JS20 Type 8842: Hardware Maintenance Manual and Troubleshooting Guide
traffic switches back to the primary Ethernet controller port. (See the
operating-system device driver documentation for information about configuring for
failover.)
Important: To support failover on the blade server Ethernet controller, the Ethernet
switch modules in the BladeCenter unit must have identical configurations to each
other.
Blade server Ethernet controller enumeration
The enumeration of the Ethernet controllers or controller ports in a blade server is
operating-system dependent. Yo u can verify the Ethernet controller or controller port
designations that a blade server uses through the operating-system settings.
The routing of an Ethernet controller or controller port to a particular BladeCenter
unit I/O bay depends on the type of blade server. You can verify which Ethernet
controller port in this blade server is routed to which I/O bay by using the following
test:
1. Install only one Ethernet switch module or pass-thru module in I/O bay 1.
2. Make sure that the ports on the switch module or pass-thru module are enabled
(I/O Module Tasks → Management → Advanced Management in the
BladeCenter management-module Web interface).
3. Enable only one of the Ethernet controller ports on the blade server. Note the
designation that the blade server operating system has for the controller port.
4. Ping an external computer on the network connected to the Ethernet switch
module. If you can ping the external computer, the Ethernet controller port that
you enabled is associated with the switch module in I/O bay 1. The other
Ethernet controller port in the blade server is associated with the switch module
in I/O bay 2.
If you have installed an I/O expansion card on a blade server, communications from
the option are routed to I/O bays 3 and 4. You can verify which controller port on
the card is routed to which I/O bay by performing the above test, using a controller
on the I/O expansion card and a compatible switch module or pass-thru module in
I/O bay 3 or 4.
Chapter 3. Configuration 19
20 BladeCenter JS20 Type 8842: Hardware Maintenance Manual and Troubleshooting Guide
Loading...