BH3710-SERVGUIDE

7/30/2019 BH3710-SERVGUIDE

http://slidepdf.com/reader/full/bh3710-servguide 1/169

Hewlett-PackardHP Carrier Grade Blade Server bh3710 Service Guide

First Edition

E0402



Notice

The information contained in this document is subject to change without notice.

Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the

implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance,

or use of this material.

Hewlett-Packard assumes no responsibility for the use or reliability of its software on equipment that is not

furnished by Hewlett-Packard.

This document contains proprietary information that is protected by copyright. All rights are reserved. No part of

this document may be photocopied, reproduced, or translated to another language without the prior written consentof Hewlett-Packard Company.

Novell NetWare is a registered trademark of Novell, Inc. Microsoft Windows NT and NTAS are registered

trademarks of Microsoft Corporation. Windows and Windows 95 are registered trademarks of Microsoft in the U.S.

and other countries. SCO UNIX is a registered trademark of The Santa Cruz Operation, Inc. Banyan and VINES are

the registered trademarks of Banyan Systems Incorporated. OS/2 is the registered trademark of the InternationalBusiness Machines Corporation.

Hewlett-Packard Company

Network Server Division

Technical Communications / MS 45SLE10955 Tantau Avenue

Cupertino, California 95014 USA

© Copyright 2001, Hewlett-Packard Company.

Audience Assumptions

This guide is written for the person who installs, administers, and troubleshoots servers. Hewlett-Packard Company

assumes that you are qualified to service computer equipment and that you are trained to recognize the dangers inworking with products that have hazardous energy levels.

ii



Table of Contents

1 Introduction to the hp Carrier Grade Blade Server bh3710............... ........... .......... ........... ........... ........... .. 1-1

Available bh3710 Documents ............................................................................................................................ 1-5 Available Blades................................................................................................................................................. 1-5

Blade Slot Numbering................................................................................................................................. 1-5 Blade Descriptions ............................................................................................................................................. 1-7

Management Blade...................................................................................................................................... 1-7 Management LAN Blade............................................................................................................................. 1-7

bp2200 Server Blade................................................................................................................................... 1-7 FC Storage Blade ........................................................................................................................................ 1-8

Other bh3710 Components................................................................................................................................. 1-8 bh3710 Chassis............................................................................................................................................ 1-8 Power Supplies............................................................................................................................................ 1-9 Fans ...........................................................................................................................................................1-10

2 System Startup for the hp Carrier Grade Blade Server bh3710 ................................................................ 2-1

Powering Up for the First Time.......................................................................................................................... 2-1 Power Requirement..................................................................................................................................... 2-1

Data Connections ............................................................................................................................................... 2-1 Console Communications............................................................................................................................ 2-1 Payload LAN Communications................................................................................................................... 2-1

Communicating with the bh3710 ....................................................................................................................... 2-2 Logging In Using Direct Connection .......................................................................................................... 2-2 Logging In Using Telnet ............................................................................................................................. 2-2 Management Blade Configuration Menu .................................................................................................... 2-3 Quick Setup Screen (Main Menu Option 1)................................................................................................ 2-4 Installed Device Information....................................................................................................................... 2-9

Server Management Application (SMA) Screen (Main Menu Option 3)...................................................2-11 Chassis Status and Configuration (Main Menu Option 4)..........................................................................2-16 Alarms and Events (Main Menu Option 5) ................................................................................................2-22 Voltages (Main Menu Option 6) ................................................................................................................2-30 Temperature Logs (Main Menu Option 7) .................................................................................................2-31 Configuration (Main Menu Option 9) ........................................................................................................2-35 Exit ...........................................................................................................................................................2-37

3 Power Supplies for the hp Carrier Grade Blade Server bh3710 ................................................................ 3-1

Shutdown Conditions ......................................................................................................................................... 3-1 Specifications ..................................................................................................................................................... 3-1 Removing and Replacing Power Supplies.......................................................................................................... 3-2

Power Supply Removal............................................................................................................................... 3-2 Power Supply Replacement......................................................................................................................... 3-3

iii



4 Management Blade ......................................................................................................................................... 4-1

Management Blade Introduction ........................................................................................................................ 4-1 Glossary.............................................................................................................................................................. 4-2 External Interfaces.............................................................................................................................................. 4-3

Operating Phases......................................................................................................................................... 4-3

Key Functions ............................................................................................................................................. 4-4 Communicating with the Management Blade .................................................................................................... 4-7

Command Line User Interface (CLUI) ....................................................................................................... 4-7 Configuration Menu CLUI.......................................................................................................................... 4-7

Alarms and Configuration.................................................................................................................................. 4-9 Non-Volatile Configuration Parameters............................................................................................................4-10

Parameter Types.........................................................................................................................................4-10 SMA and General Chassis Configuration Parameters................................................................................4-10 Chassis Slot Configuration Parameters ......................................................................................................4-11 Dial Out / Paging Configuration Parameters..............................................................................................4-13

Normal Operation..............................................................................................................................................4-13

Raised Alarms Table................................................................................................................................4-18 System Event Log (SEL)............................................................................................................................4-19 Commands..................................................................................................................................................4-19 Operator Indicators.....................................................................................................................................4-21

Resetting the Management Blade Password......................................................................................................4-22 Removing and Installing the Management Blade..............................................................................................4-23

Management Blade Removal .....................................................................................................................4-24 Management Blade Installation..................................................................................................................4-26

5 Fibre Channel (FC) and LAN Rear Transition Module (RTM) Blade for the hp Carrier Grade Blade

Server bh3710.................................................................................................................................................. 5-1

FC and LAN RTM Blade Introduction............................................................................................................... 5-1

Removing and Installing the Fibre Channel (FC) and LAN RTM Blade ........................................................... 5-1 FC and LAN RTM Slot Blockers................................................................................................................ 5-2 Removing FC and LAN RTM Blades ......................................................................................................... 5-3 Installing FC and LAN RTM Blades........................................................................................................... 5-3

iv



6 bp2200 Server Blade for the hp Carrier Grade Blade Server bh3710 ....................................................... 6-4

bp2200 Features ................................................................................................................................................. 6-4 Processor ..................................................................................................................................................... 6-4 Memory....................................................................................................................................................... 6-4 PCI Mezzanine Card ................................................................................................................................... 6-5

Storage Device ............................................................................................................................................ 6-5 Hot Swap Support ....................................................................................................................................... 6-5 Management Processor (MP) ...................................................................................................................... 6-5

bp2200 Configuration......................................................................................................................................... 6-6 Memory Installation.................................................................................................................................... 6-6 MP Configuration........................................................................................................................................ 6-7

bp2200 LED Descriptions .................................................................................................................................. 6-9 Removing and Installing the bp2200 Server Blade ...........................................................................................6-10

Cooling System Constraints .......................................................................................................................6-10 bp2200 Server Blade Removal...................................................................................................................6-11 DIMM Removal/Replacement ...................................................................................................................6-14

bp2200 Server Blade Installation ...............................................................................................................6-15 7 Cooling Fan Tray Assembly for the hp Carrier Grade Blade Server bh3710........... ........... ........... .......... 7-1

Introduction ........................................................................................................................................................ 7-1 Required Tools ............................................................................................................................................ 7-1 Fan Tray Assembly Removal ...................................................................................................................... 7-2 Fan Tray Assembly Installation................................................................................................................... 7-3

8 Mass Storage Installation for the hp Carrier Grade Blade Server bh3710 ............................................... 8-1

Fibre Channel (FC) Disk Carrier Blade Installation........................................................................................... 8-1 Installing the FC Disk Carrier Blade .................................................................................................................. 8-1

Required Tools: ........................................................................................................................................... 8-1 Installing the FC Disk Carrier ..................................................................................................................... 8-2

Installing an Individual Drive in the FC Storage Blade .............................................................................. 8-3 Hardware Path Table................................................................................................................................... 8-3 FC Disk Configuration................................................................................................................................ 8-4

9 Rack Installation ............................................................................................................................................. 9-1

Installing the bh3710 in a Rack .......................................................................................................................... 9-1

10 Blade Server bh3710 Slot Blocker Installation/Removal............................................................................10-1

Introduction .......................................................................................................................................................10-1 Required Tools and Supplies......................................................................................................................10-2

Removing and Installing the Slot Blocker.........................................................................................................10-2 Slot Blocker Removal ................................................................................................................................10-2 Slot Blocker Installation.............................................................................................................................10-2

v



11 Blade Server Chassis for the hp Carrier Grade Blade Server bh3710......................................................11-1

Introduction .......................................................................................................................................................11-1 Required Tools and Supplies......................................................................................................................11-1

Replacing the Chassis/Backplane......................................................................................................................11-2 Component Removal..................................................................................................................................11-2

Chassis/Backplane Installation...................................................................................................................11-5 12 Maintenance and Troubleshooting for the hp Carrier Grade Blade Server bh3710 .......... ........... ..........12-1

Maintenance ......................................................................................................................................................12-1 Required Tools ...........................................................................................................................................12-1 Cooling Fan Tray Assembly Maintenance .................................................................................................12-2 Removing and Installing the Fan Tray Assembly ......................................................................................12-2

Monitoring System Operation ...........................................................................................................................12-4 Configuring Hardware Monitoring.............................................................................................................12-4 Documentation ...........................................................................................................................................12-4

Troubleshooting.................................................................................................................................................12-5 Troubleshooting Tools ...............................................................................................................................12-5 Common Installation Problems..................................................................................................................12-5 Troubleshooting Sequence .........................................................................................................................12-6 General Troubleshooting............................................................................................................................12-9 Diagnostics...............................................................................................................................................12-11

A Specifications for the hp Carrier Grade Blade Server bh3710 .......... .......... ........... ........... ........... ........... ...A-1

Introduction ........................................................................................................................................................A-1 Physical, Electrical, and Environmental Specifications .....................................................................................A-1 International Standards.......................................................................................................................................A-3 Configuration Menu Command Line Interface Specifications...........................................................................A-4

Interface Definition .....................................................................................................................................A-4 Temperature Control ........................................................................................................................................A-21

Voltage Control ................................................................................................................................................A-22 SNMP...............................................................................................................................................................A-22

B Parts List for the hp Carrier Grade Blade Server bh3710..........................................................................B-1

C Additional Backplane Jumper Positions for the hp Carrier Grade Blade Server bh3710 ........... ........... .C-1

D LVM Boot Device Hardware Path Change...................................................................................................C-1

vi



Table of Figures

Figure 1-1: Block Diagram........................................................................................................................................ 1-3

Figure 1-3: Top view of bh3710 Chassis................................................................................................................... 1-4

Figure 1-5: Management Blade Identification Legend Marking ............................................................................... 1-7

Figure 1-7: Management LAN Identification Legend Marking ................................................................................ 1-7

Figure 1-9: Server Identification Legend Marking .................................................................................................... 1-7

Figure 1-11: Storage Blade Identification Legend Marking...................................................................................... 1-8

Figure 1-13: bh3710 Front Chassis View.................................................................................................................. 1-8

Figure 1-15: bh3710 Rear Chassis View ................................................................................................................... 1-9

Figure 1-17: Fan Tray Assembly............................................................................................................................. 1-10

Figure 2-1: Chassis Rear View Showing LAN Connectors....................................................................................... 2-1

Figure 2-2: Management Blade Login Screen ........................................................................................................... 2-2 Figure 2-3: Management Blade Configuration Menu (Main Menu).......................................................................... 2-3

Figure 2-4: Quick Setup Screen................................................................................................................................. 2-4

Figure 2-5: Editing LAN Parameters From the Quick Setup Screen ......................................................................... 2-5

Figure 2-6: Setting Power StateHardware Installed Table Screen (Main Menu Option 2)........................................ 2-6

Figure 2-7: Hardware Installed Table Page 1 ............................................................................................................ 2-7

Figure 2-8: "More Info..." Selected for the Management Blade ................................................................................ 2-9

Figure 2-9: Editing Gateway Address ..................................................................................................................... 2-10

Figure 2-10: Server Management Application Configuration Page (Option 2) ....................................................... 2-11

Figure 2-11: Setting the NTP Server Name............................................................................................................. 2-12 Figure 2-12: Auto Self Tests Results....................................................................................................................... 2-13

Figure 2-13: Manual Self Tests ............................................................................................................................... 2-14

Figure 2-14: Running the Manual Self Test ............................................................................................................ 2-14

Figure 2-15: Results of Manual Self Test ................................................................................................................ 2-15

Figure 2-16: Versions Screen .................................................................................................................................. 2-15

Figure 2-17: Chassis Status and Configuration Page............................................................................................... 2-16

Figure 2-18: Chassis Configuration......................................................................................................................... 2-17

Figure 2-19: Sensor Configuration Screen .............................................................................................................. 2-18

Figure 2-20: Management Blade LEDs Page .......................................................................................................... 2-19

Figure 2-21: Chassis LEDs Page ............................................................................................................................. 2-19

Figure 2-22: Chassis Fan Status .............................................................................................................................. 2-20

Figure 2-23: Fibre Channel Configuration .............................................................................................................. 2-20

Figure 2-24: LAN Switch Link Status..................................................................................................................... 2-21

Figure 2-25: Alarms and Events.............................................................................................................................. 2-22

vii



Figure 2-26: System Event Log............................................................................................................................... 2-23

Figure 2-27: More Info Screen for Event Log ......................................................................................................... 2-24

Figure 2-28: Event Log By Device.......................................................................................................................... 2-25

Figure 2-29: Event Log By Device: Chassis (Slot #1)............................................................................................. 2-26

Figure 2-30: Raised Alarms..................................................................................................................................... 2-27 Figure 2-31: Raised Alarms, More Info................................................................................................................... 2-27

Figure 2-32: SNMP Traps ....................................................................................................................................... 2-28

Figure 2-33: Editing SNMP Traps........................................................................................................................... 2-28

Figure 2-34: System Event Log After Clearing Alarms .......................................................................................... 2-29

Figure 2-35: Voltage Logs....................................................................................................................................... 2-30

Figure 2-36: Temperature Logs............................................................................................................................... 2-31

Figure 2-37: Opening "Users" Menu ....................................................................................................................... 2-32

Figure 2-38: Edit User Details Screen ..................................................................................................................... 2-33

Figure 2-39: Configure Pager Function................................................................................................................... 2-34 Figure 2-40: Create New Users Page....................................................................................................................... 2-34

Figure 2-41: Configuration...................................................................................................................................... 2-35

Figure 2-42: Device Configuration Table................................................................................................................ 2-36

Figure 2-43: Change Device Selection.................................................................................................................... 2-37

Figure 3-1: PSU Converter Unit (Front View) .......................................................................................................... 3-1

Figure 3-2: PSU DC Inlet Module (Rear View) ........................................................................................................ 3-1

Figure 3-3: Inserting Converter Module into Chassis................................................................................................ 3-3

Figure 3-4: Inserting Inlet Module into Chassis ........................................................................................................ 3-3

Figure 4-1: Management Blade ................................................................................................................................. 4-1

Figure 4-2: Alarm Events and the Blackout Period ................................................................................................. 4-17

Figure 4-3 Management Blade 9-Pin, D-Shell Pinout ............................................................................................. 4-20

Figure 4-4: Cooling System Operation.................................................................................................................... 4-23

Figure 4-5: Releasing the Locking Lever ................................................................................................................ 4-24

Figure 4-6: Loosen the Locking Screws.................................................................................................................. 4-25

Figure 4-7: Pull Blade From Chassis....................................................................................................................... 4-25

Figure 4-8: Align Blade With Blade Guides And Push Into Chassis ...................................................................... 4-26

Figure 4-9: Insert the Blade ..................................................................................................................................... 4-26

Figure 4-10: Tighten the Locking Screws ............................................................................................................... 4-27

Figure 5-1: FC and LAN RTM Blade........................................................................................................................ 5-1

Figure 5-2: Rear Slot Blocker.................................................................................................................................... 5-2

viii



Figure 5-3: Insert Rear Slot Blocker......................................................................................................................... 5-2

Figure 5-4: FC and LAN RTM Blade Captive Screw Location ............................................................................... 5-3

Figure 6-1: Layout of bp2200 Server Blade ............................................................................................................. 6-4

Figure 6-2: Memory DIMM Order of Installation..................................................................................................... 6-6 Figure 6-3: bp2200 DIMM Installation ..................................................................................................................... 6-6

Figure 6-4: bp2200 Blade Caution Label .................................................................................................................. 6-7

Figure 6-5: bh3710 Chassis (Rear View) .................................................................................................................. 6-8

Figure 6-6: Cooling System Operation.................................................................................................................... 6-10

Figure 6-7: Releasing Locking Levers..................................................................................................................... 6-11

Figure 6-8: Loosen Locking Screws....................................................................................................................... 6-12

Figure 6-9: Releasing Locking Levers..................................................................................................................... 6-12

Figure 6-10: Pull Blade From Chassis..................................................................................................................... 6-13

Figure 6-11: Slot Blocker ........................................................................................................................................ 6-13 Figure 6-12: Ejecting Memory From Slot ............................................................................................................... 6-14

Figure 6-13: Memory Keyed For Insertion.............................................................................................................. 6-14

Figure 6-14: Inserting Memory Into Slot................................................................................................................. 6-14

Figure 6-15: Align Blade With Card Guides and Push Into Chassis ....................................................................... 6-15

Figure 6-16: Insert the Blade ................................................................................................................................... 6-16

Figure 6-17: Tighten the Locking Screws ............................................................................................................... 6-16

Figure 7-1: Fan Tray Assembly (Chassis Front)........................................................................................................ 7-2

Figure 7-2: Pulling the Fan Assembly Out Of the Chassis ........................................................................................ 7-3

Figure 7-3 : Inserting the Fan Tray Assembly into the Chassis ................................................................................. 7-3

Figure 8-1: FC Disk Carrier Legend Marking........................................................................................................... 8-1

Figure 8-2: Slot Blocker ............................................................................................................................................ 8-1

Figure 8-3: FC Disk Carrier DIP switch location ..................................................................................................... 8-2

Figure 8-4: FC Disk carrier blade.............................................................................................................................. 8-2

Figure 8-5: FC Blade Act LED.................................................................................................................................. 8-3

Figure 9-1: Rack Installation Instructions ................................................................................................................. 9-2

Figure 10-1: Slot Blocker, Front.............................................................................................................................. 10-1

Figure 10-2: Front Slot Blocker, Partially Installed................................................................................................. 10-1

Figure 10-3: Slot Blocker, Rear............................................................................................................................... 10-1

Figure 10-4: Rear Slot Blocker, Partially Installed.................................................................................................. 10-1

ix



Figure 11-1: HP Blade Server Front View .............................................................................................................. 11-1

Figure 11-2: HP Blade Server Rear View .............................................................................................................. 11-1

Figure 11-3: HP Blade Server Rear View ............................................................................................................... 11-2

Figure 11-4: HP Blade Server Front view ............................................................................................................... 11-3

Figure 12-1: bh3710 Blade Server (Front View) ..................................................................................................... 12-1

Figure 12-2: Cooling Fan Tray Assembly Bulkhead............................................................................................... 12-2

Figure 12-3: Inserting the Fan Tray Assembly into the Chassis .............................................................................. 12-3

List of Tables

Table 1-1: bh3710 Initial Configuration.................................................................................................................... 1-2

Table 1-2: Slot Compatibility List............................................................................................................................. 1-5

.Table 1-3: Blade Slot Nomenclature ........................................................................................................................ 1-6

Table2-1: Hardware Installed Nomenclature............................................................................................................. 2-8

Table 4-1: Management Blade Functions.................................................................................................................. 4-2

Table 4-2: Glossary ................................................................................................................................................... 4-2

Table 4-3: Alarm Table ............................................................................................................................................. 4-5

Table 4-4: User Initiated Self-Tests........................................................................................................................... 4-8

Table 4-5: Alarms...................................................................................................................................................... 4-9

Table 4-6: Chassis Configuration Paramaters.......................................................................................................... 4-10

Table 4-7: Slot Configuration Parameters ............................................................................................................... 4-11

Table 4-8: Dial Out/Paging Configuration Parameters............................................................................................ 4-13

Table 4-9: LED Indicators....................................................................................................................................... 4-21

Table 4-10: Chassis LED Definitions...................................................................................................................... 4-21

Table 8-1: FC Hardware Paths ................................................................................................................................. 8-3

x



1 Introduction to the hp Carrier Grade BladeServer bh3710

The HP bh3710 carrier grade blade server is a new concept of modular system design focused on network-centric

environments like ISP and Telecom data centers. The bh3710 systems are implemented using the form factor andconnector technology of the open CompactPCI® specification. Each system is implemented on one or more

CompactPCI® form factor boards and interfaces to a backplane with an embedded high speed, inter-system fabric.The interface to this high-speed storage and networking fabric is composed of open, industry standard interfaces,

and as such, any architecture that supports the standard fabric connections can be used as the basis of the system

module.

The chassis is based on CompactPCI® standards, and will accommodate 10 full size CompactPCI® cards (6U x160mm) in the front slots, and 10 half size CompactPCI® cards (6U X 80mm) called Rear Transition Modules

(RTM) in the rear slots. Power is supplied by two –48VDC n+1 power supply units (PSU) housed below the main

chamber in an independent enclosure. They are fed through separate filter modules from either A or B feeds. The

CompactPCI® cards in the main chamber are cooled by 6 fans mounted on a tray. In the event of a fan failure, the

tray assembly slides in and out allowing easy replacement. Each PSU is cooled independently by its own set of fans.

The bh3710 incorporates two separate Local Area Networks (LANs). The Management Blade also controls aManagement LAN that receives, transmits, and routes signals specific to system management and configuration.

1-1

.





The block diagram of the chassis blades is shown in Figure 1-1. This figure shows the HP Server bh3710 PA-RISC

blade, the Management blade, the Management LAN blades, each with fibre channel bypass capability, and the

Storage Blades. The blades install into a two-sided “backplane” that provides connections to LAN and control

functions, as well as supplying DC power.

F1

F2

F3

F4

F5

F6

F7

F8

F9

F10

R9

R10

Management Blade

(Required)

Reserved for Future Use

Storage Blade

(Occupies 2-slots each F5/F6, F3/F4

HP Server bp2200 ( 2-slots)

CompactPCI RTM Slots

Management LAN Blade 1

R8

R7

R6

R5

R4

R3

R2

R1

F r o n t S i d e S l o t s

R e a r S i d e S l o t s

Top of Chassis

Bottom of Chassis

Management LAN Blade 2

"F" denotes Front, “R” denotes Rear

Figure 1-1: Block Diagram

1-3

.



In addition to the chassis and blades, the bh3710 incorporates redundant power supplies. A cutaway view of the

chassis appears in .

Backplane

Management LAN Blade

(FC Bypass/RTM)

Fan Tray Assembly

CompactPCI Card

(Front of Chassis)

LEDs

Figure 1-3: Top view of bh3710 Chassis

In the above view, the fan tray (shown on the right side) slides out from the front of the chassis. The 20 blade slotsare located in the front and back of the chassis. The power supplies (not shown) are located in the bottom of the

chassis. Further descriptions of these components appear later in this chapter.

1-4

.



Available bh3710 DocumentsThe following documents are supplied with the bh3710 and are referenced in this manual (most are contained only

on the CD-ROM):

• HP Carrier Grade Blade Server bh3710 Site Preparation Guide

• HP Carrier Grade Blade Server bh3710 Regulatory Guide

• HP Carrier Grade Blade Server bh3710 Installation Guide

• HP Carrier Grade Blade Server bh3710 Service Guide (this document)

Check the following web site for more current documents than those contained on the CD-ROM:

http://docs.hp.com/

Available BladesAvailable blades are listed below. More detailed descriptions follow this list.

• Management Blade

• Management LAN Blade

• bh3710 Server Blade

• FC Storage Blade

The following tabledefines the slot compatibility with various blades.

Table 1-3: Slot Compatibility List

Blade Quantity Slot Limitations Notes

Management 1 F10 Fixed location

Management LAN 2 R10 and R9 Each is a half depth blade

bh3710 Server 1 F1/F2 Occupies both slots

Storage1 1-2 F5/F6 (first) and F3/F4 Each blade occupies two slots

Blade Slot Numbering

The table shown above also shows the slot compatibility with reference to the physical slot in which the blade

resides where F denotes the front of the chassis and R denotes the rear of the chassis. The physical slot numbers are

printed on the bh3710 chassis.

There is another numbering scheme used in the bh3710 that is summarized below:

The Management Blade console program uses a “Hardware Installed Table.” This table lists the 20 slots as well asthe power supplies. Numbers 1-20 lists the slots and components serially.

1-5

.

1 The first Storage blade always occupies slots F5/F6 and if there is a second blade, it will occupy slots F3/F4. The bootdisk is on the right side for the Storage blade in F5/F6.

http://docs.hp.com/

http://docs.hp.com/



The following table defines how the physical hardware/label slot numbers correspond to the hardware installed

table, system nomenclature, and logical nomenclature.

Table 1-5: Blade Slot Nomenclature

Physical Slot

Location Blade Compatibility

Hardware

Installed Table

Slot Number System Slot Logical SlotFront 1 Server Blade 1 System Slot 1 F1

Front 2 Server Blade 2 System Slot 2 F2

Front 3 FC Storage Blade 3 Storage Slot 3 F3




Front 7 Reserved 7 Reserved F7



Front 10 Management Blade 10 Management Blade F10

Right Front Fan Tray Assembly Fan Control 1

Rear 1 Reserved 1 RTM Slot 1 R1



Rear4 Reserved 4 RTM Slot 4 R4


Rear 6 Reserved 6 RTM Slot 6 R6Rear 7 Reserved 7 RTM Slot 7 R7


Rear 9

Fibre Channel and

Management LANBlade 9 RTM Slot 9 R9

Rear 10

Fibre Channel and

Management LAN

Blade 10 RTM Slot 10 R10

Right-Hand Power Supply (viewed from

chassis front) PSU 1

Left-Hand Power Supply (viewed from

chassis front) PSU 2

1-6

.



Blade Descriptions

Management Blade

The Management Blade contains all necessary logic to run the bh3710 system and to communicate with an external

console. The Management Blade must reside in slot F10. Both the bh3710 chassis and the blade are identified with

a sticker containing a square logo, as shown in Figure 1-5 and are color-coded HP Flint Gray.

Figure 1-5: Management Blade Identification Legend Marking

Configuring the Management BladeThe Management blade arrives from the factory pre-configured.

Management LAN Blade

At least one Management LAN is required for Ethernet communication with the Management blade. The

Management blade implements an Ethernet switch with the Management LAN providing the external port for theManagement blade. The Management LAN blade provides communication expansion using either copper-based or

fiber-based channels. Management LAN blades are half depth blades installed in the rear of the bh3710. The

Management LAN must reside in the slot directly opposite the Management blade in slot R10. There is a second

Management LAN Blade located in slot R9. The identification sticker for the Management LAN is illustrated in

Figure 1-7. The blade and its slot are also color-coded HP Pewter Gray.

Figure 1-7: Management LAN Identification Legend Marking

bp2200 Server Blade

One bp2200 Server Blade resides in the chassis in slots F1/F2. The operating system does not reside on the Server

Blade but rather on the FC Storage Blade which comes pre-configured with HP-UX. A sticker, shown in Figure 1-9,

matches the blade to chassis slots, which are color-coded HP Light Blue.

Figure 1-9: Server Identification Legend Marking

1-7

.



FC Storage Blade

FC Storage Blade provides mass storage capability for the Server Blade. The storage blade can be populated with

one or two disk drives. The storage blade(s) resides in F5/F6 and F3/F4. The initial Storage Blade is inserted in

F5/F6 and comes pre-configured with HP-UX. A second Storage Blade can be added and it will be inserted in slotsF3/F4. The FC storage blade is hot swappable. Storage Blade slots are marked with the glyph shown in Figure 1-11,

and are color-coded HP Light Purple.

Figure 1-11: Storage Blade Identification Legend Marking

Other bh3710 ComponentsThe other components in the bh3710 are described in this section. Components include the chassis, power supplies,

and fan tray assembly.

bh3710 Chassis

The chassis has 10 slots on the front and 10 slots on the rear for blades and provides a centrally located backplane for all blade interconnection. The front and rear views of the chassis are shown in Figure 1-13 and Figure

1-15

Figure 1-13: bh3710 Front Chassis View

1-8

.



Grounding Lug

Figure 1-15: bh3710 Rear Chassis View

Power Supplies

The bh3710 contains n+1 redundant power supplies. The power supplies are located in the lower bay of the chassis

and are accessed from the front. A DC inlet module is located opposite each DC power supply and is accessible

from the rear of the chassis.

NOTE The required grounding lug for NEBS compliance is included. It is located at therear of the chassis above the DC inlet module located on the left side.

1-9

.



Fans

A fan tray assembly, shown as Figure 1-17, contains six fans that provide system cooling. Although there are no

visible LEDs on the chassis to indicate that a fan has failed, there are two ways to detect fan failure. A fail message

will be sent to the Management Blade console and an error message will be seen in the System Event Log (SEL). Inthe event of a single fan failure, the entire fan tray will need to be replaced. The fan tray assembly is hot swappable

and is located on the front of the chassis on the right side. Two captive screws secure the fan tray to the system

chassis.

Figure 1-17: Fan Tray Assembly

CAUTION It is recommended that the replacement fan assembly tray be unpacked and ready to install

prior to removing a faulty fan assembly tray.

Removal and replacement of fan assembly trays must be completed WITHIN 20

SECONDS or the server blades will begin to shut down and data being transmitted to the

blades will be lost

1-10

.



2 System Startup for the hp Carrier Grade BladeServer bh3710

Powering Up for the First TimeDuring initial installation described in the HP Carrier Grade Blade Server bh3710 Installation Guide, all cable

connections were made, the system was powered up and configured. The information contained in this chapter is

provided to familiarize the user with the overall start up procedures in the event it becomes necessary to re-initializethe system as a result of adding blades, relocating it, or for any other reason that it might become necessary.

Power Requirement

Power is provided to the system’s two power supplies through two separate power cords. Connect these power cords

by following the instructions in the HP Carrier Grade Blade Server bh3710 Installation Guide.

Data Connections

Console CommunicationsInitial communications with the system is made through a direct connection using the DB-9 on the ManagementBlade. Once configured with an IP address for the bh3710, connect via telnet from a remote terminal or computer.

NOTE Whether connecting directly or using telnet, the terminal or computer must be

configured as a VT-100 terminal.

Payload LAN Communications

Communications to the Payload LAN (generally an Internet backbone connection) connect via the FC Bypass/RTM

blade RJ-45 connectors as shown in Figure 2.1.

Figure 2-1: Chassis Rear View Showing LAN Connectors

2-1



Communicating with the bh3710You can monitor, configure, and set a number of parameters using the bh3710 configuration menus. These menus

are fully described in this section. First, log in to the system. Further information about the tables and definition of

their parameters appears in Chapter 4, “Management Blade.”

Logging In Using Direct Connection

When connecting directly to the Management Blade DB-9 port, connect a direct-connect cable between theManagement Blade and your terminal or computer serial port. Press <Enter> to display the login prompt: “>login:”.

At the login prompt, type:

>login: root

the password is:

>password: hpblade!

then press <Enter>. The menu in Figure 2-2 appears, from which you select “Configuration Menu.”

Logging In Using Telnet

If, after initial configuration, you wish to connect remotely using Telnet, first determine the hostname or IP address

of the bh3710 Management Blade. Bring up your Telnet program and connect to your bh3710.

Press <Enter> to display the login prompt: “>login:”. At the login prompt, type:

>login: root

the password is:

>password: hpblade!

then press <Enter>. From the menu in Figure 2-2, select “Configuration Menu.” All alterable parameters appear in

Chapter 4 “Management Blade.”

=======================================================================

Management Blade

You are: root

Options

1. Configuration Menu...

2. Serial Connect to Slot 9...

3. Exit to Linux Shell

4. Exit and Logoff

Choose option:

=======================================================================

Figure 2-2: Management Blade Login Screen

2-2



Select option 1, “Configuration Menu.” Next press the ‘Enter’ as suggested in the next screen that appears in order

to start the application.

NOTE For a complete listing of all alterable parameter values, see Chapter 4,

“Management Blade.”

Management Blade Configuration Menu

The first menu screen to appear is the Management Blade Configuration Menu displayed in Figure 2-3.

Management Blade Configuration Menu

=====================================================

1. Quick setup...

2. Hardware installed...

3. Server management application...4. Chassis status and configuration...

5. Alarms & events...

6. Voltages...

7. Temperatures...

8. Users...

9. Configuration...

Exit

=====================================================

Display/Modify device configuration

Figure 2-3: Management Blade Configuration Menu (Main Menu)

NOTE Selections are shown in the screen shots in gray for ease in understanding theNavigation.

This main menu allows access to each of the major functions. These functions are described in this chapter in the

order that they appear on the Management Blade Configuration menu.

The “Exit” function terminates the session and returns you to the menu shown in Figure 2-2. You can exit setup

from that menu.

You must set the Management LAN parameters using the Quick Setup Screen or from the Hardware Installed, MoreInfo menu, or for each blade prior to going “live” with the system. The values shown in the screen capture are the

default values as shipped from the factory. Assign your own LAN Configuration parameters.

2-3



Quick Setup Screen (Main Menu Option 1)

To facilitate rapid configuration, the Quick Setup Screen allows you to quickly set the Management LAN

parameters for the installed blades in the bh3710. Other, more robust, controls are located the other menu options.

The Quick Setup Screen is illustrated in Figure 2-4.

Quick Setup Table Page 1 of 2

=============================================================

===========

Slot Device detected Change management LAN params Change power status

10 Management blade 15.8.134.99 Automatic

1 Host processor blade 15.8.134.100 Automatic

2 No blade Automatic

3 FC storage blade Automatic


5 FC storage blade Automatic




9 No blade Automatic << < > >> Back

===========================================================

View/Modify Management LAN information

Figure 2-4: Quick Setup Screen

The navigation arrows operate as follows:

Screen

Cursor

Keyboard

Shortcut

Action

<< < Return to the first page

< , Go to the previous page

> . Go to the next page

>> > Jump to the last page

Back Go back to Main Menu page

NOTE Selections are shown in the screen shots in gray for ease in understanding thenavigation.

2-4



Change LAN ParametersUsing the navigation arrows on your keyboard, highlight the parameter you wish to setup or change and press

<Enter>. In the example in Figure 2-4, the Management Blade LAN parameters are highlighted. Pressing <Enter>

brings up the screen shown in Figure 2-5.

Edit Management LAN Parameters

===========================================================

Position: Slot 10

Host name: pb-smc

IP address: 15.8.133.217

Subnet mask: 255.255.248.0

Gateway address: 15.8.128.1

DNS address: 15.8.132.99

Domain name: rose.hp.com

NOTE: Exiting this screen (using the 'Back' button or the ESCAPE key) with changes to any of the network

parameters will cause existing networking connections to be lost.

This will not reboot the management blade.

Restore Values Reset to factory defaults Back

===========================================================

Host name

Figure 2-5: Editing LAN Parameters From the Quick Setup Screen

When you have finished editing the parameters, highlight <Back> and press <Enter> (or press <Esc>) to return to

the Quick Setup Screen.

2-5



Change Power StatusYou can also change the Power Status from the Quick Setup Screen. Highlight the blade that you want to changeand press <Enter>. The screen shown in Figure 2-6 appears, allowing you to select from the three options presented.

.Device Power State

========================================================

Select option to change the power state for this device:

Automatic

Reset

Off

Back

========================================================

Figure 2-6: Setting Power State Hardware Installed Table Screen (Main Menu Option 2)

The Hardware Installed Table screen displays a list of the currently installed hardware in the bh3710 along with the

status of each device. The complete set of hardware installed displays on four pages. An example of page one

appears in Figure 2-7.

2-6



Hardware Installed Table Page 1 of 2..==========================================================

Position Device Detected Status

Chassis 1 Small chassis OK More info...

Slot 1 Host processor blade OK More info...RTM slot 1 No RTM OK More info...

Slot 2 No blade OK More info...

RTM slot 2 No RTM OK More info...

Slot 3 FC storage blade OK More info...




Slot 5 FC storage blade OK More info...



RTM slot 6 No RTM OK More info...Slot 7 No blade OK More info...


<< < > >> Back

===========================================================

View information about this device

Figure 2-7: Hardware Installed Table Page 1

This page displays the contents of each blade slot as well as the main chassis and its associated status. To get more

detailed information on a particular device, use the <Tab> key to highlight (shown in gray) the, “More Info” for thatdevice and press <Enter>. Page 2 is similar in layout to Figure 2-7.

Hardware Installed Table NomenclatureThe Hardware Installed Table uses numerical listing for the slots and other components. There is a slot numbering

nomenclature used in the bh3710.

NOTE “Physical” slot numbering corresponds to the slot numbers printed on the bh3710chassis labels located beside the blade slots. They are referred to as “front” for slots facing the front of the bh3710 and “rear” for slots facing the rear of thebh3710.

Table2-1 defines how the slot numbers correspond to the Hardware Installed Table, physical hardware/chassis label

position, system nomenclature, and logical nomenclature.

2-7



Table 2-1: Hardware Installed Nomenclature

Physical

SlotLocation

BladeCompatibility

Hardware

Installed

Table SlotNumber System Slot Logical Slot










Front 10 Management Blade 10 Management Blade F10

Right Front Fan Tray Assembly Fan Control 1Rear 1 Reserved 1 RTM Slot 1 R1



Rear4 Reserved 4 RTM Slot 4 R4





Rear 9

Fibre Channel andManagement LAN

Blade 9 RTM Slot 9 R9

Rear 10

Fibre Channel and

Management LANBlade 10 RTM Slot 10 R10

Right-Hand Power Supply

(viewed from chassis front) PSU 1

Left-Hand Power Supply (viewedfrom chassis front) PSU 2

Selecting “More Info” for the Management Blade (for example) displays the screen shown in Figure 2-8.

2-8



Installed Device Information

==========================================================

Device status: OK

Position: Slot 10 FRU name: PB_SMC

Device detected: Management blade Firmware rev: D0Hotswap state: Available Manuf. date: 0400

Power state: Automatic Manufacturer: HP

Scan revision: 0000

Management LAN (Edit...) Part number: A6712-60001

Host name: pb-smc2 ID revision: a

IP address: 15.8.134.99 Serial number: 52SCJ3B13N

Subnet mask: 255.255.248.0

Gateway address: 15.8.128.1 MAC address: 00:30:6e:22:de:40



Location: -

Asset #: -

Contact info... Back

===========================================================

Device power state

Figure 2-8: "More Info..." Selected for the Management Blade

This screen displays detailed information about the Management Blade. Parameters that you may change can beaccessed by the <Tab> key. If a parameter cannot be changed, you will not be able to highlight it. In the Figure 2-8

example, pressing <Enter> allows you to change the Power State. Figure 2-6, shown earlier, illustrates the available

choices.

You must either set the Management LAN parameters in the Hardware Installed More Info menu, or by using the

Quick Setup Screen for each blade prior to going “live” with the system. The values shown in the screen capture areexamples only. You must assign your own LAN Configuration parameters.

NOTE If the LAN parameters are not set prior to setting the DB-9 on the front of theManagement Blade to function as a modem, you will not be able to Telnet into the

bh3710 system.

2-9



The screen shown in Figure 2-9 illustrates setting LAN parameters.

Edit Management LAN Parameters

===========================================================Position: Slot 10

Host name: pb-smc2

IP address: 15.8.134.99

Subnet mask: 255.255.248.0

Gateway address: 15.8.128.1



NOTE: Exiting this screen (using the 'Back' button or the ESCAPE key)

with changes to any of the network parameters will cause existing networkingconnections to be lost.

This will not reboot the management blade.

Restore Values Reset to factory defaults Back

=====================================================

enter=commit; esc=cancel; left,right,tab=move cursor; backspace,del=deletechar

Figure 2-9: Editing Gateway Address

When selecting a parameter, a selection menu appears at the bottom of the page, as shown in Figure 2-9. To cancel

with no changes, press <Esc>. Use the keyboard arrows to move to move the cursor to make an entry and type the

value. Backspace and Delete to delete a character. When satisfied with the entry, press <Enter> and the parameter will be changed immediately.

These functions work identically on each menu screen.

NOTE Selecting “Off” for Power State removes power from both the front and the back

slot. For example, selecting Power State “Off” for slot 4 turns power off to bothFront and Rear slot 4.

To return the LAN Configuration to the default state (shown in Figure 2-9) select the “Reset to factory defaults”menu item.

2-10





Setting the NTP Configuration

Figure 2-11 shows setting the NTP Configuration. Highlight the NTP parameter and press <Enter>.

Server Management Application===========================================================

OS version: 2.4.0-rmk1 Current time:04 Jan 2002 15:05:25

FPGA version: 9 MA version:hli011v

CPU usage: system 16.10% user 8.34% idle 75.54%

Memory usage: total 64528 kb used 62869 kb free 1658 kb

Host name: pb-smc NTP server: 15.8.133.217

IP address: 15.8.133.217 NTP status: No server

Modem location: No modemModem auto-answer: Off

Modem init string: at

Auto Self Tests Reset Modem

Versions Manual Self Tests Reset management blade Back

=========================================================

enter=commit; esc=cancel; left,right,tab=move cursor; backspace,del=deletechar

Figure 2-11: Setting the NTP Server Name

Notice the new selections available at the bottom of the screen.

2-12



Auto Self TestsSelecting “Auto Self Tests” from the SMA Configuration Page (Figure 2-10) causes the Management Blade toexecute its automatic tests and display the results. A typical self-test result screen is shown in Figure 2-12.

Management Blade Self-Tests Page 1 of 1

========================================================

Self Test Result Error code

EEPROM (basic) Passed

Ethernet Controller (basic) Passed

FLASH Memory (basic) Passed

FPGA (basic) Passed

I2C (basic) Passed

Lan Switch (basic) Passed

NVRAM (basic) PassedRTC (basic) Passed

SDRAM (basic)

<< < > >> Back

=========================================================

Return to SMA screen

Figure 2-12: Auto Self Tests Results

2-13









Chassis ConfigurationSelecting the first option, Chassis Configuration, displays a menu with the Chassis ID, Chassis Name, and ChassisSize. The Chassis Name can be modified, but the other two parameters are read-only. These parameters are

illustrated in Figure 2-18.

Chassis Configuration=========================================================

Chassis ID: 1

Chassis name: CNL_MML

Chassis size: 10 slots

Back

=========================================================

Chassis name

Figure 2-18: Chassis Configuration

2-17



Sensor ConfigurationSelecting option 2 displays the Sensor Configuration screen, shown in Figure 2-19. This screen allows you to set theinterval time between polling the listed sensors. Default values appear in Chapter 4, “Management Blade.”

Sensor Configuration

=========================================================

Polling intervals (in seconds)

Temperature: 10 Current: 10

Voltage: 10 Fan status: 10

Back

=========================================================

Polling interval (in seconds) for temperature measurements

Figure 2-19: Sensor Configuration Screen

2-18

http://s/1_%20powerbar/DATA/MS/Word/Documents%20and%20SettingskdlovDesktop%22%20l

http://s/1_%20powerbar/DATA/MS/Word/Documents%20and%20SettingskdlovDesktop%22%20l



Management Blade LEDS Option 3 on the Chassis Status and Configuration screen allows you to remotely display the condition of the LEDsvisible on the front of the Management Blade, shown in Figure 2-20. Values are defined in Chapter 4.

Management Blade Status LEDs Page 1 of 1

===========================================================

LED location LED status

Management blade status Off, steady

Management blade hotswap Off, steady

<< < > >> Back Return to ChassisStatus and Configuration Screen

Figure 2-20: Management Blade LEDs Page

Chassis LEDsOption 4 on the Chassis Status and Configuration page allows remote display of the chassis LEDs (those above each

blade) status. The first page of this screen is illustrated in Figure 2-21. Subsequent pages are not shown here,

because they are identical except for the parameters displayed.

Chassis Blade Status LEDs Page 1 of 1

===========================================================

LED Location Status indicationSlot 1 Blade running OK

Slot 2 Blade not running

Slot 3 Blade running OK






Slot 9 Blade running OK


<< < > >> Back

===========================================================

First page

Figure 2-21: Chassis LEDs Page

2-19



Chassis FansOption 5 displays the fan speed and status (fan speed is not the actual tachometer value, but the speed that theManagement Blade attempts to operate the fans). These values are read-only. This is shown in Figure 2-22.

Chassis Fan Status Page 1 of 1

==========================================================

Fan Current Speed Status

Fan 1 31 (100%) Running OK





Fan 6 31(100%) Running OK

………………………………………… Back

==========================================================

Return to Chassis Status and Configuration screen

Figure 2-22: Chassis Fan Status

Fibre Channel ConfigurationOption 6 shows the Fibre Channel Configuration.

Fibre Channel Configuration

=========================================================

No Status Model Vers Loop Mode

1 Available 7148 1.1 Single Slots... Ports...

2 Available 7148 1.1 Single Slots... Ports...

Back

==========================================================

Modify the RTM loop mode

Figure 2-23: Fibre Channel Configuration

2-20





Alarms and Events (Main Menu Option 5)

Option 5 on the Main Menu selects the Alarm and Event page. This screen displays the system event and alarm logs

and facilitates viewing with several sorting options. The screen is illustrated in Figure 2-25.

Alarms & Events

=============================================================================

1. System Event Log...

2. System Event Log (by device)...

3. Raised alarms...

4. SNMP trap destinations...

5. Save System Event Log...

6. Clear System Event Log entries..…

7. Event reporting options...

Back

===========================================================

Shows System Event Log

Figure 2-25: Alarms and Events

The screen in Figure 2-25 allows selection of viewing several alarm and event log pages. These screens are shown inthe following Figures.

2-22



System Event Log

System Event Log Page 1 of 34

==========================================================

Date and Time Alarm Type Obj State Record Type25 Jan 2002 19:56:26 Blade 9 mismatch 8 Raise SMA Event More info...

25 Jan 2002 19:56:06 No NTP server 0 Raise SMA Event More info...

25 Jan 2002 19:53:26 Blade 9 mismatch 8 Raise SMA Event More info...













<< < > >> Filter=All devices Update Back

=========================================================

View information about this event

Figure 2-26: System Event Log

The System Events Log (Figure 2-26) allows you to select which events to display by selecting the “Filter” item. As

shown, “All devices” provides no filtering.

2-23







Selecting “Show Events” and pressing <Enter> displays more information about the selected slot, as displayed in

Figure 2-29.


=============================================================================

==

Date and Time Alarm Type Obj State Record Type

25 Jan 2002 19:19:18 Blade 1 health crit 0 Clear SMA Event Moreinfo...

25 Jan 2002 19:19:18 Blade 1 health warn 0 Clear SMA Event Moreinfo...

25 Jan 2002 19:16:18 Blade 1 health crit 0 Raise SMA Event Moreinfo...

25 Jan 2002 19:16:18 Blade 1 health warn 0 Raise SMA Event Moreinfo...












<< < > >> Filter=Slot 1 Update

Back===============================================================================


Figure 2-29: Event Log By Device: Chassis (Slot #1)

2-26



Raised AlarmsFigure 2-30 shows the currently Raised Alarms.

Raised Alarms Page 1 of 1

============================================================================

Alarm Object Severity Category

No NTP server 0 Information S/W Alarm More info...

Blade 9 mismatch 8 Information H/W Alarm More info...

<< < > >> Blackout period...Back

============================================================================View information about this alarm

Figure 2-30: Raised Alarms

Selecting “More Info” displays complete details regarding that alarm event, as illustrated in Figure 2-31.

Alarm Information

============================================================================

Alarm: No NTP server

Object: 0

Type: 25

Severity: Information

Category: S/W Alarm

Parameter 1: n/a

Parameter 2: n/a

Blackout timer: 78

Back

============================================================================

Return to raised alarms table

Figure 2-31: Raised Alarms, More Info

2-27



SNMP Trap DestinationsYou can view and edit SNMP Traps using this selection from the Alarms and Events menu. The screen shown inFigure 2-323 will appear.

SNMP Managers Page 1 of 1

===============================================================================

No Address Version Status

1 15.8.129.156 snmpv2c Inactive Edit... Delete...

=

<< < > >> Create new entry...Back

===========================================================================

Edit manager details

Figure 2-32: SNMP Traps

Choosing the “Edit” function takes you to the screen shown in Figure 2-33 allows you to change the trap parameters.

SNMP Server Details

=========================================================================

Address: 15.8.129.156 Community: public

Version: snmpv2c Status: Inactive

Trap filters

SNMP traps: No

Information events: No

Warning events: No

Critical events: No

Activate De-activateBack

========================================================================

SNMP manager address

Figure 2-33: Editing SNMP Traps

2-28



Clear System Event Log EntriesSelecting this option clears all alarm events. All System Event Log data will be reset, shown in Figure 2-34.


=============================================================================

Date and Time Alarm Type Alarm Object Record Type

20 Dec 2001 07:07:13 SEL cleared 0 SMA Event More Info

<< < > >> Filter=All devicesBack

=============================================================================


Figure 2-34: System Event Log After Clearing Alarms

Save System Event LogChoosing this option permanently saves the current System Event Log for later viewing.

2-29



Voltages (Main Menu Option 6)

Option 6 from the Main Menu as shown in Figure 2-3, displays the voltage alarm and threshold page, shown in

Figure 2-35.

Voltage Logs Page 1 of

14===============================================================================

Device Type Unit Sensor Voltage Timestamp

Power Supply Unit 2 +12V 0.1V 25 Jan 2002 20:47:40






Power Supply Unit 2 +12V 0.1V 25 Jan 2002 20:36:10Power Supply Unit 2 +12V 0.0V 25 Jan 2002 20:36:00








<< < > >>

Back

==============================================================================

First page

Figure 2-35: Voltage Logs

2-30







Edit User Details

User Details

=============================================================== Name: danp

Level: USER

Password: ******

(repeat): ******

Alarms: Enabled

Pager configuration... Back

===============================================================

Edit the Pager Service Configuration

Figure 2-38: Edit User Details Screen

This screen allows you to set the user level, assign a password, enable alarms and configure paging.

NOTE Modem/paging functionality was not available as of this printing. Thisfunctionality is expected in the first half of 2002. Check www.software.hp.com (/blade-servers) for firmware update availability.

2-33

http://www.software.hp.com/




Pager Configuration

Pager Service Configuration

=============================================================================

Paging status: Disabled

Paging alert level: Warning

Pager service number: -

Pager ID: -

PPP dial back number: -

Back

=============================================================================

Enable/disable paging

Figure 2-39: Configure Pager Function

Use this function to enable/disable paging, set the alert level at which the user is paged, and set the user pager number and ID. You can also select the PPP dial back number. This feature allows a user to call the system on a

dial-up line, and then have the system return the call for PPP connection on the number you set in this line.

NOTE Modem/paging functionality was not available as of this printing. This

functionality is expected in the first half of 2002. Check www.software.hp.com (/blade-servers) for firmware update availability.

Create New User

Create New User

=============================================================================

[Enter name here]

Back

=============================================================================enter=commit; esc=cancel; left,right,tab=move cursor; backspace,del=deletechar

Figure 2-40: Create New Users Page

2-34





To create a new user, simply type the user name you wish to assign and press enter to accept. Use the other

navigation keys to alter your entry.

Configuration (Main Menu Option 9)

Selecting Option 9 on the Main Menu, Figure 2-3, allows you to view the system configuration, as illustrated in

Figure 2-41.

View/Modify Configuration

=============================================================================

1. Upload configuration...

2. Upload deferred configuration...

3. Activate deferred configuration...

4. Download configuration...

5. Configure SNMP access...

6. Device configuration...

Back

============================================================================

Device configuration

Figure 2-41: Configuration

The functions are shown below.

UploadConfiguration

By entering the full path and filename, a previously storedconfiguration can be uploaded and becomes immediatelyeffective.

Upload DeferredConfiguration

This option allows specification of the path and file name for a configuration file, but does not implement it until a later

time.

Activate Deferred

Configuration

This option activates any configuration file uploaded by

option 2.

DownloadConfiguration

This option allows downloading the current configuration toa file for later use.

Configure SNMP

Access

SNMP access to the bh7800 can be configured by selecting

this option.

Device

Configuration

View all device configurations. This screen is shown in

Figure 2-42.

2-35



Device ConfigurationSelecting option 6 shown in Figure 2-42 brings up the list of slots and their configuration, similar to the “Hardware

Installed” table. However, in this screen, you can manually change the device assigned to the selected slot, as shown

in Figure 2-43. Choosing “Learn Configuration” causes the Management Blade to determine the currentconfiguration by polling installed blades.

Hardware Configuration Table Page 1 of 2

===============================================================================

Position Device Detected Device Configured

Chassis 1 Small chassis Small chassis Changedevice...

Slot 1 Host processor blade Host processor blade Changedevice...

RTM slot 1 No RTM No RTM Changedevice...

Slot 2 No blade No blade Change

device...RTM slot 2 No RTM No RTM Changedevice...

Slot 3 FC storage blade FC storage blade Changedevice...


Slot 4 No blade No blade Changedevice...


Slot 5 FC storage blade FC storage blade Change

device...RTM slot 5 No RTM No RTM Changedevice...





<< < > >> Learn ConfigurationBack

=============================================================================

Change the device configured for this location

Figure 2-42: Device Configuration Table

2-36



Change Device

Configured Device Selection Page 1 of1

=============================================================================

=

Position: Slot 1

Device Selection

No blade Select

FC storage blade Select

Host processor blade Select

OEM blade Select

<< < > >> Back

================================================================================

Select this device for this location

Figure 2-43: Change Device Selection

Exit

When finished using the configuration function, return to the Main Menu shown in Figure 2-3, scroll to “Exit”, and

press <Enter>. This will exit the configuration function, save the configuration in NVRAM, and return to the

Management Blade login screen Figure 2- 2. Select “Exit” and “Logoff.” You may disconnect the cable from the

DB-9 on the Management Blade, or terminate your Telnet session at this time.

2-37



3 Power Supplies for the hp Carrier Grade BladeServer bh3710

Two n+1 -48VDC 400W Power Supply Units (PSU) are included with the chassis. Each PSU contains a converter module and a DC inlet module. The converter module, Figure 3-1, is installed/removed from the front of the chassis

and the DC inlet module, Figure 3-2 is installed/removed from the rear of the chassis.

Either converter module or DC inlet module can be removed one at a time without affecting performance however,one main converter module and its matching DC inlet module must be in place and operating normally or power to

the CompactPCI cards in the chassis will be lost.

Figure 3-1: PSU Converter Unit (Front View) Figure 3-2: PSU DC Inlet Module (Rear

View)

Green LED

Yellow LEDDB9 Connector

Shutdown ConditionsThe Power Supply will shut down under any of the following conditions:

• Output over-voltage

• Over temperature condition

When the supply shuts down, a yellow fault LED (shown in Figure 3-1 above) is lit and visible to the user.

SpecificationsPower supply specifications are located in Appendix B.

3-1



Removing and Replacing Power SuppliesThe bh3710 has dual power supplies. When operating normally, a green LED will glow constantly. If a power

supply fails, it will be indicated by a solid yellow LED. If this condition is detected or if it is detected through

remote monitoring, the power supply should be replaced as soon as possible.

CAUTION The DB9 connector (located on each DC inlet module) on the rear of thechassis was installed for use during the manufacturing process. It cannotbe used for anything else. If an RS232-type plug is used in this receptacle,it could cause the power supply to reset, thereby losing data beingtransmitted to the blades.DO NOT TRY TO USE THIS RECEPTACLE FOR ANY PURPOSE.

The DB9 connector is shown in Figure 3-2 above.

Because of the high velocity, positive pressure airflow, the mechanical integrity of the system must be maintained atall times to ensure proper cooling.

To ensure power supply replacement within the requisite time window, plan the installation in advance:

• Ensure you are properly grounded before commencing

• Have the replacement power supply ready for installation and near the bh3710

• Have the required tools handy

• Familiarize yourself with the operation before you begin

Required Tools:

• Number 1 Philips screwdriver

• Flat Blade screwdriver

•

Power Supply Removal

1. Remove the new converter module and DC inlet module from the protective packaging, and place on an

antistatic surface.

2. Unplug the DC power cable from the DC inlet module at the rear of the chassis.

3. Loosen and remove the four screws on the DC inlet module located on the rear of the chassis. Pull the inlet

module out of the chassis.

4. Loosen the captive screw on the converter module located at the front of the chassis. Pull the converter module

out of the chassis.

3-2



Power Supply Replacement

Slide the converter module into the chassis and tighten the captive screw to secure the converter module in place.

Figure 3-3: Inserting Converter Module into Chassis

Slide the inlet module into the chassis and secure in place using the four non-captive screws.

Figure 3-4: Inserting Inlet Module into Chassis

Plug the DC power cable in to the DC inlet module at the rear of the chassis.

Look at the power supply LED at the front of the chassis and verify that a solid green LED is illuminated

3-3



4 Management Blade

Management Blade Introduction

The Management Blade and its attendant firmware, the Server Management Application (SMA), is responsible for all management, housekeeping, and security aspects of the bh3710. The Management Blade is illustrated in

Figure 4-1. The Management Blade incorporates HP-UX, under which the SMA runs.

DB-9 Serial

Connector Status

LAN LEDs

Hot Swap LED

Figure 4-1: Management Blade

Management Blade LED Legend

LED Type Quantity Color Usage

Hot Swap LED 1 Blue Management Blade hot swap status

Status LEDs 1 Yellow SMA operating status

RTM LAN connections 3x2 Yellow/Green/ Green Link and speed status of the external Management LAN

4-1



The Management Blade has five basic functions. These functions are defined in Table 4-1.

Table 4-1: Management Blade Functions

Function Description

HardwareHousekeeping Monitors health, logs blade parameters, controls fanspeed, shuts down faulty blades, drives status LEDs on

chassis.

Hot Swap Monitor Monitors the hot swap signals from each hot swap

component and controls shutdown process.

User Interface to

bh7310

Communicates with users via RS-232 console program

and Telnet console.

Remote Firmware

Update

Handles logic to acquire and update the Management

Blade firmware.

Console Management

LAN Switch

Has integrated switch that provides 10/100 base-T access

to all other blades.

GlossaryTerms used in this chapter are defined in the following glossary.

Table 4-2: Glossary

Term Definition

Alarm Event

The generic term used to indicate an alarm or event raised by the SMA. This covers

both alarms in the traditional sense and also information.

AEM

Alarm Event Manager. The host processor blades connect to a LAN network via theManagement Blade. This allows them to be managed from a central location. On this

network, a computer runs the AEM. The Server Management Application sends anyalarm and event messages to this manager.

CM

Configuration Manager. This is a processor, remote from the management platform,

responsible for downloading/uploading configuration information to/from the SMA.

CompactPCI

Download

Compact Peripheral Component Interconnect Download. This term is used to describe

the process of a transfer of configuration data to a given entity, from an external entity.

See “Upload”. Also known as cPCI.

Configuration

Menu

Allows the technician to view status information and configure the system. It may be

accessed locally via the serial port, or remotely over the Management LAN.

EEPROM

Electrically Erasable Programmable ROM. This type of non-volatile storage is used onvarious devices that may be attached to the bh7800 chassis, including the Management

Blade.

FLASH

A type of constantly powered non-volatile memory that can be erased and

reprogrammed in units of memory called blocks. The Management Blade does not

have any magnetic disc storage, thus software and downloaded configuration

information is stored in FLASH.

4-2



Term Definition

FC and LAN

RTM

Fibre Channel and Local Area Network Rear Transition Module. The term

“Management LAN Blade” refers to either of the two FC and LAN RTM blades

associated with the Management Blade.

IPMBIntelligent Platform Management Bus. A protocol defining a byte-level transport for transferring IPMI messages between intelligent I2C devices.

IPMI

Intelligent Platform Management Interface. A standard defining an abstracted interface

to platform management hardware.

Management

Blade

Server Management Blade. A cPCI blade that provides a hardware platform for the

SMA firmware, and the hardware interfaces required between the SMA firmware, and

other hardware external to the Management Blade.

Management

LAN

The SMA connects to a LAN that sends status information and receives downloadconfiguration information. This information pertains to the management of the

monitoring system, as distinct from the monitored LAN.

NVRAM Non-Volatile RAM

SEL System Event Log. A buffer of all events recorded by the SMA.

SMA

Server Management Application. The firmware, as defined in this document, that runs

on the Management Blade.

SNMPSimple Network Management Protocol. The SMA uses an SNMP agent to

communicate with the AEM and the CM.

TCP Telecom Computer Platform.

Upload The process of a transfer of configuration data from a given entity to an external entity.

External InterfacesThe Management Blade electrically connects to the other components through the backplane. In most cases the

interface is via I2C bus. These busses allow bi-directional communication so that status information can be sent to

the SMA and configuration information sent from the SMA.

Operating Phases

The SMA has three distinct phases of operation. These phases are:

• Start-up — Entered on power-up or reset and controls the sequence needed to make the SMAoperational. The SMA also provides the minimal configuration information to allow the chassis to

communicate on the Management LAN.

4-3

• Normal Operation — Entered after the Start-up mode is completed. This mode monitors all other devices and logs events internally. Normally the SMA has full communication with the Alarm Event



Manager; but, when the Management LAN is not available, the SMA loses the ability to report errors

to the management system.

• Hot Swap — Entered when there is an attempt to remove the blade from the chassis. An advancewarning of the power fail is available to allow the software to shutdown gracefully.

The operation in each of these phases is defined in detail in the following sections.

Key FunctionsDuring normal operation, the SMA firmware has the following main functions.

MonitoringWhen the SMA is operating in the Normal or Stand Alone Modes it continuously monitors the health of the chassis

and its components. The SMA typically monitors:

• Chassis Environment (e.g. temperature, fans, input signals)

• Removal and Insertion of other blades

• Operational state of the other FRUs

Configuration Commands

During normal operation, the SMA accepts and performs configuration commands. These commands are used toconfigure the chassis for desired operations.

Commands can originate from the blade-front serial connection or from a Telnet connection to the Management

LAN.

Alarms and EventsThe SMA reports alarm events to an onboard Alarm Event Manager. The Alarm Event Manager determines what to

do with the alarm or event and instigates any recovery or reconfiguration that may be needed. There may be some

exception handling taken by the SMA in case of critical temperature conditions.

Normally all known alarm events are reported. However, a blackout mechanism is employed to avoid flooding theAlarm Event Manager or the system event log.

A System Event Log (SEL) keeps a record of the alarms and events. This is held in non-volatile memory and ismaintained over power cycles, and resets of the SMA. The SEL contents can be viewed using the Configuration

Menu described in Chapter 2.

4-4



Table 4-3: Alarm Table

Alarm Text Severity Type Maskable

Check mgt LANs Critical Transitional Yes

Blade xx health critical Critical Transitional Yes

No LAN to blade xx Critical Transitional Yes No link to blade xx Critical Transitional Yes

Blade xx temp critical Critical Transitional Yes

Chassis mismatch Warning Transitional Yes

SMC battery low Warning Transitional Yes

PSU xx not as configured Warning Transitional Yes

Blade xx health warn Warning Transitional Yes

Blade xx can't poll Warning Transitional Yes

Chassis temp alarm Warning Transitional Yes

PSU xx temp alarm Warning Transitional Yes

Blade xx temp alarm Warning Transitional Yes

PSU xx 5V current alarm Warning Transitional Yes

PSU xx 3.3V current alarm Warning Transitional Yes

Device xx no EEPROM Warning One-shot YesRTC mismatch to TOD Information Transitional Yes

No NTP server Information Transitional Yes

Modem not detected Information Transitional Yes

Blade xx unknown Information Transitional Yes

Blade xx mismatch Information Transitional Yes

Application running Information One-shot Yes

RTM port configuration Information One-shot Yes

Using last configuration Information One-shot Yes

Using default configuration Information One-shot Yes

Modem incoming call Information One-shot Yes

Blade xx powered down Information One-shot Yes

Blade xx powered up Information One-shot Yes

Blade xx reset Information One-shot YesBlade xx inserted Information One-shot Yes

Blade xx removed Information One-shot Yes

Blade xx voltage Information One-shot Yes

Blade xx event message Information One-shot Yes

IPMI event message Information One-shot Yes

User logged in Information One-shot Yes

User logged out Information One-shot Yes

SwitchThe Management Blade incorporates a 10-port unmanaged LAN switch that connects to one or two (for redundancy)Management LAN blades. All the Server Blades’ management circuitry is connected via the backplane to the

Management Blade switch.

User ConnectivityA user may interact with the SMA through a number of different interfaces. These are:

• A console directly attached to the RS-232 port,

4-5





Communicating with the Management Blade

Complete configuration menu screen captures appear in Chapter 2.

Command Line User Interface (CLUI)

The Management Blade supports a set of CLUI commands. While programming a single system is much easier

using the Configuration Menu CLUI, writing a script of CLUI commands and then executing them on each blade

server can facilitate programming a group of bh3710 blade servers. There are several thousand parameters in a

complete list of CLUI commands that can be displayed by typing:

smc-cmd –w

smc-cmd –e <string>

Commands are entered by typing the command at the CLI prompt.The following command allows you to set a parameter of a command:

smc-cmd –s <param> <value>

smc-cmd –g <param>

In addition to the smc-cmd command, two other user commands are also available:

smc-ethcfg is used to configure management LAN parameters

smc-flash is used to update onboard management firmware.

Communication with, and configuration of, the Management Blade and the other devices in the system take place

via a Command Line Interface, or the configuration menu.

You can search for commands by specifying part of the command name. This is a much better way to list commands

than to list the entire set using the above command. The following returns a list of all commands that start with the

specified string:

You can get the setting of a parameter with the following syntax:

Configuration Menu CLUI

The Configuration Menu provides an operator interface to the SMA. This allows you to query the status of thechassis and (with the required authority level) change the configuration of the chassis.

There are three levels of authority:

• User: the user level of authority can only use commands that display information.

• Operator: the operator level of authority can use all commands except those with the highest security

level.

• Super User: the super-user level of authority can use all commands.

Configuration Upload / DownloadThe Configuration Menu allows a connected user to transfer configuration information between the SMA andanother location, whether uploading or downloading.

When a configuration upload or download is requested by a Super User or Operator, the terminal displays a prompt

for the name of the configuration file to transfer. The file can be stored and retrieved, even remotely.

4-7



Visible InformationThe Configuration Menu provides the user with access to the following information:

• Alarm Event Log

• Current state of any alarm event (without any blackouts)

• All the temperature logs

• All the voltage logs

• Chassis Hardware Installed Table

• The current setting of all configurable parameters

The Configuration Menu supports the following operations. The configuration menu will not allow users to access

operations that are only available to higher lever users.

Configuration Menu information is located in the Configuration Menu Command Line Interface Specificationssection in Appendix A, Specifications for the hp Carrier Grade Blade Server bh3710.

User Initiated Self Test

You can run Self Tests at any time during the normal operation of the SMA application. The tests themselves are

accessed through the “Manual Self Test” menu item from the Configuration Menu interface. Table 4-4 summarizesthe self-tests.

These tests are executed through use of an operator level command.

Table 4-4: User Initiated Self-Tests

Test Description

RTC (extended) Performs the extended Real Time Clock test.

Temperature Sensor (basic)Performs the basic Management Blade temperaturesensor test.

Fan Control (basic) Performs the basic fan control test.

I2C bus (basic) Performs the basic I2C controller test.

Serial Port (basic) Performs the basic serial port controller test.

In “Manual Self Tests”, each test can be run individually. You can also run all tests automatically by selecting the

“Auto Self Tests” menu item. These menu screens appear in Chapter 2.

4-8



Alarms and ConfigurationThis section lists the set of alarm events that are generated by the SMA. Note that all alarms are logged in the

System Event Log (SEL). Errors that are encountered may cause the SMA and chassis LEDs to change state. They

may also cause messages to be displayed on the console. These messages are shown in Table 4-5. All alarms shownin the table below are maskable.

Table 4-5: Alarms

Alarm Text Severity

Critical Alarms

Check mgnt LANs Critical

Blade xx health crit Critical

No LAN to blade xx Critical

No link to blade xx Critical

Blade xx temp crit Critical

Warnings

Chassis mismatch Warning

SMC battery low Warning

PSU xx not as config Warning

Blade xx health warn Warning

Blade xx can't poll Warning

Chassis temp alarm Warning

PSU xx temp alarm Warning

Blade xx temp alarm Warning

PSU xx 5V curr alarm Warning

PSU xx 3.3V curr alrm Warning

Devc xx no EEPROM Warning

Information

RTC mismatch to TOD Information

No NTP server Information

Modem not detected Information

Blade xx unknown Information

4-9



Blade xx mismatch Information

Appn running Information

RTM port config Information

Using last config Information

Using default config Information

Modem incoming call Information

Blade xx powered dwn Information

Blade xx powered up Information

Blade xx reset Information

Blade xx inserted Information

Blade xx removed Information

Blade xx voltage Information

Blade xx event msg Information

IPMI event msg Information

User logged in Information

User logged out Information

Operating system boot errors, other than a critical stop error, are reported by the kernel to the console serial port and

are not reported on the Management Blade LEDs or to the system event log. Kernel boot errors must therefore bedetected using a console connected to the serial port.

Non-Volatile Configuration ParametersThis section lists all the configuration parameters. These tables are all held in non-volatile memory. They may bechanged by the user or may be updated via the Management LAN.

Parameter Types

Configuration parameters can be configured dynamically by applications or the Configuration Menu:

SMA and General Chassis Configuration Parameters

These configuration parameters are specific to the Management Blade and to the chassis in general. Table 4-6 is a

list of implemented configuration parameters.

Table 4-6: Chassis Configuration Parameters

Configuration Parameter When Applied

Default

Value

Min

Value

Max

Value

4-10









Management Blade On-Board BatteryThe SMA periodically monitors the status of the backup battery on-board the Management Blade.

The battery management device on the Management Blade provides a single status bit that indicates whether or not

the battery power is sufficient. On detecting that the battery is low, the SMA raises the alarm.

Blades InstalledBlade Present Detection

The SMA uses the “blade present” signal to detect if a blade is present or not in any given slot.

The SMA maintains a record of all the blades installed in the chassis along with their type, hardware revision and

serial number. This is stored in the Hardware Installed table, which can be viewed using the configuration menu.

Blade TypesThe SMA can determine the types of blades installed in the chassis. Each of these blades has an EEPROM. If a

blade is present in a slot and fails to respond to an I2C poll to that EEPROM then an alarm event is reported.

These blades are:

• bp2200 Server Blades

• Management LAN Blade (RTM)

• FC Storage Blades

New Blade DetectedWhen a new blade is detected, the SMA creates an alarm event.

When a new blade has been detected the SMA polls the identification EEPROM on that blade. Once the EEPROM

is successfully read, the information in the Hardware Installed table is updated.

Blade RemovalThe SMA detects blade removal by monitoring the “blade healthy” signal for each blade. When the SMA detects

that a blade has been removed, the alarm event is generated, and the Hardware Installed table is updated.

Blade Operating StatusThe SMA monitors the operating state of the Host Processor Blades. The SMA periodically posts an IPMI query to

each of the blades to ensure that they are operational. If the query fails then an alarm event is reported.

In addition, the SMA receives IPMI event messages autonomously generated by the Host Processor Blades.

Host Processor - PingThe SMA periodically uses the ping command to verify the communication path to each of the Server Blades. If

the ping to one of the Server Blades fails, an alarm event is raised.

The SMA uses the IP address defined in the configuration to address each of the Host Processor Blades.

Checking TimeThe SMA confirms that the UTC time returned by the Host Processor is within a suitable window of the UTC time

that it contains. If the time returned by the Host Processor is outside this window then an alarm event is raised.

This check is not performed when the SMA is operating from a default time.

NOTE The UTC is now optional. Local time can be used.

4-14





Dial InIf there is a modem attached to the modem port specified in the downloaded configuration, the SMA configuration

indicates whether it is to be initialized to permit a user to dial-in, or whether auto-answer should be disabled. If

enabled, the application detects any incoming call to the modem and enables a PPP session via the modem. If the

caller is confirmed as one of the configured users then the SMA will hang up the connection, dial out to a number

configured for that user and start a PPP session. The user may then connect a Telnet session to the SMA or to any

other connected Host Processor.

Dial OutIf there is a modem attached to the configured modem port, then this may be used to dial out to generate pager

events under certain circumstances.

Error ReportingAll alarms and status changes are reported via alarm events. When any part of the software needs to report a change

of status, it is done with this common procedure. Under certain alarm conditions (as defined by the configuration

parameters for a specific pager user), the paging service will be invoked.

Alarm Event Generation

State ChangesTwo types of alarms may be raised by the SMA:

• “One-shot alarms” to indicate a one-off event (i.e. maintains no state).

• “Transition alarms” that occur when a change of state occurs (i.e. set when an alarm goes active andcleared when rectified).

“Transition alarms” are raised when a change of status occurs (i.e. for both an alarm going active and for it going

clear).

DestinationAlarm events may be reported to any combination of the following destinations:

• The internal event log

• The Host Processor Blades

• The Management Blade front panel LEDs

• The chassis LEDs

• The Alarm Event Manager

• A logged in user (Telnet, RS-232 console)

• A registered pager user

4-16









Chassis Slot ResetThe SMA can be instructed to reset a blade in any one of the chassis slots, and each is controlled independently.

The reset signal is applied for a duration of at least 100 milliseconds.

Temperature Threshold ControlThe Alarm and Critical temperature thresholds may be set for the chassis temperature sensor, the Management Blade

temperature sensor, and the PSU temperature sensor.

RS-232 Port ControlThe RS-232 ports are initialized at power up to operate in the configured state for RS-232 port initialization. The

default configuration is for eight data bits, no parity and one stop bit.

The SMA does not provide any commands to specifically control the serial ports. If required, the parameters may be

changed under software control using the existing operating system commands.

Modem Control

NOTE Modem/paging functionality was not available as of this printing. Thisfunctionality is expected in the first half of 2002. Check www.software.hp.com for

firmware update availability.

If there is a modem attached at power-up, and the downloaded configuration indicates a modem should be presenton that port, then it will be initialized. This will be according to the modem initialization parameter in the

downloaded configuration.

The pin out for the male 9-pin D-shell connector is defined in Figure 4-3.

Figure 4-3 Management Blade 9-Pin, D-Shell Pinout

Pinout Legend

Pin Number Signal Description

1 DCD Data Carrier Detect

2 Rx Receive

3 Tx Transmit

4 DTR Data Terminal Ready

5 GND Ground

6 DSR Data Set Ready

7 RTS Request To Send

8 CTS Clear To Send

9 RI Ring Indicator

4-20





Operator Indicators

The Management Blade has eight LEDs that are used to inform the operator of the operating status of theManagement Blade. The SMA also controls the LEDs located near the chassis fans that are used to inform the

operator of fan operating status. The usage of these LEDs is summarized in Table4-9.

Table4-9: LED Indicators

LED Type Quantity Color Usage

Hot Swap LED 1 Blue Management Blade hot swap status

Status LEDs 1 Yellow SMA operating status

RTM LANconnections 3x2 Yellow/Green/ Green

Link and speed status of the externalManagement LAN

In addition, the chassis has an LED strip, with two colored LEDs for each slot in the chassis. This is arranged so that

each LED pair is positioned above the corresponding chassis slot.

Management Blade Hot Swap LEDThe Hot Swap LED is off during normal operation. The LED indicates a steady blue during the Hot Swap

procedure.

Status LEDThe status LED, when illuminated, indicates a fault in the Management Blade.

Management LAN LEDsTwo rows of three LEDs indicates a LAN link and the speed (10/100 baseT) of the two possible Management LANBlade connections, as labeled on the front of the Management Blade.

Chassis LEDsThese LEDs are located on the Fan Tray Assembly bulkhead, on the right side of the server front, and are arrangedvertically so that there is a green (left) and an amber (right) LED beside each chassis slot. They are arranged

horizontally in pairs to avoid any color distinction issues. One LED may be on at a time, either flashing or steady, or

both may be off. Both will not be continuously on at the same time.

Table4-10: Chassis LED Definitions

Green LED Amber LED Blade Status

OFF OFF Blade off or not present

ON OFF Blade running without errors

Flash OFF Blade running, needs user input.

OFF Flash Blade error, needs user input.

OFF ON Blade selected by Management Blade for configuration

4-21



Resetting the Management Blade Password

If the password should ever be forgotten or compromised, it can be reset to “hpblade!” with an onboard jumper. Toreset the password, follow this procedure:

1. Ground yourself by connecting to the ground connector near the bottom left of the front of the bh7800.

2. Remove the Management Blade from the bh3710 using hot swap techniques. (This procedure begins

on the following page)

3. Locate jumper P6. Looking at the component side of the blade with the bulkhead to the left it is about

one inch to the right of the backup battery near the bottom of the blade.

4. Place a jumper on P6. Wait at least 10 seconds.

5. Remove the jumper.

6. Reinstall the Management Blade.

The password will now be reset.

4-22





Management Blade Removal

CAUTION You must complete removal and replacement within 3 minutes to complywith cooling requirements. Failure to do so will result in the systemshutting down.

1. Begin by releasing the button-release lever on the blade. Do this by pressing the red release button on therelease lever. It will release with a “snap”, but only travel about 1/8 of an inch. Do NOT attempt to remove

the blade at this point, as it must be allowed to power down. Figure 4-5 illustrates this step. The blade will

now enter its hot-swap shutdown routine. Blades cannot be removed until they have completed this function,signified by illumination of the blue hot-swap LED.

Figure 4-5: Releasing the Locking Lever

2. While waiting for the blade to shut down, loosen the screws located in the top locking lever and bottom

locking lever. Do NOT attempt to remove the blade at this time.

4-24





Management Blade Installation

1. Pick up the replacement blade from an antistatic surface using the two locking levers.

2. Holding the Management Blade using the locking levers, align it with the blade guides inside the open slot

and carefully push the blade fully into the chassis as shown in Figure 4-8.

Figure 4-8: Align Blade With Blade Guides And Push Into Chassis

1. 3. Ensure that the “hooks” on the locking levers engage the blade retaining pins at the top and bottom of

the blade slot.

2. 4. Once the “hooks” are engaged with the pins on the chassis, grasp the two locking levers and

simultaneously push them toward each other to securely seat the blade in the connector on the backplane,as shown in the figure. It may take additional force to pull the board into final seating, because it must mate

with several connectors on the backplane. Figure 4-9 illustrates the “hooks” engaging the blade retaining

pins and the direction of force needed to close the locking levers.

Figure 4-9: Insert the Blade

4-26



3. 5. Use a screwdriver to tighten the small screws in each locking lever (as shown in the Figure 4-9). Thiscompletes the replacement of a blade

Figure 4-10: Tighten the Locking Screws

4. 6. Attach any previously-removed cables to the blade.

5. 7. Verify that the operating system boots.

4-27



5 Fibre Channel (FC) and LAN Rear TransitionModule (RTM) Blade for the hp Carrier GradeBlade Server bh3710

FC and LAN RTM Blade Introduction

The FC and LAN RTM blade provides communication between the bh3710 Management Blade, other server bladesand peripherals.

The FC and LAN RTM blade supplies the following ports:

• Two LAN ports for server blades

• One LAN port for the Management Blade and MP

• One serial port for the Management Blade

• One Fibre Channel port bypass port

Figure 5-1: FC and LAN RTM Blade

Removing and Installing the Fibre Channel (FC) and LAN RTMBladeFC and LAN RTM Blades provide an external LAN connection for the Management Blade. There are a maximum

of two FC and LAN RTM blades in the Blade Server. The two FC and LAN RTM Blades provide redundant

operation capability, if required. The FC and LAN RTM Blade does not have top and bottom locking levers, buthandles are attached to them.

NOTE If two FC and LAN RTM blades are installed in the bh3710, do not attempt toconnect both of them to the same LAN segment. This will make both bladesunavailable.

5-1



FC and LAN RTM Slot Blockers

Figure 5-2: Rear Slot Blocker

If you remove an FC and LAN RTM blade and cannot replace it within the three minute time limitation, install arear slot blocker to maintain system cooling integrity. Insert a rear slot blocker in the open slot and tighten the

screws on the sides.

Figure 5-3: Insert Rear Slot Blocker

5-2



Removing FC and LAN RTM Blades

WARNING You must complete removal and replacement within 3 minutes tocomply with cooling requirements.

Captive Screw

Captive Screw

Figure 5-4: FC and LAN RTM Blade Captive Screw Location

To remove either top or bottom Blade, complete the following steps:

1. Observe all standard safety and ESD precautions and connect ground to the ground lug on the front of thechassis.

2. Label and remove the cable connected to the selected FC and LAN RTM Blade.

3. Loosen the captive screws located at the sides of the selected blade. See Figure 5-4.

4. Grasp the handles of the selected FC and LAN RTM Blade and pull it from the chassis.

5. Place the FC and LAN RTM Blade on an anti-static surface.

Installing FC and LAN RTM BladesTo replace an FC and LAN RTM Blade, complete the following steps:

1. Grasp the selected FC and LAN RTM Blade and align it with the top and bottom blade guides in the

carrier.

2. Push the blade into the chassis until it seats with the backplane.

3. Tighten the captive screws located at the sides of the blade.

4. Reconnect the LAN cable to the blade.

5. Verify that the LAN connectivity is restored.

NOTE If two FC and LAN RTM blades are installed in the bh3710, do not attempt toconnect both of them to the same LAN segment. This will cause that segment tobecome unavailable to all.

5-3





PCI Mezzanine Card

The Mezzanine Core IO contains the console LAN, two payload LANs, two Fibre Channel controllers, the

Management Processor and the local-Blade power management circuitry.

The Core I/O can be split into four sections: the primary I/O section, the secondary I/O section, the hot swap

controller, and the 1.60V DC/DC Converter.

The devices in the primary I/O section share a single 66MHz, 64-bit, 3.3V PCI bus, which is driven from one dual-roped Elroy (Elroy 0.) The Primary Core I/O devices consist of a 10/100 Base-T LAN (Intel 21143 MAC), and a

1Gbit FC interface (Agilent Tachyon-TL controller.)

The devices on the secondary I/O section share a single 33MHz, 64-bit, 3.3V PCI bus, which is driven from a

second dual-roped PCI Controller. The secondary core I/O devices consist of a 10/100 Base-T LAN (Intel 21143

MAC), and a 1Gbit FC interface (Agilent Tachyon-TL controller) and the Management Processor (MP). It must benoted the performance of this bus is degraded by the MP processor (SP2.0), which runs at 33Mhz, otherwise the bus

would run at 66MHz.

Both PCI busses are local to the board, and there is no way to attach any external IO cards into the bus. While the

PCI busses are 64-bits wide, the only 64-bit devices on the bus are the PCI Controller and the FC controller – Tachyon TL. When any other device communicates on the bus, it uses only 32 bits.

Storage Device

The bp2200 blade does not include on board disk storage. Disk storage is provided via the FC Storage Blade. Refer

to Chapter 8 “Mass Storage Installation for the hp Carrier Grade Blade Server bh3710”

Hot Swap Support

The dual PA-8600 processor module is designed to allow hot insertion or removal without damage to either the

removed assembly or other components. The LAN/Management provides the ability to power off the assembly inthe event of overheating or for reset purposes.

A blue LED, located on the blade bulkhead, is illuminated when the board can be extracted. This LED indicates that

system software is ready to allow extraction of the board. The hardware connection layer provides protection onlyfor the hardware during insertions and extractions.

Upon insertion, the LED is illuminated automatically by the hardware until the hardware connection processcompletes. The LED then remains OFF until used by software to indicate that extraction is once again permitted.

Management Processor (MP)

The MP provides both a firmware and OS visible console device as well as a secondary seat of control for out-of-

band communication and control to the platform hardware, independent of the operational state of the primarycomputing resources. The software is a VxWorks RTOS application running on an ARM processor with integrated

I/O devices.

6-5



bp2200 Configuration

Memory Installation

Use the bulkhead as a reference point when installing the DIMMs in the sockets. Slot 1 is located closest to the bulkhead, slot 2 next, then slot 3 and finally slot 4. See Figure 6-2 for slot number locations and DIMM loading

order. When installing memory DIMMs, the first DIMM is installed in slot 1 which is the slot closest to the bulkhead. The second DIMM is installed in slot 3. The third DIMM is installed in slot 4. The fourth DIMM is

installed in slot 2. The slot numbers are also labeled on the processor board.

Bulkhead Side of Blade

Slot 2

Slot 3

3rd DIMM

2nd DIMM

4th DIMM

1st DIMM

Slot 4

Slot 1

Load Order

Figure 6-2: Memory DIMM Order of Installation

Bulkhead Side

Figure 6-3: bp2200 DIMM Installation

6-6





Figure 6-5: bh3710 Chassis (Rear View)

Boot to BCHThe blade will boot to BCH upon insertion in the chassis. Every time the blade is powered on, it will boot to BCH

automatically. If the power has not been cycled, a reset may be issued from the MP prompt with the “rs” command.

After responding with a “yes”, the MP will proceed to reset the processor board and start the booting process to theMP.

Boot to HP-UXAn installed disk with properly installed operating system is required for this operation. Verify your boot path with

the “pa pri” command. If the path is correct, issue the “bo” command. Chose not to interact with IPL.

6-8



bp2200 LED DescriptionsThe bp2200 server blade provides LEDs on the blade bulkhead for determining the state of the server blade. These

LEDs are the green Run LED, the yellow Attn/Fault LED, and the blue Hotswap LED. The combination of these

LEDs indicate the state of the bp2200 server blade and are listed below:

NOTE Some LED combinations are not valid. If a LED combination is not shown in thetable below, it is not valid and should not be displayed on the bp2200 server blade.

Table 6-1: bp2200 LED Combinations

GREEN

Run

LED

YELLOW

Attn/

Fault

LED

BLUE

Hotswap

LED Description

Off Off Off Main Power ON, but system is not fetching code

On Off Off System normal operation. OS running.

Flash Off Off System running (non-OS code).

Off Off On Main Power OFF.

Flash Off On Main Power OFF.

Off Flash On Main Power OFF.

Flash Flash On Main Power OFF.

On Flash Off OS not running. Non-critical operator intervention needed. Check console logs.

On Flash Off OS is running. Non-critical operator intervention needed. Check console logs.

Flash Flash Off

OS coming up (non OS code). Non-critical operator intervention needed.

Check console logs.

Off On On Fault occurred that caused 1.55V rail to shut off.

On On On MP is in reset state or hung.

Off On Off A fault has occurred. OS NOT running.

Flash On Off System has crashed and is rebooting.

6-9



Removing and Installing the bp2200 Server Blade

Cooling System Constraints

Before discussing blade installation, it is important to understand the cooling system constraints within the contextof a live system. The bh3710 uses a closed, pressurized cooling system. The CompactPCI® cards in the main

chamber are cooled by 6 fans mounted on a tray which slides in and out allowing easy access to the fans for replacement. Each PSU is cooled independently by its own set of 4 fans. All CompactPCI® Cards, Fan Tray and

PSU's are hot swappable.

Figure 6-6: Cooling System Operation

Because of the high velocity, positive pressure airflow, the mechanical integrity of the system must be maintained atall times to ensure proper cooling.

• Blade installation must be completed within three minutes to ensure air flow maintenance.

• If the three minute installation time limit cannot be met, slot blockers must be installed in empty slotsto ensure proper airflow

Any deviation from these requirements may result in the Management Blade either shutting down other blades, or

the entire system, due to an over-temperature condition inside the chassis.

6-10



bp2200 Server Blade Removal

CAUTION You must complete removal and replacement within 3 minutes to complywith cooling requirements. Failure to do so will result in the systemshutting down.

The best way to ensure blade replacement within the required time window is to plan your replacement in advance:• Ensure that you are properly grounded before commencing and connect to the ground lug on the front

of the chassis.

• Have the replacement blade ready for replacement and near the server.

• If removing a blade without replacement, have a slot blocker ready.

• Have the required tools available.

• Familiarize yourself with the operation before you begin.

WARNING Make sure that the rack is anchored securely before removing any componentsfrom the Blade Server. Failure to do so may cause serious injury or damage to

the Blade Server.

Required ToolsA number 1 Philips screwdriver is required to successfully remove and replace the bp2200 Server Blade.

Figure 6-7: Releasing Locking Levers

1. Slide a thumb or forefinger under the front lip of the red tabs, located on the inside of both left and rightlocking levers and gently pulling out. This action begins the blade shut-down procedure. Figure 6-7

illustrates the location of the red tabs.

6-11



The blade will now enter its hot-swap shutdown routine. Do NOT attempt to remove the blade at this time or

data may be lost . When the blade is completely shut down, a blue LED on the right side of the blade bulkhead

will illuminate to indicate that the blade is ready to be removed. It can take up to two minutes for the blue LED

to illuminate.

NOTE The blue LED will remain illuminated until power is removed by loosening the

blade from the backplane

17. 2. While waiting for the blue LED to illuminate, loosen the screws located in the left locking lever and

right locking levers as shown in Figure 6-8. Do NOT attempt to remove the blade at this time.

Figure 6-8: Loosen Locking Screws

18. 3. To release the blade from the backplane, apply pressure to the left locking lever and to the right

locking lever at the same time. You should be able to “snap” the levers away from each other. Figure 6-9

illustrates this step.

Figure 6-9: Releasing Locking Levers

19. 4. After the blue LED illuminates, grasp the two locking levers and push them toward the center to

unlatch the two integral “hooks” from the chassis.

6-12



20. 5. Still grasping the locking levers, firmly pull the blade from the chassis (Figure 6-10). The blades fit

snugly in the backplane and it may take additional effort to disengage the blade connectors from the

backplane.

Figure 6-10: Pull Blade From Chassis

6. Extract the blade completely from the chassis and carefully place it on an antistatic-protected area.

NOTE If the blade will not be replaced within the requisite three minutes, install two slotblockers as follows:

a. Align a slot blocker, open side up (Figure 6-11), with the card guides insidethe open slot and carefully push it fully into the chassis on the side rails.

b. Using the appropriate screwdriver, tighten the small screws on each end of the slot blocker.

Figure 6-11: Slot Blocker

6-13



DIMM Removal/Replacement

Remove DIMMs in the order shown below. If you are transferring DIMMs from the blade just removed from the

chassis to a replacement blade, load the DIMMs in the same slot locations on the replacement blade.

21. 1. Carefully push down on the ejector handles on each side of the DIMM at the same time to remove each

DIMM from the memory slot (Figure 6-12).

Figure 6-12: Ejecting Memory From Slot

22. Note that the memory DIMM is keyed so that it will only go into the memory slots one way.

Keyed DIMM

Figure 6-13: Memory Keyed For Insertion

23. 2. Carefully insert each memory DIMM into the respective slot on the new blade

Figure 6-14: Inserting Memory Into Slot

6-14





3. Ensure that the “hooks” on the locking levers engage the chassis at the left and right edges of the blade slot.Once the “hooks” are engaged, grasp the two locking levers and simultaneously push them toward each other

to securely seat the blade in the connector on the backplane, as shown in Figure 6-16. It may take additional

effort to push the board into final seating, because it must mate with several connectors on the backplane. The red tabs on the inside of each locking lever will automatically “click” into position. Figure 6-16 the

direction of force needed to close the locking levers.

NOTE The blue LED will briefly illuminated when power is reestablished as the blademates with the backplane connectors.

Figure 6-16: Insert the Blade

4. Using the appropriate screwdriver, tighten the small screws in each locking lever (as shown in Figure6-17). This completes the replacement of a blade

Figure 6-17: Tighten the Locking Screws

24. 5. Verify that the operating system boots.

6-16



7 Cooling Fan Tray Assembly for the hp Carrier Grade Blade Server bh3710

IntroductionThis chapter describes the removing and replacing the fan tray assembly used by the bh3710. The cooling fan

assembly is located in a tray on the right side on the front of the bh3710. The illustrations below show the fan tray

and where the fan tray is located in the chassis.

CAUTION It is recommended that the replacement fan assembly tray be unpackedand ready to install because removal and replacement of fan assemblytrays must be completed WITHIN 20 SECONDS or the server blades willbegin to shut down and data being transmitted to the blades will be lost.

WARNING Make sure that the rack is anchored securely before removing any componentsfrom the HP Server. Failure to do so may cause injury or death.

Required Tools

Either a Torx T-10 or a flat blade screwdriver may be used.

7-1





Figure 7-2: Pulling the Fan Assembly Out Of the Chassis

Fan Tray Assembly Installation

1. Carefully place the rear of the fan tray assembly into the opening in the fan bay. See Figure 7-3.

Figure 7-3 : Inserting the Fan Tray Assembly into the Chassis

2. Push the fan assembly completely into the chassis. Press firmly when the fan nears full insertion to ensuresolid joining with the power connector in the chassis.

3. Using a Torx T-10 or flat blade screwdriver, tighten the two securing screws to complete installation.

Check all Management Blade fan status LEDs on the Fan Tray Assembly bulkhead to ensure that they are OFF.

7-3



8 Mass Storage Installation for the hp Carrier Grade Blade Server bh3710

Fibre Channel (FC) Disk Carrier Blade InstallationStorage capacity for the bp2200 server blade can be added by installing FC disk carrier blades that hold two

additional disk drives per carrier. The carrier and drives utilize two slots and can be installed in slots F5/F6 (the

default slots) and F3/F4. Slots accommodating FC disk carrier blades are identified by the symbol shown in Figure8-1 below:

Figure 8-1: FC Disk Carrier Legend Marking

NOTE Default slots for the Fiber Channel Disk Carrier are F5 and F6. If the FC DiskCarrier containing the bootable disk is moved to a different pair of slots, thesystem will not automatically boot to UNIX. The system must either bereconfigured to identify the new location, or the FC Disk Carrier must be returnedto its original pair of slots.

Installing the FC Disk Carrier Blade

Required Tools:

A Torx T-10 driver or a number 1 Philips screwdriver may be used.

Remove the Slot Blockers

If you are installing an FC disk carrier blade for the first time or installing an additional FC disk carrier blade, youwill need to remove two slot blockers first:

1. Locate the two slots to be used for FC disk carrier blade insertion (either f5/f6 (default) or f3/f4) and loosenthe screws on each side of each slot blocker.

2. Remove the slot blockers from the chassis and store them for future use.

Figure 8-2: Slot Blocker

8-1



Installing the FC Disk Carrier

FC disk carrier blades are designed to operate in both 19 slot (13U) and ten slot (6U) blade servers, but not

automatically. Prior to inserting the blade into the chassis, turn the blade back-to-front and examine the DIP switch

located on the rear circuit card, left side top (as you are looking at it. The backplane connectors will be at the top of the circuit card, as shown in Figure 8-3). Ensure that both slides on the switch are set to the ten slot position. The

DIP switch location is also illustrated in Figure 8-3.

Backplane Connectors

Figure 8-3: FC Disk Carrier DIP switch location

CAUTION You must complete the following steps within 3 minutes to comply withcooling requirements. Failure to do so may cause loss of data when theblades begin to power down.

3. Grasp the blade by the handles and align it with the card guides inside the open slots.

Figure 8-4: FC Disk carrier blade

4. Carefully push the blade into the chassis until the connecters mate with the backplane.

5. Tighten the captive screws at each side to securely seat the blade into the backplane.

8-2



Installing an Individual Drive in the FC Storage Blade

1. Attach an anti-static wrist strap to your wrist before beginning.

2. Remove the new drive from the anti-static bag.

3. Remove the empty slot cover from the FC Storage Blade.

4. Grasp the handle of the new drive and insert it in the FC Storage Blade.

5. Tighten the screws on each side of the handle to secure the drive in the Storage Blade.

6. Look for the green LED marked “Act” (third from the left among the four LEDs shown on each drive

below) that indicates the drive is powering up.

Act LED

Disk mounting Screws

Figure 8-5: FC Blade Act LED

Hardware Path Table

Table 8-1 lists required FC hardware paths.

Table 8-1: FC Hardware Paths

6U Chassis Fibre Channel Hardware Paths

Upper RTM Prefix 0/2/2/0.8.0.255.Geo Address

(backplane jumper) Lower RTM Prefix 0/0/2/0.8.0.255.

SGA1:SGA0 FRONT SLOTS # 1 2 3 4 5 6 7 8

Right Disk Suffix 0.2 0.4 0.6 0.8 0.10 0.12 0.14 1.00:0

Left Disk Suffix 0.3 0.5 0.7 0.9 0.11 0.13 0.15 1.1


Left Disk Suffix 2.3 2.5 2.7 2.9 2.11 2.13 2.15 3.1


Left Disk Suffix 4.3 4.5 4.7 4.9 4.11 4.13 4.15 5.0


Left Disk Suffix 6.3 6.5 6.7 6.9 6.11 6.13 6.15 7.1

Valid Disk Path Upper or Lower RTM + Single Disk Suffix. Ex: 0/0/2/0.8.0.255.1.0

8-3



FC Disk Configuration

The following figures, schematics and tables provide configuration information for bh3710 FC disks.

System Slot (PA Blade with Two Tachyon TL 3.0 Chips)

(Uses Soft Addressing for Tachyon TL Chips)

Loop A Tachyon = 0/0/2/; Loop B Tachyon = 0/2/2/

10

98

7

6

5

4

3

2

1

Fibre Channel Dual Disk Carrier (uses Hard Addressing for disks)

Each Disk is Dual Ported(SGA0,1 = 1,1) Left Disk Address = 0.8.0.255.6.7; Right Disk Address = 0.8.0.255.6.6

Slot not occupied at first release (LAN Switch Card will be used in

Future)

Server Management Card



Empty Slot

Figure 1: 6U Front View

10

98

7

6

5

4

3

2

1

6U RTMB

6U RTMA

S l o t F 1

N / A

S l o t F 2

N / A

S l o t F 3

N / A

S l o t F 4

N / A

N / A

S l o t F 8

N / A

S l o t F 7

N / A

S l o t F 6

N / A

S l o t F 5

VSC7148

S l o t F 1

N / A

S l o t F 2

N / A

S l o t F 3

N / A

S l o t F 4

N / A

N / A

S l o t F 8

N / A

S l o t F 7

N / A

S l o t F 6

N / A

S l o t F 5

VSC7148

Figure 2: 6U Rear View

Figure 3: Default FC Loop

Configuration (per RTM)

Figure 4: Dual FC Loop

Configuration (per RTM)

Figure 1 and 2 show a fully configured first release 6U PowerBar. This configuration provides six internal dual ported

disks. When using the configuration shown in Figure 3 for the two RTMs, then all 6 disks are seen from the external FC

connector as well as its corresponding Tachyon TL chip. When the configuration shown in Figure 4 is used then the

Tachyon TL Chip for each loop can only see the two disks located in slot 3 or 4. Also, the external FC connector can

only see the four disks located in slots 5 through 8.The current POR (February 20, 2002) l ists only the 18 GB FibreChannel Disk (Seagate ST318451FC) as supported.

This disk supports concurrent access from each port. Each port will share the same hard address (minus the path of

the Tachyon TL controller) unless another device with the same address exists on the same loop.

Empty Slot

8-4



RTM A

Vitesse

Port Bypass

Chip

RTM B

Vitesse

Port Bypass

Chip

FC Disk0.8.0.255.6.11

Port A Port B

FC Disk0.8.0.255.6.10

Port A Port B

FC Disk

0.8.0.255.6.7

Port A Port B

FC Disk

0.8.0.255.6.6

Port A Port B

Tachyon TL 3.0

0/0/2/

Tachyon TL 3.0

0/2/2/

8-5



RTM A

Vitesse

Port Bypass

Chip

(Set to create to two Loops)

RTM B

Vitesse

Port Bypass

Chip

(Set to create two loops)

FC Disk0.8.0.255.6.11

Port A Port B

FC Disk0.8.0.255.6.10

Port A Port B

FC Disk

0.8.0.255.6.7

Port A Port B

FC Disk

0.8.0.255.6.6

Port A Port B

Tachyon TL 3.0

0/0/2/

Tachyon TL 3.0

0/2/2/

8-6



10 10

9

8

7

6

5

4

3

2

1

6U RTMB

6U RTMA

Figure 8: 6U Rear Config B

10

9

8

7

6

5

4

3

2

1

6U RTMB

6U RTMA

Figure 6: 6U Rear Config A

C r o s s - Ov er

C onn e c t i onL o o pA t oL o o pB

C r o s s - Ov er

C onn e c t i onL o o pB t oL o o pA

Figure 5-8 shows two possible configuration based on two fully loaded 6U PowerBar Chassis'. The differences between

the two possible configuration is in how you connect the two boxes together. The blue dashed lines show a cross-over

connection, wherein loop A in one box connects to loop B in the other box. This other setup (red solid lines) show the

straight through method. These two connection types are effectively the same. Each PA blade will see the same possible

disk addresses irregardless of connection type. (assuming the user connects both cables up.)

An important note to consider in this configuration is that the user will be required to change the SGA Jumper settings on

the second box. This will change the hard addressing for the disks of the second box, preventing any conflicts from

occuring on the Arbitrated Loop.




9

8

7

6

5

4

3

2

1




Future)




(Not Shipping at First Release) Fibre Channel Dual Disk Carrier


Figure 5: 6U Front Config A (SGA0,1 = 1,1)




9

8

7

6

5

4

3

2

1




Future)




(Not Shipping at First Release) Fibre Channel Dual Disk Carrier


Figure 7: 6U Front Config B (SGA0,1 = 0,1)

10

S t r a i g h t C o n n e c t i o n L o o p B t o L o o p B

S t r a i g h t C o n n e c t i o n L o o p A

t o L o o p A

8-7



F i g u r e

3 : T a b l e o

f P o t e n t i a l D i s k A d d r e s

s

T h i s P a g e c o n t a i n s t h e D i s k A d d r e s s i n g I n f o r m a t i o n f o r t h e t w o d i s k s i n a g i v

e n D i s k C a r r i e r p l u g g e d i n t o a s l o t .

( N o t e : S i n c e t h e D i s k C a r r i e r t a k e s u p t w o s l o t s , t w o o f t h e p o s s i b l e d i s k a d d r e

s s a r e n ' t u s e d . U s e t h e b o t t o m m o

s t

s l o t o f t

h e t w o u s e d t o s e l e c t t h e a d d r e s s .

i . e . i f y o u p l u g a d i s k c a r r i e r i n t o s l o t 3 / 4 t h e n t h e d i s k s a r e a d d r e s s e d

b a s e d o n S l o t 3 . I f y o u p u t i t i n t o 4 / 5 t h e n t h e d i s k s a r e a d d r e s s e d b a s e d o n S l o t 4 . )

T h e S G A

s e l e c t i o n j u m p e r s a r e c u r r e n t l y ( F e

b r u a r y 2 0 , 2 0 0 2 ) n o l o a d e d . T h i s r e s u l t s i n S G A 0 a n d S G A 1 b e i n g e q u a l

t o 1 . I f y o

u p l u g i n a j u m p e r o v e r S G A 0 o r 1

t h e n t h a t p i n w i l l b e g r o u n d e d a n d t h e s i g n a l w i l l g o t o 0 . W i t h t h e a b o

v e

t a b l e

s y o u s h o u l d b e a b l e t o d e t e r m i n e t h e a d d r e s s y o u r i n t e r n a l d i s k d r i v e

s w i l l b e a s s i g n e d i n m o s t c a s e s .

SGA1 1

SGA0 1

SIDE SLOT GA[0:4] SEL[4:1]

F 1 1 1 99 36 63 0.8.0.255.6.3

F 2 2 2 101 60 65 0.8.0.255.6.5

F 3 3 3 103 84 67 0.8.0.255.6.7

F 4 4 4 105 12 69 0.8.0.255.6.9F 5 5 5 107 36 6B 0.8.0.255.6.11

F 6 6 6 109 60 6D 0.8.0.255.6.13

F 7 7 7 111 84 6F 0.8.0.255.6.15

F 8 8 8 113 12 71 0.8.0.255.7.1

LEFT

DRIVE

ADDR

(DEC)

SPIN

TIME

DELAY

(sec)

LEFT

DRIVE

ADDR

(HEX)

LEFT DRIVE

ADDR (FC

PATH

FORMAT)

SGA1 1

SGA0 0


F 1 1 1 67 36 43 0.8.0.255.4.3

F 2 2 2 69 60 45 0.8.0.255.4.5

F 3 3 3 71 84 47 0.8.0.255.4.7

F 4 4 4 73 12 49 0.8.0.255.4.9

F 5 5 5 75 36 4B 0.8.0.255.4.11

F 6 6 6 77 60 4D 0.8.0.255.4.13

F 7 7 7 79 84 4F 0.8.0.255.4.15

F 8 8 8 81 12 51 0.8.0.255.5.1

LEFT

DRIVE

ADDR

(DEC)

SPIN

TIME

DELAY

(sec)

LEFT

DRIVE

ADDR

(HEX)

LEFT DRIVE

ADDR (FC

PATH

FORMAT)

SGA1 0

SGA0 1


F 1 1 1 35 36 23 0.8.0.255.2.3

F 2 2 2 37 60 25 0.8.0.255.2.5

F 3 3 3 39 84 27 0.8.0.255.2.7F 4 4 4 41 12 29 0.8.0.255.2.9

F 5 5 5 43 36 2B 0.8.0.255.2.11

F 6 6 6 45 60 2D 0.8.0.255.2.13

F 7 7 7 47 84 2F 0.8.0.255.2.15

F 8 8 8 49 12 31 0.8.0.255.3.1

LEFT

DRIVE

ADDR

(DEC)

SPIN

TIME

DELAY

(sec)

LEFT

DRIVE

ADDR

(HEX)

LEFT DRIVE

ADDR (FC

PATH

FORMAT)

SGA1 0

SGA0 0


F 1 1 1 3 36 3 0.8.0.255.0.3

F 2 2 2 5 60 5 0.8.0.255.0.5

F 3 3 3 7 84 7 0.8.0.255.0.7

F 4 4 4 9 12 9 0.8.0.255.0.9

F 5 5 5 11 36 B 0.8.0.255.0.11

F 6 6 6 13 60 D 0.8.0.255.0.13

F 7 7 7 15 84 F 0.8.0.255.0.15

F 8 8 8 17 12 11 0.8.0.255.1.1

LEFT

DRIVE

ADDR

(DEC)

SPIN

TIME

DELAY

(sec)

LEFT

DRIVE

ADDR

(HEX)

LEFT DRIVE

ADDR (FC

PATH

FORMAT)

1

s e

F 9 9 SW SW SW SW SW SW SW SW SW

F 10 10 SMC SMC SMC SMC SMC SMC SMC SMC SMC

B 10 10 RTMB RTMB RTMB RTMB RTMB RTMB RTMB RTMB RTMB

B 9 9 RTMA RTMA RTMA RTMA RTMA RTMA RTMA RTMA RTMA













98 24 62 0.8.0.255.6.2

100 48 64 0.8.0.255.6.4

102 72 66 0.8.0.255.6.6

104 0 68 0.8.0.255.6.8106 24 6A 0.8.0.255.6.10

108 48 6C 0.8.0.255.6.12

110 72 6E 0.8.0.255.6.14

112 0 70 0.8.0.255.7.0

RIGHT

DRIVE

ADDR

(DEC)

SPIN

TIME

DELAY

(sec)

RIGHT

DRIVE

ADDR

(HEX)

RIGHT DRIVE

ADDR (FC

PATH

FORMAT)

66 24 42 0.8.0.255.4.2

68 48 44 0.8.0.255.4.4

70 72 46 0.8.0.255.4.6

72 0 48 0.8.0.255.4.8

74 24 4A 0.8.0.255.4.10

76 48 4C 0.8.0.255.4.12

78 72 4E 0.8.0.255.4.14

80 0 50 0.8.0.255.5.0

RIGHT

DRIVE

ADDR

(DEC)

SPIN

TIME

DELAY

(sec)

RIGHT

DRIVE

ADDR

(HEX)

RIGHT DRIVE

ADDR (FC

PATH

FORMAT)

34 24 22 0.8.0.255.2.2

36 48 24 0.8.0.255.2.4

38 72 26 0.8.0.255.2.640 0 28 0.8.0.255.2.8

42 24 2A 0.8.0.255.2.10

44 48 2C 0.8.0.255.2.12

46 72 2E 0.8.0.255.2.14

48 0 30 0.8.0.255.3.0

RIGHT

DRIVE

ADDR

(DEC)

SPIN

TIME

DELAY

(sec)

RIGHT

DRIVE

ADDR

(HEX)

RIGHT DRIVE

ADDR (FC

PATH

FORMAT)

2 24 2 0.8.0.255.0.2

4 48 4 0.8.0.255.0.4

6 72 6 0.8.0.255.0.6

8 0 8 0.8.0.255.0.8

10 24 A 0.8.0.255.0.10

12 48 C 0.8.0.255.0.12

14 72 E 0.8.0.255.0.14

16 0 10 0.8.0.255.1.0

RIGHT

DRIVE

ADDR

(DEC)

SPIN

TIME

DELAY

(sec)

RIGHT

DRIVE

ADDR

(HEX)

RIGHT DRIVE

ADDR (FC

PATH

FORMAT)

8-8



9 Rack Installation

Installing the bh3710 in a Rack

The racking kit facilitates the installation of the bh3710 chassis into a rack. Rack kit installation documentation isshipped with each server inside the rack kit box. A graphic presentation of the installation document is included as

Figure 9-1. Racking information may also be found at the Web site < >http://www.hp.com/racksolutions .

9-1

http://www.hp.com/racksolutions

http://www.hp.com/racksolutions



Figure 9-1: Rack Installation Instructions

9-2



10 Blade Server bh3710 Slot Blocker Installation/Removal

IntroductionA slot blocker must be installed in every slot that does not contain a blade and, since the rear slots are not as deep as

the front, the rear slot blocker is shorter . The front slot blocker is depicted in Figure 10-1 and Figure 10-2. Rear

slot blockers are depicted in Figure 10-3 and Figure 10-4.

Figure 10-1: Slot Blocker, Front Figure 10-2: Front Slot Blocker, Partially Installed

Figure 10-3: Slot Blocker, Rear Figure 10-4: Rear Slot Blocker, Partially Installed

10-1



Required Tools and Supplies

• Number 1 Phillips screwdriver

• Antistatic wrist strap

Removing and Installing the Slot Blocker This section describes the procedures necessary to remove and to replace the slot blocker.

WARNING Make sure that the rack is anchored securely before removing any componentsfrom the bh3710. Failure to do so may cause injury or server damage.

Slot Blocker Removal

CAUTION Blade installation/removal must be completed within 3 minutes of SlotBlocker installation/removal to ensure that proper airflow is maintained.

To remove the slot blocker, complete the following steps:

1. Observe all standard safety and ESD precautions.2. Loosen the screws on the slot blocker and remove it from the chassis. Lay it aside for future reuse.

Slot Blocker Installation

1. Observe all standard safety and ESD precautions.

2. Insert the slot blocker into the empty slot and slide it all the way into the chassis until it stops.

3. Tighten both screws to secure the bulkhead

.

10-2



11 Blade Server Chassis for the hp Carrier GradeBlade Server bh3710

IntroductionThis chapter describes how to remove components from, and replace the bh3710 chassis/backplane combination, in

the event of a backplane failure. Schedule system shutdown with all the users in advance to allow them time to exit

the system prior to removing components and replacing the chassis.

Required Tools and Supplies

The following tools will be required to remove and install the chassis.

• Phillips screwdriver #1

• Small flat-bladed screwdriver

• Anti-static wrist strap

•Torx T-25 driver

• Torx T-10 driver

Figure 11-1: HP Blade Server Front View Figure 11-2: HP Blade Server Rear View

11-1



Replacing the Chassis/Backplane

Component Removal

WARNING Before removing components from the chassis, always disconnect the power

cords and unplug the LAN cables. Disconnect the power cord to avoid exposureto high energy levels that may cause burns when parts are short-circuited bymetal objects such as tools or jewelry. Failure to do so may cause injury or death.

To remove the chassis:

1. Observe all standard safety and ESD precautions.

2. Shutdown the HP-UX operating system for the bp2200 server blade.

FC and LAN RTM

DC Inlet Filter ModulesGrounding Lug

Figure 11-3: HP Blade Server Rear View

NOTE The greater the number of backplane connectors for a given blade, the greater the pressure required to insert and remove the card. This is a normal condition.

11-2



At the Rear of the Blade Server:1. Remove the DC power supply cable from each power supply.

2. Unfasten the four screws that secure each DC inlet filter module.

3. Slide both DC inlet filter modules out of the chassis and set aside.

4. Tag and remove the cables from each FC and LAN RTM blade.

5. Unfasten the two screws that secure each FC and LAN RTM blade in the chassis and snap the ejector levers

outward. Pull each FC and LAN RTM blade out of the chassis and set aside.

6. Loosen the two screws on each of the slot blockers. Pull all the slot blockers out of the chassis and set

aside.

7. Loosen and remove both nuts from the dual grounding lug (Figure 11-3). Pull the grounding lug cable

away from the bh3710 and set aside.

Converter Module

bp2200 Server Blade

FC Storage Blade

Management Blade

Figure 11-4: HP Blade Server Front view

At the Front of the Blade Server:1. Loosen the screw on each power converter module. Slide each converter module out of the chassis.

NOTE Make a diagram showing where blades are located in the chassis. They need tobe replaced in the same order.

11-3



2. Press the red button located in each lever on the bp2200 server blade. Unfasten the two screws that secure

the bp2200 server blade in the chassis and snap the ejector levers outward. Pull the bp2200 server blade out

of the chassis and set aside.

3. Unfasten the four screws (two on each side) on each FC storage blade. Pull each FC storage blade out of the

chassis and set aside.

4. Press the red button located in each lever on the Management blade. Unfasten the two screws that secure the

Management blade in the chassis and snap the ejector levers outward. Pull the Management blade out of the

chassis and set aside.

5. Loosen the two screws on each of the slot blockers. Pull all the slot blockers out of the chassis and set aside.

6. Loosen the two screws on the fan tray assembly. Grasp the handle on the fan tray assembly and slowly pull

the tray assembly out of the chassis.

7. Lift the chassis out of the cabinet and set it on a flat work surface.

11-4



Chassis/Backplane Installation

Observe all standard safety and ESD precautions.

At the Front of the Blade Server:1. Install the empty replacement chassis/backplane into the rack following the rack manufacturer’s

instructions.

2. Grasp the handle on the fan tray assembly with one hand and the back portion of the tray assembly with the

other hand. Slowly slide the tray assembly into the chassis. Tighten the two screws on the fan tray

assembly to secure it in place.

3. Insert the Management blade back into the chassis in slot 10 and slide it all the way in until it contacts the backplane then push firmly until it seats. Snap the locking levers inward to lock the blade in place. Tighten

the two screws to secure the Management blade in the chassis.

4. Insert the bp2200 server blade into the chassis in slots 1 and 2 and slide it all the way in until it contacts the

backplane then push firmly until it seats. Snap the locking levers inward to lock the blade in place. Tighten

the two screws to secure the bp2200 server blade in the chassis.

CAUTION Ensure that the FC storage blade(s) are inserted into the original slot(s).Failure to do so will result in a system boot failure.

5. Insert each FC storage blade in the chassis and slide it all the way in until it contacts the backplane then push

firmly until it seats.. Tighten the four screws (two on each side) on each FC storage blade to secure the blade

in the chassis.

6. Insert all the slot blockers in the chassis and slide all the way into the chassis until they seat against thechassis. Tighten the two screws on each of the slot blocker bulkheads to secure the slot blocker in the

chassis.

7. Slide each converter module into the chassis. Tighten the screw on each converter module to secure the

module to the chassis.

At the Rear of the Blade Server:1. Insert each FC and LAN RTM blade into slots 9 and 10 in the chassis and slide it all the way in until it

contacts the backplane then push firmly until it seats.. Snap the locking levers inward to lock the blade intothe chassis. Tighten the two screws on each FC and LAN RTM blade to secure the blade in the chassis.

2. Insert all the slot blockers into the chassis and slide into the chassis. Tighten the two screws on each of theslot blockers to secure the slot blockers to the chassis.

3. Slide both DC inlet modules into the chassis, ensuring that they connect with the corresponding converter

module.

4. Fasten the four screws on each DC inlet module to secure each module in the chassis.

5. Plug the previously tagged cables into the Management LAN blades.

6. Attach the grounding lug cable to the bh3710 (Figure 11-3). Tighten both nuts to secure the dual groundinglug cable in place.

7. Plug the DC power supply cable into each DC inlet module.

8. Verify that the operating system boots.

11-5



12 Maintenance and Troubleshooting for the hpCarrier Grade Blade Server bh3710

This chapter discusses operation and maintenance of the bh3710. Information has been divided into these threemain categories:

Maintenance

Monitoring System Operation

Troubleshooting

WARNING Make sure that the rack is anchored securely before removing any componentsfrom the Blade Server. Failure to do so may cause injury or death.

Maintenance

Required Tools

• Torx T-10 driver

Figure 12-1: bh3710 Blade Server (Front View)

12-1



Cooling Fan Tray Assembly Maintenance

The only recommended maintenance for the bh3710 is replacement of the cooling fan tray assembly. Hewlett-

Packard recommends that the fan tray assembly be replaced once every five years to ensure maximum cooling

capacity for the bh3710.

Removing and Installing the Fan Tray Assembly

The bh3710 contains six cooling fans mounted in a tray assembly located at the front of the bh3710 on the right side.The left side of the tray assembly bulkhead shows each blade’s status via a green or yellow LED depending on the

blade status at the time. The right side of the tray assembly bulkhead allows airflow to the fans.

dividual Blade Status LEDs

Airflow

Ca tive Screws

Fan Tray Handle

Figure 12-2: Cooling Fan Tray Assembly Bulkhead

12-2



CAUTION: Fan assembly trays are hot swappable. However, only 20 seconds areallowed to perform the hot-swap procedure. Ensure that the replacementfan assembly tray is nearby and ready to be inserted before removing thefan assembly tray to be replaced.

Fan Tray Assembly Removal1. Loosen the top screw and the bottom screw located on the right side of the fan assembly. See Figure 12-2.

2. Grasp the handle and pull the fan tray from the chassis. See Figure 12-2.

3. Place the failed fan assembly on a sturdy surface.

Fan Tray Assembly Installation

27. 1. Carefully place the rear of the replacement fan tray assembly into the opening in the fan bay. See

Figure 12-3.

Figure 12-3: Inserting the Fan Tray Assembly into the Chassis

2. Push the fan assembly completely into the chassis. Press firmly when the fan nears full insertion to ensure

solid joining with the power connector in the chassis.

3. Using a T-10 Torx screwdriver, tighten the two securing screws to complete installation.

4. Ensure that the fans start up after replacement.

12-3



Monitoring System OperationThe Event Monitoring Service (EMS) Hardware Monitors are an important tool for maintaining system availability.

The EMS hardware monitors allow you to monitor the operation of a wide variety of hardware products and be

alerted immediately if any failure or other unusual event occurs. Hardware event monitoring is available to usersrunning HP-UX 11i, 11.00, or 10.20 (IPR 9902 and later).

Hardware event monitoring provides a high level of protection against system hardware failure. By using hardware

event monitoring, you can virtually eliminate undetected hardware failures that can interrupt system operation andcause data loss.

Configuring Hardware Monitoring

The EMS Hardware Monitors are installed at the same time as the Support Tools Manager. Once the monitoring

software is installed, monitoring is automatically enabled.

By default, messages regarding major warnings and serious or critical events that occur on hardware being

monitored will be handled two ways:

Written to /var/adm/syslog/syslog.log

Sent to e-mail address root.

All events will be stored in /var/opt/resmon/log/event.log.

To configure, enable, or disable hardware event monitoring, run the monitoring request manager:

/etc/opt/resmon/lbin/monconfig .

Documentation

For the latest and most complete information on EMS Hardware Monitors, see the Web page

http://docs.hp.com/hpux/diag/ for details. At this Web site, you will find Overviews, Tutorials, Quick Reference

Cards, Frequently Asked Questions (FAQs), and much other material.

For complete information on installing and using EMS hardware monitors, as well as a list of supported hardware,refer to the "EMS Hardware Monitors User's Guide" available at the above Web site. An electronic copy of this

book is also included on the Support Plus CD-ROM in the <mount_point>/DIAGNOSTICS directory.

12-4

http://docs.hp.com/hpux/diag/

http://docs.hp.com/hpux/diag/



TroubleshootingIf you are having problems installing or booting your Blade Server, this section provides information on the

different tools available for common installation problems, troubleshooting operational problems and error

messages.

Troubleshooting ToolsThe following tools are available for system troubleshooting:

Event Monitoring Service (EMS). EMS provides a mechanism for monitoring system resources on HP-UX and

sending notifications about these system resources to the user.

Support Tool Manager (STM). STM is a software application that operates from the console to obtain status and

descriptive information about the A6829A adapter, diagnose problems, etc.

Simple Network Management Protocol (SNMP) SNMP is an industry-standard management protocol, originally

designed for managing TCP/IP networks.

Information and operating instructions may be found at:

www.docs.hp.com

Search for EMS, STM, or SNMP.

Common Installation Problems

The following sections contain general procedures to help you locate installation problems. If you need assistance, itis recommended that you contact your reseller first. If you require assistance from Hewlett-Packard, see the

"Warranty or Service/Support Booklet" or refer to the Blade Server Online Documentation CD-ROM included with

your product.

CAUTION Replace the covers before operating the Blade Server, even for a shorttime. Otherwise, overheating can damage chips, boards, and mass storagedevices.

However, you can safely remove the PCI access panel while the Blade

Server is running to remove and replace PCI Hot Plug boards. For anyother service activity requiring access to the processor baseboard or I/Obaseboard, power down the Blade Server and observe all safetyprecautions.

12-5

http://www.docs.hp.com/

http://www.docs.hp.com/



Troubleshooting Sequence

Most Blade Server problems are the result of incorrect Blade Server and SCSI subsystem configurations. To

troubleshoot an installation problem, perform the following checks in the order given:

1. Check all cable and power connections, including those in the rack, etc.

2. Ensure that the Blade Server is configured properly.

• Check the Quick Setup Utility.

• If the error is a network-related problem, verify that all network configurations have been setup correctly in the Management Blade, the bp2200 MP, and the HPUX Operating system

network.

• Consult your network operating system manual.

3. Verify all cables and boards are securely plugged into the appropriate connectors or slots then verify the

following:

• The bp2200 blade must be in front slot 1.

• The factory configured location of the boot disk is in front slots 5-6. The boot disk is the onenext to the slot status LEDs.

• The Management blade must be in front slot 10.

• The FC LAN and RTMs must be in rear slots 9 and 10

4. Remove any optional blades, one at a time, checking its affect on the Blade Server.

5. Unplug the power cord, wait 20 seconds, plug the power cord in again, and restart the Blade Server.

6. If you suspect a hardware error, follow these steps:

28. a. Power down the Blade Server.

29. b. Simplify the Blade Server configuration to the minimum required:

30. For normal operation, the minimum configuration is the Server Management Card and Rear Transition

Module fitted to the PowerBar chassis. The Management LAN should be connected to the SMC and beoperational. If the Management LAN is not available then the SMA will operate in Stand Alone mode and

use its last configuration.

31. c. Remove all third-party options, and reinstall each one, one at a time, checking the Blade Server after each installation.

32. d. Reconnect the power cord and other cables.

33. e. Boot the Blade Server. If it does not function properly, refer to the following procedures.

12-6



If the Blade Server Will Not Power OnUse these steps to check for power related problems:

1. On the fan tray assembly, verify that the LEDs are illuminated

2. If LEDs are illuminated, the Blade Server is receiving power.

3. If LEDs are not illuminated, ensure that the Blade Server power cords are connected.4. Check the Blade Server's power supplies. Two n+1 -48VDC 400W Power Supply Units (PSU) are

included with the chassis. Each PSU contains a converter module and a DC inlet module. The converter

module is installed/removed from the front of the chassis and the DC inlet module is installed/removed

from the rear of the chassis.

5. Ensure that both PSUs and both power cords are plugged in to the chassis.

6. Each PSU has two LEDs and the green LED is the Power (PWR) LED. The PWR LED glows a steadygreen when the Blade Server's DC power is on.

7. If the PWR LED on any power supply is not a steady green, reseat the PSU.

8. If you remove the PSU to reseat it, wait 15 seconds before reinstalling. This prevents tripping the inrushcurrent limit of the circuit breaker.

9. Ensure that the blades, FC and LAN RTMs, and the fan module are properly seated.

Blade Server Fan Tray AssemblyFan Tray Assembly trouble shooting consists of the following:

34. 1. If one of the six fans in the Fan Tray Assembly fails, the SMC sends a message to the console and

continues to operate. Replace the Fan Tray Assembly as soon as possible to restore n+1 functionality.

35. 2. If the second fan fails, The Management Blade will begin to shut down the remaining blades to prevent

overheating. The Fan Tray Assembly must be replaced before the Management Blade will boot the

remaining blades.

If the Blade Server Powers On but Shuts Down

Use this checklist to verify the following problems when the Blade Server powers on and then off:• Verify that a conductive item has not been dropped or left inside the server chassis.

• Check the connections on all blades and PSUs.

• Check the cables for bent pins.

• Check the processors for bent pins.

If the Blade Server Powers On but Fails POST (Power-On Self Test)Use this checklist to check for the following problems when the Blade Server fails POST:

• Attempt a recovery boot.

• Run the Event Log Report Utility.

12-7



If the Blade Server Powers On but Error Messages Are Displayed.Use these steps to troubleshoot the errors.

36. 1. If an error message displays on the Management blade console screen, read the error message text for

recommended actions to take.

37. 2. If the actions do not solve your problem, or if no actions are displayed, refer to the Management BladeErrors section for additional information..

38. 3. If there is no error message, follow these steps:

a. Turn off the Blade Server and remove all external peripherals if attached, except the console and

keyboard.

b. Reboot the Management Blade

c. If the Blade Server still is not operational, turn off the Blade Server and all external devices, and

check the internal hardware, as follows:

i. Unplug the power cords.

ii. Ensure that PSUs, input power modules, and the fan module are firmly seated in their slots.

iii. Verify that all the blades are in the proper order and firmly seated on the backplane.

iv. Ensure that all disk drive power and data cables are securely and properly connected.

v. Verify the FC configuration with the cabling and switch diagrams.

vi. Replace both power cords.

vii. Turn on the monitor.

viii. Check for error messages.

If the Fans Do Not OperateVerify that the fan assembly tray is properly seated.

If the Blade Server’s FC Drives Are Not Recognized During a BCH Search or Boot

1 Check the following if the FC drives are not recognized during a BCH search or boot command:

• Check the seating of the FC drives in the carrier and also check the seating of the FC carrier in thechassis backplane.

• Verify the FC disk carrier is installed in the correct chassis slot.

• Verify that the boot path specified matches the actual path configured. The FC path is dependent on

the chassis slot, FC carrier slot, and the backplane FC address jumpers.

12-8



General TroubleshootingHow to detect that there is trouble:Generally, a problem will fall into one of the categories below. Determine which category applies and then refer to

that section for troubleshooting guidance.

• The chassis is in critical shutdown mode

• One or more blades are shut down

• A blade does not power up when “hot swapped” in

• The Management Blade is unreachable over the network

• The Management LAN on a bp2200 blade is unreachable over the network

• A Management Blade fails to boot

• The Amber LED next to a blade is blinking.

10. 1. The chassis is in critical shutdown mode.

• All blades (except the Management Blade) “hot swap” (blue) LEDs are on

• The console displays the message “Critical shutdown”.

What to check:• •Make sure the fan tray is installed and working

• •Make sure fans in the PSUs are working

• •Make sure ambient air is within specifications

What to do:

• Manually set each blade’s power state to “Automatic” or “Reset” all blade using ‘smc-menu’

command

• •Unplug and re-plug power to the chassis

2. One or more blades are shut down

• The “hot swap” (blue) LED is illuminated for every blade except the Management Blade

• The console displayed the message “Blade xx mismatch”

What to check:

• Make sure the power state for the blade is set to “Automatic” on the Management Blade

• Make sure the hot swap latch is “in place”

• Make sure there are no bent/broken pins on backplane

12-9



What to do:

• Manually set each blade’s power state to “Automatic” or “Cycle” all blade using ‘smc-menu’command

• Hot swap the blade out and re-insert each blade

•

Swap out blades as needed.

3. A blade does not power up when “hot swapped” in

None of the LEDs come on

What to check:

• Make sure the power state for the blade is set to “Automatic” on the Management Blade

• Make sure the hot swap latch is “in place”

• Make sure there are no bent/broken pins on backplane

What to do:

• Manually set each blade’s power state to “Automatic” or “Cycle” all blade using ‘smc-menu’command

• Hot swap each blade out and re-insert

• Swap out blades as needed

4. The Management Blade is unreachable over the network

Cannot ‘telnet’ or ‘ping’ the Management Blade

What to check:

• Using the RS-232 port or the LCD panel, verify the Management LAN’s network parameters

• Make sure only one network cable of the Rear Transition Modules (RTMs) is attached to a singlenetwork

What to do:

• Change the Management Blade’s network parameters to the correct values via the ‘smc-menu’, ‘smc-

ethcfg’ or the LCD panel

• Attach Management LAN cable to the network

12-10



5. The MP on a bp2200 blade is unreachable over the network

Cannot ‘browse or “ping” the MP

What to check:

• •Using either the Management Blade LAN or the RS-232 console attached to the Management Blade,

verify the network parameters of the MP

• •Make sure there are not “No LAN to blade xx” and “No link to blade xx” Alerts on the Management

Blade console

What to do:

• Change the MP network parameters to correct values

• Manually ‘ping’ the IP address of the MP from the Management Blade

6. The Management Blade fails to boot

• •The Management Blade does not boot to the “login:’ prompt

• •Management Console does not display boot messages

What to check:

• Make sure there is no jumper attached in positions 1 or 2 on J7 on the Management Blade

What to do:

• Monitor boot sequence via the RS-232 console

• Hot swap each blade out and re-insert

• Swap out Management Blade if needed

7. The Amber LED next to a blade is blinking

• •The blinking Amber LED indicates that there is an issue with the blade that requires user intervention

• •An alarm message printed on the Management Blade console

What to do:

• See Management Blade Alarms section and follow recommended actions

Diagnostics

For information on diagnostics, please go to the following website:

www.docs.hp.com/hpux/diag/index.html

12-11

http://www.docs.hp.com/hpux/diag/index.html

http://www.docs.hp.com/hpux/diag/index.html



A Specifications for the hp Carrier Grade BladeServer bh3710

IntroductionThis appendix contains the following specifications for the Blade Server:

• Physical, Electrical, and Environmental Specifications

• International Standards

• Configuration Menu Command Line Interface Specifications

Physical, Electrical, and Environmental SpecificationsTable A- 1: Physical, Electrical, and Environmental Specifications

Description Specification

Dimensions (H, W, D) 10.5 x 17 x 14 in (26.25 x 42.50 x 35.00 cm)

Weight (configured) approximately 51 lbs (23.4 Kg)

Input Power

Operational:

Recommended:

-40 to -70 VDC (Margin included)

-48 to –60 VDC

Temperature

Operational:

Non-Operational:

+5 to +35C. (Goal: derate 4C/1000m above 1500m altitude)

(Commit: derate 2C/1000m above sea level)

Recommended: +20 to +25C

-40 to +70C

Humidity

Operational

Recommended

15% to 80% RH non-condensing @35C

40% to 60% RH non-condensing

Maximum Altitude

Operational

Non-Operational

3000 meters above sea level

4500 meters above sea level

Acoustics

A-1



Sound Power 54.0 dBA Bels LwA (not to exceed 7.5 Bels)

A-2



International Standards

• Compact PCI Specification, PICMG 2.9 Rev.1.0, April 2000

• The I2C-Bus Specification, Version 2.0, December 1998

•Intelligent Platform Management Interface Specification, Version 1.0, Rev.1.1, November 15, 1999.

• Intelligent Chassis Management Bus Specification, Version 1.0, Rev.1.2, May 11, 2000.

• Bellcore GR-63-CORE Network Equipment Building System Requirements Iss1, October 1995

A-3



Configuration Menu Command Line Interface Specifications

Interface Definition

TerminologyIn the tables below, the Name column refers to the command used. Most of these commands are for the

Configuration Menu, so their use from the command line is sometimes a little clumsy. The Read/Write columnindicates the user level required to set the value - all values are readable by all users. The Description field is a one-

line summary of what the field does. The Values column indicates how to use the command.

To read (get) a value:

smc-cmd -g name.x

Example: # smc-cmd –g configuration SMC IP Address: ______________ requested field configuration SMC IP

Address Retrieved field Configuration SMC P Address.0 = 15.8.133.217

Use one of the values from the Name column in place of name. If the “.x” is missing, it will default to “.0”. This

value is an index where there are a table of these values.

To write (set) a value:

smc-cmd -s name.x new-value

Example: # smc-cmd –s configuration

Use one of the valid values from the Values column in place of new-value. You must have permissions at least as

great as that indicated in the Read/Write column. “RO” means that the value is read-only. “Manufacture” meansthat only the manu user can perform this operation. “Superuser” means that any superuser can perform the

operation (root is the only default superuser). “Operator” means that any operator can perform the operation (there

are no operators defined by default). Other users cannot change any values (there are no other ‘normal’ users

defined).

The first table in each section contains commands for which only a single index is available. Subsequent tablescontain multiple instances of the same data as appropriate to the command

A-4



The following Configuration Menu Command Line Interface Specifications tables are displayed in this section of

Appendix A:

Table A- 2: Configuration

Table A- 3: Temperature Configuration Table

Table A- 4: RTM Port Configuration Table (External Ports)

Table A- 5: RTM Slot configuration Table (Internal Ports)

Table A- 6: User Configuration Table

Table A- 7: Event Log

Table A- 8: Event Log Table

Table A- 9: Hardware Fitted

Table A- 10: Chassis LEDs Table

Table A- 11: Fan Status Table

Table A- 12: SMC LEDs Table

Table A- 13: LAN Table

Table A- 14: RTM Registers Table

Table A- 15: Device Data Table

Table A- 16: Currently Raised Alarms

Table A- 17: Raised Alarms Table

Table A- 18: SMA General

Table A- 19: Connected Users Table

Table A- 20: Level 3 Self Tests (automatic) Table

Table A- 21: Level 3 Self Tests (manual) / Level 4 Self Tests Table

Table A- 22: Component Versions Table

Table A- 23: Temperature Control Table

Table A- 24: Voltage Control Table

Table A- 25: SNMP General

Table A- 27: SNMP Trap Destinations Table

Table A- 28: SNMP Authenticated Managers Table

.

A-5



Table A- 2: Configuration

Name Read/Write Description Values

configurationActivateDeferredConfiguration Operator Activate deferred configuration Any

configurationAlarmEventBlackoutPeriod Operator Alarm event blackout period Second

configurationAlarmEventsToRoot Superuser Display alarms on terminal being used by logged in user

0 = Ala

configurationChassisId Operator Chassis identity 1 = 6U

no oper

configurationChassisName Operator Chassis name String

configurationChassisSize RO Chassis size Numbe

configurationCreateNewUser Superuser Create new user Set this

name

configurationCurrentPollingInterval Operator Current polling interval Second

configurationDownloadConfiguration Operator Download configuration Filenam

configurationFanStatusPollingInterval Superuser Fan status polling interval Second

configurationFcRtmOneAvailable RO FC RTM 1 available “Availa

configurationFcRtmOneLoopMode Superuser FC RTM 1 loop mode 1 = dua

configurationFcRtmTwoAvailable RO FC RTM 2 available “Availa

configurationFcRtmTwoLoopMode Superuser FC RTM 2 loop mode 1 = dua

configurationLanConfigTimeout Operator LAN configuration lock timeout Second

configurationModemAutoAnswer Operator Modem auto-answer setting 0 = aut

configurationModemInitString Operator Modem initialisation string String o

configurationModemLocation Operator Modem location 0 = no

configurationNtpServerName Operator NTP server name IP addr

configurationSelBackupFilename Operator SEL backup filename Filenam

configurationSmcDnsAddress Superuser SMC DNS server address IP addr

A-6




configurationSmcDomainName Superuser SMC domain name Domai

configurationSmcGatewayAddress Superuser SMC gateway address IP addr

configurationSmcHostName Superuser SMC hostname Hostna

configurationSmcIpAddress Superuser SMC IP address IP addr

configurationSmcMacAddress Superuser SMC MAC address MAC a

configurationSmcSubnetMask Superuser SMC subnet mask IP addr

configurationTemperaturePollingInterval Operator Temperature polling interval Second

configurationUploadConfiguration Operator Upload active configuration Filenam

configurationUploadDeferredConfiguration Operator Upload deferred configuration Filenam

configurationVoltagePollingInterval Operator Voltage polling interval Second

Table A- 3: Temperature Configuration Table


configurationChassisTempThreshold Manufacture Chassis Temperature Threshold Tempe

Index 0

configurationPsuTempThreshold Operator PSU Temperature Threshold Tempe

Index 0

A-7



Table A- 4: RTM Port Configuration Table (External Ports)


configurationFcRtmOnePortIndex RO FC RTM 1 Port Index Index n

configurationFcRtmOnePortStatus Superuser FC RTM 1 Port Status 0 = dis

configurationFcRtmTwoPortIndex RO FC RTM 2 Port Index Index N

configurationFcRtmTwoPortStatus Superuser FC RTM 2 Port Status 0 = dis

Table A- 5: RTM Slot configuration Table (Internal Ports)


configurationFcRtmOneSlotIndex RO FC RTM 1 Slot Index Index n

configurationFcRtmOneSlotStatus Superuser FC RTM 1 Slot Status 0 = dis

configurationFcRtmTwoSlotIndex RO FC RTM 2 Slot Index Index n

configurationFcRtmTwoSlotStatus Superuser FC RTM 2 Slot Status 0 = dis

Table A- 6: User Configuration Table


configurationPagingUserActive Operator Paging User Active 1 = act

configurationPagingUserAlert Operator Paging User Alert Level 1 = info

configurationPagingUserDialbackNumber Operator User dialback number Modem

configurationPagingUserPagerNumber Operator Paging user pager number Pager I

configurationPagingUserPagerServiceNumber Operator Paging user pager service number Pager s

A-8




configurationUserDelete Superuser User delete Any

configurationUserLevel Superuser User level 0 = nor

configurationUserName RO User name Name (see abo

configurationUserPassword Superuser User password Passwo

Table A- 7: Event Log


eventlogEvLogClearLog Superuser Clear log any

eventlogEvLogSaveToFile Operator Saves event log to an NFS file NFS fi

Table A- 8: Event Log Table


eventlogEvLogAlarmObject RO Alarm object Indicat

eventlogEvLogAlarmText RO Alarm text Textua

eventlogEvLogAlarmType RO Alarm type Alarm

eventlogEvLogData1 RO Event parameter 1 Alarm

eventlogEvLogData2 RO Event parameter 2 “”

eventlogEvLogData3 RO Event parameter 3 “”

eventlogEvLogDirection RO Event direction Variou

eventlogEvLogEventData RO Event data

A-9




eventlogEvLogGenBusId RO Generator bus ID

eventlogEvLogGenIPMBLun RO Generator LUN

eventlogEvLogGenIPMBSlaveAddr RO Generator slave address

eventlogEvLogGenIsSysSoftware RO Generator was system software

eventlogEvLogGenSysSoftwareId RO System software ID

eventlogEvLogManufId RO Manufacturer ID

eventlogEvLogMessageRev RO Event message version

eventlogEvLogRaising RO Raising / Clearing “Raise”

eventlogEvLogRecordType RO Record type

eventlogEvLogSensorNumber RO Sensor number

eventlogEvLogSensorType RO Sensor type

eventlogEvLogTimestamp RO Timestamp Time a

eventlogEvLogType RO Event type

Table A- 9: Hardware Fitted


hardwarefittedConfigSynch Operator Synchronise configuration with currentlydetected hardware

Any

hardwarefittedFcRtmOneModelNumber RO RTM 1 model number Module

hardwarefittedFcRtmOneVersionNumber RO RTM 1 version number Version

A-10




hardwarefittedFcRtmTwoModelNumber RO RTM 2 model number Model

hardwarefittedFcRtmTwoVersionNumber RO RTM 2 version number Version

hardwarefittedLanSwitchExt1Status RO LAN switch external port 1 status “Opera

hardwarefittedLanSwitchExt2Status RO LAN switch external port 2 status “Opera

hardwarefittedLanSwitchIntegrity RO LAN switch integrity “Opera

hardwarefittedModemReset Operator Reset external modem Any. S

hardwarefittedNtpStatus RO NTP status Status

hardwarefittedRemoveUnderConfig Operator Remove under config status from all

blades

Any

hardwarefittedSmcTemperatureReading RO SMC temperature reading Curren

Table A- 10: Chassis LEDs Table


hardwarefittedChassisLedName RO Chassis LED name/unit Name a

hardwarefittedChassisLedStatus RO Chassis LED status LED c

A-11



A-12

Table A- 11: Fan Status Table


hardwarefittedFanName RO Fan number 1 – 6

hardwarefittedFanPercentage RO Fan speed as percentage of max speed 0 – 100

hardwarefittedFanStatus RO Fan status Status

Table A- 12: SMC LEDs Table


hardwarefittedSmcLedName RO SMC LED name/unit Name a

hardwarefittedSmcLedStatus RO SMC LED status LED co

Table A- 13: LAN Table


hardwarefittedLanSwitchLinkIndex RO LAN switch status index Integer

hardwarefittedLanSwitchLinkStatus RO Internal lan status Status

Table A- 14: RTM Registers Table


hardwarefittedFcRtmOneRegister Operator RTM 1 register read/write Hex va

hardwarefittedFcRtmRegisterName RO RTM register name Name o

hardwahardwa

hardwarefittedFcRtmTwoRegister Operator RTM 2 register read/write Hex va



A-13






hardwarefittedDeviceGatewayAddress Operator Gateway Address IP addr

hardwarefittedDeviceGuid RO Device global unique ID Ordere

AND a

unique

hardwarefittedDeviceHardwareType Operator Hardware Type Enume

hardwarefittedDeviceHealth RO Device health Enume

hardwarefittedDeviceHostName Operator Hostname Hostna

hardwarefittedDeviceHotswapState RO Slot hotswap state Hotswa

hardwarefittedDeviceHwVersion RO Device Hardware version ‘unkno

hardwarefittedDeviceIdName RO Device ID name From F

hardwarefittedDeviceIndex RO Device ID number Index n

hardwarefittedDeviceIpAddress Operator IP Address IP addr

hardwarefittedDeviceLanSettings Operator Apply all LAN settings in one command Formathostnam

hardwarefittedDeviceLocation Operator Device physical location String

hardwarefittedDeviceMacAddress Operator Device MAC address MAC a

hardwarefittedDeviceManagementUrl Operator Device management URL www a

hardwarefittedDeviceManagementUrlLabel Operator Device management URL label www a

hardwarefittedDeviceManufactureDate RO Device manufacturing date From F

hardwarefittedDeviceManufactureInfo RO Device manufacturing info From F

hardwarefittedDeviceManufacturer RO Device manufacturer HP or ‘

A-15




hardwarefittedDevicePartNumber RO Device part number From F

hardwarefittedDevicePowerState Operator Power State 0 = off

hardwarefittedDeviceRackId RO Device rack ID Chassi

hardwarefittedDeviceRackPosition RO Device rack position Type a

hardwarefittedDeviceRelationshipType RO Device relationship type Enume

hardwarefittedDeviceRestoreDefaultLan Operator Restore LAN settings to factory settings Any

hardwarefittedDeviceRestoreLanSettings Operator Restore LAN settings to previous values Any

hardwarefittedDeviceRevision RO Device revision From F

hardwarefittedDeviceRomVersion RO Device ROM version ‘unkno

hardwarefittedDeviceSerialNumber RO Device serial number From F

hardwarefittedDeviceStatus RO Device status Status

hardwarefittedDeviceSubnetMask Operator Subnet Mask Address IP addr

hardwarefittedDeviceSysObjId RO Device system object ID ASCII

hardwarefittedDeviceType RO Component type Name o

hardwarefittedDeviceTypeUnit RO Device type and unit Device

hardwarefittedDeviceUnderConfig Operator Device under configuration Any. S

hardwarefittedDeviceUnitNumber RO Component unit number Driver

hardwarefittedDeviceVersion RO Device version From F

A-16

Table A- 16: Currently Raised Alarms




alarmsClearCounts Superuser Clear alarms Any

Table A- 17: Raised Alarms Table


alarmsBlackoutTimer RO Alarm blackout timer Integer

alarmsCategory RO Alarm category Catego

alarmsInfo RO Alarm information Alarm

alarmsObject RO Alarm object Alarm

alarmsParam1 RO Alarm parameter 1 Alarm

alarmsParam2 RO Alarm parameter 2 “”

alarmsParam3 RO Alarm parameter 3 “”

alarmsSeverity Alarm severity Severit

alarmsText RO Alarm description Alarm

alarmsType RO Alarm type Alarm

RO

A-17



Table A- 18: SMA General


smaCpuIdle RO CPU idle usage Percen

smaCpuSystem RO CPU system usage Percen

smaCpuUser RO CPU user usage Percent

smaDateTime RO Date and time Datesta

smaFanControlVersion RO Fan control versions Version

smaFpgaType RO FPGA type Integer

smaFpgaVersion RO FPGA version Integer

smaLastBootTime RO Last SMC boot time Datesta

smaMemoryFree RO Memory free Kiloby

smaMemoryTotal RO Memory total Kiloby

smaMemoryUsed RO Memory used Kiloby

smaOsVersion RO SMA operating system version Version

smaSmaPowerDown Operator SMA power down Any

smaSmaReset Operator SMA reset “norma

smaSmaResetClear Operator SMA clear configuration and reset “config

smaSmaSoftwareVersion RO SMA software version Version

smaSmcModuleRevision RO SMC module revision Integer

smaUpTime RO SMA uptime Time s

A-18






Manufa

A-20



Table A- 22: Component Versions Table


smaVersionName RO Name of component Descrip

smaVersionValue RO Version number Version

Temperature Control

Table A- 23: Temperature Control Table


temperaturecontrolComponent RO Component Device

temperaturecontrolComponentName RO Name and unit Device

temperaturecontrolComponentUnit RO Component unit Device

temperaturecontrolReading RO Reading Tempe

temperaturecontrolSensor RO Sensor Device

temperaturecontrolTimestamp RO Timestamp Datesta

A-21



Voltage Control

Table A- 24: Voltage Control Table


voltagecontrolComponent RO Component Device

voltagecontrolComponentName RO Name and unit Device

voltagecontrolComponentUnit RO Component unit Device

voltagecontrolReading RO Reading Voltag

voltagecontrolSensor RO Sensor Device

voltagecontrolSensorSubType RO Sensor sub type Device

voltagecontrolTimestamp RO Timestamp Datesta

SNMP

Table A- 25: SNMP General


snmpAuthMgrCreate Superuser Create a new authenticated manager

entry

Supply

snmpCommunityCreate Superuser Creates a new community index Supply

snmpDownloadDestination Operator Destination of transfer /config

snmpDownloadErrorStatus RO Error status "idle",

"aborte

A-22




or "har

snmpDownloadErrorText RO Textual version of error status Text st

snmpDownloadFilename Operator Remote path and filename to downloadto

Filenam63 char

snmpDownloadIndex RO Download Index Only le

snmpDownloadLogMaxSize RO Download log max size “0”

snmpDownloadLogSize RO Download log size “0”

snmpDownloadOctetCount RO Bytes transferred so far The nu

current

snmpDownloadOwnerAddress Operator IP address of requestor IP addr

snmpDownloadOwnerDomain RO Download owner domain “snmpU

snmpDownloadPassesLeft RO Download passes left “1” or

snmpDownloadResetType Operator Reset type after download “warm

snmpDownloadServerAddress Operator FTP/tFTP server IP address & port e.g xxx

snmpDownloadStatus Operator Current status of operation “active

snmpDownloadTDomain RO Download transport domain “snmpU

snmpSelftestResultCode RO Self test result code “ok”, “

snmpSelftestResultText RO Self test result details String

snmpSelftestResultTime RO Self test result time Value ofailure snmpS

snmpSelftestState Operator Self test state flag “stExec

A-23




snmpTrapDestCreate Operator Create new SNMP trap entry Supply

Table A- 26: SNMP Community Table


snmpCommunityIndex RO Identifies this community name entry Integer

snmpCommunityName Superuser Community name for this entry Name s

snmpCommunityReadView Superuser View used for read requests “none”

snmpCommunityStatus Superuser Status of this community entry “Active

snmpCommunityWriteView Superuser View used for write requests none, r

Table A- : SNMP Trap Destinations Table27


snmpTrapDestCommunity RO Trap destination community public

snmpTrapDestDelete Operator Delete SNMP server entry messag

snmpTrapDestFilter RO Trap destination filter Integer

snmpTrapDestFilterCritical Operator Trap destination filter critical “Yes” o

snmpTrapDestFilterInformation Operator Trap destination filter information “Yes” o

snmpTrapDestFilterSnmpTraps Operator Trap destination filter SNMP traps “Yes” o

snmpTrapDestFilterWarning Operator Trap destination filter warning “Yes” o

snmpTrapDestIndex RO Trap destination index Integer

A-24




snmpTrapDestStatus Operator Trap destination status “Active

snmpTrapDestTAddress Operator Trap destination transport address IP addr

snmpTrapDestTDomain Operator Trap destination domain Domain

snmpTrapDestVersion Operator Trap destination version ‘snmpv

Table A- 28: SNMP Authenticated Managers Table


snmpAuthMgrAddress Superuser Manager IP address IP addr

snmpAuthMgrAddressType RO IP

snmpAuthMgrCommunityIndex Superuser Community ID for manager address Integer

snmpAuthMgrDelete Superuser Delete an authenticated manager entry messag

snmpAuthMgrMask Superuser Manager IP mask IP addr

snmpAuthMgrStatus Status of this manager entry “Active

snmpAuthMgrSubIndex RO Index of manager address within a

community

Integer

A-25



B Parts List for the hp Carrier Grade BladeServer bh3710

The following list contains all the parts in the bh3710 designed to be removed and replaced by the customer

Table B- 1: hp Carrier Grade Blade Server bh3710 Parts List

Qty Part No.

Exchange

Part No. Component

A6715-62001 A6715-69003 6 EIA Unit Blade Server Chassis with backplane

2 A6790-62001 A6790-69002 DC Power Supply

1 A6715-04001 A6715-69002 Blade Server Cooling Fan Tray Assembly

2 A6780-60001 A6780-69001 Fibre Channel (FC) and LAN RTM Blade

1-6 5065-7804 A6783-69001 18GB Fibre Channel Disk

1-3 A6711-62001 A6711-69001 FC Disk Carriers

1 to 4 A6709-60001 A6709-69001 256 MB DIMM

1 A6708-62001 A6708-69001 bp2200 Blade (2 slot) (front load only)

1 A6712-60001 A6712-69001 Management Blade

0 to 3 A6707-00014 N/A DIMM Filler

3 to 7 A6474-00161 N/A Compact PCI Slot Blocker (front only)

8 A6474-00162 N/A Compact PCI Slot Blocker (rear only)

2 A6715-63001 N/A DC External Power Input Cable

1

B-1



C Additional Backplane Jumper Positions for the hp Carrier Grade Blade Server bh3710

The following information is available in this Appendix:

• Figure C- 1: Fibre Channel Disk Drive Controller (FCDDC) Address Mapping 0-0

Figure C- 2: Fibre Channel Disk Drive Controller (FCDDC) Address Mapping 0-1


Figure C- 4: SGA0 and SGA1 Jumper Positions

Figure C- 5: Jumper location in rp3710 Fan Tray Assembly Bay

Table C- 1: SGA Configuration Links

•

•

•

• .

•

C-1




C-2




C-3




C-4



Table C- 1: SGA Configuration Links

Unused position for the Jumpers

Address 0/0/2/0.8.0.255.6.xx

C-5

S G A 0

S G A 1

S G A 2

S G A 3

X 1

S G A 0

S G A 1

S G A 2

S G A 3

X 1

Address 0/0/2/0.8.0.255.4.xx

Address 0/0/2/0.8.0.255.2.xx

S G A 0

S G A 1

S G A 2

S G A 3

X 1

Address 0/0/2/0.8.0.255.0.xx

S G

A 0

S G

A 1

S G

A 2

S G

A 3

X 1



Figure C- 4: SGA0 and SGA1 Jumper Positions

C-6



Figure C- 5: Jumper location in rp3710 Fan Tray Assembly Bay.

C-7



D LVM Boot Device Hardware Path Change

D-1

