Administrator's Guide - Hewlett Packardh20628. · 2013-12-23 · HP PC Blade Enclosure Integrated...

Administrator's Guide

HP BladeSystem PC Blade Enclosure IntegratedAdministrator v4.40

© Copyright 2007–2009 Hewlett-PackardDevelopment Company, L.P. Theinformation contained herein is subject tochange without notice.

Microsoft and Windows are trademarks ofMicrosoft Corporation in the U.S. and othercountries.

The only warranties for HP products andservices are set forth in the express warrantystatements accompanying such productsand services. Nothing herein should beconstrued as constituting an additionalwarranty. HP shall not be liable for technicalor editorial errors or omissions containedherein.

This document contains proprietaryinformation that is protected by copyright. Nopart of this document may be photocopied,reproduced, or translated to anotherlanguage without the prior written consent ofHewlett-Packard Company.

User Guide

HP BladeSystem PC Blade EnclosureIntegrated Administrator v4.40

Fourth Edition (May 2009)

Third Edition (January 2009)

Second Edition (February 2008)

First Edition (May 2007)

Document Part Number: 449377–004

About This BookWARNING! Text set off in this manner indicates that failure to follow directions could result in bodilyharm or loss of life.

CAUTION: Text set off in this manner indicates that failure to follow directions could result in damageto equipment or loss of information.

NOTE: Text set off in this manner provides important supplemental information.

ENWW iii

iv About This Book ENWW

Table of contents

1 About This GuideAudience Assumptions ......................................................................................................................... 1Important Safety Information ................................................................................................................ 1Symbols on Equipment ........................................................................................................................ 1Related Documents .............................................................................................................................. 2Getting Help ......................................................................................................................................... 2

Contact HP .......................................................................................................................... 2Support and Troubleshooting .............................................................................................. 2HP Web Site ........................................................................................................................ 2

2 HP PC Blade Enclosure System Software FeaturesHP PC Blade Enclosure Integrated Administrator ................................................................................ 3Integrated Administrator Features ........................................................................................................ 3

Dedicated Local Area Network (LAN) Connectivity ............................................................. 3Simple Network Management Protocol (SNMP) Alerts from Integrated Administrator toa Management Console ....................................................................................................... 4E-mail Alerts from Integrated Administrator to an E-mail Account (AlertMail) ..................... 4Remote Access and Control ................................................................................................ 4User Administration and Security ........................................................................................ 4Automatic Network Configuration ........................................................................................ 5Network Time Protocol (NTP) .............................................................................................. 5SOAP Interface .................................................................................................................... 5Power Reporting .................................................................................................................. 5Enclosure Power Management and Power Redundancy .................................................... 5Integration with the HP Systems Insight Manager Utility ..................................................... 6Integration with HP Session Allocation Manager (SAM) Utility ............................................ 6Event Notification ................................................................................................................. 6

Overview of HP BladeSystem Software Tools ..................................................................................... 6Blade ROM-Based Setup Utility (RBSU) ............................................................................. 6Headless Operation ............................................................................................................. 7ProLiant Essentials Rapid Deployment Pack ...................................................................... 7HP Systems Insight Manager .............................................................................................. 7Enclosure Self Recovery (ESR) ........................................................................................... 7HP PC Blade Enclosure Management System and Utilities ................................................ 7

ENWW v

3 Getting StartedReviewing Configuration Tools and Information ................................................................................... 8Identifying Integrated Administrator Components ................................................................................ 9Determining the Integrated Administrator’s Initial IP Address .............................................................. 9

Requirements for Local Client Devices .............................................................................. 10Default HP BladeSystem PC Blade Switch Accounts and Passwords .............................. 10Default Values for the Integrated Administrator ................................................................. 10Determining the IP Address Using the Local Console ....................................................... 11

Setting Up the Web-Based User Interface ......................................................................................... 12Additional Steps ................................................................................................................................. 14

4 Web Browser InterfaceAccessing the Web-based User Interface .......................................................................................... 15Web-Based Navigation ....................................................................................................................... 16

Top Panel .......................................................................................................................... 16Left Panel ........................................................................................................................... 17Deck Panel ........................................................................................................................ 17

Enclosure Tab .................................................................................................................................... 18Enclosure Information ........................................................................................................ 19Network Configuration ....................................................................................................... 26SNMP Configuration .......................................................................................................... 30Power Readings ................................................................................................................ 32Virtual Buttons ................................................................................................................... 33System Log ........................................................................................................................ 34System Log Policy ............................................................................................................. 34

Enclosure Power Management Tab ................................................................................................... 36Bays Tab ............................................................................................................................................ 37

Bay List .............................................................................................................................. 37Bay Power Consumption ................................................................................................... 39Bay Temperature ............................................................................................................... 40Bay Information .................................................................................................................. 41Remote Console ................................................................................................................ 44Virtual Buttons ................................................................................................................... 45Console Log ....................................................................................................................... 47

Administration Tab ............................................................................................................................. 47User List ............................................................................................................................. 47Group List .......................................................................................................................... 48Add User ............................................................................................................................ 49Add Group ......................................................................................................................... 51View/Modify User ............................................................................................................... 53View/Modify Group ............................................................................................................ 53Update IA Firmware ........................................................................................................... 53Configuration Scripts ......................................................................................................... 54

vi ENWW

Event List Tab .................................................................................................................................... 56Event Log Policy ................................................................................................................ 59

Interconnect Tab ................................................................................................................................ 59

5 Command Line InterfaceAccessing the Command Line Interface ............................................................................................. 63

Accessing Remotely through the Management Connector ............................................... 63Accessing Locally through the Console Connector ........................................................... 63

Operating the Command Line Interface ............................................................................................. 64General Commands ........................................................................................................... 64General Management Commands ..................................................................................... 64User Account Commands .................................................................................................. 68Enclosure Network Configuration Commands ................................................................... 71Enclosure Management Commands ................................................................................. 74Blade PC Bay Management Commands ........................................................................... 80Command Line Event Messages ....................................................................................... 83

Functionality Exclusive to the Command Line Interface ..................................................................... 85

6 Setting Up the SystemUser Permissions ............................................................................................................................... 90Customizing the Enclosure Settings ................................................................................................... 91

Modifying Enclosure and Rack Names .............................................................................. 92Modifying the Asset Tag Number ...................................................................................... 93Modifying the Date and Time ............................................................................................. 94

Setting Up User Accounts .................................................................................................................. 95Adding a Group .................................................................................................................. 95Adding a User .................................................................................................................... 98

Enabling Remote Console Sessions to Blade PCs .......................................................................... 101Setting Up AlertMail .......................................................................................................................... 101

E-mail Alerts .................................................................................................................... 102Setting Up IP Security ...................................................................................................................... 103Setting Up Automatic Network Time Protocol Configuration (NTP) ................................................. 104Configuring SNMP Support .............................................................................................................. 105

Entering a Community String ........................................................................................... 105Modifying the System Location ........................................................................................ 106Modifying the System Contact Information ...................................................................... 106Adding Trap Targets ........................................................................................................ 106Removing Trap Targets ................................................................................................... 107Modifying Trap Policy ...................................................................................................... 107

7 Configuring SOAP Support TasksEnabling SOAP Interface ................................................................................................................. 108Disabling SOAP Interface ................................................................................................................. 108

ENWW vii

Supported SOAP Interface Commands ........................................................................................... 109

8 Performing Common Administrative TasksManaging Blade PC Bays ................................................................................................................ 110

Opening a Remote Console Session to a Blade PC ....................................................... 110Accessing the ROM-Based Setup Utility for a blade PC ................................................. 111Reviewing Activity for a Blade PC ................................................................................... 113Powering Off the Blade PC .............................................................................................. 113Identifying a Blade PC Using the Unit Identification LED ................................................ 114

Managing the Enclosure ................................................................................................................... 116Reviewing the Activity of the Enclosure ........................................................................... 116Identifying the Enclosure Using the Unit Identification LED ............................................. 118Generating an Enclosure Summary ................................................................................. 119Identifying Problem Components ..................................................................................... 120

Managing Users ............................................................................................................................... 125Modifying a User’s Rights to Blade PC Bays ................................................................... 125

Creating a New Group with the Updated Access Rights ................................. 125Modifying Group Rights to Blade PC Bays ..................................................... 125

Disabling and Deleting User Accounts ............................................................................ 127Deleting a User Account ................................................................................. 128Deleting Group Accounts ................................................................................ 129

9 Performing Advanced FunctionsReplicating the Configuration of the Integrated Administrator .......................................................... 132Administering Security Certificates ................................................................................................... 132

Creating a Certificate Request ......................................................................................... 133Downloading a Security Certificate .................................................................................. 133

Key-Based SSH Authentication ........................................................................................................ 133Configuring Blade PC Boot Order .................................................................................................... 134Powering Off the Enclosure .............................................................................................................. 135Disabling Network Protocols ............................................................................................................ 136Upgrading the Integrated Administrator Firmware ........................................................................... 137

Configuring the Update Feature ...................................................................................... 137Recovering a Lost Administrator Password ..................................................................................... 138Launching Flash Disaster Recovery ................................................................................................. 139

Appendix A Command Line Conventions

Appendix B Error MessagesWarning Messages ........................................................................................................................... 142

Enclosure Warning Messages ......................................................................................... 142Blade PC Warning Messages .......................................................................................... 143Administration Warning Messages .................................................................................. 143

viii ENWW

Error Messages ................................................................................................................................ 144Enclosure Error Messages .............................................................................................. 144Blade PC Bay Error Messages ........................................................................................ 144Administration Error Messages ........................................................................................ 144

Appendix C Blade PC Diagnostic Messages

Appendix D Maskable Enclosure System Log Messages

Appendix E Maskable Enclosure Event Messages

Appendix F Troubleshooting

Appendix G Event Icons and Details

Appendix H Power Management and Redundant Power Supply

Appendix I Factory Default SettingsEnclosure ......................................................................................................................................... 162Users ................................................................................................................................................ 163Groups .............................................................................................................................................. 164Network ............................................................................................................................................ 164Protocol ............................................................................................................................................ 164

Appendix J Time Zone SettingsUniversal .......................................................................................................................................... 165Africa ................................................................................................................................................ 166Asia .................................................................................................................................................. 166Europe .............................................................................................................................................. 167Oceania ............................................................................................................................................ 168Polar ................................................................................................................................................. 169Americas .......................................................................................................................................... 169

Appendix K Open Source Availability

Appendix L Supported SNMP Traps

Index ................................................................................................................................................................. 175

ENWW ix

x ENWW

1 About This Guide

Audience AssumptionsThis guide is for the person who installs, administers, and troubleshoots HP Blade PC solutions. HPassumes you are qualified in the servicing of computer equipment and trained in recognizing hazardsin products with hazardous energy levels.

Important Safety InformationWARNING! Before installing this product, read the Important Safety Information document includedwith the system.

Symbols on EquipmentThe following symbols may be placed on equipment to indicate the presence of potentially hazardousconditions:

Table 1-1 Equipment Symbols Indicating Potentially Hazardous Conditions

This symbol, in conjunction with any of the following symbols, indicates the presence of a potentialhazard. The potential for injury exists if warnings are not observed. Consult your documentationfor specific details.

This symbol indicates the presence of hazardous energy circuits or electric shock hazards. Referall servicing to qualified personnel.

WARNING: To reduce the risk of injury from electric shock hazards, do not open this enclosure.Refer all maintenance, upgrades, and servicing to qualified personnel.

This symbol indicates the presence of electric shock hazards. The area contains no user or fieldserviceable parts. Do not open for any reason.

WARNING: To reduce the risk of injury from electric shock hazards, do not open this enclosure.

This symbol on an RJ-45 receptacle indicates a network interface connection.

WARNING: To reduce the risk of electric shock, fire, or damage to the equipment, do not plugtelephone or telecommunications connectors into this receptacle.

This symbol indicates the presence of a hot surface or hot component. If this surface is contacted,the potential for injury exists.

WARNING: To reduce the risk of injury from a hot component, allow the surface to cool beforetouching.

ENWW Audience Assumptions 1

These symbols, on power supplies or systems, indicate that the equipment is supplied by multiplesources of power.

WARNING: To reduce the risk of injury from electric shock, remove all power cords to completelydisconnect power from the system.

This symbol indicates that the component exceeds the recommended weight for one individualto handle safely.

WARNING: To reduce the risk of personal injury or damage to the equipment, observe localoccupational health and safety requirements and guidelines for manual material handling.

Related DocumentsFor additional information on the topics covered in this guide, refer to the following documents:

● Network Considerations Guide white paper

● QuickSpecs

● Setup and Installation Guide: HP BladeSystem bc2000 and bc2500 Blade PC and PC BladeEnclosure

● Setup and Installation Guide: HP BladeSystem bc2200 and bc2800 Blade PC and HP BladeSystemPC Blade Enclosure G2

● HP Rack 9000 and 10000 Series installation and best practices white paper

● Installation Guide: HP BladeSystem PC Blade Switch

● Command Line Interface Reference Guide: HP BladeSystem PC Blade Switch

● Embedded Web System User Guide for the HP BladeSystem PC Blade Switch

Getting HelpIf you have a question about the HP PC Blade Enclosure and have exhausted the information in thisguide, you can get additional information and other help in the following locations:

Contact HPThe Contact HP Web site provides various ways to contact HP, including online chat, e-mail, andtelephone. Access this Web site at http://welcome.hp.com/country/us/en/contact_us.html.

Support and TroubleshootingThe HP Support and Troubleshooting Web site allows you to download software and drivers and searchfor support and troubleshooting information for specific products. Access this Web site athttp://welcome.hp.com/country/us/en/support.html?pageDisplay=support.

HP Web SiteThe HP Web site has information on this product as well as the latest drivers and flash ROM images.You can access the HP Web site at http://www.hp.com.

Table 1-1 Equipment Symbols Indicating Potentially Hazardous Conditions (continued)

2 Chapter 1 About This Guide ENWW

http://welcome.hp.com/country/us/en/contact_us.html

http://welcome.hp.com/country/us/en/support.html?pageDisplay=support

http://www.hp.com

2 HP PC Blade Enclosure SystemSoftware Features

The HP BladeSystem offers an extensive set of features and optional tools to support effective bladePC management and software deployment. This chapter describes the HP PC Blade EnclosureIntegrated Administrator and provides a brief overview of software associated with the system.

HP PC Blade Enclosure Integrated AdministratorThe HP PC Blade Enclosure Integrated Administrator is a centralized management and monitoringsystem for the HP PC Blade Enclosure and blade PCs. The Integrated Administrator acts as acombination console server and remote power controller, enabling in-band (default) or out-of-band,secure, serial console connections to all blade PCs in the enclosure.

The Integrated Administrator provides enclosure health, blade health, and enables remote blademanageability. Integrated Administrator features can be accessed from any network-based client. TheIntegrated Administrator can provide remote access to any authorized network client, sends alerts, andprovides many other blade PC management functions.

The Integrated Administrator subsystem is embedded on a module included with each interconnect trayand includes an intelligent microprocessor, secure memory, and a dedicated network interface that canbe configured for either in-band (default) or out-of-band remote access. This design makes theIntegrated Administrator independent of the host blade PC and its operating system.

Integrated Administrator FeaturesThe following subsections describe Integrated Administrator functions that deliver management of theenclosure and blade PCs.

Dedicated Local Area Network (LAN) ConnectivityEach Integrated Administrator provides a dedicated network connection. The uplink port 42 can auto-select speeds between 10 Mbps and 100 Mbps. When the PC Blade Switch (optional) is installed, bydefault the Integrated Administrator is configured to route through a Gigabit uplink connector usingVirtual LANs (VLANs), eliminating the need for a separate management network.

NOTE: The default configuration for the HP BladeSystem PC Blade Switch option has the dedicatedIA port and both uplink ports 45 and 46 in the same VLAN.

ENWW HP PC Blade Enclosure Integrated Administrator 3

Simple Network Management Protocol (SNMP) Alerts from IntegratedAdministrator to a Management Console

The Integrated Administrator provides notification of enclosure problems. Using a management console,you can access various alerts, such as hardware health and status change events, using SNMP traps.

The CPQRACK.MIB file contains HP-specific SNMP Object Identifiers (OIDs) and traps for managingthe enclosure infrastructure and blades. The Integrated Administrator 4.4 implements support forCPQRACK version 1.12.

E-mail Alerts from Integrated Administrator to an E-mail Account(AlertMail)

AlertMail enables the Integrated Administrator to send system events by e-mail instead of using SNMPtraps. AlertMail is completely independent of SNMP, and both can be enabled at the same time. AlertMailuses standard Simple Mail Transfer Protocol (SMTP) commands to communicate with any SMTPcapable mail server or in addition to SMTP relay agent.

Remote Access and ControlThe Integrated Administrator provides remote functionality to access a limited text-only console of thehost blade PC, change the state of the Unit Identification LED on an enclosure or any of its blade PCs,and power up, power down, or reboot a blade PC or groups of blade PCs.

The Integrated Administrator displays alerts regardless of the state of the blade PC and can integratewith industry standard SNMP management tools such as HP Systems Insight Manager using SNMPversion 1 to provide alerts and diagnostics for the system.

If a blade PC does not respond, this feature enables an administrator to initiate a cold reboot to bringthe blade PC back online. The Integrated Administrator can be used to remotely operate a power buttonor Unit Identification LED (UID) of any blade PC within the enclosure.

The Integrated Administrator is fully accessible by common Web browsers. The Integrated Administratoralso has a command line interface (CLI) accessible using Secure Shell (encrypted) or Telnet(unencrypted) protocols, providing extensive management capability to remote network users. Localusers can access the CLI by attaching a client computer (using a terminal emulator) to the IntegratedAdministrator’s console (RS-232 serial) port.

NOTE: With a Telnet session, all data - including passwords - are passed as clear text.

User Administration and SecurityThe Integrated Administrator supports up to 25 users with customizable access rights and login names.Groups are first assigned bays, and then users are given membership to those groups. This group-centered methodology is designed to facilitate user management across blade PCs.

The Integrated Administrator provides strong security for remote management in distributed ITenvironments by using industry standard Secure Sockets Layer (SSL) encryption of HTTP datatransmitted across the network. SSL encryption (up to 128-bit) ensures that the HTTP information issecure as it travels across the network. You can encrypt all remote console data as well.

4 Chapter 2 HP PC Blade Enclosure System Software Features ENWW

The Integrated Administrator provides secure password encryption, tracking all login attempts andmaintaining a record of all login failures. The Integrated Administrator also provides the followingadditional security features:

● User actions logged in the Integrated Administrator System Log

● Login legal warning

IP Security allows an administrator to define a set of IP addresses that are the only ones allowed toconnect to the services provided (Secure Shell (SSH), HTTP, Hypertext Transfer Protocol over SecureSocket Layer (HTTPS), Telecommunications network (TELNET), SNMP). This means that anadministrator can make sure only a certain set of machines have access to the Integrated Administrator.

Automatic Network ConfigurationThe Integrated Administrator provides automatic network configuration of the IP address and host nameusing Dynamic Host Configuration Protocol (DHCP) and Dynamic DNS/WINS. The IntegratedAdministrator comes with a default name and DHCP client that leases an IP address from the DHCPserver on the network. For networks that do not use DHCP, the Integrated Administrator can use a staticIP configuration.

Network Time Protocol (NTP)Automatic time configuration allows the Integrated Administrator to synchronize its date and time witha compatible Network Time Protocol (NTP) Time Server.

SOAP InterfaceThe Integrated Administrator provides a handful of commands via the Simple Object Access Protocol(SOAP) interface for manageability tools that utilize SOAP. This interface provides a handful ofcommands for inventory and power management of the enclosure and blades managed by the IA. AllAdministrator access level accounts can use the SOAP interface, and it is enabled using a commandline (CLI) command or the graphical user interface (GUI).

Power ReportingThe Integrated Administrator collects power measurements from bc2000, bc2200, bc2500, and bc2800blades and reports them via the CLI and GUI. These blades self measure using hardware measurementcomponents specifically in the bc2000, bc2200, bc2500, and bc2800 blades. Using thesemeasurements, a +-10% estimate of power consumption for the enclosure is calculated. Additionally,the BladeSystem PC Blade Enclosure G2 utilizes new self-measuring power supplies that are used tocalculate a measured, rather than estimated, power consumption. The overall enclosure powerconsumption estimate can be collected by the CLI, GUI, and SOAP interface.

Enclosure Power Management and Power RedundancyThe IA will attempt to ensure all blades, regardless of blade type, continue to run at full power in theevent of a loss of a single power supply.

PC Blade Enclosure G2 enclosures running with a line voltage of ≥200V are always AC redundant.

For PC Blade Enclosures or PC Blade Enclosure G2 enclosures running at <200V, the IA will allowblades to continue to run full speed after the loss of a power supply as long as the blade populationdoesn’t exceed the maximum redundant power budget. The IA reports a value for the maximumredundant, resilient, and total capacity and uses that in power managing the enclosure. These values

ENWW Integrated Administrator Features 5

are compared to the allocated power budget which is based on blade configuration to determine theappropriate course of action for ensuring enclosure power supply redundancy.

For more information, see Power Management and Redundant Power Supply on page 160.

Integration with the HP Systems Insight Manager UtilityThe Integrated Administrator provides full integration with the HP Systems Insight Manager utility underkey operating environments. This integration provides:

● Support for SNMP management—Support for SNMP trap delivery to a HP Systems InsightManager console

● Management processor—The HP Systems Insight Manager utility adds support for a new devicetype, the management processor. All Integrated Administrators (in HP PC Blade Enclosure) on thenetwork are discovered in the HP Systems Insight Manager utility as management processors. Themanagement processors are associated with the blade PCs they manage.

● The Integrated Administrator hyperlinks—The HP Systems Insight Manager utility provides ahyperlink on the blade PC device page to launch and connect to the Integrated Administrator.

● Grouping of Integrated Administrator processors—All Integrated Administrator managementprocessors can be grouped together logically and displayed on one page in HP Systems InsightManager. This capability provides access to all Integrated Administrators on the network from onepoint in HP Systems Insight Manager.

For more information on the HP Systems Insight Manager utility, refer tohttp://h18013.www1.hp.com/products/servers/management/hpsim/index.html. For configuringyour deployment for SNMP, please consult the Network Considerations white paper.

Integration with HP Session Allocation Manager (SAM) UtilityThe Integrated Administrator provides features for the HP Session Allocation Manager software tomanage and report on the hardware. HP SAM leverages the SOAP interface that can gather powerreporting data or power cycle the blades within the enclosure. The Integrated Administrator has a built-in account that is provided for ease of implementing within a deployment that uses HP SAM. This accountis disabled by default.

Event NotificationThe Integrated Administrator provides real-time event notifications for an enclosure. When an eventoccurs, the Integrated Administrator notifies connected users by generating an event text message inthe command line interface (CLI) or via text and selectable icon within the event log page in the GUIthat the user can click to view more details.

Overview of HP BladeSystem Software ToolsThe following subsections described tools and utilities supported by the HP BladeSystem blade PCsystems to facilitate monitoring and management of the enclosure.

Blade ROM-Based Setup Utility (RBSU)The Blade RBSU (F10) performs a wide range of configuration activities and provides access tonumerous settings, including those for system devices, operating system selection, and boot controller

6 Chapter 2 HP PC Blade Enclosure System Software Features ENWW

http://h18013.www1.hp.com/products/servers/management/hpsim/index.html

order. RBSU (F10) is also fully compatible with remote serial console mode using the IntegratedAdministrator.

Headless OperationHP bc-series blade PCs include Video Graphics Array (VGA), keyboard, mouse, and Universal SerialBus (USB) interfaces; however, these blade PCs are designed primarily for headless operation andmanagement with no keyboard or monitor attached.

ProLiant Essentials Rapid Deployment PackThe ProLiant Essentials Rapid Deployment Pack features a graphical deployment console, whichprovides intuitive drag-and-drop events, such as scripts and images, to deploy the operating systemsand applications on any combination of blade PCs installed in the enclosures.

With the Rapid Deployment Pack, users can automatically install pre-defined configurations on newlyinstalled blade PCs. For more information about the Rapid Deployment Pack, refer to an authorizedreseller, the Rapid Deployment CD that ships with the enclosure, or go to http://www.hp.com/go/rdp.

HP Systems Insight ManagerHP Systems Insight Manager is a software utility designed for collecting blade PC information, includingfault conditions, performance, security, remote management, and recovery services. The HPBladeSystem is fully compatible with the HP Systems Insight Manager utility.

Enclosure Self Recovery (ESR)ESR is a self-monitoring reliability feature of the Integrated Administrator. If the Integrated Administratordoes not boot or hangs during operation, ESR automatically resets the Integrated Administrator for anattempted self-recovery. The blade PCs and interconnect tray are not affected by ESR.

HP PC Blade Enclosure Management System and UtilitiesThe HP PC Blade Enclosure Management System and Utilities provide a full suite of configuration andmanagement interfaces and tools for the HP PC Blade Enclosure (option). Both Web and consoleinterfaces are provided for management of the interconnect switch and enclosure.

You can configure both interfaces to require a valid user name and password for authentication. RemoteNetwork Monitoring (RMON) (for the switch) and SNMP manageability are supported. You can alsosave the interconnect switch configuration to a Trivial File Transfer Protocol (TFTP) server as backupsand as templates for preconfiguring other switches.

ENWW Overview of HP BladeSystem Software Tools 7

http://www.hp.com/go/rdp

3 Getting Started

The HP PC Blade Enclosure Integrated Administrator enables monitoring and management of allfunctions within an enclosure, including functions specific to the blade PCs housed within it. Onceconfigured, the Integrated Administrator provides these features through both a Web-based userinterface and CLI.

This chapter addresses first-time configuration of the Integrated Administrator after the enclosure isinstalled and powered up in a rack:

● Reviewing configuration tools and information

● Identifying the Integrated Administrator connectors

● Determining the Integrated Administrator initial IP address

● Setting up the Web-based user interface

● Additional steps

● Help

Reviewing Configuration Tools and InformationThe Integrated Administrator is ready for operation immediately after powering up. The followingfeatures and information are designed to facilitate the setup and management of the IntegratedAdministrator:

● Each Integrated Administrator ships with a unique preconfigured Administrator password and hostname.

● If the network uses Dynamic Domain Name System (DNS) or Windows® Internet Name Service(WINS), you can access the Integrated Administrator using the factory-configured host name.

NOTE: The preconfigured Administrator password and host name are displayed on theIntegrated Administrator Default Network Settings Tag (settings tag) attached to the interconnecttray.

● If the network uses Dynamic Host Configuration Protocol (DHCP), an IP address can beautomatically assigned to the Integrated Administrator.

● The blade PC health service (if installed on the blade) provides the Integrated Administrator withthe name as defined within the operating system of the blade PC and operating system type foreach blade PC.

8 Chapter 3 Getting Started ENWW

CAUTION: Without an Advanced Configuration and Power Interface- (ACPI) compliant operatingsystem, the Integrated Administrator cannot gracefully shut down a blade PC. This condition may resultin the permanent loss of critical data.

Identifying Integrated Administrator ComponentsEach HP PC Blade Enclosure interconnect tray ships with the Integrated Administrator module alreadyinstalled and provides external connectivity using two connectors on the rear panel.

Table 3-1 Integrated Administrator Rear Panel Components

Item Description

1 Management (10/100 Ethernet) connector for remote access through a Web-based user interface, Telnet,or Secure Shell.

2 Console (serial) connector for local access to the command line interface using a laptop computer.

3 Integrated Administrator reset button.

4 Integrated Administrator health LED

5 Enclosure Unit Identification button/LED

6 Fan cage health status LED

7 Power button/ status LED combination

Determining the Integrated Administrator’s Initial IPAddress

HP recommends that you connect a local client device, such as a laptop computer, to the console (serial)connector in order to determine the initial IP address used by the network to recognize the IntegratedAdministrator. After using that IP address to access the Integrated Administrator locally using theconsole (serial) connector, you can use the Integrated Administrator default values to complete the initialconfiguration.

ENWW Identifying Integrated Administrator Components 9

The organization of this section reflects this process:

● Requirements for local client devices

● Default values for the Integrated Administrator

● Determining the IP address using the local console

Requirements for Local Client DevicesYou can access the Integrated Administrator locally using the serial connector on the rear panel of theenclosure using a local client device, such as a laptop computer. The local client device must run aterminal emulator, such as HyperTerminal for Windows systems or Kermit for Linux systems.

The terminal emulator must operate at the following settings:

● Bits per second: 9600

● Bits: 8

● Parity: None

● Stop bits: 1

● Flow control: none

● Emulation: VT100

● Backspace key sends Ctrl-H

Default HP BladeSystem PC Blade Switch Accounts and PasswordsThe HP BladeSystem PC Blade Switch, part number PX829AW and PX830AW has one account:

Username: switch

Default Password: switcha

The ProLiant BL e-Class C-GbE Interconnect Switch, part number 243283-B21 and the HP e-ClassGbE Switch, part number DW367A has two default accounts. Each account corresponds to one of itstwo unique integrated switches:

● Username: switcha

Default Password: switcha

● Username: switchb

Default Password: switchb

Default Values for the Integrated AdministratorThe Integrated Administrator is configured with a default user name, password, and DNS name. Asettings tag with the preconfigured values is attached to the interconnect tray containing the Integrated


Administrator module. There is also a built-in administrator account for SOAP access, which is disabledby default.

Username: SAM

Default Password: SamUser123

NOTE: This administrator privileged account is disabled by default. You cannot login using thisaccount until you enable the SAM account.

It is important that the account password is changed from the default account password if the accountis enabled prior to normal usage by HP SAM. Lastly, the SOAP interface for all other accounts is disabledby default, but is always enabled for the SAM account.

NOTE: For security reasons, HP recommends changing the Administrator account password afteraccessing Integrated Administrator for the first time.

Because there is an eight-character limit to the password that is selectable, the password cannot bechanged back to the default password via the command if you change it.

Determining the IP Address Using the Local ConsoleTo determine the Integrated Administrator IP address using the local console perform the followingsteps:

1. Access the Integrated Administrator console:

a. Connect a local client device (such as a laptop computer) with VT100 terminal emulationsoftware to the Integrated Administrator (serial) console connector using a null modem serialcable.

b. Open a terminal emulation session with the following settings: 9600 bps, 8 data bits, no parity,and 1 stop bit.

c. Log into the Integrated Administrator using the password on the settings tag attached to theinterconnect tray.

2. Establish the Integrated Administrator IP address.

For a detailed explanation of the command line conventions used in this document, see CommandLine Conventions on page 141.

If a DHCP server is attached to the network, determine the Integrated Administrator IP address.Type the following command at the command line interface:

SHOW NETWORK

If a DHCP server is not attached to the network, type the following command to assign a static IPaddress to the Integrated Administrator:

SET IPCONFIG STATIC <IP address> <subnet mask> {<gateway> {<DNS1 address> {<DNS2 address>}}}

You can now access the Integrated Administrator using a Web browser, Secure Shell, Telnet, orSNMP.

CAUTION: All settings are immediate and can only be manually restored.

ENWW Determining the Integrated Administrator’s Initial IP Address 11

Setting Up the Web-Based User InterfaceTo set up the Web-based user interface, proceed as follows:

1. Type the Integrated Administrator IP address or DNS name in the address bar of the Web browser.A security alert displays as shown below.

If you click Yes, the browser continues to the Login window of Integrated Administrator. The alertmessage appears each time you access the Integrated Administrator management processor in abrowser.

If you click No, you are returned to what was previously displayed on your browser.

If you click View Certificate, a popup window displays the certificate information. Installing thecertificate to your browser prevents the security alert message from displaying in the future.

NOTE: To install your own certificate onto the Integrated Administrator rather than theautomatically generated certificate, see the information on certificate-related commands inAdministering Security Certificateson page 132.

If the certificate is removed from your browser, the security alert message is displayed again.

2. Install the certificate to your browser:

a. Click Install Certificate. The Certificate Manager Import Wizard starts.

b. Click Next.

c. Click Next for the browser to automatically select the certificate store when the CertificateStore window appears.

d. Click Finish when the Completing the Certificate Manager Import Manager Wizard windowdisplays.

e. Click Yes to confirm the installation of the certificate when the confirmation window displays.


3. The Account Login screen (shown below) prompts you for a user name and password. Use thedefault user name and password from the settings tag attached to the interconnect tray, and thenclick Log In.

After the default user name and password have been verified, the summary window appears.

The Integrated Administrator summary window provides general information about the IntegratedAdministrator, such as the user currently logged on, enclosure name and status, and IntegratedAdministrator IP address and name.

ENWW Setting Up the Web-Based User Interface 13

Additional StepsHP recommends performing the following tasks:

● Change the Administrator account password

● Set the date and time

● Name the enclosure and rack

● Set up groups, users, and access privileges

For detailed instructions on performing these tasks, see the appropriate sections in Setting Up theSystem on page 89.


4 Web Browser Interface

This chapter provides information for navigating the Integrated Administrator Web-based user interface:

NOTE: Values appearing in the screens of this chapter are for illustrative purposes only.

Accessing the Web-based User InterfaceAccessing the Web-based user interface is not supported from the console (serial) connector.

To access the Integrated Administrator Web-based user interface with HTTP:

1. Get the DNS name from the settings tag attached to the interconnect tray.

2. Open a Web browser and type the IP address or DNS name for the enclosure to access.

CAUTION: If your network does not provide DHCP and either Dynamic DNS or WINS services,you need to configure a static IP address. See Determining the IP Address Using the LocalConsoleon page 11.

3. Type the user name and password at the Login prompt.

ENWW Accessing the Web-based User Interface 15

Web-Based NavigationThe Web-based user interface displays information and receives input in the following areas:

● Top panel

● Left panel

● Deck panel

Top PanelThe following illustration shows the location of the top panel.

The top panel information is displayed at all times, including the following items:

● Enclosure name

● Current user

● Tabs

The Integrated Administrator top panel provides real-time event notifications for an enclosure accordingto two categories: caution and critical. When an event occurs, the Integrated Administrator notifies theuser by generating an icon that the user can click to view more details:

Table 4-1 Event Notification Icons

Icon Description

Unknown Event

Informational

Minor Event

Caution

Warning

Critical

Two buttons appear on the top panel:

● Summary View—Opens a separate window that shows enclosure status and configurationinformation for cutting and pasting purposes.

● Log Out—Logs you out of the Web-based user interface.

16 Chapter 4 Web Browser Interface ENWW

Left PanelThe following illustration shows the location of the left panel.

The left panel displays which screens are available under each tab. Information appearing in the leftpanel depends on which tab the user chooses from within the top panel.

Deck PanelThe following illustration indicates the position of the deck panel.

ENWW Web-Based Navigation 17

The deck panel displays the areas of information provided by the available screens under each tab.Information appearing in the deck panel depends on the option chosen by the user from within the toppanel and the left panel.

Enclosure TabThe Enclosure tab provides access to the following screens:

● Enclosure Information

● Network Configuration

● SNMP Configuration

● Power Readings

● Virtual Buttons

● System Log

● System Log Policy

● Enclosure Power Management


Enclosure InformationAll users have read access to the information in this screen:

● Status

● Temperature

● Power

● General

● Integrated Administrator

● Network

● Date and Time

The following illustration shows the information presented on the Enclosure Information screen (statusarea).

ENWW Enclosure Tab 19

The Enclosure Information screen enables an enclosure administrator account with administratorprivileges to update/observe the global configuration for the enclosure, such as the rack name, enclosurename, asset tag, time zone, date, time, status and general information.

Two buttons appear on the Enclosure Information screen:

● Apply—Saves changes made to the screen.

● Cancel—Restores all fields on the screen to their original values.

The following table describes the information displayed in the areas that comprise the EnclosureInformation screen.

Table 4-2 Enclosure Information Field Descriptions—Status Area

Field Possible Values Description

Enclosure Name Maximum 32 characters including allalphanumeric, dash, and underscorecharacters.

Name of enclosure.

Only enclosure administrators have writeaccess to this field.

For the default enclosure name, see FactoryDefault Settings on page 162.

Rack Name Maximum 32 characters including allalphanumeric, dash, and underscorecharacters.

Name of rack.


For the default rack name, see Factory DefaultSettings on page 162.

Enclosure Status OK, Degraded, or Failed. Status of the enclosure.

Fan Status Redundant or non-redundant. Redundant: all fans are functional. Non-redundant: at least one fan is not functional.

Fan #1–Fan #4

Fan Cage fans

OK, Standby, Degraded, Failed, or Testing.Percentage of full fan speed.

Status of fans 1 through 4.

Fan Spare Number The spare number for the fans installed in theenclosure.

Fan #5–Fan #6

Power Supply fans

NOTE: HP BladeSystemPC Blade Enclosure G2enclosures only

OK, Standby, Degraded, Failed, or Testing.Percentage of full fan speed.

Status of power supply fans 5 and 6.

Power Supply Fan SpareNumber

The spare number for the fans installed in thepower supplies.


Figure 4-1 Enclosure Information-Temperature Area

Table 4-3 Enclosure Information Field Descriptions—Temperature Area


Chassis Temperature OK, Warm, Caution, or Critical. Enclosure component temperaturesensor.

Fan Exhaust Temperature OK, Warm, Caution, or Critical. Enclosure component temperaturesensor.

Blade Bays Temperature OK, Warm, Caution, or Critical. Enclosure component temperaturesensor.

Interconnect Tray Temperature OK, Warm, Caution, or Critical. Enclosure component temperaturesensor.

Power Supply Bay 1 InternalTemperature

OK, Warm, Caution, or Critical. Enclosure component temperaturesensor.

Power Supply Bay 2 InternalTemperature

OK, Warm, Caution, or Critical. Enclosure component temperaturesensor.

Power Supply Bay 1 Inlet Temperature OK, Warm, Caution, or Critical. Enclosure component temperaturesensor.

Power Supply Bay 2 Inlet Temperature OK, Warm, Caution, or Critical. Enclosure component temperaturesensor.

NOTE: Power supply sensors are only supported by the HP BladeSystem PC Blade Enclosure G2.


Figure 4-2 Enclosure Information-Power Area

Table 4-4 Enclosure Information Field Descriptions—Power Area


Power Subsystem Status Redundant, Resilient, Resilient(throttling), Non-redundant, Non-redundant (throttling).

Redundant: both power supplies arefunctional.

Resilient: blades may throttleperformance due to power supply failure/loss.

Resilient (throttling): all bladespreemptively throttled to preventenclosure or blade shutdown due topower supply loss; total blade populationhas exceeded the resilient powercapacity.

Non-redundant: one power supply is notfunctional or allocated capacity hasexceeded resilient capacity.

Non-redundant (throttling): Loss of apower supply has occurred; all bladesare now throttled to ensure they meet thebudgeted power capacity for a singlesupply; total blade population hasexceeded the redundant power capacity.

Total Capacity Watts. Total capacity of the power supplies.



Power Supply #1 and #2 Status OK, Degraded, or Failed. Status of power supply #1 and powersupply #2.

AC Input #1 and #2 Status OK, Degraded, or Failed. Status of AC input to power supply #1and AC input to power supply #2.

Power Supply #1 and #2 Current InputRange

NOTE: For G2 enclosure only

Low, Medium or High The current input voltage range forpower supplies #1 and #2.

Power Supply Spare Number The spare number for the power suppliesinstalled in the enclosure.

Figure 4-3 Enclosure Information

Table 4-5 Enclosure Information Field Descriptions—General Area


Enclosure Type Enclosure product type.

Part Number Part number for the enclosure.

Serial Number Serial number for the enclosure.

Asset Tag Maximum 31 characters including allalphanumeric, dash, and underscorecharacters

Asset tag


For the default asset tag value, seeFactory Default Settings on page 162.

Table 4-4 Enclosure Information Field Descriptions—Power Area (continued)



Interconnect Tray Type HP PC Blade Enclosure InterconnectSwitch

HP PC Blade Enclosure RJ-45Interconnect Patch Panel

Type of interconnect tray.

Interconnect Tray Part Number Part number for the interconnect tray.

Interconnect Tray Spare Number Spare number for the interconnect tray.

Interconnect Tray Serial Number Serial number for the interconnect tray.

Blade Auto Power On Feature Enabled or Disabled If enabled, the enclosure IA willautomatically power on blades wheninserted or when AC cycle is applied tothe enclosure. When disabled, bladeswill not automatically power on wheninserted.

Enabled by default.

Auto Power On Delay 1 to 60 minutes The feature delays the automatic power-on and/or allowance of powering onblades by a programmable amount oftime after an enclosure is powered on.

Default is 4 minutes.

This is global setting which affects theinitial auto power on of all blades.

Table 4-6 Enclosure Information Field Descriptions—Integrated Administrator Area


Hardware Version Hardware version of the IntegratedAdministrator of the enclosure.

Software Version Software version of the IntegratedAdministrator of the enclosure.Additionally, build version is displayed.

Table 4-7 Enclosure Information Field Descriptions—Network Area


IP Address ###.###.###.###, where ### rangesfrom 0 to 255.

The IP address of the IntegratedAdministrator.

DHCP Enabled or Disabled. Shows the status of the Dynamic DNS

This field appears only if DHCP isenabled.

MAC Address ##:##:##:##:##:## where ## ranges from00 to FF.

The MAC address of the IntegratedAdministrator.

Table 4-5 Enclosure Information Field Descriptions—General Area (continued)


Figure 4-4 Enclosure Information (continued)

Table 4-8 Enclosure Information Field Descriptions—Date and Time Area


Time Zone Drop-down box with standard time zoneslisted

Time zone assigned to the enclosure

For the default time zone, see FactoryDefault Settings on page 162.

For a list of all supported time zones,see Time Zone Settings on page 165.

For a detailed description of how to setthe time zone of the enclosure to a valuenot listed in the drop down box, selectOther.

For additional information, seeTroubleshooting on page 155.

Date mm/dd/yy The date assigned to the enclosure

Time hh:mm (24-hour format) The time assigned to the enclosure

Only enclosure administrators have access to the Date and Time information. If those fields are notbeing modified, the Integrated Administrator updates these fields every 20 seconds. If automatic timeconfiguration is enabled, the date and time fields are grayed out and cannot be modified.

If you select Other for time zone, use the following window to set a user-defined time zone:


Three buttons appear on this window:

● Apply—Applies the new time zone.

● Reset—Clears the time zone text box.

● Cancel—Cancels all changes and closes the window.

For more information on accepted time zones, refer to Time Zone Settings on page 165.

Network ConfigurationNOTE: Only enclosure administrators have access to these settings.

The Network Configuration screen (shown below) enables the enclosure administrator to modify thenetwork settings of an enclosure. These settings are specific to the enclosure and do not affect thenetwork configurations for blade PCs.


Two buttons appear at the bottom of this screen:



CAUTION: Both the Web and Secure Shell protocols must be enabled to allow access to the Web-based user interface.

The following table describes the information displayed in the areas that comprise the NetworkConfiguration screen.

Table 4-9 Network Configuration Field Descriptions—Information Area


IP Address The IP address of the IntegratedAdministrator.

MAC Address The MAC address of the IntegratedAdministrator.

Table 4-10 Network Configuration Field Descriptions—Protocols Area


Web (HTTP/HTTPS) Enabled or Disabled. The default setting is Enabled.

SNMP Enabled or Disabled. The default setting is Enabled.



Secure Shell Enabled or Disabled. The default setting is Enabled.

Telnet Enabled or Disabled. The default setting is Enabled.

SOAP Enabled or Disabled. The default setting is Disabled.

Table 4-11 Network Configuration Field Descriptions—Network Area


DHCP Gets the IP address of the IntegratedAdministrator from the DHCP.

Static IP Sets a static IP address of the IntegratedAdministrator.

Dynamic DNS Determines whether the IntegratedAdministrator uses Dynamic DNS.

IP Address ###.###.###.###, where ### rangesfrom 0 to 255.

Static IP address for the IntegratedAdministrator (mandatory if Static IP isselected).

Subnet Mask ###.###.###.###, where ### rangesfrom 0 to 255.

Subnet mask for the IntegratedAdministrator (mandatory if Static IP isselected).

Gateway Address ###.###.###.###, where ### rangesfrom 0 to 255.

Gateway address for the IntegratedAdministrator (optional field if Static IP isselected).

DNS Server 1 ###.###.###.###, where ### rangesfrom 0 to 255.

The IP address for the primary DNSserver (optional field if Static IP isselected).

DNS Server 2 ###.###.###.###, where ### rangesfrom 0 to 255.

The IP address for the secondary DNSserver (optional field if Static IP isselected).

Table 4-10 Network Configuration Field Descriptions—Protocols Area (continued)


Table 4-12 Network Configuration Field Descriptions—Alertmail Configuration Area


Alertmail Enabled or Disabled. The default setting is Disabled.

E-mail Address Maximum 32 characters including allalphanumeric, dash, and underscorecharacters.

The E-mail address of the sender.

Sender Domain Maximum 32 characters including allalphanumeric, dash, and underscorecharacters.

The domain of the sender.

SMTP Server ###.###.###.###, where ### rangesfrom 0 to 255.

The IP address for the SMTP server.

NOTE: Alertmail cannot be enabled:

• if an invalid SMTP server or e-mail address is provided

• if NTP is enabled but the primary server is invalid

Table 4-13 Network Configuration Field Descriptions—NTP Configuration Area


NTP Enabled or Disabled. The default setting is Disabled.

Primary Server ###.###.###.###, where ### rangesfrom 0 to 255.

The IP address for the primary NTPserver.



Secondary Server ###.###.###.###, where ### rangesfrom 0 to 255.

The IP address for the secondary NTPserver.

Poll Interval ###, where ### ranges between 60 and9999 seconds.

Interval of time between collecting NTPdata from the server.

SNMP ConfigurationThe SNMP Configuration screen (shown below) enables an enclosure administrator to modify the SNMPsettings of an enclosure. These settings are specific to the enclosure and do not affect the networkconfigurations for blade PCs.




The following table describes the information presented on the SNMP Configuration screen:

Table 4-14 SNMP Configuration Field Descriptions—System Information Area


SNMP Status Enabled or Disabled Displays if SNMP is enabled or disabled.

Table 4-13 Network Configuration Field Descriptions—NTP Configuration Area (continued)



System Name The name of the enclosure.

System Location Up to 20 characters including allalphanumeric, dash, underscore, @, andspace characters

The SNMP location of the enclosure

For the default SNMP contact, seeFactory Default Settings on page 162.

System Contact Up to 20 characters including allalphanumeric, dash, underscore, andspace characters

The SNMP contact of the enclosure

For the default SNMP contact, seeFactory Default Settings on page 162.

Table 4-15 SNMP Configuration Field Descriptions—Community Strings and Trap Destinations Area


Read Community Up to 20 characters including allalphanumeric, dash, underscore, andspace characters

Displays the SNMP read communitystring

If this is left blank, “public” is assigned.

For the default read Community string,see Factory Default Settingson page 162.

Write Community Up to 20 characters including allalphanumeric, dash, underscore, andspace characters

Sets the SNMP write community string

If this is left blank, SNMP SETcommands are disabled.

For the default write Community string,see Factory Default Settingson page 162.

Add Adds an IP address to the list of trapdestinations.

Remove Removes the selected IP addressesfrom the list of trap destinations.

Table 4-14 SNMP Configuration Field Descriptions—System Information Area (continued)


Power Readings

The Power Readings screen provides power consumption estimates for the enclosure. This screenincludes the following fields:

NOTE: Power readings are shown only if the enclosure has a non-power-aware blade present. Thisis a feature of HP BladeSystem bc2x00 Blade PCs only.

The screen may differ from the image shown here.

● Enclosure Average Supply Input Power—The immediate average power consumption averagedover the last 5 second sample interval.

● Enclosure Average Supply Input Power 24-Hour Sample Intervals—This is a rolling averageof power consumption over the course of preceding last 24 hours of uptime.

● Enclosure Peak Supply Input Power 24-Hour Sample Intervals—This is the peak of powerconsumption over the course of the preceding 24 hours of uptime.

● Enclosure Average Supply Input Power Time Averaged Since Powered—This is the powerconsumption averaged over the total uptime for the IA. This is since the previous power cycle orIA reset.

● Enclosure Peak Supply Input Power Time Averaged Since Powered—This is the peak of powerconsumption over the total uptime for the IA. This is since the previous power cycle or IA reset.

NOTE: All statistics are calculated from the time of the last reboot, up to 24-Hours.


Virtual ButtonsNOTE: Only enclosure administrators can execute these commands.

The Virtual Buttons screen (shown below) enables an enclosure administrator to modify the power stateof the enclosure and Unit Identification LED from a remote location to facilitate troubleshooting bytechnicians in the data center.

The Toggle On/Toggle Off button remotely changes the state of the enclosure Unit Identification LED.The illustration below shows the information presented in the Enclosure Power area of the VirtualButtons screen:

You can select the appropriate function with the following buttons:

● Restart Integrated Administrator—Restarts the Integrated Administrator and does not affect theblade PCs.

● Power Off Enclosure—Attempts a graceful shutdown of the system for 5 minutes, after which timethis command powers down all components of the enclosure immediately.

CAUTION: HP recommends that you use the operating system shutdown procedures beforepowering down a blade PC or enclosure. After the enclosure is powered off, powering on can onlyoccur by local access to the system.


System LogThe System Log screen (shown below) provides an enclosure administrator with a chronological list ofevents and updates associated with the enclosure.


● Refresh—Refreshes the screen.

● Clear—Clears the system log.

System Log PolicyThe System Log Policy screen (shown below) provides an enclosure administrator account withadministrator privileges with display and control over the logging of some system logged eventmessages.


There are two radio buttons for each event severity classification corresponding to enclosure and baysystem log policies:

● Critical—ON / OFF

NOTE: Enclosure and bay critical syslog messages cannot be masked.

● Major—ON / OFF

● Minor—ON / OFF

● Normal—ON / OFF

● Informational—ON / OFF

The Informational default is OFF; all other enclosure and bay system log policies are defaulted toON.

For details concerning specific system log messages, see Error Messages on page 142 for supportedsystem log messages and severity classification.


Enclosure Power Management Tab

This tab will show power subsystem information as it pertains to power management. The status andcapacity values are

Table 4-16 Power management values

Displayed Information Description Allowable values

Power Subsystem Status Current power subsystem state Redundant, Resilient, Resilient(throttling), Non-Redundant, and Non-Redundant (throttling)

Total Capacity In watts; sum of each power supply’ssteady state redundant capacity

PC Blade Enclosure G2

● @220V = 2400W

● @110V =1800W

● @100V =1600W

PC Blade Enclosure

● 1200W

Redundant Capacity This value is the maximum rated powersupply capacity of the lowest rated powersupply in the enclosure. Thus, thisdefinition allows for possibleheterogeneity of power supplies.


● @220V = 1200W

● @110V = 900W

● @100V = 800W

PC Blade Enclosure

● 600W


Displayed Information Description Allowable values

Resilient Capacity This value is the maximumoversubscription over the redundantpower value limit of any one powersupply. This represents the maximumsafe oversubscription value for theenclosure power budget to ensureoperation of all devices within theenclosure.


● @220V = 1440W

● @110V = 1080W

● @100V = 960W

PC Blade Enclosure

● 827W

Allocated Capacity Calculated maximum possible powerbudget based on the currentconfiguration of blades and enclosure.This number is used to by the IA todetermine the possible actions, if any, forchanging the power configuration of theenclosure.

Variable value in watts.

Available Capacity Redundant Capacity - AllocatedCapacity

Variable value in watts.

For more information, see Power Management and Redundant Power Supply on page 160.

Bays TabThe Bays tab provides access to the following screens:

● Bay List

● Bay Information

● Remote Console

● Virtual Buttons

● Console Log

● Bay Power Consumption

● Bay Temperature

Bay ListThe Bay List screen (shown below) enables an enclosure administrator to observe and update theassignment of groups to blade PC bays, as well as monitor the status of each blade PC installed in theenclosure.

Table 4-16 Power management values (continued)

ENWW Bays Tab 37

Group administrators and group members with permissions can view the blade PC bays assigned totheir groups. A group administrator account is an account set up by the Administrator user account tohave administrative privileges to administer only the bays that have been assigned to it. A groupadministrator does not have enclosure administration rights but bay-only administration rights.

The following table describes the information presented in the Bay List screen:

Table 4-17 Bay List Field Descriptions


Bay # 1-20 Blade PC number.

UID Displays a blue circle if the unitidentification (UID) LED of the blade is lit.

Blade PC Name Name of the blade PC in that blade PCbay as defined by the operating systemof the blade PC.

NOTE: The blade PC health servicemust be installed for the IntegratedAdministrator to obtain the blade PCname and operating system type.

Assigned to Group Name of the group that owns that bay.

Status OK, Degraded, or Failed The status and power state of the bladePC.

The following table lists permissions that are related to the action buttons of the Bay List screen


Table 4-18 Bay List Action Buttons and Permissions


View/Modify Opens the Blade Information screen. Enclosure administrators, groupadministrators, and group members withpermissions.

Remote Console Opens the Remote Console screen. Enclosure administrators, and groupadministrators with permissions.

Console Log Opens the Console Log screen. Enclosure administrators, groupadministrators, and group members withpermissions.

View Group Opens the View/Modify Group screen. Enclosure administrators only.

Bay Assignment Opens the Bay Assignment dialog box.

NOTE: If a blade PC is to be re-assigned, it must be unassigned first.

Enclosure administrators only.

Bay Power ConsumptionThe Bay Power Consumption screen (shown below) enables an enclosure administrator to observe thepower consumption of all populated bays within the enclosure.

ENWW Bays Tab 39

The table reports the following information:

● Bay #

● Bay Type—This is necessary to know this since only bc2x00 blades are power-aware and reportpower to the IA.

● WDC—This is direct current (DC) power consumption in Watts of the blade averaged over the last1 second sampling interval.

● WDC (24hr Avg.)—This is direct current (DC) power consumption in Watts of the blade averagedover the last 24 hours of operation within the enclosure.

● WDC (Overall Avg.)—This is direct current (DC) power consumption in Watts of the bladeaveraged over the last 24 hours of operation within the enclosure.

NOTE: Power reporting is a feature limited to bc2x00 series of blades. All others will not report a valuein the any of wattage columns.

Unknown indicates that a blade has not completed the initial post transfer.

All statistics are calculated from the time of the last reboot, up to 24-Hours.

Bay TemperatureThe Bay Temperature screen enables an administrator to check the ambient temperature for a bladePC in a given blade PC bay. Group administrators and group members with View rights to the blade PCbay can also observe this information.


Table 4-19 Bay Temperature Field Descriptions


Bay # Bay number.

Bay Type Bay type.

CPU C/F Temperature of the CPU in degreesCentigrade or Fahrenheit.

Graphics C/F Temperature of the blade graphicscontroller in degrees Centigrade orFahrenheit.

Ambient C/F Ambient temperature of the Bay indegrees Centigrade or Fahrenheit.

Bay InformationNOTE: Be sure the Integrated Administrator displays up-to-date blade PC information by rebootingthe blade PC after installing the blade PC health service. The blade PC may need to be rebooted asecond time to fully update the Integrated Administrator.

The Bay Information screen (shown below) enables an enclosure administrator to observe the statusand general information for a blade PC in a given blade PC bay. Group administrators and groupmembers with View rights to the blade PC bay can also observe this information.

ENWW Bays Tab 41

NOTE: bc2x00 blades with BIOS 3.x provide additional informational fields.

To be sure that the Bay Information screen displays the optimal number of possible values, you musthave the blade PC health driver installed.

The following table describes the information presented on the Bay Information screen for all enclosureadministrators and for group members and groups with rights to the blade PC bay.

Table 4-20 Bay Information Field Descriptions—Status Area


Status Area

Bay Number Bay number.

Blade PC Name Name of blade PC as specified with theblade PC operating system.

Status OK, Degraded, or Failed Status of the blade PC.

NOTE: In the case of a failed ordegraded bc2x00 blade, an additionaldiagnostic message is posted inparentheses.



Thermal Condition OK, Warm, Caution, or Critical Thermal condition of the blade.

NOTE: In the case of a thermal criticalor caution condition, bc2x00 bladesprovide thermal measurements for theCPU, Graphics processor, and ambientsensors in degrees Celsius at the time offailure detection.

Enclosure Name Name of enclosure.

For the default enclosure name, seeFactory Default Settings on page 162.

Rack Name Name of rack

POST Status Started, Completed, Off The blade power on self test POSTstatus. Displayed for bc2x00 blades withBIOS 3 series only.

Diagnostic Adaptor Status Present, Absent, and N/A (Off) Indicates whether the blade diagnosticadaptor has been inserted into the bladefront IO connector. This status indicatoris only valid when the blade power is on.Displayed for bc2x00 blades with BIOS 3series only.

Automated System Recovery (ASR)Mode Status

Enabled, Disabled, and N/A (off) Indicates whether the AutomatedSystem Recovery Mode (ASR) isenabled or disabled. The status is onlyvalid when the blade is powered on.Displayed for bc2x00 blades with BIOS 3series only.

Network (PXE) Booting Status In Progress, Not In Progress, and N/A(Off)

Indicates whether the blade is currentlyin network Pre-boot-execution (PXE)mode. This is only valid when the bladeis powered on. Displayed for bc2x00blades with BIOS 3 series only.

Front IO Blanking Feature Status Enabled, Disabled, and N/A (Off) This status indicates whether the bladehas it's front IO disabled to allow forsession privacy when a user is using thatblade. This is only valid when the bladeis powered on. Displayed for bc2x00blades with BIOS 3 series only.

Table 4-21 Bay Information Field Descriptions—General Area


General Area

Blade PC Type Product name of the blade PC.

Blade PC Installed OS Operating system installed on the bladePC.

Spare Number Spare number of the blade PC.

Serial Number Serial number of the blade PC.

Asset Tag Asset tag number of the blade PC.

Table 4-20 Bay Information Field Descriptions—Status Area (continued)

ENWW Bays Tab 43


BIOS Version mm/dd/yy ROM version on the blade PC.

CPU # Type Type of processor on the blade PC.

CPU # Max Speed Speed associated with the blade PCprocessor.

Installed RAM Amount of memory installed on the bladePC.

NIC #1 and #2 MAC Addresses ##:##:##:##:##:##, where ## rangesfrom 00 to FF.

MAC address of the NIC 1 interface andthe NIC 2 interface.

BMC Revision 00 to FF BMC Revision: For bc2x00 blades, theBlade Management Controller (BMC)revision will be posted here. The BMCversions prior to version 23 do not reportthis value. N/A will be shown inparentheses. Future versions of the BMCwill provide this information.

Universal Unique Identifier (UUID) Universal Unique Identifier (UUID).Displayed for bc2x00 blades with BIOS 3series only.

Pending Boot Order Changes {HDD, PXE, PXE} ={First, Once, Always} Shows the boot device to be used on thenext boot of the bay(s) specified. Thissetting is only valid on present bladesand is cleared if the blade is removed.

Remote ConsoleEnclosure administrators and group administrators with access to the bay can click Remote Consoleto open a remote text-based console (shown below) to the blade PC in the bay.

NOTE: Click on the command window to assure it has focus, otherwise no commands can be entered.

Table 4-21 Bay Information Field Descriptions—General Area (continued)


For information on establishing remote console connectivity, see Enabling Remote Console Sessionsto Blade PCs on page 101.

Virtual ButtonsEnclosure administrators and group administrators with permissions can use the Virtual Buttons screen(shown below) to modify the state of the power state and Unit Identification LED of a blade PC in orderto facilitate troubleshooting from a remote location.

ENWW Bays Tab 45

The Virtual Buttons screen enables group administrators and enclosure administrators to reboot, poweroff, or identify the blade PC with the following items:

● The Toggle On/Off button remotely changes the state of the blade PC Unit Identification LED.

● You can select the appropriate function in the Blade PC Power area using the following radiobuttons:

◦ Reboot reboots the blade PC.

◦ Power Off attempts a graceful shutdown of the blade PC for 5 minutes, after which time thiscommand powers down the blade PC immediately. This is the equivalent to a less than 3-second power button press on a standard desktop PC.

◦ Power Off Immediately powers off the blade PC forcefully. This is the equivalent to a 5-second power button press on a standard desktop PC.

CAUTION: Without service, an ACPI-compliant operating system, the Integrated Administrator cannotgracefully shut down a blade PC. This condition can result in the permanent loss of data.

NOTE: Click Apply for these settings to take effect.

Whenever possible, HP recommends that you use the operating system shutdown procedures beforepowering down a blade PC or enclosure. Once the enclosure is powered off, powering on can only occurwith local access to the system.


Console LogNOTE: Only group members, group administrators, and enclosure administrators can view a consolelog of a blade PC.

The Console Log screen displays the console log for the specified bay. The console log of the bay isnot stored between reboots of the Integrated Administrator, so the information will only include what hastaken place since the last power on of the Integrated Administrator.

The data captured in the console log is all output from the serial console of the blade PC that occurredwhile no one was connected to the console. For security reasons, console output during a userconnection session is not logged.

The Refresh button refreshes the console log for the current blade PC.

Administration TabFor an explanation of user rights associated with the Integrated Administrator, see Enabling RemoteConsole Sessions to Blade PCs on page 101.

The Administration tab provides access to the following screens:

● User List

● Group List

● Add User

● Add Group

● View/Modify User

● View/Modify Group

● Update IA FW

● Config Scripts

User ListThe User List screen (shown below) enables an appropriate group administrator or enclosureadministrator to observe and update user access to groups and blade PC bays.

ENWW Administration Tab 47

The following table lists the permissions related to the action buttons of the User List screen.

Table 4-22 User List Action Buttons and Permissions

Button Function Permissions

View/Modify User Opens the View/Modify User screen. Enclosure administrators can accessand modify the information for any user.

Users can access and modify theinformation for own account.

Remove User Removes the selected user (unless theaccount is your own).

Only enclosure administrators canexecute this command.

The following table describes the information presented in the User List screen.

Table 4-23 User List Field Descriptions

Button Function Permissions

User Name User login name.

Full Name User full name.

Account Type Administrator or User Shows if the user is an enclosureadministrator.

Account Status Enabled or Disabled Shows if the user’s account is enabled.

Group Membership Shows the groups in which the user hasmembership.

Group ListThe Group List screen (shown below) enables an enclosure administrator to observe and update theassignment of groups and users to blade PC bays.


Two buttons appear on this screen:

● View/Modify Group—Opens the View/Modify Group screen.

● Remove Group—Removes the selected group.

NOTE: Enclosure administrators can view and modify the information for all groups. Groupadministrators and group members can view the information for the groups in which they are members.

Table 4-24 Group List Field Descriptions

Field Description

Group Name Group name

Assigned Bays Blade PC bays that the group owns

Group Members Users with membership in the group

Add UserNOTE: Only enclosure administrators have access to this area of the Integrated Administrator.

The Add User screen (shown below) enables an enclosure administrator to create a user profile,including group and blade PC bays assignments.



● Apply—Saves changes made to this screen.

● Cancel—Restores all fields on this screen to their original values.

The following table describes the fields of the Add User screen.

Table 4-25 Add User Field Descriptions


User Name 1-13 characters including alphanumeric,dash, and underscore characters.

The user name must begin with a letter.A maximum of 25 users can be createdin addition to the reserve accounts.

Login name of the user.

NOTE: “Administrator,” switch,”switcha, ”switchb,” “SAM,” and “all” arereserved names and cannot be used.This restriction is not case-sensitive.

Password 3-8 characters including all printablecharacters

User’s password.

Confirm Password 3-8 characters including all printablecharacters

User’s password.

Account Type Radio buttons (Administrator and User) Determines if the user has enclosureadministrator rights.

Account Status Radio buttons (Enabled and Disabled) Determines if the user’s account isenabled.

Full Name (optional) 1-20 characters

Accepts only alphanumeric, dash,underscore, and space characters

Full name of user.



Contact Information (optional) 1-20 characters

Accepts only alphanumeric, dash,underscore, and space characters

Optional user contact information.

Group Names All groups are listed A list of all possible groups.

Group Membership x number of groups (all groups in whichthe user has membership)

A list of all groups of which the user is amember.

Add User [View]>>> Adds the user to the selected groups inthe Group Names text box with Viewrights for group members

These groups appear in the GroupMembership text box. The user losesView/Modify rights if they previously hadthem.

Add User [View/Modify]>>> Adds the user to the selected groups inthe Group Names text box with View/Modify rights for group administrators orview rights for group members.

<<< Removes the user from the selectedgroups in the Group Membership textbox.

Add GroupNOTE: Only enclosure administrators have access to this area of the Integrated Administrator.

The Add Group screen (shown below) enables an enclosure administrator to create a group profile,including user and blade PC bays assignments.

Table 4-25 Add User Field Descriptions (continued)


NOTE: Grayed-out check boxes are unavailable because they are already assigned to another group.


● Apply—Saves changes made to this screen.

● Cancel—Restores all fields on this screen to their original values.

Table 4-26 Add Group Field Descriptions—Group Information Area


Group Information Area

Group Name 1-13 characters including alphanumeric,dash, and underscore characters.

The group name must begin with a letter.A maximum of 20 users can be created.

Name of group.

Group Description (optional) 1-20 characters

Accepts only alphanumeric, dash, andunderscore characters.

Description of group.

Table 4-27 Add Group Field Descriptions—Bay Assignment Area


Bay Assignment Area



Bay 1 - Bay 20 Determines which bays the group owns.

Only one group can own a particular bay.If a check box is disabled, another groupalready owns the bay.

Select All Selects all check boxes of the bays.

Clear All Clears all check boxes of the bays.

Table 4-28 Add Group Field Descriptions—Group Membership Area


Group Membership Area

User Names All users and enclosure administratorsare listed.

A list of all possible users.

Group Members x number of users (all users that aremembers of the group).

A list of all users that are members of thegroup.

Add User [View]>>> Adds selected users in the User Namestext box to the group with View rights forgroup members.

Users lose View/Modify rights for groupadministrators if they previously hadthem.

Add User [View/Modify]>>> Adds selected users in the User Namestext box to the group with View/Modifyrights for group administrators.

<<<Remove User Removes selected users in the GroupMembers text box from the group.

View/Modify UserYou can access the View/Modify User screen by clicking any row in the User List and then clicking View/Modify User. The View/Modify User screen provides the same functions and has the same access asthe Add User screen. See the “Add User” section in this chapter.

View/Modify GroupYou can access the View/Modify Group screen by clicking any row in the Group List and then clickingView/Modify Group. The View/Modify Group screen the provides same functions and has the sameaccess as the Add Group screen. See Add Group on page 51 in this chapter.

Update IA FirmwareThe Update IA Firmware screen provides the firmware information.

Table 4-27 Add Group Field Descriptions—Bay Assignment Area (continued)


Table 4-29 Update IA Firmware Field Descriptions


Current Firmware Status Area

Firmware Version Firmware version.

Update Firmware

New Firmware Location URL The URL of the new firmware.

NOTE: The IIS manager may need to be updated to handle specific file extension MIME types(i.e., .rom) as an "application/octet-stream."

Configuration ScriptsThe Configuration Scripts screen displays the URLs from which and to which configuration scripts areloaded.


Table 4-30 Configuration Scripts Field Descriptions


Download Config Script

URL to download the configuration scriptfrom

URL to download the configuration scriptfrom

Upload Config Script

URL to upload the configuration script to URL to upload the configuration script to


Event List TabThe Event List tab provides access to the following screens:

● Event List

● Event Log Policy

The Event List differs from the System Log in the following ways:

● Any user can view the Event List. Only enclosure administrators can access the System Log.

● The messages in the Event List are limited to cautions and critical failures. Refer to the enclosureSystem Log for information on both failures and fixes.

● Minor, informational, and normal events are also reported and are displayed based on event logpolicy settings. Informational and normal events are disabled by default.

● The Event List only displays messages received since the user logged into the IntegratedAdministrator. The System Log displays every message generated by the enclosure diagnostics.A maximum of 50 event log messages is displayed. Older messages are dropped from the queueas that threshold is crossed.

The Event List screen (shown below) provides the following information for each event:

● Severity

● Source

● Date

● Time

● Event Details (the example below indicates a heatsink not properly atttached)


This example above shows a bay in a degraded state. You can click on the event to display the bay listthat contains additional details concerning the fault.

ENWW Event List Tab 57

The Integrated Administrator provides real-time event notifications for an enclosure according to fourcategories of severity (normal, minor, caution, and critical) described in the following table. For detailedinformation regarding the Event List, including a comprehensive list of event messages, see Event Iconsand Details on page 157.

Table 4-31 Event Notification Icons

Icon Description

Informational—A message that is for information purposes.

Information messages have no impact on continued operability.

Normal—An event that is a usual occurrence in the operation of the enclosure.

When a normal event occurs, there is a reasonable expectation of continued operability.

Caution–Minor—An event that does not prevent the enclosure from operating, maintaining power, orserving its user community

When a minor event occurs, a reasonable guarantee that operability can persist exists.

Caution–Major—An event that does not prevent the enclosure from operating, maintaining power, orserving its user community

When a caution event occurs, a reasonable guarantee that operability can persist no longer exists.

Critical—An event that prevents the continued operation of the enclosure.

When a critical event occurs, the inoperability of the enclosure is imminent.


Event Log Policy

● Critical—ON / OFF

● Caution–Major—ON / OFF

● Caution–Minor—ON / OFF

● Normal—ON / OFF

● Informational—ON / OFF

The default is ON for all Enclosure event log policies. The default is ON for all Bay event log policiesexcept Normal and Informational.

For details concerning specific event log messages, see Error Messages on page 142 for supportedevent log messages and severity classification.

Interconnect TabThe Interconnect Tray screen (shown below) allows anyone to view information about the interconnecttray. It allows enclosure administrators to connect to the remote console of one of the interconnectswitches if installed.

ENWW Interconnect Tab 59

The following table describes the information displayed in the areas that comprise the Interconnect Trayscreen.

Table 4-32 Interconnect Tray Screen Field Descriptions—Interconnect Tray Information Area


Interconnect Tray Information Area

Status OK, Degraded, or Failed Status of the interconnect tray.

Temperature OK, Warm, Caution, or Critical Thermal status of the interconnect tray.

Switch A Status OK, Degraded, or Failed Status of Switch A. This will only bedisplayed if an interconnect switch isinstalled.

Switch B Status* OK, Degraded, or Failed Status of Switch B. This will only bedisplayed if an interconnect switch isinstalled.

Manufacturer Manufacturer of the interconnect tray.

Product Name Product name of the interconnect tray.

Interconnect Tray Part Number Spare part number of the interconnecttray.

Interconnect Tray Serial Number Serial number of the interconnect tray.

* Proliant C-GbE e-Class switch only.


Table 4-33 Interconnect Tray Screen Field—Switch Terminal Console Area (only present if an interconnectswitch is installed)


Switch Terminal Console Area (only present if an interconnect switch is installed)

Switch A button Opens a new window to the remoteconsole of switch A.

Switch B button* Opens a new window to the remoteconsole of switch B.

* Proliant C-GbE e-Class switch only.

ENWW Interconnect Tab 61

5 Command Line Interface

This chapter provides reference material for operating the Integrated Administrator Command LineInterface (CLI). This chapter provides command line related information with the following sections:

● Accessing the Command Line Interface

● Operating the Command Line Interface

◦ General commands

◦ General management commands

◦ User account commands

◦ Enclosure network configuration commands

◦ Enclosure management commands

◦ Blade PC management commands

● Functionality exclusive to the command line interface

For a detailed explanation of the command line conventions used in this document, see CommandLine Conventions on page 141.

For easy reference, the index of this book also provides a comprehensive listing of the commandssupported by the Integrated Administrator.

62 Chapter 5 Command Line Interface ENWW

Accessing the Command Line InterfaceYou can access the CLI remotely through the management (10/100 Ethernet) connector, locally throughthe console (serial) connector on the rear panel of the enclosure, or through any uplink depending onVLAN configuration.

Accessing Remotely through the Management ConnectorTo access the Integrated Administrator command line interface remotely through the management(10/100 Ethernet) connector:

1. Get the default host name from the settings tag attached to the interconnect tray.

2. Open a Telnet or Secure Shell application and type the IP address or DNS name for the enclosureyou wish to access.

CAUTION: Using Telnet instead of Secure Shell means your remote session, includingpassword, appears in clear text on that network.

3. Type the user name and password into the Login prompt.

Accessing Locally through the Console ConnectorTo access the Integrated Administrator locally through the serial connector:

1. Connect a local client device, such as a laptop computer, to the serial connector using a null-modemcable.

NOTE: Client devices must satisfy the requirements provided in Requirements for Local ClientDeviceson page 10.

2. Open the terminal emulator and press Enter one or more times to get the login prompt.

3. Type the user name and password.

ENWW Accessing the Command Line Interface 63

Operating the Command Line InterfaceGeneral Commands

The following table describes the information displayed in the areas that comprise the EnclosureInformation screen.

Table 5-1 General Commands

Command Description Restrictions

CLEAR SCREEN Clears the terminal screen None

EXIT Exits the command line interpreter None

HELP {<command>} |Tree If a command is given, the usage and help text for thecommand are shown in a tree format. If no argument is given,all base commands are displayed.

None

LOGOUT Exits the command line interpreter None

QUIT Exits the command line interpreter

SLEEP <seconds> Pauses the sessions for a fixed period of time. Useful foradding delays to scripts. The <seconds> field can be any wholenumber from 1 - to 86400 seconds. Once the pause hasstarted, no way exists to continue the session before time runsout, but you can terminate the session and start another one.

None

? or H Provides help text for CLI commands. None

General Management CommandsThe following table describes the information displayed in the areas that comprise the EnclosureInformation screen.

Table 5-2 General Management Commands


CLEAR SESSION SWITCH[A | B]

Terminate a Terminal session from the enclosure.

This is not a graceful termination. The connected user losesany unsaved work.

Group administrators may onlyexecute this command for theblade PC bays to which theyhave access.

CLEAR SSHKEY Remove the contents of the Secure Shell authorized keys file.After performing this command, you will not be able to loginusing the public key-based authentication.

Only enclosure administratorsmay execute this command.



CONNECT SWITCH [A | B] Opens a remote console connection to switch A or B.

A single switch cannot support multiple, simultaneous remoteconsole sessions.

NOTE: Once you have connected to a switch the keysequence CTRL + SHIFT + _ (underscore) will cause a shortmenu of commands to appear. These commands are:

Disconnect

Change Settings

Reboot Switch - when connected via RS232 console

Break - when connected via telnet

Exit


DOWNLOAD CERTIFICATE

<URL>

Download a CA-supplied PKCS#7 file to replace the currentsecurity certificate on the system.

Supported protocols are http, ftp, and tftp. Format the URL asprotocol://host/path/file.

If your ftp server does not support anonymous connections,you can specify a username and password by augmenting thehost part in the above format with username:password@host.


DOWNLOAD SSHKEY Downloads an authorized key file to use with Secure Shell v2,which can contain the public keys for any enclosureadministrator. Supported protocols are http, ftp, and tftp.Format the URL as protocol://host/path/file. If yourftp server does not support anonymous connections, you canspecify a username and password by replacing the host partin the previous format with username:password@host.


GENERATE CERTIFICATEREQUEST

Generates a PKCS#10 certificate request. Only enclosure administratorsmay execute this command.

GENERATE CERTIFICATESELFSIGNED

Generates a self-signed certificate. Only enclosure administratorsmay execute this command.

PING

{<number>}

{<IP address>} | <servername>}

Sends ICMP echo messages to a remote IP device.

If <number> is omitted, only 5 packets are sent. Packets aresent out at 1-second intervals.

The <IP address> must be inthe form “###.###.###.###”where ### ranges from 0 to255.

SET DISPLAY EVENTS

[ ON | OFF | ENCLOSURE |BAY]*

Turns event notification on or off. The Integrated Administratorpreservers this setting across all logins only for the global ON/OFF.

None

SET EXPERT {MODE}

[ ON | OFF ]

Turns EXPERT MODE on or off. When EXPERT MODE is on,the system will not prompt the user to confirm actions. Usersshould exercise caution when working in EXPERT MODE asmany actions are not reversible.

None

Table 5-2 General Management Commands (continued)

ENWW Operating the Command Line Interface 65


SET FACTORY Sets the Integrated Administrator back to its factory defaults.

The Administrator account password does not change. TheIntegrated Administrator is restarted after all the changes aremade.

NOTE: This command removes all groups, users, and othercustomization from the memory of the enclosure, and theinformation is unrecoverable.

This command is an exception to the SET EXPERT command.When executing a SET FACTORY command with theEXPERT MODE on, the command still requires confirmationaction. To suppress confirmation, you must have the SCRIPTMODE on.

Executing SET FACTORY defaults the asset tag to equal theserial number.

This command cannot beexecuted if any blades arepowered on. Please power offall blades prior to executingthis command.

SET POWERON DELAY<value>

Sets the global bay power on delay for all blades after theenclosure is powered on from a cold boot or AC cycle in unitsof minutes.

Allowed value range is from 1to 60 minutes. The default is 4minutes.

SET SCRIPT MODE

[ ON | OFF ]

When SCRIPT MODE is ON, the following commands requirea password argument: ADD USER <user name> <password>,SET USER <user name> <password>, and SET PASSWORD<password>. When SCRIPT MODE is OFF, the followingcommands do not require a password argument: ADD USER,SET USER PASSWORD, and SET PASSWORD.

Default values require user interaction.

None

SHOW SESSIONS Displays the connection to each bay and switch if one exists.

Only one user may connect to each bay and switch at a time.It also shows each user that is currently logged in, the user’sport number, connect time, and remote system name.

Users may not run thiscommand. Group membersand group administrators mayonly see the sessions for baysassigned to groups to whichthey belong. Enclosureadministrators see all sessions

SHOW SSHFINGERPRINT Displays the key fingerprint of the host SSH pubic key of theIntegrated Administrator. This can be used from the serialconsole to validate the identity of the Integrated Administratorbefore initializing an SSH connection across a network.

None

SHOW SSHKEY Displays the contents of the existing Secure Shell authorizedkeys file that is being used for enclosure administrator key-based authentication.


SHOW ENCLOSUREPOWER

Display power consumption estimates for the enclosure,including all sub-components. This information includesoverall power consumption of the enclosure and the peakpower and time averaged power across a 24-hr-and-sincepowered / reset interval.

This command provides onlyestimated power usage basedon measurements reportedfrom power-aware blades andestimates from enclosuresubsystem components. Use itonly as reference information.

NOTE: This is only displayedwhen all blades are power-aware (e.g., bc2x00) only. Anote is displayed indicatingthat the enclosure cannotaccurately estimate powerconsumption.




ENABLE AUTOPOWERON If enabled, the enclosure IA will automatically power on bladeswhen inserted or when AC cycle is applied to the enclosure.

None

DISABLE AUTOPOWERON If disabled, the blades must be powered on by local access orby using the IA to remotely power on the blades.

None

* For event display severity policy-specific settings, these are session-specific only and were added to provide granular controlover a specific classification of event severity types.

● SET DISPLAY EVENTS ENCLOSURE

◦ SET DISPLAY EVENTS ENCLOSURE ALL [ ON | OFF ]

◦ SET DISPLAY EVENTS ENCLOSURE CRITICAL [ ON | OFF ]

◦ SET DISPLAY EVENTS ENCLOSURE INFORMATIONAL [ ON | OFF ]

◦ SET DISPLAY EVENTS ENCLOSURE MAJOR [ ON | OFF ]

◦ SET DISPLAY EVENTS ENCLOSURE MINOR [ ON | OFF ]

◦ SET DISPLAY EVENTS ENCLOSURE NORMAL [ ON | OFF ]

● SET DISPLAY EVENTS BAY

◦ SET DISPLAY EVENTS BAY ALL [ ON | OFF ]

◦ SET DISPLAY EVENTS BAY CRITICAL [ ON | OFF ]

◦ SET DISPLAY EVENTS BAY INFORMATIONAL [ ON | OFF ]

◦ SET DISPLAY EVENTS BAY MAJOR [ ON | OFF ]

◦ SET DISPLAY EVENTS BAY MINOR [ ON | OFF ]

◦ SET DISPLAY EVENTS BAY NORMAL [ ON | OFF ]

For details concerning event classification see Event Icons and Details on page 157.



User Account CommandsTable 5-3 User Account Commands


ADD GROUP

<group name>

Adds a group to the system

The default group description is blank.

Only enclosure administratorsmay execute this command. Amaximum of 20 groups maybe added to the system.

The <group name> must beunique to all other groupnames and user names and iscase-sensitive. It must be1-13 characters long and caninclude alphanumeric, dash,and underscore characters. Itmust begin with a letter.

NOTE: “Administrator,”switch,” switcha, ”switchb,”“SAM,” and “all” are reservednames and cannot be used.This restriction is not case-sensitive.

See Factory Default Settingson page 162 for factorydefault groups accounts.

ADD USER

<user name>

{<password>}

Adds a user to the system

If a password is not given, the user is prompted for one. IfSCRIPT MODE is enabled, the password is not optional andmust be provided.

Only enclosure administratorsmay execute this command. Amaximum of 25 users may beadded in addition to thereserved accounts.

The <user name> must beunique to all other groupnames and user names and iscase-sensitive. It must be1-13 characters long and caninclude alphanumeric, dash,and underscore characters. Itmust begin with a letter.

The <password> must be 3-8characters long and includesall printable characters. If apassword is not entered, theuser is prompted for one.

NOTE: “Administrator,”switch,” switcha, ”switchb,”“SAM,” and “all” are reservednames and cannot be used.This restriction is not case-sensitive.

See Factory Default Settingson page 162 for factorydefault user accounts.



ASSIGN ADMINISTRATOR(RIGHTS)

<user name>

Promotes a user to have enclosure administrator permissions.

Group membership is not detected in case of enclosureadministrator rights are removed at a later time.


The <user name> is case-sensitive.

ASSIGN BAY

[ALL | <bay number> {[ , | - ]<bay number>}] <groupname>

Assigns one or more bays to a group.

If a bay is already assigned to a group, it must first beunassigned before executing this command.


The <group name> is case-sensitive.

ASSIGNS USER

<user name>

<group name>

{[VIEW | MODIFY]}

Assigns a user to a group with View rights (for group members)or View/Modify rights (for group administrators)

If View or View/Modify is not specified, View is chosen bydefault.



DISABLE USER

<user name>

Disables a user account.

The user is immediately logged out of the system andprevented from log in until the account is enabled.


The <user name> is case-sensitive. The administratoraccount cannot be disabled.

ENABLE USER

<user name>

Enables a user account that was previously disabled by theDISABLE USER command



NOTE: The default ‘SAM’administrator account isdisabled by default. This wasprovided for HP SessionAllocation Manager (SAM)support. It is highlyrecommended that the SAMaccount password bechanged either before orimmediately after enabling, asall Integrated Administratorswill have the same defaultSAM account password ofSamUser123.

REMOVE GROUP

[ ALL | <group name> ]

Removes a group and automatically unassigns all bays withinthe group.



REMOVE USER

[ALL | <user name>]

Removes a user from the system.

If ALL is specified, the command is run for all users except thedefault system accounts.



NOTE: Administrator,“switch”, “SAM”, “switcha,”and “switchb,” cannot beremoved.

Table 5-3 User Account Commands (continued)



SET GROUP{DESCRIPTION} <groupname> <description>

Sets a group’s description. Only enclosure administratorsmay execute this command.The <description> must be1-20 characters long and caninclude alphanumeric, dash,and underscore characters.The default group descriptionis blank. If spaces are part ofthe contact information,enclose the information inquotes.

SET PASSWORD

{<password>}

Sets the password of the user currently logged into theIntegrated Administrator. If a password is not given on thecommand line, the user is prompted for one.

NOTE: This command is not valid in SCRIPT MODE ifpassword is not specified.

The <password> must be 3-8characters long and caninclude all printablecharacters.

SET USER CONTACT

{<user name>} <contact info>

If no <user name> exists, the command modifies the contactinfo of the user that executed the command.

Only enclosure administratorsmay modify another user’scontact information.

The <user name> is case-sensitive. The <contact info>must be 1-20 characters longand can includealphanumeric, dash,underscore, @ sign, andspace characters. The defaultcontact information is blank. Ifspaces are part of the contactinformation, enclose theinformation in quotes.

SET USER FULL NAME

{<user name>} <full name>

Sets a user’s full name.

If no <user name> exists, the command modifies the full nameof the user that is currently logged in.

Only enclosure administratorsmay modify another user’s fullname.

The <user name> is case-sensitive. The <contact info>must be 1-20 characters longand can includealphanumeric, dash,underscore, and spacecharacters. The default fullname is blank. If spaces arepart of this information,enclose the information inquotes.

SET USER PASSWORD

<user name>

Sets a user’s password.

If you do not supply a password on the command line, you areprompted for one.

NOTE: This command is not valid in SCRIPT MODE ifpassword is not specified.

Only enclosure administratorsmay modify another user’spassword. Only theAdministrator account maymodify the password of theAdministrator account.

The <user name> is case-sensitive. The <newpassword> must be 3-8characters long and caninclude all printablecharacters.




SHOW GROUP

[<group name> | ALL]

Displays the group’s description, a list of members with Viewpermission, a list of members with View/Modify permission,number of bays, and a list of each of the bay the groupmanages.

Group members and groupadministrators only see thegroups in which they havemembership. Users may notexecute this command.


If spaces are part of thisinformation, enclose theinformation in quotes.

SHOW USER

[<user name> | ALL]

Displays the user’s full name, contact, whether the user hasadministrator rights, whether the account is enabled, and thegroups for which the user has View or View/Modifypermissions.

If ALL is entered, this information is given for every user andan asterisk before the user name denotes the current user.

Only enclosure administratorsmay view another user’sinformation.

The <user name> is case-sensitive. Users who do nothave enclosure administratorpermissions only see theiruser information.

UNASSIGNADMINISTRATOR (RIGHTS)

<user name>

Takes enclosure administrator rights from a user. Only enclosure administratorsmay execute this command.The Administrator accountcannot have enclosureadministrator rights takenaway.


UNASSIGN USER

<user name> <group name>

Removes the user from the specified group. Only enclosure administratorsmay execute this command.

The <user name> and <groupname> are case-sensitive.

Enclosure Network Configuration CommandsTable 5-4 Enclosure Network Configuration Commands


ADD SNMP TRAPRECEIVER

<IP address>

Adds an IP address to receive SNMP traps.

Only v1 traps are supported. Traps are directed to the SNMPdefault port of 162.

Only enclosure administratormay execute this command.

DISABLE SECURESH Disables Secure Shell account to the Integrated Administrator. Only enclosureadministrators may executethis command.

DISABLE SNMP Disables SNMP support for the Integrated Administrator.

Does not clear the SNMP trap receivers that have beenconfigured. SNMP trap receivers can still be added andremoved. If SNMP is disabled, Systems Insight Manageagents do not work properly.

Only enclosureadministrators may executethis command.




DISABLE TELNET Disables Telnet access to the Integrated Administrator. Only enclosureadministrators may executethis command.

DISABLE WEB Disables HTTP and HTTPS access to the IntegratedAdministrator.

This command prevents access to the Web-based userinterface.


DOWNLOAD CONFIG

<URL>

The files are auto-executed in script mode. The file is notallowed to change the password of the Administrator account.Supported protocols are http, ftp, and tftp. Format the URLas protocol://host/path/file. If your ftp server doesnot support anonymous connections, you can specify a username and password by replacing the host part in the previousformat with username:password@host.


The IP address must be in theform ###.###.###.### where### ranges from 0 to 255.

ENABLE SECURESH Enables Secure Shell account to the Integrated Administrator. Only enclosureadministrators may executethis command.

ENABLE SOAP Enables SOAP support for the Integrated Administrator for alladministrator accounts.

This does not affect the built-in SAM user account. SeeEvent Icons and Detailson page 157 for supportedSOAP commands.

DISABLE SOAP Disables SOAP support for the Integrated Administrator for alladministrator accounts.

This does not affect the built-in SAM user account. SeeEvent Icons and Detailson page 157 for supportedSOAP commands.

ENABLE SNMP Enables SNMP support for the Integrated Administrator. Only enclosureadministrators may executethis command.

ENABLE TELNET Enables Telnet access to the Integrated Administrator. Only enclosureadministrators may executethis command.

ENABLE WEB Enables HTTP and HTTPS access to the IntegratedAdministrator.


REMOVE SNMPTRAPRECEIVER

<IP address>

Removes an IP address from the list of systems to receiveSNMP traps



SET DNS

<primary address>{<secondary address>}

Sets the primary and secondary DNS server addresses

These servers are only used if the system is currentlyconfigured to use a static IP address.



Table 5-4 Enclosure Network Configuration Commands (continued)



SET GATEWAY

<IP address>

Sets the network default gateway

This gateway is only used if the system is configured to use astatic IP address.



SET IPCONFIG DHCP{DYNAMICDNS}

Sets up the Integrated Administrator in dynamic IP addressingmode.

Any established gateway and DNS addresses are cleared.The optional DYNAMICDNS argument enables Dynamic DNS.


SET IPCONFIG STATIC <IPaddress> <netmask>{<gateway> {<DNS1address> {<DNS2address>}}}

Establishes the Integrated Administrator IP configuration instatic addressing mode.

In this mode the IP address and Netmask will be set to <IPaddress> and <netmask> respectively. These will take affectimmediately. The gateway address and/or DNS addresses willbe cleared if they are omitted.

NOTE: The Gateway and DNS address can also be set byusing the SET GATEWAY and SET DNS commands.



SET SNMP COMMUNITY

[READ | WRITE] <communityname>

Sets the community name for the read or write SNMPcommunity

The default names for the read and write community arepublic and blank, respectively. If a blank write communityname is given, SNMP set commands are disabled until a non-empty community name is given.

Only enclosureadministrators may modifyanother user’s contactinformation.

The write <community name>must be 1-20 characters long,and the read <communityname> must be 1-20characters long. Both caninclude alphanumeric, dash,and underscore characters.The default read communityname is public. The defaultwrite community name isblank.

SET SNMP CONTACT<contact>

Configures the name of the system contact. Can use anyASCII-printable character like @ sign for contact and location.


The <contact> must be 1-20characters long and caninclude alphanumeric, dash,underscore, @ sign, andspace characters. If spacesare part of this information,enclose the information inquotes. The only way to clearthis field is with the SETFACTORY command.




SET SNMP LOCATION<location>

Configures the SNMP location of the enclosure. Empty stringsare not allowed.

The default location is blank.


The <location> must be 1-20characters long and caninclude alphanumeric, dash,underscore, @ sign, andspace characters. If spacesare part of this information,enclose the information inquotes. The only way to clearthis field is with the SETFACTORY command.

SHOW NETWORK Displays the DHCP state, Dynamic DNS state, IP address,subnet mask, gateway address, primary and secondary DNSaddresses, HTTP and HTTPS server status, SNMP status,Secure Shell status, Telnet status, MAC address, SOAPstatus, NTP status, IP Security status, IP security configurationand AlertMail status of the enclosure.

None

SHOW SNMP Displays the SNMP system name, location, and contact, readcommunity name, write community name, and a list of the trapdestinations.


SET TRAP POLICY This configures the enclosure SNMP agent to send traps asper selection in the trap policy settings. See trap description inthe Management Information Base (MIB) file CPQRACK.MIBfor further details.


SHOW TRAP POLICY This displays the list of enclosure SNMP traps that theenclosure will generate. The trap is selected if an 'X' is in shownin the brackets. See trap description in the ManagementInformation Base (MIB) file CPQRACK.MIB for specfic trapfunctionality.

None

Enclosure Management CommandsTable 5-5 Enclosure Management Commands


CLEAR SYSLOGENCLOSURE

Clears the enclosure system log. Only enclosure administratorsmay execute this command.Once deleted, this informationcannot be restored.

DISABLE ALERTMAIL Disables sending e-mail for Integrated Administrator alerts. Only enclosure administratorsmay execute this command.

DISABLE NTP Disables automatic updates of the date and time to theIntegrated Administrator.

Some network enable/disableparameters are exclusive.

ENABLE ALERTMAIL Enables sending e-mail for Integrated Administrator alerts. Only enclosure administratorsmay execute this command.

ENABLE NTP Enables automatic time and date updates to IntegratedAdministrator.





SET SYSLOG POLICY[ENCLOSURE | BAY ]

This command turns system log message posting on or off perseverity type. The Integrated Administrator preservers thissetting across all logins/users

None

POWEROFF ENCLOSURE

{FORCE}

Performs a graceful shutdown of the enclosure. Each blade isfirst gracefully shut down. If the FORCE argument is given, theenclosure and all blades are immediately shutdown.


RESTART Restarts the Integrated Administrator. This does not affectoperation of bays in the system.


SET ALERTMAIL [MAILBOX |SENDERDOMAIN |SMTPSERVER]

Sets the e-mail address of the alert recipient, the domainname, and the mail server address.

None

SET DATE MMDDhhmm{{CC}YY} {TZ}

Sets the date of the enclosure with the following definitions:

● MM: month

● DD: day

● hh: hour (24-hour format)

● mm: minute

● CC: century

● YY: year

● TZ: time zone (case-sensitive)

If the time zone is left blank, the current time is left in effect.

NOTE: After setting the time-zone, you must perform an IArestart command.


● MM is an integer from1-12

● DD is an integer from1-31

● hh is an integer from0-23

● mm is an integer from0-59

For a list of time zones, seeTime Zone Settingson page 165. NTP must bedisabled before manuallysetting the date and time.

SET NTP [PRIMARY |SECONDARY | POLL]

Sets the IP address of the primary and secondary NTPservers. Also sets the frequency of the updates.

None

SET TIME MMDDhhmm{{CC}YY} {TZ}

Changes the enclosure time with the following definitions:

● MM: month

● DD: day

● hh: hour (24-hour format)

● mm: minute

● CC: century

● YY: year

● TZ: time zone (case-sensitive)

If the time zone is left blank, the current time is left in effect.

NOTE: After setting the time, you must perform an IA restartcommand.


● MM is an integer from1-12

● DD is an integer from1-31

● hh is an integer from0-23

● mm is an integer from0-59

For a list of time zones, seeTime Zone Settingson page 165. NTP must bedisabled before manuallysetting the date and time.

Table 5-5 Enclosure Management Commands (continued)



SET ENCLOSURE ASSET{TAG}

<asset tag>

Changes the enclosure asset tag Only enclosure administratorsmay execute this command.

The <asset tag> must be 1-32characters long and caninclude alphanumeric, dash,and underscore characters.

The default enclosure assettag is blank. To set a blankasset tag, specify the blankvalue using the quotes.

SET ENCLOSURE NAME

<enclosure name>

Changes the enclosure name Only enclosure administratorsmay execute this command.

The <enclosure name> mustbe 1-32 characters long andcan include alphanumeric,dash, and underscorecharacters.

The default enclosure name isIA-MAC, where MAC isreplaced with the actual MACaddress.

SET ENCLOSURE UID [ON |OFF]

Turns the enclosure Unit Identification LED on or off Only enclosure administratorsmay execute this command.

SET RACK NAME

<rack name>

Sets the name for the rack where that enclosure resides Only enclosure administratorsmay execute this command.

The <rack name> must be1-32 characters long and caninclude alphanumeric, dash,and underscore characters.

The default rack name isUnnamedRack.

SET POWER HISTORYINTERVAL [BLADE |ENCLOSURE]

Sets the policy for the power reporting data collection intervalfor both an individual blade and for the enclosure


Allowable settings are 1, 5, 10,30 and 60 minutesrespectively and themaximum buffer size is 24hours.

SHOW CONFIG Displays the script required to recreate the settings of theenclosure

Passwords are not included for any user.

Only the enclosureadministrators may executethis command.

SHOW DATE Displays the current date, time, and time zone of the internalclock of the enclosure.

None

SHOW TIME Displays the current time and time zone of the internal clockof the enclosure.

None

SHOW DISPLAY EVENTS Displays whether event notification is on or off. None




SHOW ENCLOSURE FAN

[<fan number> | ALL]<

Displays the status, redundancy, partner, speed, location andpart number for the requested fan.

If ALL is entered, this information is shown for all fans.

NOTE: This command may also be used to displayinformation for fan #5 and fan #6, the non-removable powersupply fans. Fan #5 and #6 are only available for HPBladeSystem PC Blade Enclosure G2 enclosures.

None

SHOW ENCLOSURE INFO Displays the enclosure name, type, part number, serialnumber, and asset tag; the Integrated Administrator software(including build #) and hardware version; the IntegratedAdministrator MAC address, and the autopoweron featureinformation, the bay power on delay value, the interconnecttray type, UUID, part number, and serial number.

None

SHOW ENCLOSUREPOWERSUPPLY

[<power supply number> |ALL]

Displays the enclosure version, power supply status, AC inputstatus, capacity, input voltage range #1 (measured in Volts),input voltage range #2 (if necessary, measured in Volts), inputfrequency range (measured in Hertz), part number, serialnumber, power supply spare part number, and hardwarerevision for either the specified power supply or for all powersupplies if ALL is specified.

For the PC Blade Enclosure G2, an additional value, InputVoltage Range #3 is displayed.

None

SHOW ENCLOSURESTATUS

Displays the enclosure status, Integrated Administrator health,unit identification LED status of the enclosure, along with thefollowing values for the power subsystem: status, redundancystate, total capacity, redundant capacity, resilient capacity,power allocated and power available.

None

SHOW ENCLOSURE TEMP Displays the locale, status (OK, warm, degraded, or failed),temperature in degrees Fahrenheit, thresholds, andtemperature sensors.

For the HP BladeSystem PC Blade Enclosure G2, alsodisplays power supply temperatures from internal and inletsensors

None

SHOW ENCLOSURE TEMPLIST

Displays sensors in tabular format None

SHOW RACK NAME

<rack name>

Shows the name for the rack where the enclosure resides

The default rack name is UnnamedRack.

None

SHOW POWER SUMMARY This command displays the redundancy state, the totalmaximum capacity, the resilient capacity, and the redundantcapacity of the power subsystem. It indicates the currentlyallocated and available capacity as compared to the redundantcapacity and will indicate, in Watts, if the redundant capacityhas been exceeded. Also, the current instantaneous powerconsumption is indicated as well within this section. Pleasesee section H ‘Power Management and Redundant PowerSupply’ for additional details.

Additionally, the enclosure and per bay allocation is displayedin tabular form to indicate how the enclosure IA has allocatedpower for the enclosure.

None




SHOW POWER HISTORYBLADE

<bay number>

Displays the last 24 hours worth of data points for averagepower consumption for the specified bay or blade asdetermined by the interval setting and number of samples.

NOTE: These samples are not preserved through a powercycle or reset.

None

SHOW POWER HISTORYENCLOSURE

Displays the last 24 hours worth of data points for averagepower consumption as determined by the interval setting andnumber of samples.

NOTE: These samples are not preserved through a powercycle or reset.

None

SHOW POWER HISTORYINTERVAL

[BLADE | ENCLOSURE |<bay number> | ALL]

Shows the interval for the blade or enclosure power history. IfBLADE is selected, can show interval for ALL.

None

SHOW SYSLOGENCLOSURE

[CRIT | WARN | NOTICE |INFO]

Displays the syslog of the enclosure with 22 lines per screen.

Displays the syslog for the enclosure and uses optionalparameter to filter the display if provided.

● The SYSLOG Type:IML conversion is as follows:

◦ CRIT: Critical

◦ WARN: Major

◦ WARN: Minor

◦ NOTICE: Normal

◦ INFO: Informational

Typing q quits the command, any other key shows the nextscreen if more information exists to display.

Typing c continuously displays the System Log without pagebreaks.


SHOW TRAY INFO Displays the manufacturer, product name, part number, serialnumber, and spare number of the interconnect tray.

None




UPDATE IMAGE

<URL>

Downloads a new image from a blade over the network anduses the image to update the firmware of the enclosure.


URL can be any of thefollowing:

● http://host/path

● tftp://host/path

● ftp://username:password

● @host/path

● ftp://host/path wherehost is a fully qualifieddomain name or an IPaddress and path is thepathname of the flashimage to download

UPLOAD CONFIG

<URL>

Upload the current runtime configuration to the specified FTPor TFTP server.


For system log severity policy specific settings, these are global and set by the administrator account only. These were addedto provide granular control over a specific classification of system log message severity types.

● SET SYSLOG POLICY ENCLOSURE

◦ SET SYSLOG POLICY ENCLOSURE ALL [ ON | OFF ]

◦ SET SYSLOG POLICY ENCLOSURE INFORMATIONAL [ ON | OFF ]

◦ SET SYSLOG POLICY ENCLOSURE MAJOR [ ON | OFF ]

◦ SET SYSLOG POLICY ENCLOSURE MINOR [ ON | OFF ]

◦ SET SYSLOG POLICY ENCLOSURE NORMAL [ ON | OFF ]

● SET SYSLOG POLICY BAY

◦ SET SYSLOG POLICY BAY ALL [ ON | OFF ]

◦ SET SYSLOG POLICY BAY INFORMATIONAL [ ON | OFF ]

NOTE: Default is OFF.

◦ SET SYSLOG POLICY BAY MAJOR [ ON | OFF ]

◦ SET SYSLOG POLICY BAY MINOR [ ON | OFF ]

◦ SET SYSLOG POLICY BAY NORMAL [ ON | OFF ]



Blade PC Bay Management CommandsTable 5-6 Blade PC Bay Management Commands


CLEAR BAY BOOT [FIRST |ONCE | ALWAYS] [ALL | <aynumber> {[ , | - ] <baynumber>}]

Clears the setting for the IPL to be passed to the blade at thenext reboot. The FIRST argument resets the IPL for allsubsequent reboots. The ONCE argument resets the IPL forthe next reboot only. The Always argument resets the IPL forevery reboot. This command is only valid for present blades.

This command may require a firmware update for the BIOSROM of certain HP blade PCs.


CLEAR SESSION BAY

<bay number>

Terminates a Terminal session from the enclosure.


Enclosure administrators mayexecute this command forblade PC bays and theinterconnect switch.

CONNECT BAY

<bay number>

Opens a remote console session to the blade PC with thatblade PC bay number.

A blade PC can only support one remote console session at atime.

Only enclosure and groupadministrators may executethis command.

GENERATE NMI

<bay number>

Generates an NMI on the specified blade.

The consequences of an NMI are operating system specific.


NOTE: The blade’s specificoperating system must supportthe NMI ‘crash dump’ featureor unpredictable results couldoccur on the blade. Pleaseconsult with your specific OSdocumentation or vendor fordetails.

POWEROFF BAY

<bay number> {[ , | - ] <baynumber>} {FORCE}

Performs a graceful shutdown of the blade PC in the specifiedbay.

If the FORCE argument is given, the blade PC is immediatelyshut down. This means the blade PC could lose data orbecome unstable. If no blade PC is in the specified bay, theuser is told that the bay is empty.


POWERON BAY

<bay number> {[ , | - ] <baynumber>} {[PXE | HDD |RBSU]}

Powers on the specified blade PC.

If no blade PC is in the specified bay, the user is told that thebay is empty.

The optional boot arguments may require a firmware updatefor the BIOS ROM of certain HP blade PCs.

Adding an optional boot argument forces the blade to abandonthe regular boot order and forces a boot using the specifiedmethod.




REBOOT BAY <baynumber> {[ , | - ] <baynumber>} {FORCE} {[PXE |HDD | RBSU]}

Sends a request to the blade PC to perform a gracefulshutdown.

The blade PC is then powered on. If no blade PC is in thespecified bay, the user is told that the bay is empty.

The optional boot arguments may require a firmware updatefor the BIOS ROM of certain HP blade PCs.



SET BAY BOOT FIRST[HDD | PXE] <bay number>{[ , | - ] <bay number>}

Sets the IPL for each subsequent reboot. This setting is onlyvalid for present blades and is cleared if a blade is removed.



SET BAY BOOT ONCE[HDD | PXE | RBSU] <baynumber> {[ , | - ] <baynumber>}

Sets the boot device to be used on the next boot of the bay(s)specified. This setting is only valid on present blades and iscleared if the blade is removed.



SET BAY UID <bay number>{[ , | - ] <bay number>} [ON |OFF]

Turns a Unit Identification LED on the blade PC on or off. Only enclosure and groupadministrators may executethis command.

SHOW BAY INFO [ALL |<bay number> {[ , | - ] <baynumber>}]

Displays the following fields: Assigned to group, type, name,installed operating system, part number, serial number, assettag, BIOS version, all CPU types and associated maximumspeeds, memory, NIC #1 MAC, and NIC #2 MAC. For bc2x00blades, the BMC revision is also displayed. BMC version 22 orearlier does not provide this information, so it is assumedversion 22h or earlier and indicated as such. When available,future versions will support this feature. Earlier versions areindicated by (N/A).

For blades with BIOS 3.x series, also displays blade UniversalUnique Identifier (UUID).

If no blade PC is in the bay, the user is shown the assigned togroup and the blade PC type.

Group members and groupadministrators only seeinformation for the bays in theirgroups.

SHOW BAY INFO LIST

[ALL | <bay number> {[ , | - ]<bay number>}]

Displays Blade Management Controller (BMC) revision, BIOSrevision, and pending boot order for blades in tabular format.


SHOW BAY LIST [ALL |<group name>]

Displays the assigned to group, remote console user, andblade PC name for each bay in a particular group if a groupname is specified or all bays if ALL is specified.


Table 5-6 Blade PC Bay Management Commands (continued)



SHOW BAY STATUS [ALL |<bay number> {[ , | - ] <baynumber>}]

Displays the power (On or Off), assigned to group, remoteconsole user, health, thermal (OK, warm, degraded, or failed),Unit Identification LED (On or Off), and power state for theblade PC.

For bc2x00 blades with BIOS 3.x series, also displaysdiagnostic adaptor, system BIOS POST status, network (PXE)booting status, front IO blanking feature status, and automatedsystem recover (ASR) mode status.


SHOW BAY STATUS LIST

[ALL | <bay number> {[ , | - ]<bay number>}]

Displays bay temperature info and status in tabular format. Group members and groupadministrators only seeinformation for the bays in theirgroups.

SHOW BAY POWER [ ALL |<bay number> {[ , | - ] <baynumber>}]

Displays the measured DC power consumption, AC powerconsumption estimate, power averaged over the last 24-hrperiod, and the time averaged power since the blade wasinserted.


NOTE: AC Estimate equalsthe measured blade DC powerdivided by the estimated powersupply efficiency of theenclosure. Earlier versions areindicated by (N/A).

SHOW BAY POWER LIST[ ALL | <bay number> {[ , | - ]<bay number>}]

Displays all of the blade power consumption metrics asmentioned above except for the AC power consumptionestimate in a tabular form for ease of viewing.


NOTE: Only bc2x00 bladesprovide power measurements.All non-power-aware bladesreport an (N/A).

SHOW BAY TEMP [ ALL |<bay number> {[ , | - ] <baynumber>}]

Displays the actual temperature measures for the CPU,graphics processor, and ambient sensors.


SHOW BAY TEMP LIST

[ ALL | <bay number> {[ , | - ]<bay number>}]

Displays bay temperature info and status in tabular format. Group members and groupadministrators only seeinformation for the bays in theirgroups.

SHOW SYSLOG BAY

<bay number>

Displays the syslog of the specified blade with 22 lines perscreen.

Typing q quits the command; any other key shows the nextscreen if more information is available to display. The systemlog of the blade PC is not stored between reboots, so theinformation only includes what has taken place since the lastpower on of the Integrated Administrator.

Typing c continuously displays the System Log without pagebreaks.


UNASSIGN BAY [ALL | <baynumber> {[ , | - ] <baynumber>}]

Removes the bay(s) from their assigned group. Only enclosure administratorsmay execute this command.

Table 5-6 Blade PC Bay Management Commands (continued)


Command Line Event MessagesTable 5-7 Command Line Event Messages

Message Possible Cause

User Event Messages

User Permission Change One of the following has occurred:

● A user has been added, removed, or modified.

● A user’s group membership has been modified.

The blade PC bay membership has been changed for a groupwith at least one user.

Enclosure Event Messages

Enclosure Shutdown The enclosure is being shut down

Enclosure Status Change The Integrated Administrator detected a change in status dueto a change in the state of one or more hardware componentsor blade PC readings.

Fan Inserted A fan has been inserted.

Fan Removed A fan has been removed.

Fan Status Change The status of fan has changed.

Power Supply Inserted A power supply has been inserted.

Power Supply Overload The power system is overloaded. Check each power supplystatus to determine cause.

Power Supply Redundancy Change The power supplies are now either redundant or no longerredundant.

The power subsystem changed to either redundant, resilient,or non-redundant status.

Power Supply Removed A power supply has been removed.

Power Supply Status Change The status of a power supply has changed.

Restart Event The Integrated Administrator is about to restart.

Thermal Status Change The state of a thermal sensor has changed.

NOTE: For bc2x00 blades, thermal events reported by thebay sensor include the bay temperature for the hottestsubcomponent sensor reported value.

Bay Event Messages

Bay Event A blade PC bay has been assigned or unassigned from agroup.

Blade Inserted A blade PC was inserted into the enclosure.

Blade Removed A blade was removed from the enclosure.


Message Possible Cause

Blade Status Change The health service or Blade Management Controller (BMC)detected a change in status due to a change in the state ofone or more hardware components or due to a software OSlockup if Automatic System Recovery (ASR) is enabled on theblade.

For bc2x00 blades, a diagnostic string accompanies the eventmessage. See Error Messages on page 142 for possiblediagnostic strings and their descriptions.

● Blade in bay # has powered off.

● Blade in bay # has powered on.

● Blade in bay # has started flash mode.

NOTE: Only blades that support a BMC display thismessage. Additionally, once flash mode is completed aBAY REMOVED, a BAY INSERTED event messageappears. This is a normal part of the flash process andcan be safely ignored.

Blade BMC in bay # has exited flash mode and will auto-powercycle in 10 seconds.

Blade BMC in bay # will now auto powercycle OFF and thenback ON.

Blade in bay # POST completed.

Blade in bay # unexpected shutdown occurred.

Blade in bay # entered PXE boot mode.

Blade in bay # exited PXE boot mode.

Blade in bay # warm reset occurred.

Blade in bay # Diagnostic Adaptor status changed to [Present |Absent].

Blade in bay # Front IO Blanking Feature status changed to[Active | Inactive].

Blade in bay # system BIOS flashing completed.

Blade in bay # system BIOS flashing started.

Power On Delay

Blades will be allowed to power on in # seconds

Blades will auto-power on now (manual power control isallowed)

Blades are allowed to power on now (manual power control isallowed)

Table 5-7 Command Line Event Messages (continued)


Functionality Exclusive to the Command Line InterfaceThe following table identifies functions or capabilities available to the Command Line Interface (CLI) andunavailable when using the Web-based interface.

Table 5-8 Functions Exclusive to the Command Line Interface—General and General ManagementCommands

Function Description Capability Exclusive to CLI

General Commands

Sleep

<seconds>

Pauses the sessions for a fixed period of time. Useful for addingdelays to scripts. The <seconds> field can be any wholenumber from 1 – 86400. Once the pause has started, no wayexists to continue the session before time runs out, but you canterminate the session and start another one.

None

General Management Commands

CLEAR SESSION SWITCH[A | B]

Terminates a Terminal session from the enclosure


All

CLEAR SSHKEY Removes the contents of the Secure Shell authorized keys file.After performing this command, you will not be able to loginusing public key-based authentication.


DOWNLOAD CERTIFICATE

<URL>

Downloads a CA supplied PKCS#7 file to replace the currentsecurity certificate on the system.

Supported protocols are http, ftp, and tftp. Format the URLas protocol://host/path/file. If your ftp server does not supportanonymous connections, you can specify a username andpassword by augmenting the host part in the above format withusername:password@host.

All

DOWNLOAD SSHKEY Downloads an authorized key file to use with Secure Shell v2which can contain the public keys for any enclosureadministrator. Supported protocols are http, ftp, and tftp.Format the URL as protocol://host/path/file. If your ftp serverdoes not support anonymous connections, you can specify ausername and password by replacing the host part in theprevious format with username:password@host.


GENERATE CERTIFICATEREQUEST

Generates a PKCS#10 certificate request All

GENERATE CERTIFICATESELFSIGNED

Generates a self-signed certificate All

PING {<number>} [<IPaddress> | <server name>]

Sends ICMP echo messages to a remote IP device

If <number> is omitted, only 5 packets are sent. Packets aresent out at 1-second intervals.

All

SET DISPLAY EVENTS [ON| OFF]

Turns event notification on or off All

SET EXPERT {MODE} [ON |OFF]

Turns EXPERT MODE on or off. When EXPERT MODE isturned on, the system will not prompt the user to confirmactions. Users should exercise caution when working inEXPERT MODE as many actions are not reversible.

None

ENWW Functionality Exclusive to the Command Line Interface 85


SET FACTORY Sets the Integrated Administrator back to its factory defaults

The password of the Administrator account does not change.The Integrated Administrator is restarted after all the changesare made.

NOTE: This command removes all groups, users, and othercustomization from the memory of the enclosure, and theinformation is unrecoverable.

This command is an exception to the SET EXPERT command.When executing a SET FACTORY command with the EXPERTMODE on, the command still requires confirmation action. Tosuppress confirmation, you must have the SCRIPT MODE on.

Executing SET FACTORY defaults the asset tag to equal theserial number.

All

SET SCRIPT MODE [ON |OFF]

When SCRIPT MODE is on, all prompting and verifications ofentries cease.

If SCRIPT MODE is on, the following commands require apassword argument or a blank password will be assigned: ADDUSER, SET USER PASSWORD, or SET PASSWORD.

An enclosure administrator must change the password so thatthe user can log in to the system. Default values are used forany parameters that would normally require user interaction.

All

SHOW EXPERT {MODE}: Displays the current EXPERT MODE setting for the currentuser.

None

SHOW SESSIONS Displays the connection to each bay and switch if one exists.

Only one user may connect to each bay and switch at a time.It also shows the users that are currently logged in, their portnumber, connect time, and remote system name.

All

SHOW SSHFINGERPRINT Displays the key fingerprint of the host SSH public key for theIntegrated Administrator. This can be used from the serialconsole to validate the identity of the Integrated Administratorbefore initializing an SSH connection across a network.

None

SHOW SSHKEY Displays the contents of the existing Secure Shell authorizedkeys file that is being used for enclosure administrator key-based authentication.


Table 5-9 Functions Exclusive to the Command Line Interface—Enclosure Management Commands


Enclosure Management Commands

SHOW CONFIG Displays the script required to recreate the settings of theenclosure.

Passwords are not included for any user.

All

SHOW ENCLOSURE FAN[<fan number> | ALL]

Displays the status, redundancy, partner, speed, and partnumber for the requested fan.

The command line adds thefan partner.

Table 5-8 Functions Exclusive to the Command Line Interface—General and General Management Commands(continued)



SHOW ENCLOSUREPOWERSUPPLY [<powersupply number> | ALL]

Displays the status of the power supply, AC input status,capacity, input voltage range #1 (measured in Volts), inputvoltage range #2 (measured in Volts), input frequency range(measured in Hertz), part number, serial number, and hardwarerevision for the specified power supply if one is specified or forall power supplies if ALL is given.

The command line adds theinput voltage ranges, inputfrequency range, serialnumber, and hardwarerevision.

SHOW ENCLOSURESTATUS

Under an enclosure status heading, this command displays thehealth of the enclosure, Integrated Administrator health, andunit identification LED.

Under a power status heading, this command displays thepower status and capacity.

The command line adds theIntegrated Administratorhealth.

CLEAR SESSION BAY

<bay number>

Terminates a Terminal session from the enclosure. All

CLEAR BAY BOOT [FIRST |ONCE] [ALL | <bay number>{[ , | - ] <bay number>}]

Clears the setting for the IPL to be passed to the blade at thenext reboot. The “FIRST” argument resets the IPL for allsubsequent reboots. The “ONCE” argument resets the IPL forthe next reboot only. This command is only valid for presentblades.

This command may require a firmware upgrade for the BIOSROM of certain HP blade PCs.


GENERATE NMI <baynumber>

POWERON BAY <baynumber> {[ , | - ] <baynumber>} {[PXE | HDD |RBSU]}

Powers on the specified blade PC.

If no blade PC is in the specified bay, the user is told that thebay is empty.

The optional boot arguments may require a firmware upgradefor the BIOS ROM of certain HP blade PCs.


Allows for optional bootargument

REBOOT BAY <baynumber> {[ , | - ] <baynumber>} {FORCE} {[PXE |HDD | RBSU]}

Sends a request to the blade PC to perform a gracefulshutdown.

The blade PC is then powered on. If no blade PC is in thespecified bay, the user is told that the bay is empty.

The optional boot arguments may require a firmware upgradefor the BIOS ROM of certain HP blade PCs.

Adding an optional boot argument with force the blade toabandon the regular boot order and force a boot using thespecified method.

Allows for optional bootargument

SET BAY BOOT FIRST[HDD | PXE] <bay number>{[ , | - ] <bay number>}

Sets the IPL for each subsequent reboot. This setting is onlyvalid for present blades and is cleared if a blade is removed.

This command may require a firmware upgrade of the BIOS.

Only enclosure administratorsmay execute this command

Table 5-9 Functions Exclusive to the Command Line Interface—Enclosure Management Commands(continued)

ENWW Functionality Exclusive to the Command Line Interface 87


SET BAY BOOT ONCE[HDD | PXE | RBSU] <baynumber> {[ , | - ] <baynumber>}

Sets the boot device to be used on the next boot of the bay(s)specified. This setting is only valid on present blades and iscleared if the blade is removed.

This command may require a firmware upgrade for the BIOSROM of certain HP blade PCs.


SHOW BAY LIST [ALL |<group name>]

Displays the assigned to group, remote console user, andblade PC name for each bay in a particular group if a groupname is specified or all bays if ALL is specified.

The command line displaysthe remote console user.

ADD IPMANAGER <IPaddress>

Adds an IP address to the list of clients allowed to connect toIntegrated Administrator.


DISABLE IPSECURITY Allows all clients to connect to Integrated Administrator. Only enclosure administratorsmay execute this command.

ENABLE IPSECURITY Restricts clients from being able to connect to IntegratedAdministrator.


REMOVE IPMANAGER <IPaddress>

Removes the IP address from the list of clients allowed toconnect to Integrated Administrator.


SHOW NETWORK Displays the DHCP state, Dynamic DNS state, IP address,subnet mask, gateway address, primary and secondary DNSaddresses, MAC address, HTTP and HTTPS server status,SNMP status, Secure Shell status, Telnet status, NTP status,NTP primary and secondary server address, NTP poll interval,NTP last update time, IP security configuration, AlertMailstatus, AlertMail mailbox, SMTP server address and senderdomain of the enclosure.


SET ENCLOSURE SERIAL{NUMBER} <serial number>

Allows modification of the serial number reported by theenclosure information.

Only enclosure administratorsmay execute this command.The serial number may be 1–14 characters in length

Table 5-9 Functions Exclusive to the Command Line Interface—Enclosure Management Commands(continued)


6 Setting Up the System

This chapter explains the levels of user rights recognized by the Integrated Administrator and providesdetailed procedures to configure the management functions provided by the Integrated Administrator.

● Customizing the enclosure settings

◦ Changing the Administrator password

◦ Modifying enclosure and rack names

◦ Modifying the asset tag number

◦ Modifying the date and time

◦ Enabling/Disabling Blade Auto-poweron Feature

● Setting up user accounts

◦ Adding a group

◦ Adding a user

● Enabling remote console sessions to blade PCs

● Setting up AlertMail

◦ Adding mailbox address

◦ Adding SMTP server address

◦ Adding Sender Domain

◦ Enabling AlertMail

◦ Disabling AlertMail

● Setting up IP Security

◦ Adding IP address

◦ Enabling IP Security

◦ Disabling IP Security

● Setting up Automatic Time Configuration (NTP)

◦ Adding primary NTP server

◦ Adding secondary NTP server

ENWW 89

◦ Setting the poll interval

◦ Enabling NTP

◦ Disabling NTP

◦ Configuring trap policy settings

● Configuring SNMP support

◦ Entering a community string

◦ Modifying the system location

◦ Modifying the system contact information

◦ Adding trap targets

◦ Removing trap targets

◦ Configuring SOAP

◦ Enabling SOAP Interface

◦ Enabling SAM Account

For a detailed explanation of the command line conventions used in this document, see Command LineConventions on page 141.

These procedures are supported by the Web-based user interface and the CLI unless otherwise noted.

NOTE: Most of these tasks are limited to a subset of users. For more information on who can performeach task, see User Permissionson page 90 and the section describing that task in this chapter.

User PermissionsThe group-centered approach of Integrated Administrator to user permissions facilitates themaintenance of user groups and groups of blade PC bays. This approach operates according to thefollowing principles:

● A blade PC bay is assigned exclusively to one group only.

● A group can be assigned many blade PC bays.

● A user can have various permission levels within any number of groups.

● Access to a blade PC by users or groups depends on the rights assigned to the blade PC bay inwhich the blade PC is installed.

Use the following table to distinguish the various permission levels available from the HP PC BladeEnclosure Integrated Administrator.

90 Chapter 6 Setting Up the System ENWW

Table 6-1 HP PC Blade Enclosure Integrated Administrator Permissions Levels

Title Account Type Permissions Description

Enclosure Administrator Administrator View/Modify for allgroups in the enclosure

Enclosure administrators may maintain bladePC bay privileges, manage the enclosure,manage blade PC bays, and create andmaintain groups.

One special enclosure administrator account(named Administrator) cannot be deleted,disabled, or stripped of enclosureadministrator permissions. No other enclosureadministrator may change the password to thisaccount.

Enclosure administrators cannot disable ordelete their own accounts.

Group Administrator User View/Modify Group administrators may manage blade PCbay data for groups in which they areadministrators.

Group administrators may view blade PC baydata for groups in which they are members.

Group administrators may modify their profile(not their privileges) and view enclosure data.

Group member User View Group members may view blade PC bay datafor groups in which they are members.

Group members may modify their profile (nottheir privileges) and view enclosure data.

Group member User Group member

Customizing the Enclosure SettingsNOTE: Only enclosure administrators may execute these commands.

To change the default Administrator password using the Web-based user interface:

1. Click the Administration tab.

2. Click User List in the side panel.

3. Click the Administrator user name in the user list.

4. Click View/Modify User. The View/Modify User screen displays.

5. Click Change Password.

6. Type in the new Administrator password in the Password and Confirm password fields.

7. Click OK.

To change the default Administrator password using the CLI, type:

SET USER PASSWORD Administrator <new password>

ENWW Customizing the Enclosure Settings 91

NOTE: The user name (Administrator) is case-sensitive. The <new password> must be 3-8 characterslong and can include all printable characters.

Modifying Enclosure and Rack NamesTo modify the enclosure name or rack name using the Web-based user interface:

1. Click the Enclosure tab.

2. Click Enclosure Information in the left panel.

3. Click the Enclosure Name field of the Status area.

4. Type the enclosure name.

5. Click the Rack Name field of the Status area.

6. Type the rack name.

7. Click Apply.


To modify the enclosure name or rack name using the CLI, type the following commandssequentially: SET ENCLOSURE NAME <enclosure name>

NOTE: The <enclosure name> must be 1-32 characters long and includes all alphanumeric, the dash,and the underscore characters.

The default enclosure name is IA-XXXXXXXXXXXX where XXXXXXXXXXXX is replaced with thedevices's physical MAC address: SET RACK NAME <rack name>

NOTE: The <rack name> must be a maximum of 32 characters long and includes all alphanumeric,dash, and underscore characters. The default rack name is UnnamedRack.

NOTE: The only way to completely clear the enclosure and/or rack names is with the SET FACTORYcommand

Modifying the Asset Tag NumberTo modify the asset tag number using the Web-based user interface:



3. Scroll down to the General area.

4. Click the Asset Tag field.

5. Type the asset tag number.

6. Click Apply.

ENWW Customizing the Enclosure Settings 93

To modify the asset tag number using the CLI, type:

SET ENCLOSURE ASSET {TAG} <asset tag>

NOTE: The <asset tag> must be 1-32 characters long and includes alphanumeric, dash, andunderscore characters. The default enclosure asset tag is blank.

Modifying the Date and TimeTo modify the date and time settings using the Web-based user interface:



3. Scroll down to the Date and Time area.

4. Select the proper time zone from the pull-down list.

5. Click the Date or Time field.

6. Type the date or time.

7. Click Apply.

To modify the date and time settings using the CLI, type:

SET DATE MMDDhhmm{{CC}YY} {TZ}


where:

● MM: month

● DD: day

● hh: hour (24-hour time, an integer from 0-23)

● mm: minute

● CC: century

● YY: year

● TZ: timezone

NOTE: If the time zone is left blank, the current time zone is left in effect. For a list of supported timezones, see Time Zone Settingson page 165.

Setting Up User AccountsNOTE: Only enclosure administrators may perform this task.

The Integrated Administrator enables you to manage blade PC bays and administer users by organizingthose blade PC bays and users into groups.

This approach enables enclosure administrators, for example, to re-assign user permissions to groupsof blade PCs en masse, instead of requiring enclosure administrators to modify permissions one userat a time.

Enclosure administrators assign users access rights to blade PC bays through the following tasks:

● Adding groups with access to specific blade PC bays in an enclosure

● Adding users with certain permissions within specific groups

Adding a GroupNOTE: Restricted default names of group and user accounts (Administrator, switch, switcha, switchb,and SAM) are not case-sensitive. Nondefault group and user names are case-sensitive.

For more information on the Web-based user interface screens for this function, see Group Liston page 48. For information on using the CLI, see User Account Commands on page 68.

To create a group using the Web-based user interface:


2. Click Add Group in the left panel.

3. Type the group name and description in the fields.

ENWW Setting Up User Accounts 95

4. Select bays for the group by selecting the appropriate check boxes.

NOTE: If a blade PC bay is gray, that blade PC bay is inaccessible because it already belongsto another group.


5. To add existing users to this group:

a. Select users in the User Names area.

b. Click Add User [View] or Add User [View/Modify]. For more information on permissionlevels, see User Permissions on page 90 in this chapter.

6. Click Apply.

To create a group using the CLI, type the following commands sequentially:

ADD GROUP <group name>

NOTE: The <group name> must be unique to all other group names and user names and is case-sensitive. It must be 1-13 characters long and can include all alphanumeric characters, the dash, andthe underscore.

SET GROUP {DESCRIPTION} <group name><description>

NOTE: The <description> must be 1-20 characters long and can include all alphanumeric characters,the dash, the underscore, and spaces.

ASSIGN BAY [ALL | <bay number> {[ , | - ]<bay number>}] <group name>

ASSIGN USER <user name> <group name> {[VIEW | MODIFY]}

NOTE: The <use name> and <group name> are case-sensitive. The Administrator account cannot beadded to a group. The default setting is View.


Adding a UserNOTE: Restricted default names of group and user accounts are not case-sensitive. Nondefault groupand user names are case-sensitive.

For information on permission levels, see User Permissions on page 90 in this chapter.

To create a user using the Web-based user interface:


2. Click Add User in the left panel.

3. Type the user information in the appropriate field. For information on “Account Type,” see UserPermissions on page 90 in this chapter.

NOTE: The Account Type setting determines whether the account holder has managementpermissions. The optional Full Name and Contact Information fields provide the account holder’sname and a readily accessible means of contact in case of emergency.


4. To assign the user to an existing group:

a. Select groups in the Group Names area.


b. Click Add User [View] or Add User [View/Modify]. For more information on permissionlevels, see User Permissions on page 90 in this chapter.

5. Click Apply.

To add a user using the CLI, type the following commands sequentially:

ADD USER <user name> {<password>}

NOTE: The <user name> must be unique to all other user names and group names and is case-sensitive. It must be 1-13 characters long and can include all alphanumeric characters, the dash, andthe underscore. The <password> must be 3-8 characters long and includes all printable characters.

ASSIGN ADMINISTRATOR {RIGHTS} <user name>

SET USER FULLNAME {<user name>} <full name>

NOTE: The <full name> must be 1-20 characters long and can include all alphanumeric characters,the dash, the underscore, and spaces.

SET USER CONTACT {<user name>} <contact info>

NOTE: The <contact info> must be 1-20 characters long and can include all alphanumeric characters,the dash, the underscore, and spaces.

ASSIGN USER <user name> <group name> {[VIEW | MODIFY]}


Enabling Remote Console Sessions to Blade PCsThe remote console feature of the Integrated Administrator enables a user to connect to the console(serial) connector of the blade PC in order to access the ROM-Based Setup Utility (RBSU). Accessingthe RBSU of the blade PC requires nothing more than connecting to the blade PC.

Setting Up AlertMailAlertMail enables users to receive system events by e-mail instead of using SNMP traps. AlertMail iscompletely independent from SNMP and both can be enabled at the same time. AlertMail uses standardSMTP commands to communicate with an SMTP capable mail server.

To set up AlertMail using the Web-based user interface:


2. Click Network Administration in the left panel.

3. Scroll down to the Alertmail Configuration area.

4. Click the Enabled button.

5. Type the e-mail address in the E-Mail Address field.

6. Type the sender domain in the Sender Domain field.

7. Type the SMTP server address in the SMTP Server fields.

8. Click Apply.

Table 6-2 AlertMail CLI Commands

Function Command

Add an e-mail address using command line interface SET ALERTMAIL MAILBOX <e-mailaddress>

Add an SMTP server address SET ALERTMAIL

SMTPSERVER

<IP address>

Set the sender domain SET ALERTMAIL

SENDERDOMAIN

<domain name>

Enable Alertmail ENABLE ALERTMAIL

Disable Alertmail DISABLE ALERTMAIL

* For security reasons, some SMTP servers will only forward mail if the sender’s domain is set properly.You may need to set this parameter to match the network domain.

ENWW Enabling Remote Console Sessions to Blade PCs 101

E-mail AlertsAlertMail, if enabled, will send out alerts by e-mail for the following events:

● Enclosure boot message

● IA reboot message

● Fan status change

● Fan inserted

● Fan removed

● Enclosure thermal status change

● Power supply status change

● Power supply inserted

● Power supply removed

● Power subsystem redundancy change

● Blade inserted

● Blade removed

● Blade status change

● Blade thermal change

● Blade fault

● Blade diagnostic string (bc2x00 only) (See Error Messages on page 142 for a list of blade specificdiagnostic strings.)

NOTE: If the enclosure has a switch installed, it can take up to 60 seconds before the system will sendout an AlertMail after a system boot up. Events generated within this period of time will be sent out whenthe switch has come online.

All e-mails have the following header:

Subject: HP AlertMail-SEQ: <SEVERITY> SUBJECT

Date: Date in standard format

From: Enclosure ENCLOSURE-NAME <enclosure-name@domain>

To: RECEIVER MAILBOX

Where SEVERITY is one of the following (from highest to lowest):

● # CRITICAL

● # WARNING

● # NOTICE

● # INFO

Example e-mail:


----SAMPLE START----

Subject: HP AlertMail-010: (CRITICAL) Power Supply #1: Failed

Date: Wed, 23 Apr 2003 15:02:22 +0200

From: Enclosure IA-00508BEBA571 <[email protected]>

To: user@userdomain

X-OS: HP Integrated Administrator

X-Priority: 1

Content-Type: text/plain; charset=us-ascii

EVENT (26 May 07:09): Power Supply #1 Status has changed to: Failed

Enclosure, IA-00508BEBA571, has detected that a power supply in bay 1 has changed from status OK to Failed.

The power supply should be replaced with the appropriate spare part. You can ensure that the center wall assembly is operating correctly by swapping the two power supplies. Make sure that there are no bent pins on the power supply connectors before reinserting and that each power supply is fully seated.

An amber LED on the power supply indicates either an over-voltage, over-temperature, or loss of AC power event has occurred. A blinking LED on the power supply indicates a current limit condition.

Enclosure Status: Degraded

Enclosure Management URL: <https://192.168.0.100/>

- PLEASE DO NOT REPLY TO THIS EMAIL –

----SAMPLE END----

Setting Up IP SecurityNOTE: This is not IPSec.

IP security allows an administrator to define a set of IP addresses that are the only ones allowed toconnect to the services provided (SSH, HTTP, TELNET, SNMP). This means that an administrator canmake sure only a certain set of machines have access to Integrated Administrator. You can enter amaximum of five IP addresses.

Table 6-3 IP Security Commands

Function Command

Add an IP address ADD IPMANAGER <IP address>

Remove an IP address REMOVE IPMANAGER <IP address>

Enable IP security ENABLE IPSECURITY

Disable IP security DISABLE IPSECURITY

ENWW Setting Up IP Security 103

Setting Up Automatic Network Time ProtocolConfiguration (NTP)

Automatic time configuration allows the Integrated Administrator to synchronize its date and time withan NTP-capable device supporting the NTP.

To set up NTP using the Web-based user interface:


2. Click Network Administration in the left panel.

3. Scroll down to the NTP Configuration area.

4. Click the Enabled button.

5. Type the server addresses in the Primary Server and Secondary Server fields.

6. Type the poll interval in the Poll Interval field.

7. Click Apply.

Table 6-4 Automatic Time Configuration CLI Commands

Function Command

Set the NTPpoll interval* SET NTP POLL

<seconds>

Set the primary NTP server SET NTP PRIMARY

<IP address>

Set the secondary NTP server SET NTP SECONDARY <IP address>

Disable the secondary NTP server SET NTP SECONDARY NONE

Enable NTP ENABLE NTP

Disable NTP DISABLE NTP

* If an NTP poll interval is not set, it will default to 720 seconds. The minimum time is 60 seconds andthe maximum time is 9999 seconds.


Configuring SNMP SupportNOTE: Only enclosure administrators may execute these tasks.

Entering a Community StringTo enter a read community or write community string using the Web-based user interface:


2. Click SNMP Configuration in the left panel.

3. Click the Read Community or Write Community field.

4. Type the string.

NOTE: Entering a blank string into the Read Community field sets the Read Community to“public.” Entering a blank string into the Write Community field disables the SNMP set commands.

5. Click Apply.

To enter a read community or write community string using the CLI, type:

SET SNMP COMMUNITY [READ | WRITE] <community name>

ENWW Configuring SNMP Support 105

The write <community name> must be 1-20 characters long and the read <community name> must be1-20 characters long. Both community names support all alphanumeric characters, the underscore, andthe dash characters.

The default read community name is “public,” and the default write community name is blank.

Modifying the System LocationNOTE: The SNMP protocol can be disabled in the Network Configuration area of the Web-based userinterface.

To modify the system location information using the Web-based user interface:



3. Set the cursor in the System Location field and type the appropriate information.

4. Click Apply.

To modify the system location information using the CLI, type:

SET SNMP LOCATION <location>

The <location> must be 1–20 characters in length. Acceptable characters include alphanumeric, dash,underscore, @ sign, and spaces. You must use double quotes around the contact if it includes spaces

NOTE: The only way to clear the <location> is with the SET FACTORY command

Modifying the System Contact InformationTo modify the system contact information using the Web-based user interface:



3. Set the cursor in the System Contact field and type the appropriate information.

4. Click Apply.

To modify the system contact information using the CLI, type:

SET SNMP CONTACT <contact>

The <contact> field must be 1-20 characters long and supports all the alphanumeric characters, theunderscore, the dash, and spaces with quotes.

NOTE: The only way to clear the <contact> information is with the SET FACTORY command.

Adding Trap TargetsTo add a trap target using the Web-based user interface:




3. Type the IP address in the appropriate field of the SNMP area.

4. Click Add.

5. Click Apply.

To add a trap target using the CLI, type:

ADD SNMP TRAPRECEIVER <IP address>

The <IP address> must be in the form ###.###.###.###, where ### ranges from 0 to 255.

The Integrated Administrator only supports v1 traps and directs the traps to SNMP port 162 by default.You can add a maximum of eight IP addresses to receive SNMP traps.

Removing Trap TargetsTo remove a trap target list using the Web-based user interface:



3. Type the list name in the appropriate field of the SNMP area.

4. Click Remove.

5. Click Apply.

To add or remove a trap target list using the CLI, type:

REMOVE SNMP TRAPRECEIVER <IP address>

The <IP address> must be in the form ###.###.###.###, where ### ranges from 0 to 255.

Modifying Trap PolicyTo modify trap policy using the CLI:

For enclosure:

SET TRAP POLICY ENCLOSURE [ALL | CRITICAL | MAJOR | MINOR | INFORMATIONAL] [ON | OFF]

For bay:

SET TRAP POLICY BAY [ALL | CRITICAL | MAJOR | MINOR | INFORMATIONAL] [ON | OFF]

For a specific trap number:

SET TRAP POLICY TRAP [TRAP # {optional range}]

For traps and further information, see Supported SNMP Traps on page 172.

ENWW Configuring SNMP Support 107

7 Configuring SOAP Support Tasks

Enabling SOAP InterfaceTo enable the SOAP interface via the Web-based user interface:


2. Click Network Configuration in the left panel.

3. Click the SOAP button to Enable

4. Click Apply.

To enable the SOAP interface via the CLI-based user interface, type:

ENABLE SOAP

Disabling SOAP InterfaceTo disable the SOAP interface via the Web-based user interface:



3. Click the SOAP button to Disable

4. Click Apply.

To disable the SOAP interface via the CLI-based user interface, type:

DISABLE SOAP

108 Chapter 7 Configuring SOAP Support Tasks ENWW

Supported SOAP Interface CommandsThe following table contains a summary of the supported SOAP interface commands a short description:

Table 7-1 Supported SOAP Interface Commands

Command Description

userLogin Establishes a SOAP session with the IA for using SOAP interface Web services.

userLogout userLogout Closes a SOAP session with the IA.

modifyPassword Change user account password via SOAP interface.

getEnclosurePowerCollectionInfo Gets information about the power regulator and power reporting capabilities of theenclosure.

setEnclosurePowerCollectionInfo Sets information about the power regulator and power reporting capabilities of theenclosure. Allows setting of a 1 minute, 5 minute, 10 minute, 1 hour, or for 24 hour samplerate.

getEnclosurePowerRecords Returns collected power history data points for the enclosure.

getBladePowerCollectionInfo Gets information about the power regulator and power reporting capabilities of a given bay.

setBladePowerCollectionInfo Sets information about the power regulator and power reporting capabilities of a given bay.Allows setting of a 1 minute, 5 minute, 10 minute, 1 hour, or for 24 hour sample rate.

getBladePowerRecords Returns collected power history data points for the a given bay.

getEnclosureInfo Functions like CLI Get Enclosure Info command minus some IA specific information.

getIAInfo Gets IA specific information.

getEnclosureStatus Functions like CLI Get Enclosure Status command.

setBladePowerState Functions like CLI power[on / off] {bay #} command.

getBladePowerState Gets the power state of the blade.

getBladeStatus Functions like CLI Get Blade Status {bay #} command.

getBladeStatusArray Functions like CLI Get Blade Status All command.

getBladeInfo Functions like CLI Get Blade Info {bay #} command.

getEnclosurePowerData Provides a snapshot of the most recent power data points collected.

SetBladeOneTimeBoot Changes boot order for the blade on next POST. Functions like CLI command SET BAYBOOT ONCE.

SetBladeIPLBootPriority Changes boot order for the blade on next POST. Functions like CLI command SET BAYBOOT ALWAYS.

flashIAROM Can flash the IA via the SOAP interface but only with Administrator account.

getBladeBootInfo Returns pending boot order settings for blade as set by the IA.

setBladeUID Changes the UID LED on the blade.

setEnclosureUID Changes the UID LED on the enclosure.

You can download the WDSL file for XML schema and description for these commands directly fromthe Integrated Administrator by entering this URL: https://<IA IP address>/iasoap.wsdl, where <IA IPaddress> is the IP address of the Integrated Administrator.

ENWW Supported SOAP Interface Commands 109

8 Performing Common AdministrativeTasks

This chapter explains the following Integrated Administrator management functionalities:

● Managing blade PC bays

◦ Opening a remote console session to a blade PC

◦ Accessing ROM-Based Setup Utility for a blade PC

◦ Reviewing the activity for a blade PC

◦ Powering off the blade PC

CAUTION: The Integrated Administrator cannot gracefully shutdown a blade PC unless theblade is using an ACPI-supported OS.

◦ Identifying a blade PC using the Unit Identification LED

● Managing the enclosure

◦ Reviewing the activity for the enclosure

◦ Identifying the enclosure using the Unit Identification LED

◦ Generating an enclosure summary

◦ Identifying problem components

● Managing users

◦ Modifying a user’s rights to blade PC bays

◦ Disabling and deleting user accounts

Managing Blade PC BaysOpening a Remote Console Session to a Blade PC

NOTE: Enclosure administrators and group administrators with access to the bay can click the RemoteConsole button to open a remote text-based console to the blade PC in the bay.

110 Chapter 8 Performing Common Administrative Tasks ENWW

To access the remote console using the Web-based user interface:

1. Click the Bays tab.

2. Click Bay List in the left panel.

3. Select the blade PC from the blade list.

NOTE: The blade PC name is listed in the column titled Blade Name. When a blade PC ishighlighted, the Bay Information buttons become active.

4. Click Remote Console. The Remote Console screen displays.

5. Click Remote Console to open a new window that enables you to connect to the blade PC terminalinterface.

To access the remote console using the CLI, type:

CONNECT BAY <bay number>

NOTE: A blade PC can only support one remote console session at a time.

Accessing the ROM-Based Setup Utility for a blade PCNOTE: Enclosure administrators and group administrators with access to the bay can select theRemote Console button to open a remote text-based console to the blade PC in the bay.

ENWW Managing Blade PC Bays 111

To access the ROM-Based Setup Utility (RBSU) for a blade PC using the Web-based user interface:



3. Select the bay from the bay list.

4. Click Remote Console at the bottom of the screen.

5. Click Remote Console from the Remote Console screen.

6. If the blade PC is running the Windows 2000 operating system:

a. Return to the Web-based user interface and click Virtual Buttons in the left panel.

CAUTION: Without the blade PC health driver, the Integrated Administrator cannot reboota blade PC.

b. If the blade PC is off, select Power On at the bottom of the screen; otherwise, selectReboot at the bottom of the screen.

c. Click Apply and return to the remote console session.

7. When prompted, press F10 for ROM-Based Setup Utility:

a. Press Esc.

b. Press the 0 key.

8. To exit RBSU:

a. Press Esc.

b. When prompted, press F10, press the Esc key and the 0 key to confirm.

9. To close the remote console session:

a. Press the Ctrl+Shift+_ keys.

b. Press the D key.

To access the RBSU for a blade PC using the command line interface:

CAUTION: Without the blade PC health driver, the Integrated Administrator cannot reboot a blade PC.

1. If the blade PC is running the Windows 2000 operating system, reboot the blade PC by enteringthe following commands sequentially:

REBOOT BAY <bay number>

Yes

2. Connect to the blade PC by observing its bay number and typing:

CONNECT BAY <bay number>

3. When prompted, press the F10 key for ROM-Based Setup Utility for Blade PCs:

a. Press Esc.

b. Press the 0 key.


4. To exit RBSU:

a. Press Esc.

b. When prompted, press F10, press the Esc key and the 0 key to confirm.

5. To close the remote console session:

a. Press the Ctrl+Shift+_ keys.

b. Press the D key.

Reviewing Activity for a Blade PCNOTE: This task can only be performed for a given blade PC bay by enclosure administrators, groupadministrators, and group members with access rights to the blade PC bay.

To access the console log for a blade PC using the Web-based user interface:



3. Choose the bay from the Bay list.

4. Click Console Log under Bay Information.

To view the system log for a blade PC using the CLI, type:

SHOW SYSLOG BAY <bay number>

NOTE: Typing q quits the command. Typing any other key shows the next screen if more informationis available to display. The system log of the blade PC is not stored between reboots, so the informationonly includes what has taken place since the last power-on of the Integrated Administrator.

Powering Off the Blade PCCAUTION: Without the blade PC health driver or an ACPI-compliant operating system, the IntegratedAdministrator cannot gracefully shutdown a blade PC. This condition may result in the permanent lossof critical data.

Rebooting or powering off the blade PC removes all power from the blade PC and ends all opensessions.

NOTE: This task can only be performed for a given blade PC bay by enclosure administrators andgroup administrators with access rights to the blade PC bay.

To reboot or power off the blade PC using the Web-based user interface:



3. Click the blade PC whose power state to modify.

4. Click Virtual Buttons at the bottom of the screen.


5. Click Reboot, Power Off or Power Off Immediately.

6. Click Apply.

When the blade PC power is off, the Power Off button text becomes Power On.

To reboot the blade PC using the CLI, type:

REBOOT BAY <bay number> {[ , | - ] <bay number>} {FORCE} {[PXE | HDD | RBSU]}

NOTE: This command sends a request to the blade PC in a given bay to perform a graceful shutdownand then reboots the blade PC.

To power off the blade PC (immediately or otherwise) using the CLI, type:

POWEROFF BAY <bay number> {[ , | - ] <bay number>} {FORCE}

NOTE: If the FORCE argument is invoked, the blade PC powers down immediately and could losedata or become unstable.

Identifying a Blade PC Using the Unit Identification LEDNOTE: You can perform this task only for a given blade PC bay by enclosure administrators and groupadministrators with access rights to the blade PC bay.

The virtual button for the Unit Identification LED of the blade PC physically changes the state of the UnitIdentification LED on the front panel of the blade PC from off to on, or vice-versa. The Unit IdentificationLED illuminates bright blue and is designed to help a technician quickly identify a specific blade PC inthe data center.


To change the state of a Unit Identification LED of for a blade PC using the Web-based user interface:



3. Click the blade PC whose Unit Identification LED you wish to toggle.

4. Click Virtual Buttons at the bottom of the screen.

5. Click Toggle ON or Toggle OFF depending on the current state of the Unit Identification LED forthe blade PC.

To change the state of the Unit Identification LED for a blade PC using the CLI, type:

SET BAY UID <bay number> {[ , | - ] <bay number>} [ON | OFF]


Managing the EnclosureReviewing the Activity of the Enclosure

The system log of the Integrated Administrator is a chronology of system activities, such as user logins,enclosure shutdowns, and system failures. The system log also displays warnings and errors that occurin the HP PC Blade Enclosure, including:

● User account modifications

● Group modifications

● Bay assignment modifications

● Valid and invalid login attempts

● System failures

● System status changes

● Blade insertion and removals

● DHCP, Dynamic DNS, and WINS messages

● Updates to the Integrated Administrator’s firmware

● Bay health status changes

● Bay power state changes

Enclosure administrators can view events in the enclosure by accessing the System Log. Additionally,administrators can filter the severity of events that are recorded in the system log using the system logpolicies. This is useful for tracking specific bay vs. enclosure event classes for diagnostic purposes. Incontrast to the Event List, no other users can access the System Log. For more information on how theEvent List differs from the System Log, see Identifying Problem Components on page 120 in thischapter.

To view the System Log using the Web-based user interface:



2. Click System Log in the left panel.

3. To update the System Log, click Refresh.

4. To clear the System Log, click Clear Log. The Integrated Administrator prompts you to confirmthis decision.

To view the System Log of the enclosure using the CLI, type:

SHOW SYSLOG ENCLOSURE

Only enclosure administrators can execute this command.

To view the System Log Policies of the enclosure using the CLI, type:

SHOW SYSLOG POLICIES

Only enclosure administrators can execute this command.

To set the System Log Policies of the enclosure using the CLI, type:

SET SYSLOG POLICY ENCLOSURE {ALL, MAJOR, MINOR, NORMAL, INFORMATIONAL} [ ON | OFF ] for enabling / disabling enclosure system log message types.

SET SYSLOG POLICY BAY {ALL, MAJOR, MINOR, NORMAL, INFORMATIONAL} [ ON | OFF ] for enabling / disabling bay system log message types.

Only enclosure administrators can execute this command. See Error Messages on page 142 for a listof maskable system log messages and their severity classification.

ENWW Managing the Enclosure 117

Identifying the Enclosure Using the Unit Identification LEDThe virtual button for the Unit Identification LED of an enclosure physically changes the state of the UnitIdentification LED on the rear panel of the enclosure from Off to On, or vice versa. The Unit IdentificationLED illuminates bright blue and is designed to help a technician quickly identify a specific enclosure inthe data center.

To change the state of the Unit Identification LED of the enclosure using the Web-based user interface:


2. Click Virtual Buttons in the left panel.

3. Click Toggle ON or Toggle OFF depending on the current state of the Unit Identification LED forthe enclosure.

To change the state of the Unit Identification LED for the enclosure using the CLI, type:

SET ENCLOSURE UID [ON | OFF]

Only enclosure administrators may execute this command.


Generating an Enclosure SummaryYou can generate a printable synopsis of all the data for the enclosure including the enclosure nameand type; the part, serial, and asset tag numbers of the enclosure; the software and hardware versionsof the Integrated Administrator; the MAC address of the Integrated Administrator; and the type, partnumber, and serial number of the interconnect tray.

To generate a printable synopsis of all the data for the enclosure using the Web-based user interface,click Summary View in the top panel. The Web-based user interface opens a new window that you cancopy and paste into a printable file.

To obtain the enclosure information using the CLI, enter the following commands as needed:

SHOW ENCLOSURE FAN [<fan number> | ALL]

This command displays the status, redundancy, partner, speed, and part number for one or all fans inthe enclosure.

SHOW ENCLOSURE INFO

This command displays the enclosure name and enclosure type; the software and hardware version ofthe Integrated Administrator; the part number, serial number, and asset tag number of the enclosure;the MAC address of the Integrated Administrator; and the type, part number, and serial number of theinterconnect tray.

SHOW ENCLOSURE POWERSUPPLY [<power supply number> | ALL]


This command displays the status, AC input status, capacity, input voltage range #1 (Volts), input voltagerange #2 (Volts), input frequency range (Hz), part number, serial number, and hardware revision for oneor all power supplies in the enclosure.

SHOW ENCLOSURE STATUS

This command displays the status of enclosure health, Integrated Administrator health, and the UnitIdentification LED under the heading “enclosure status,” and displays the status and capacity of thepower supplies of the enclosure under the heading “power status.”

SHOW ENCLOSURE TEMP

This command displays the location, status (OK, warm, degraded, or failed), and temperature (degreesFahrenheit and Celsius) for all the temperature sensors of the enclosure.

Identifying Problem ComponentsThe Integrated Administrator alerts you to problem conditions or failed components in the enclosure,such as:

● A fan

● A power supply

● A blade PC

● Over-temperature conditions

If the enclosure enters a degraded state at any time, the Web-based user interface of the IntegratedAdministrator alerts the user with icons along the top of the deck panel.


Identify the degraded components in the enclosure and their respective part numbers in the followingways:

● Opening the enclosure system log

● Opening the event list - the event list differs from the system log in the following ways:

◦ Any user can view the event list. Only enclosure administrators can access the system log.

◦ The messages in the event list are limited to cautions and critical failures. Refer to theenclosure system log for information on fixes.

◦ The event list only displays messages received since the user logged into the IntegratedAdministrator. The system log displays every message generated by the enclosurediagnostics.

● Clicking on the Caution or Critical icon along the top of the deck panel

This action opens the event list. By highlighting an item in the event list and clicking View EventDetails, you can access the area within the Integrated Administrator that provides detailed informationabout that degraded component.

NOTE: As soon as you click the Caution or Critical icon, that icon disappears whether the degradedconditions are corrected or not.

To identify a degraded component using the System Log from the Web-based user interface:

1. Click on the Enclosure tab.


2. Click on System Log in the left panel.

3. Go to the appropriate area in the Integrated Administrator for the spare number of the degradedcomponent.


To identify a degraded component using the event list from the Web-based user interface:

1. Click the Event List tab.

2. Click the degraded item in the event list.

3. Click View Event Details at the bottom of the screen. This action opens the page in the IntegratedAdministrator that displays information about the degraded component.

To identify a degraded component using the Caution or Critical icons along the top of the deck panelfrom the Web-based user interface, click an icon. This action opens the event list.

By highlighting an item in the event list and clicking View Event Details, you can access the area withinthe Integrated Administrator that provides detailed information about that degraded component.


To identify a degraded component using the CLI:

1. Type: SET DISPLAY EVENTS [BAY | ENCLOSURE | ON | OFF] to ON.

2. Type: SET DISPLAY EVENTS ENCLOSURE ALL ON.

3. Type: SET DISPLAY EVENTS BAY ALL ON.

4. Type the appropriate commands:

SHOW ENCLOSURE FAN [<fan number> | ALL]

This command displays the status, redundancy, partner, speed, and part number for one or all fansin the enclosure.

SHOW ENCLOSURE INFO

This command displays the enclosure name, type, part number, serial number, and asset tagnumber; the Integrated Administrator software and hardware version; the MAC address of theIntegrated Administrator, and the interconnect tray type, part number, and serial number.

SHOW ENCLOSURE POWERSUPPLY [<power supply number> | ALL]

This command displays the status, AC input status, capacity, input voltage range #1 (Volts), inputvoltage range #2 (Volts), input frequency range (Hz), part number, serial number, and hardwarerevision for one or both power supplies in the enclosure.

SHOW ENCLOSURE STATUS


This command displays the status of enclosure health, Integrated Administrator health, and theUnit Identification LED under the heading “enclosure status,” and displays the status and capacityof the power supplies of the enclosure under the heading “power status.”

SHOW ENCLOSURE TEMP

This command displays the location, status (OK, warm, degraded, or failed), and temperature(degrees Fahrenheit or Celsius) for all the temperature sensors of the enclosure.

Managing UsersNOTE: Only enclosure administrators may perform these tasks.

Restricted default names of group and user accounts (Administrator, switch, switcha, switchb, and SAM)are not case-sensitive. Nondefault group and user names are case-sensitive.

Modifying a User’s Rights to Blade PC BaysYou can only modify a user’s rights to blade PC bays by modifying their group rights, specifically bychoosing one of the following methods:

● Creating a new group for the user with the updated access rights to the blade PC bays

● Modifying the rights to blade PC bays for a group to which the user has membership

Creating a New Group with the Updated Access RightsTo create a new group with the updated blade PC access profile you wish to assign your user, seeAdding a Group on page 95.

Modifying Group Rights to Blade PC BaysTo modify group rights to blade PC bays using the Web-based user interface:


ENWW Managing Users 125

2. Click Group List in the left panel.

3. Click on the group whose rights you wish to modify.


4. Click View/Modify Group.

5. Select the appropriate check boxes for the available blade PC bays that reflects the updated rightsyou wish to give the group.

6. Click Apply.

To modify rights to blade PC bays for an existing group using the CLI, choose from among the followingcommands:

NOTE: Only enclosure administrators may execute these commands.

● To expand the number of blade PCs assigned to a group, type:

ASSIGN BAY [ALL | <bay number> {[ , | - ]<bay number>}] <group name>

If a blade PC bay is currently assigned to a group, this command re-assigns the bay from its currentgroup to the new group.

● To remove access rights to blade PC bays for any group, type:

UNASSIGN BAY [ALL | <bay number> {[ , | - ] <bay number>}]

Disabling and Deleting User AccountsNOTE: Only enclosure administrators may execute this command. Group accounts can be deleted,but cannot be disabled.

To disable a user account using the Web-based user interface:



2. Click on User List in the left panel.

3. Select the user whose account you wish to disable from the user list.

4. Click View/Modify User.

5. Set the account status to Disabled.

6. Click Apply.

To disable a user account using the CLI, type:

DISABLE USER <user name>

When this command is executed, the user is immediately logged out of the system and prevented fromlogging in until the account is enabled.

Deleting a User AccountTo delete a user account using the Web-based user interface:


2. Click User List in the left panel.


3. Select the user account you wish to delete from the user list.

4. Click Remove User.

To delete a user account using the CLI, type:

REMOVE USER [ALL | <user name>]

If ALL is specified, the command deletes all the user accounts except the Administrator account. TheAdministrator account cannot be removed.

Deleting Group AccountsTo delete a group account using the Web-based user interface:


2. Click Group List in the left panel.


3. Select the group from the group list.

4. Click Remove Group.

To delete a group account using the CLI, type:

REMOVE GROUP [ALL | <group name>]

If ALL is specified, the command deletes all the group accounts.


9 Performing Advanced Functions

This chapter provides an explanation of the following advanced tasks you can perform using theIntegrated Administrator. These procedures are supported by the Web-based user interface and theCLI unless otherwise noted:

● Replicating the configuration of the Integrated Administrator

● Administering security certificates

◦ Creating a security certificate

◦ Downloading a security certificate

● Key-Based SSH Authentication

● Configuring a Blade PC Boot Order

● Powering off the enclosure

● Disabling network protocols to the Integrated Administrator

● Upgrading the firmware of the Integrated Administrator

● Recovering a lost Administrator password

● Launching flash disaster recovery

NOTE: Only enclosure administrators may perform the tasks in this chapter.

ENWW 131

Replicating the Configuration of the IntegratedAdministrator

NOTE: The Integrated Administrator does not support this task using the Web-based user interface.

To set up several enclosures with the same configuration, configure one enclosure (such as add all useraccounts, add all groups, and assign bays) and then replicate that configuration on the other enclosures.

To replicate the configuration of the Integrated Administrator using the CLI:

1. Login as Administrator on the first enclosure.

2. Type: UPLOAD CONFIG <url>. This command uploads the current runtime configuration to thespecified TFTP or FTP server. If your FTP server does not allow anonymous uploading, specify anFTP username and password using the syntax:

ftp://username:password@ftpserver/filename

3. Edit the uploaded configuration file using a text editor to customize the configuration (such as usernames, passwords, and network settings) for the other enclosures.

NOTE: Step 4 only applies if the other enclosures have been configured previously.

For security reasons, passwords are never replicated in the configuration file.

4. Restore the factory defaults on each of the other enclosures to clear any previous configuration:

a. Login as Administrator on an enclosure to which you intend to replicate the configuration.

b. Type: SET FACTORY. This command sets the Integrated Administrator back to its factorydefault settings and clears credentials such as the SSH fingerprint, although the password ofthe Administrator account does not change. The Integrated Administrator is restarted after allthe changes are implemented. IMPORTANT: Only the Administrator account may executethis command.

5. Download the configuration to each of the other enclosures:

a. Log in as Administrator on an enclosure to which you intend to replicate the configuration.

b. Type: DOWNLOAD CONFIG <url>. The Integrated Administrator does not check theconfiguration file for errors, but auto-executes the file in script mode. The file is not allowedto change the password of the Administrator account. Supported protocols are http, ftp, andtftp. Format the URL as protocol://host/path/file. If your ftp server does not supportanonymous connections, specify a user name and password by replacing the host part in theabove format with username:password@host.

NOTE: Step c applies only if you did not set user account passwords in the configurationfile.

c. Set the password for each user account. For commands, see User Account Commandson page 68.

Administering Security CertificatesNOTE: The Integrated Administrator does not support these tasks using the Web-based userinterface.

132 Chapter 9 Performing Advanced Functions ENWW

Creating a Certificate RequestTo create a security certificate using the CLI, type: GENERATE CERTIFICATE REQUEST

This command generates a PKCS#10 certificate request. This certificate request can be sent to yourcertification authority (CA) to obtain a PKCS#7 certificate file to use below.

To create a self-signed security certificate using the CLI, type: GENERATE CERTIFICATE SELFSIGNED

This command generates a self-signed PKCS#7 certificate to replace the existing SSL certificate. Thiscertificate is signed with the current name of the enclosure and will be valid for 10 years. Users who donot have a certificate authority (CA) may use this certificate as a replacement.

Downloading a Security CertificateTo download a security certificate using the CLI, type:

DOWNLOAD CERTIFICATE <url>

This command downloads a CA supplied PKCS#7 file to replace the current security certificate on thesystem.

Supported protocols are http, ftp, and tftp. Format the URL as: protocol://host/path/file

If your ftp server does not support anonymous connections, you can specify a username and passwordby replacing the host part in the previous format: username:password@host

Key-Based SSH AuthenticationUsers may install their own public SSH keys for password-less logins to the Integrated Administrators.Only enclosure administrators can use key-based authentication. The CLI features four commands toinstall and manage the authorized SSH keys.

▲ To view any current installed authorized SSH keys, type: SHOW SSHKEY

This command shows any keys currently installed on the Integrated Administrator that areauthorized to log in using an enclosure administrator account.

▲ To view the fingerprint of the Integrated Administrator host key, type: SHOW SSHFINGERPRINT

This command shows the fingerprint of the host key for the Integrated Administrators. Users maycompare this fingerprint with the fingerprint displayed by their SSH client when connecting to theIntegrated Administrators to guarantee the authenticity of the Integrated Administrator connection.Users who need guaranteed authenticity will want to use the Integrated Administrator serial consoleto obtain the SSH fingerprint for the first time.

▲ To clear any currently installed authorized SSH keys, type: CLEAR SSHKEY

This command clears any authorized keys currently installed on the Integrated Administrator thatare authorized to log in. After this command has been issued, all users have to enter a validpassword in order to log in.

▲ To download and install one or more SSH keys, type: DOWNLOAD SSHKEY <url>

ENWW Key-Based SSH Authentication 133

This command downloads and install a file containing one or more SSH keys which are authorizedto log into the Integrated Administrator. The new file will replace any existing keys.

Supported protocols are http, ftp and tftp. Format the URL as: protocol://host/path/file.

If your ftp server does not support anonymous logins, you can specify a username and password byreplacing the host part (in previous format) with: username:password@host.

The Integrated Administrator supports multiple SSH keys in one downloaded file. Max file size for SSHkeys is 16K.

Key-based SSH logins have an advantage for use with scripting as well. Remote commands can besent to any Integrated Administrator after installing the appropriate authorized key without having toenter a password between each command. Using the OpenSSH package, the user can send commandsusing the following syntax: ssh user@host command

You can group together commands to perform a series of actions. To view the health status of theenclosure and all blades with a single command, type:

ssh user@host “SHOW ENCLOSURE STATUS; SHOW STATUS BAY ALL”

By having an authorized key file installed on the Integrated Administrator, the user can combine thesewithout having to enter a password between each command sent to the Integrated Administrator.

Configuring Blade PC Boot OrderEnclosure and group administrators may change the boot order, sometimes referred to as Initial ProgramLoad (IPL), of their blade PCs by using the CLI of the Integrated Administrator. The change can be madepermanently or only for the next reboot. Several commands are available in the CLI to control the bladesin this manner.

To set a blade PC boot order, type:

SET BAY BOOT FIRST [HDD | PXE] [ALL | <bay number> {[,|-] <bay number>}]

During the next reboot, this will set the specified blade PC boot order to use the given boot device first.This has the same effect as changing the Standard Boot Order (IPL) setting in the RBSU on the bladePC.

To set a blade PC boot order for the next boot only, type:

SET BAY BOOT [ONCE | ALWAYS] [HDD | PXE | RBSU] [ALL | <bay number> {[,|-] <bay number>}]

This will force the specified blade PC to boot to the specified media on the next boot only. The RBSUsetting will make the blade PC(s) boot into the RBSU which can be viewed with the Remote Consolefunctionality. The HDD setting forces the blade PC to boot from the hard drive first, and the PXE settingforces it to boot from the integrated NIC first.

To reset blade boot order settings which have not yet taken effect, type:

CLEAR BAY BOOT [FIRST | ONCE | ALWAYS] [ALL | <bay number> {[,|-] <bay number>}]

This will clear changes to the specified blade PC boot order that were made with the SET BAY BOOTcommand. It only affects pending changes so if the blade PC has been rebooted since the SET BAYBOOT command, this command will have no effect.


The POWERON BAY and REBOOT BAY commands have been extended to allow an argument whichsets blade PC boot order for that boot only. These settings are the same as the SET BAY BOOT ONCEcommand.

To determine if any boot order changes are pending for a specific blade, use the SHOW BAY INFOcommand. The Pending Boot Order status line will show any pending changes to the boot order, eitherone-time or permanent.

Powering Off the EnclosureCAUTION: Powering off the enclosure removes all power from the blade PCs and ends all opensessions. After powering off the enclosure, you can only power on the enclosure if you have physicalaccess to the enclosure.

To power off the enclosure using the Web-based user interface:


2. Click Virtual Buttons.

3. Click Power Off.

4. Click Apply.

ENWW Powering Off the Enclosure 135

To power off the enclosure using the CLI, type: POWEROFF ENCLOSURE

This command attempts to perform a graceful shutdown of the enclosure by powering off each bladePC and then powering off the enclosure. After 5 minutes, the command powers down all componentsof the system immediately if they are not already powered off.

CAUTION: Without the blade PC health driver or an ACPI-compliant operating system, the IntegratedAdministrator cannot gracefully shutdown a blade PC. This condition may result in the permanent lossof critical data.

Disabling Network ProtocolsTo modify the supported communications protocols of the enclosure using the Web-based userinterface:



3. Select the appropriate radio buttons in the Protocols area.

4. Click Apply.


To modify the supported communications protocols of the enclosure using the CLI, choose from amongthe following commands:

● To disable http/https communication, type: DISABLE WEB

Disabling http/https causes the users to lose access to the Web-based user interface.

● To disable automatic time updates, type: DISABLE NTP

● To disable SNMP communication, type: DISABLE SNMP

● To disable Secure Shell communication, type: DISABLE SECURESH

Disabling Secure Shell causes the users to lose access to the Web-based user interface.

● To disable Telnet communication, type: DISABLE TELNET

● To disable the SOAP interface, type: DISABLE SOAP

Upgrading the Integrated Administrator FirmwareThe firmware associated with the Integrated Administrator can be upgraded remotely using the CLI usingthe management (10/100 Ethernet) connector located on the rear panel of the enclosure.

UPDATE IMAGE <url>

The <url> can be any of the following:

● http://host/path

● tftp://host/path

● ftp://username:password@host/path

● ftp://host/path

...where “host” is a fully qualified domain name or an IP address and path is the pathname of the flashimage to download. Refer to the documentation associated with the firmware upgrade for detailedinformation.

NOTE: You can also upgrade the Integrated Administrator firmware through the GUI in theadministration tab update image page.

Configuring the Update FeatureTo make sure the update feature works when using http, you must have the following in place:

● For your Windows-based Web server, ensure that the IIS manager is configured to handle the .romfile extension.

● The Web server must have the MIME Type set correctly. To set the MIME Type:

1. Go to the site's Properties > http headers tab > MIME Types.

A MIME Types window containing Registered MIME Types (File Extensions) opens.

2. Click New.

ENWW Upgrading the Integrated Administrator Firmware 137

3. Under Extension, type .rom.

4. Under MIME Type, type application/octet-stream.

Recovering a Lost Administrator PasswordTo recover a lost Administrator password:

1. Be sure the local client device is properly configured for local access to the Integrated Administrator.See Chapter 3, in Requirements for Local Client Devices on page 10.

2. Connect a local client device to the Integrated Administrator (serial) console connector using thenullmodem serial cable (provided with the enclosure).

3. Open a terminal emulation application.

4. Press and hold the enclosure Unit Identification button (1) and press the Integrated AdministratorReset button (2) simultaneously on the rear panel of the blade PC to place the enclosure in LostPassword/Flash Disaster Recovery mode.

5. When the serial console prompt appears, press the L key.

This command boots the system in Lost Password mode, which resets the Administrator password tothe factory default and displays it on the console.


Launching Flash Disaster RecoveryFlash Recovery mode requires the following items:

● DHCP server

● TFTP server

● a network connection accessible to both DHCP and TFTP Server

● A connection to the Integrated Administrator serial console

● Integrated Administrator ROM image file on the TFTP server

NOTE: The filename of the ROM image of the Integrated Administrator can be any valid ASCIIfilename. The ROM image of the Integrated Administrator can be any valid image that supports the“update image" facility in the operating system.

The Integrated Administrator will automatically enter Flash Recovery mode when a corrupted image isdetected. Flash Recovery mode can also be manually initiated.

NOTE: No timeout exists for obtaining a DHCP address.

The Flash Recovery process should only be initiated when the Integrated Administrator fails to bootproperly because an operating system image is corrupted by some unforeseen problem, such as apower/catastrophic failure during the standard “update image” flash procedure.

Flash Recovery mode makes every attempt to successfully flash the operating system image of theIntegrated Administrator. The only way to leave Flash Recovery mode without successfully updating theimage is to reset the Integrated Administrator.

You can manually place the Integrated Administrator in Flash Recovery mode:

1. Connect a local client device to the Integrated Administrator (serial) console connector using thenullmodem serial cable (provided with the enclosure). See Requirements for Local ClientDevices on page 10.

ENWW Launching Flash Disaster Recovery 139

2. Press and hold the enclosure Unit Identification button (1) and press the Integrated AdministratorReset button (2) simultaneously on the rear panel of the blade PC to place the enclosure in LostPassword/Flash Disaster Recovery mode.

3. When the serial console prompt appears, press the F key.

NOTE: This command is case-insensitive.

Pressing the L key launches Lost Password recovery mode. Pressing any other key exits Lost Password/Flash Disaster Recovery mode and reboots the system.

This command boots the system in Flash Disaster Recovery mode, prints a message, and resets theenclosure.

Upon entering Flash Disaster Recovery mode, the Integrated Administrator attempts to acquire a DHCPaddress. If successful, the Integrated Administrator prompts the user for:

● IP address of the TFTP server

● Filename of the ROM on the TFTP server

The Integrated Administrator then downloads and verifies the ROM and updates the flash memory.

NOTE: No timeout exists for obtaining a DHCP address.

NOTE: If the ROM does not download properly or if the verification step fails, Flash Disaster Recoverymode restarts with another attempt to acquire a DHCP address.

The Integrated Administrator reboots.


A Command Line Conventions

The following table lists the conventions used by the Command Line Interface (CLI).

Table A-1 CLI Conventions

Symbol Description

<lower case> Denotes input to be keyed in

UPPER CASE Denotes input to be keyed in as shown

[] Denotes choices to be made where a choice is mandatory

{} Denotes choices to be made where a choice is optional

| Separates input options

““ Used to enclose arguments that contain spaces

For example, the following command requires the user to input whether the Integrated Administrator isoperating in a “DHCP” or “Static” network environment.

SET IPCONFIG [DHCP {DYNAMICDNS} | STATIC <IP address> <netmask>

Specifying “Dynamic DNS” is optional for executing this command for the DHCP environment, butspecifying the IP address and netmask are required for executing this command for the staticenvironment.

ENWW 141

B Error Messages

The messages provided in this appendix are divided into the following categories:

● Warning messages

● Error messages

Warning MessagesThis section provides a comprehensive list of warning messages specific to the major components ofthe Integrated Administrator. These warning messages advise you that you have implemented aconfiguration change or prompt you to confirm whether you wish to proceed with your requested action.

Enclosure Warning MessagesTable B-1 Enclosure Warning Messages

Warning Message Cause

Are you sure you want to disable the Web protocol? Disabling this protocol willprevent access to the Web-based user interface until a terminal session re-enablesthe Web protocol.

Attempting to disable the Web (HTTP /HTTPS) protocol

Are you sure you want to disable the Secure Shell protocol? Disabling this protocolwill prevent access to the Web-based user interface and Secure Shell terminalinterface until a terminal session re-enables the Secure Shell protocol.

Attempting to disable the Secure Shellprotocol

The SNMP protocol is currently disabled. The new settings will not take effect untilthis protocol is enabled on the Network Configuration screen.

Changing an SNMP value with theSNMP protocol disabled

The Read Community field is empty. The Read Community will be set to “public”.The SNMP protocol may be disabled on the Network Configuration screen.

Attempting to set a blank ReadCommunity string

Are you sure that you want to power off the enclosure? Attempting to power off the enclosure

Are you sure that you want to restart the Integrated Administrator? This process willtake several minutes.

Attempting to restart the IntegratedAdministrator

Are you sure that you want to clear the system log? Attempting to clear the system log

Enabling IP Security may disconnect this session. Are you sure you still want toperform this action?

Attempting to enable IP Security

142 Appendix B Error Messages ENWW

Blade PC Warning MessagesTable B-2 Blade PC Warning Messages


This blade has been removed from the enclosure. The blade that is being viewed has beenremoved from the enclosure.

This blade has been powered off. All open sessions will be closed. The current blade has been powered off.

Are you sure that you want to power off the blade immediately? This process mayresult in the loss of any unsaved data on the blade.

Attempting to immediately power off ablade.

Administration Warning MessagesTable B-3 Administration Warning Messages


Are you sure you want to permanently remove <user name>? All data for this accountwill be removed from the system.

Attempting to delete a user

Are you sure you want to permanently remove <group name>? All bays in this groupwill be unassigned and the data for this group will be permanently removed from thesystem.

Attempting to delete a group

ENWW Warning Messages 143

Error MessagesEnclosure Error Messages

Table B-4 Enclosure Error Messages

Error Message Cause Valid Input

The maximum number (8) of trap destinations hasbeen reached.

Attempting to add a 9th trapdestination

N/A

The trap destination of ###.###.###.### is alreadyon the list. Enter a new value.

Attempting to add a duplicate trapdestination

N/A

An error occurred while clearing the system log.Please try again.

Attempting to clear the system log N/A

Blade PC Bay Error MessagesTable B-5 Blade PC Bay Error Messages


You no longer have permissions to view this bay. User permission change N/A

Administration Error MessagesTable B-6 Administration Error Messages


The user name field is empty. Please enter a username.

Attempting to create a user with ablank user name

1-13 characters includingalphanumeric, dash, andunderscore characters. The username must begin with a letter.

This user name already exists. Please select adifferent user name.

Attempting to create a user withouta unique user name

1-13 characters includingalphanumeric, dash, andunderscore characters. The username must begin with a letter.

The Password fields are empty. Please enter avalue in each password field.

Attempting to create a user with ablank password

3-8 characters including allprintable characters

The Password field is empty. Please enter apassword.

Attempting to create a user with ablank Password field


The Confirm Password field is empty. Please entera password.

Attempting to create a user with ablank Confirm Password field


The password must be at least 3 characters inlength. Please enter a new password.

Attempting to create a user with apassword that is less than 3characters long


The passwords do not match. Please try again. Different strings in the Passwordand Confirm Password fields


The maximum number (25) of users exists on thesystem.

Attempting to create a 26th user N/A



The group name is blank. Please enter a validname.

Attempting to create a group with ablank group name

N/A

The maximum number (20) of groups exists on thesystem.

Attempting to create a 21st group N/A

The Password fields are empty. Please enter avalue in each password field.

Attempting to create a user with ablank password


The Password field is empty. Please enter apassword.

Attempting to create a user with ablank Password field


The Confirm Password field is empty. Please entera password.

Attempting to create a user with ablank Confirm Password field


The password must be at least 3 characters inlength. Please enter a new password.

Attempting to create a user with apassword that is less that 3characters long


The passwords do not match. Please try again. Different strings in the Passwordand Confirm Password fields


NTP Poll-Interval has to be between 60 and 9999seconds.

Attempting to set an NTP pollinterval that is not between 60 and9999 seconds.

60-9999

Invalid NTP address supplied. IP address shouldbe in ###.###.###.### format where ### isbetween 0 and 255.

Attempting to enter an IP addressthat is not in the correct format.

###.###.###.### where ### isbetween 0 and 255

###.###.###.### is not a valid NTP server. Attempting to set an NTP serveraddress, but the address entered isnot an NTP server.

N/A

Please set at least the Primary NTP server beforeenabling NTP.

Attempting to enable the NTPserver before enabling the primaryNTP server set.

N/A

<IP address> is already set as secondary NTPserver.

Attempting to set the primary NTPserver to <IP address> when the<IP address> is already set assecondary.

N/A

<IP address> is already set as primary NTP server. Attempting to set the secondaryNTP server to <IP address> whenthe <IP address> is already set asprimary.

N/A

Primary NTP server is already cleared. Attempting to clear the primary NTPserver that has previously beencleared or never set.

N/A

The secondary NTP server is already cleared. Attempting to clear the secondaryNTP server that has previouslybeen cleared or never set.

N/A

Please set the primary NTP server first. Attempting to set the secondaryNTP server without first setting theprimary NTP server.

N/A

Invalid IP address supplied. IP address should bein ###.###.###.### or ###.###.###.###/## formatwhere ### is between 0 and 255 and ## is between0 and 32.

Attempting to set an IP address thatis not in the correct format.

###.###.###.### where ### isbetween 0 and 255 and ## isbetween 0 and 32.

Table B-6 Administration Error Messages (continued)

ENWW Error Messages 145


Invalid e-mail address supplied. Address should bein [email protected] format.

Attempting to enter an e-mailaddress that is not in the correctformat.

E-mail addresses formatted“[email protected]” and containinga maximum of 64 characters.

E-mail address is too long. Length must be lessthan 65 characters.

Attempting to enter an e-mailaddress containing more than 64characters.

E-mail addresses formatted“[email protected]” and containinga maximum of 64 characters.

Table B-6 Administration Error Messages (continued)


C Blade PC Diagnostic Messages

The IA produces a diagnostic string associated with a degraded or critical health event from the blade.The following table lists the possible diagnostic strings it produces upon detection of a blade healthchange condition. Not all blades models support this feature. See the Models Supported column forspecific model types.

Table C-1 Blade PC Diagnostic Messages

Blade HealthState

Major Code Minor Code Diagnostic Message Models Supported

Critical /Degraded

0 0 Unknown. Please check blade for possible cause. ALL MODELS

Degraded /Critical

-1 -1 Unknown. Please check blade for possible cause. ALL MODELS

Degraded 1 0 (1800) - Temperature Alert* ALL MODELS

Critical 2 65 (101) - Option ROM Checksum Error bc2000 / bc2200 /bc2500 / bc2800

Critical 2 66 (102) - System Board Failure bc2000 / bc2200 /bc2500 / bc2800

Critical 2 67 (103) - System Board Failure 2 bc2000 / bc2200 /bc2500 / bc2800

Critical 2 201 (201) - Memory Error bc2000 / bc2200 /bc2500 / bc2800

Critical 2 1782 (1782) - Disk Controller Failure bc2000 / bc2200 /bc2500 / bc2800

Degraded 3 162 (162) - System Options Not Set bc2000 / bc2200 /bc2500 / bc2800

Degraded 3 163 (163) - Time & Date Not Set bc2000 / bc2200 /bc2500 / bc2800

Critical 3 163 (164) - Memory Size Error bc2000 / bc2200 /bc2500 / bc2800

Degraded 3 301 (301) - Keyboard Controller Error bc2000 / bc2200 /bc2500 / bc2800



Degraded 3 304 (304) - Keyboard or System Unit Error bc2000 / bc2200 /bc2500 / bc2800

ENWW 147

Blade HealthState


Degraded 3 1720 (1720) - SMART Hard Drive Detects ImminentFailure

bc2000 / bc2200 /bc2500 / bc2800

Degraded 3 1780 (1780) - Disk 0 Failure bc2000 / bc2200 /bc2500 / bc2800

Degraded 3 1790 (1790) - Disk 0 Error bc2000 / bc2200 /bc2500 / bc2800

Degraded 3 1792 (1792) - No fixed disk present bc2000 / bc2200 /bc2500 / bc2800

Degraded 3 1998 (1998) - Master Boot Record Backup Has BeenLost

bc2000 / bc2200 /bc2500 / bc2800

Degraded 3 9999 (9999) - Invalid Electronic Serial Number bc2000 / bc2200 /bc2500 / bc2800

Degraded 3 6928 (6928) - POST under Recovery BIOS image bc2000 / bc2200 /bc2500 / bc2800

Degraded 3 6929 (6929) - Blade performance is reduced due toinsufficient enclosure power and/or cooling.

bc2000 / bc2200 /bc2500 / bc2800

Critical 6 0 (6906) - Embedded Network Controller BHardware Failure Detected

bc2000 / bc2200 /bc2500 / bc2800

Critical 7 0 (6907) - System Embedded Network Controller AHardware Failure Detected

bc2000 / bc2200 /bc2500 / bc2800

Critical 8 0 (6908) - System Board Failure Detected bc2000 / bc2200 /bc2500 / bc2800

Critical 9 0 (6909) - System Graphics Subsystem FailureDetected

bc2000 / bc2200 /bc2500 / bc2800

Critical 10 0 (201) - System Memory Subsystem FailureDetected

bc2000 / bc2200 /bc2500 / bc2800

Critical 11 0 (6911) - System Board CPU Failure Detected ALL MODELS

Critical 12 0 (6912) - System On-Board Regulator FailureDetected

bc2000 / bc2500

Critical 13 0 (6913) - System Main Voltage Failure ALL MODELS

Critical 14 0 (6914) - System Has Indicated a Thermal CriticalFault Condition*

ALL MODELS

Critical 15 0 (6915) - System CPU Not Present on CurrentAttempt to Boot

bc2000 / bc2200 /bc2500 / bc2800

Degraded 16 0 (6916) - System CPU Heatsink Attachment Fault bc2000 / bc2200 /bc2500 / bc2800

Degraded 17 0 (6917) - System rebooted due to an AutomatedSystem Recovery (ASR) timer expiration

bc2000 / bc2200 /bc2500 / bc2800

Critical 18 0 (6918)- System Real Time Clock Oscillator notrunning within tolerance

bc2000 / bc2200 /bc2500 / bc2800

Critical 19 0 (6919) - Temperature and Power MonitoringHardware failure

bc2000 / bc2200 /bc2500 / bc2800

Table C-1 Blade PC Diagnostic Messages (continued)

148 Appendix C Blade PC Diagnostic Messages ENWW

Blade HealthState


Degraded 20 0 (6920) - Processor Running in ForcedPerformance Throttling Mode

bc2000 / bc2200 /bc2500 / bc2800

Degraded 21 0 (6921) - System BMC Operating Using BackupImage

bc2000 / bc2200 /bc2500 / bc2800

Degraded 22 0 (6922) - System temperature detected to bebelow 0 degrees Celsius

bc2000 / bc2200 /bc2500 / bc2800

Critical 23 0 (6923) - System CPU Temperature MonitoringHardware failure

bc2000 / bc2200 /bc2500 / bc2800

Critical 24 0 (6924) - Graphics Temperature MonitoringHardware failure

bc2000 / bc2200 /bc2500 / bc2800

Critical 25 0 (6925) - Blade / Enclosure Communication Error bc2000 / bc2200 /bc2500 / bc2800

Degraded 27 0 (6927) - System Operating Using Recovery BIOSImage

bc2000 / bc2200 /bc2500 / bc2800

*Blade caution or critical events will cause the enclosure fans to ramp and stay at 100% until the event is cleared. These eventswill cause a blade shutdown and you must power the blade back on to clear it.

NOTE: This message is equivalent to the blade system BIOS POST message. Many of these are onlydetected by the blade system BIOS during or at the end of blade POST and may not be displayed bythe blade video subsystem or transmitted via remote console to the IA when encountered.

Table C-1 Blade PC Diagnostic Messages (continued)

ENWW 149

D Maskable Enclosure System LogMessages

The IA provides a method of masking system log messages from being posted in the system logmessages based on severity classification. See system log policy CLI and GUI command details in thepreceding sections. All critical enclosure messages are not maskable as they represent catastrophicconditions that should not be prevented from logging to the system log. The following table lists whichmessages are controllable using the SET SYSLOG POLICY command.

Table D-1 Maskable Enclosure System Log Messages

Class Sub-Class System Log Message Level

Enclosure General Automatic Operating System Shutdown Initiated by a SoftPower Down

Info

Power Supply System Power Supply: General Failure (Power Supply #) Critical

System Power Supply Removed (Power Supply #) Normal

System Power Supply Inserted (Power Supply #) Normal

System Power Supply: AC Power Restored (Power Supply #) Minor

System Power Supplies are Redundant Minor

System Power Supply: Repaired (Power Supply #) Minor

System Power Supplies Operating In Non-Redundant Mode Info

System Power Supplies Operating In Resiliency Mode Info

System Power Supplies Operating In Redundant Mode Info

Thermals Blade Bay # Temperature has returned to normal. Minor

Network Tray Temperature has returned to normal Minor

Fan Exhaust Temperature has returned to normal. Minor

Chassis Temperature has returned to normal. Minor

System Overheating (Zone 0, Location bay#, Temperaturevalue deg. C)

NOTE: Blade models bc2x00 display the temperature valuefor the overheating component.

Major

Fans System Fans: Repaired (Fan #) Minor

System Fan Removed (Fan #, Location #) Normal

System Fan Inserted (Fan #, Location #) Minor

150 Appendix D Maskable Enclosure System Log Messages ENWW

Class Sub-Class System Log Message Level

System Fans are Redundant. Minor

System Fans Not Redundant (Location #) Major

Network Tray Interconnect Switch A has returned to normal. Minor

Interconnect Switch A status is degraded Major

Interconnect Switch B has returned to normal. Minor

Interconnect Switch B status is degraded. Major

Interconnect Switch Degraded: Low Performance Major

Interconnect Switch Degraded: Temp Degrade Major

Interconnect Switch has returned to normal. Minor

Bay General Bay # has been inserted Normal

Bay # has been removed Normal

Bay # power state changed to: [ON (S0) | OFF (S5)|] Info

Bay # BMC Flash Process Started

NOTE: bc2x00 Only

Info

Health Bay # has reported a failure with fault code (#, #). Diagnosis:Diagnostic Fault String

NOTE: Message is displayed for both critical or degradedhealth conditions

Critical, Major

Blade Bay # Status Normal Minor

Blade Bay # warm reset occurred Info

Bay Blade # Front IO Blanking Feature status changed toactive

Info

Bay Blade # Front IO Blanking Feature status changed toinactive

Info

Bay Blade # POST completed Info

Bay Blade # diagnostics adaptor state changed to present Info

Bay Blade # diagnostics adaptor state changed to absent Info

Bay Blade # unexpected shutdown occurred Info

Bay Blade # BIOS Flash Process Started Info

Bay Blade # BIOS Flash Process Completed Info

Bay Blade # entered PXE boot Info

Bay Blade # exited PXE boot mode Info

Bay Blade # powered off due to power management policyviolation

Info

Bay Blade # BMC flash process completed and will auto-powercycle in 10 seconds

Info

Bay Blade # will auto-powercycle now Info

Table D-1 Maskable Enclosure System Log Messages (continued)

ENWW 151

E Maskable Enclosure Event Messages

The IA provides a method of masking event messages from being displayed by the CLI during an activesession based on severity classification. See event log policy CLI and GUI command details in thepreceding sections. The policy settings are session resident only. All bay informational events aredisabled by default and must be enabled. The following table lists which messages are controllable usingthe SET EVENT POLICY command.

Table E-1 Maskable Enclosure Event Messages

Class Sub-Class Event String Notes

Level

Enclosure General Enclosure Status has changed to: Failed Critical

Enclosure Status has changed to: Degraded Major

Enclosure Status has changed to: OK Minor

Blades will auto-power on in # seconds (manual power onsuppressed)

Info

Blades will be allowed to power on in # seconds (manual poweron suppressed)

Info

Blades will auto-power on now (manual power control isallowed)

Info

Blades are allowed to power on now (manual power control isallowed)

Info

Power Supply Power Supply bay# Status has changed to: Failed Critical

Power Supply bay# Status has changed to: Degraded Major

Power Supply bay# Status has changed to: OK Minor

Power Supply bay# was inserted. Info

Power Supply bay# was removed. Normal

Power Supply bay# has an AC line problem Critical

System Power Supplies Operating In Non-Redundant Mode Info

System Power Supplies Operating In Resiliency Mode Info

System Power Supplies Operating In Redundant Mode Info

Thermals Enclosure Temperature value F / value C: Degraded Major

Enclosure Temperature value F / value C: Warm Minor

Enclosure Temperature value F / value C: OK Minor

152 Appendix E Maskable Enclosure Event Messages ENWW


Level

Fans Fan # Status has changed to: Failed - pair# (paired with Fan#)

Critical

Fan # Status has changed to: Degraded - pair# (paired withFan #)

Major

Fan # Status has changed to: OK - pair# (paired with Fan #) Info

Fan bay# was inserted Info

Fan bay# was removed. Info

Network Tray Interconnect Tray Status has changed to Failed Critical

Interconnect Tray Status has changed to Degraded Major

Interconnect Tray Status has changed to OK Minor

Interconnect Tray has reset Info

Bay Faults Blade in bay # status has changed to: Critical Critical

Blade in bay # status has changed to: Degraded Major

Blade in bay # status has changed to: OK Minor

Blade in bay # has experienced CPU Failure

NOTE: If this message was issued from a bc2x00 blade, itwill be followed by the message:

Reason: Fault Diagnostic String

The Reason string will only be masked if the parent statusevent is masked. The level of this message will be Info

Critical

Blade in bay # has experienced VRD Failure

NOTE: If this message was issued from a bc2x00 blade, itwill be followed by the message:

Reason: Fault Diagnostic String

The Reason string will only be masked if the parent statusevent is masked. The level of this message will be Info

Critical

General Blade in bay # was inserted. Normal

Blade in bay # was removed Normal

Blade in bay # has powered on Info

Blade in bay # has powered off. Info

Blade in bay # has started BMC flash mode. Info

Thermal Blade in bay # thermal state has changed to: Critical Critical

Blade in bay # thermal state has changed to: Caution Major

Blade in bay # thermal state has changed to: Warm Minor

Blade in bay # thermal state has changed to: OK Minor

Table E-1 Maskable Enclosure Event Messages (continued)

ENWW 153


Level

Bay # Temperature (CPU {value} deg. C, Graphics {value} deg.C, Ambient {value} deg. C)

NOTE: For blade models bc2x00 only. Produced after a baythermal event occurs. Masked only if thermal status is masked.

Critical, Major andMinor

Blade Blade in bay # system BIOS flashing started Info

Blade in bay # system BIOS flashing completed Info

Blade in bay # Front IO Blanking Feature status changed toactive

Info

Blade in bay # Front IO Blanking Feature status changed toabsent

Info

Blade in bay # Diagnostic Adaptor status changed to present Info

Blade in bay # Diagnostic Adaptor status changed to absent Info

Blade in bay # warm reset occurred Info

Blade in bay # entered PXE boot mode Info

Blade in bay # exited PXE boot mode Info

Blade in bay # unexpected shutdown occurred Info

Blade in bay # POST completed Info

Blade BMC in bay # has exited flash mode and will auto-powercycle in 10 seconds

Info

Blade BMC in bay # will now auto powercycle OFF and thenback ON

Info

Notes to table

● pair# = paired fan status

● bay# = bay number

Table E-1 Maskable Enclosure Event Messages (continued)

154 Appendix E Maskable Enclosure Event Messages ENWW

F Troubleshooting

This appendix provides troubleshooting information for the Integrated Administrator that ships as partof the HP PC Blade Enclosure. Use it to find details about solving performance problems that may arisewhen viewing or managing enclosure, blade PC, or user information using the Integrated Administrator.

For information on LEDs, switches, and troubleshooting information for the HP PC Blade Enclosure,refer to the HP PC Blade Enclosure Setup and Installation Guide.

Table F-1 Integrated Administrator Troubleshooting

Problem Possible Solution

My Web browser flickers when I view theIntegrated Administrator applet.

Be sure the client browser has at least 16-bit color depth.

My Web browser is not supported by theIntegrated Administrator.

Be sure to use a supported Web browser. For the most up-to-date information onsupported Web browsers, please view the customer advisories located at:

http://www.hp.com/go/cci

I am having general browser problems. For the most recent tips regarding the Integrated Administrator, refer to the customeradvisories on the following Web site:


My Web browser seems unstable when Iaccess the Integrated Administrator.

Your Java Virtual Machine (JVM) must be build 3802 or newer. Netscape users areadvised to use Netscape 6.2 or later to include this JVM and Internet Explorer userscan download the latest JVM from Sun Microsystems

This update is mandatory for Windows 95 and Windows 98 users and is availablein Service Pack 2 for Windows 2000 users. For Windows XP or Vista, please visitSun Microsystems Web site to download the latest JVM support, as well.

The Integrated Administrator does notshow the most up-to-date bladeinformation.

The blade PC information is unknown.

The blade PC configuration information is exchanged with the IntegratedAdministrator during the blade PC Power-On Self Test (POST).

If the Integrated Administrator is restarted after the blade PCs have booted, theIntegrated Administrator does not display the blade PC configuration informationuntil the blade PCs are rebooted.

Also, the blade PC BIOS obtains part of the information of the blade PC from thehealth service; so after installing the health service and/or OS; you may need to cyclethe blade PC power to enable the Integrated Administrator to see new information.

I just got logged out of the GUI. Why?What should I do?

Your rights may have changed. If so, log in again to use your new rights. If theproblem continues, contact the enclosure administrator.

When I ran “upload config,” garbageprinted to the screen and then astatement printed saying the commandcompleted successfully.

Did an error occur?

No error occurred in this command. Everything ran as expected.

ENWW 155



Problem Possible Solution

My fans periodically increase speed andthen return to their normal speed.

Fans perform a self-test for 60 seconds every 24 hours.

Although my username and mypassword are valid, I am unable to loginto the Integrated Administrator.

The Integrated Administrator supports up to 48 concurrent sessions. Be sure thenumber of sessions has not reached this threshold and check with an enclosureadministrator to be sure your account is not disabled.

The Event List does not report eventrepairs.

The Integrated Administrator does report repairs and all normal or informationalevents, however, the user has to select event policy to display them.

The user can also view the System Log of the enclosure.

Table F-1 Integrated Administrator Troubleshooting (continued)

156 Appendix F Troubleshooting ENWW

G Event Icons and Details

The Integrated Administrator provides real-time event notifications for an enclosure according to twocategories: caution and critical. When an event occurs, the Integrated Administrator notifies the user bygenerating an icon that the user can click to view more details:

Table G-1 Event Notification Icons

Icon Description

Informational—A message that is for information purposes.

Information messages have no impact on continued operability.

Normal—An event that is a usual occurrence in the operation of the enclosure.

When a normal event occurs, there is a reasonable expectation of continued operability.

Caution–Minor—An event that does not prevent the enclosure from operating, maintaining power, or serving itsuser community

When a minor event occurs, a reasonable guarantee that operability can persist exists.

Caution—An event that does not prevent the enclosure from operating, maintaining power, or serving its usercommunity

When a Caution event occurs, a reasonable guarantee that operability can persist no longer exists.

Warning—

Currently in a state that might become a problem.

Critical—An event that prevents the continued operation of the enclosure

When a Critical event occurs, the inoperability of the enclosure is imminent.

The following table provides a comprehensive list of event messages in a format that reflects the displayof the Integrated Administrator.

Table G-2 Event Details

Severity Source Date Time Event Details

Enclosure <date> <time> The enclosure has experienced a failure.

Enclosure <date> <time> Fan # has experienced a failure.

Enclosure <date> <time> Power supply # has experienced a failure.

Enclosure <date> <time> The enclosure temperature has exceeded the criticalthreshold.

ENWW 157


Blade in bay # <date> <time> Blade # has experienced a failure.

Blade in bay # <date> <time> The temperature on blade # has exceeded the criticalthreshold.

Enclosure <date> <time> Power Supply # Status has changed to: OK

Enclosure <date> <time> Fan # Status has changed to: OK - Redundant Change

Blade in bay # <date> <time> Blade in bay # thermal has changed to: Warm

Enclosure <date> <time> The enclosure is in a degraded state.

Enclosure <date> <time> Fan # is in a degraded state.

Enclosure <date> <time> The redundancy of the power supplies is in an unknown state.

Enclosure <date> <time> The power supplies are no longer redundant.

Enclosure <date> <time> Power supply # is in a degraded state.

Enclosure <date> <time> The enclosure temperature has exceeded the cautionthreshold.

Blade in bay # <date> <time> Blade # is in a degraded state.

Blade in bay # <date> <time> The temperature on blade # has exceeded the cautionthreshold.

Enclosure <date> <time> Power Subsystem capacity status changed to redundant

Enclosure <date> <time> Power Subsystem capacity status changed to resilient.

Enclosure <date> <time> Power Subsystem capacity status changed to resilient.

Enclosure <date> <time> Power Supply Hot-Plug Insertion

Enclosure <date> <time> Power Supply Hot-Plug Removal

Enclosure <date> <time> Fan Hot-Plug Insertion

Enclosure <date> <time> Fan Hot-Plug Removal

Blade in bay # <date> <time> Blade Hot Plug Insertion

Blade in bay # <date> <time> Blade Hot Plug Removal

Enclosure <date> <time> Blades will auto-power on in # seconds (manual power onsuppressed)

Enclosure <date> <time> Blades will be allowed to power on in # seconds (manual poweron suppressed)

Enclosure <date> <time> Blades will auto-power on now (manual power control isallowed)

Enclosure <date> <time> Blades are allowed to power on now (manual power control isallowed)

Blade in bay # <date> <time> The blade in bay # has powered on.

Table G-2 Event Details (continued)

158 Appendix G Event Icons and Details ENWW


Blade in bay # <date> <time> The blade in bay # has powered off.

Blade in bay # <date> <time> Blade in bay # blade management controller (BMC) has startedflash mode.

Blade in bay # <date> <time> Blade in bay # POST completed.

Blade in bay # <date> <time> Blade in bay # has powered on.

Blade in bay # <date> <time> Blade in bay # has powered off.

Blade in bay # <date> <time> Blade in bay # unexpected shutdown occurred.

Blade in bay # <date> <time> Blade in bay # system BIOS flashing started.

Blade in bay # <date> <time> Blade in bay # system BIOS flashing completed

Blade in bay # <date> <time> Blade in bay # Front IO Blanking Feature status changed to“Unknown”, “N/A”, “Inactive”, or “Active”.

Blade in bay # <date> <time> Blade in bay # Diagnostic Adaptor status changed to“Unknown”, “N/A”, “Absent”, or “Present”.

Blade in bay # <date> <time> Blade in bay # warm reset occurred.

Blade in bay # <date> <time> Blade in bay # entered PXE boot mode.

Blade in bay # <date> <time> Blade in bay # exited PXE boot mode.

Blade in bay # <date> <time> Blade management controller(BMC) in bay # has exited flashmode and will auto-powercycle in 10 seconds.

Blade in bay # <date> <time> Blade management controller (BMC) in bay # will now autopowercycle OFF and then back ON.

Table G-2 Event Details (continued)

ENWW 159

H Power Management and RedundantPower Supply

The Integrated Administrator provides power supply redundancy support for both the HP PC BladeEnclosure and HP PC Blade Enclosure G2. If both power supplies in a PC Blade Enclosure G2 enclosureare connected to an AC line voltage source of 200 volts or greater, all blades in the PC Blade EnclosureG2 enclosure will continue to run at full performance in the event of a power supply loss, regardless ofthe number of, or type of blade PCs present. This is considered best practice and is the preferreddeployment method to use when the use of redundant power supplies is desired.

In the case where less than 200 volts are available for the PC Blade Enclosure G2 enclosure, or if a HPPC Blade Enclosure is being used that has not been upgraded to a PC Blade Enclosure G2, then thedegree of power supply redundancy will vary based on the amount of AC current available and the totalblade population and blade type mix.

NOTE: A PC Blade Enclosure with IA FW installed, with both power supplies connected to an ACsource, and populated with only bc2000 or bc2200 blades, is always power supply redundant. The sameis true for a PC Blade Enclosure G2, even at line voltages as low as 100 volts.

The remainder of this section describes how the IA power supply redundancy support works in a PCBlade Enclosure G2 enclosure connected to less than 200 volts, or an enclosure that has not beenupgraded to a PC Blade Enclosure G2. In both cases, the enclosures are populated with either bc2500,bc2800, or both.

There are five power subsystem states. The power subsystem state (or status) of the enclosure isdetermined by the blade population number and mix and by the amount of line voltage available.Variations in either population or line voltage will result in changes to the enclosure’s power subsystemstate and resulting status. The five states are:

● Redundant: no blade throttling due to power supply loss. Total blade population is within theredundant power capacity.

● Resilient: all blades will be throttled due to power supply loss. Total blade population has exceededthe redundant capacity, but is within the resilient power capacity.

● Resilient (Throttling): all blades preemptively throttled to prevent enclosure or blade shutdown dueto power supply loss. Total blade population has exceeded the resilient power capacity.

● Non-Redundant: Loss of a power supply has occurred and the enclosure is no longer power supplyredundant. However, all blades are running at full performance because either the line voltage is>= 200V or the total blade population is within the redundant capacity.

● Non-Redundant (Throttling): Loss of a power supply has occurred. All blades are now throttled toensure they meet the budgeted power capacity for a single supply. Total blade population hasexceeded the redundant power capacity.

160 Appendix H Power Management and Redundant Power Supply ENWW

As long as the total blade population remains at or below the maximum number of blades allowed bythe enclosure’s redundant power capacity, the enclosure is considered to be power supply redundantand all blades will be allowed to run at full power in the event of a power supply loss. In order to determinethe maximum number of blades that will fit inside the enclosure’s redundant power budget, the powercalculator tool will need to be used. See Power Calculator Links at http://h30099.www3.hp.com/configurator/calc/Power%20Calculator%20Catalog.xls.

The following diagram illustrates the different power states and resultant blade and enclosure statusthat results by changes to line voltage and blade population.

Table H-1 Power States and Resultant Blade and Enclosure Status

Blade Population No. ofPowerSupplies

PowerSubsystem Status

Blade Status Enclosure Status

< Redundant Max

2 Redundant ● Full Power

● Green LED

● Health status OK

● Green LED

1 Non-Redundant

● Full Power

● Green LED

● Health = degraded

● Amber LED

● Syslog, event, and SNMP trapsindicating health degraded

> Redundant Max

<= Resilient Max

2 Resilient ● Full Power

● Green LED


● Amber LED


1 Non-Redundant(Throttling)

● Throttled

● Health Degraded

● Amber LED


● Amber LED


> Resilient Max

2 Resilient(Throttling)

● Throttled

● Health Degraded

● Amber LED


● Amber LED


1 Non-Redundant(Throttling)

● Throttled

● Health Degraded

● Amber LED


● Amber LED


NOTE: The HP BladeSystem bc2800 Blade PC requires the additional power and cooling supportprovided by the HP BladeSystem PC Blade Enclosure G2. Therefore, installing a bc2800 into a previousgeneration HP PC Blade Enclosure will result in the blade running at reduced performance. In order torun the bc2800 at full performance, you will need to either purchase a HP PC Blade Enclosure G2 orupgrade your existing enclosure to a PC Blade Enclosure G2 using the enclosure upgrade kit, soldseparately.

ENWW 161

http://h30099.www3.hp.com/configurator/calc/Power%20Calculator%20Catalog.xls

http://h30099.www3.hp.com/configurator/calc/Power%20Calculator%20Catalog.xls

I Factory Default Settings

This appendix provides the factory default settings for the following components of the HP PC BladeEnclosure Integrated Administrator.

● Enclosure

● Users

● Groups

● Network

● Protocol

EnclosureThe following table provides the default values in the Integrated Administrator for fields related to theblade PC enclosure.

NOTE: If you execute a SET FACTORY commant, Trap Policy and Syslog Policy settings will alsoreturn to their factory defaults.

Table I-1 Default Enclosure Values

Field Default Value

Name IA-XXXXXXXXXXXX

where XXXXXXXXXXXX is the MAC address of the Integrated Administrator

Rack Name UnnamedRack

Asset Tag Asset tag = serial number

Time Zone CST6CDT

Autopoweron Enabled

Auto Power On Delay 4 mins

Trap Policy All Enabled

Syslog Policy All Enabled

162 Appendix I Factory Default Settings ENWW

UsersIf you are using a newer HP BladeSystem PC Blade Switch (part numbers PX829AW or PX830AW),the Integrated Administrator provides the following default users:

● Administrator

● switch

● SAM (HP Session Allocation Manager)

If you are using HP BladeSystem PC Blade Switch, part number 243283-B21 or DW367A, the IntegratedAdministrator provides the following default users:

● Administrator

● switcha

● switchb

● SAM (HP Session Allocation Manager)

NOTE: The switch, switcha, and switchb accounts are used when accessing the optionally installedinterconnect switch console.

ENWW Users 163

GroupsNo default groups are in the Integrated Administrator.

NetworkThe Integrated Administrator ships with the following default values assigned:

Table I-2 Default Enclosure Values

Field Default Value

DHCP Enabled

Dynamic DNS Enabled

ProtocolThe following table provides the default values in the Integrated Administrator for fields related to networkinterface protocols:

Table I-3 Default Network Values

Field Default Value

HTTP On

SSH On

TELNET On

SOAP OFF

SNMP On

SNMP location (blank)

SNMP contact (blank)

READ community Public

WRITE community (blank)

NTP Disabled

IP Security Disabled

AlertMail Disabled

164 Appendix I Factory Default Settings ENWW

J Time Zone Settings

This appendix provides a comprehensive list of time zones supported by the HP PC Blade EnclosureIntegrated Administrator. These time zones are organized into the following categories:

● Universal

● Africa

● Asia

● Europe

● Oceania

● Polar

● The Americas

UniversalThe following table provides the Universal time zone settings supported by the Integrated Administrator.

CAUTION: For the Integrated Administrator to recognize GMT time zones, the “Etc.” string mustprecede them.

Table J-1 Universal Time Zone Values

CET Etc:GMT+5 Etc:GMT-4 HST

CST6CDT Etc:GMT+6 Etc:GMT-5 MET

EET Etc:GMT+7 Etc:GMT-6 MST

EST Etc:GMT+8 Etc:GMT-7 MST7MDT

EST6EDT+1 Etc:GMT+9 Etc:GMT-8 Navajo

Etc:GMT Etc:GMT+10 Etc:GMT-9 PST8PDT

Etc:GMT0 Etc:GMT+11 Etc:GMT-10 UCT

Etc:GMT+0 Etc:GMT+12 Etc:GMT-11 Universal

Etc:GMT+1 Etc:GMT-0 Etc:GMT-12 UTC

Etc:GMT+2 Etc:GMT-1 Etc:GMT-13 WET

Etc:GMT+3 Etc:GMT-2 Etc:GMT-14 W-SU

Etc:GMT+4 Etc:GMT-3 Greenwich Zulu

ENWW Universal 165

AfricaThe following table provides the African time zone settings supported by the Integrated Administrator.

Table J-2 African Time Zone Values

Africa:Abidjan Africa:Ceuta Africa:Lagos Africa:Niamey

Africa:Accra Africa:Conakry Africa:Libreville Africa:Nouakchott

Africa:Addis Ababa Africa:Dakar Africa:Lome Africa:Ouagadougou

Africa:Algiers Africa:Dar_es_Salaam Africa:Luanda Africa:Porto-Novo

Africa:Asmera Africa:Djibouti Africa:Lubumbashi Africa:Sao_Tome

Africa:Bamako Africa:Douala Africa:Lusaka Africa:Timbuktu

Africa:Bangui Africa:El_Aaiun Africa:Malabo Africa:Tripoli

Africa:Banjul Africa:Freetown Africa:Maputo Africa:Tunis

Africa:Bissau Africa:Gaborone AfricaMaseru: Africa:Windhoek

Africa:Blantyre Africa:Harare Africa:Mbabane Egypt

Africa:Brazzaville Africa:Johannesburg Africa:Mogadishu Libya

Africa:Brazzaville Africa:Kampala Africa:Monrovia —

Africa:Cairo Africa:Kigali Africa:Nairobi —

Africa:Casablanca Africa:Kinshasa Africa:Ndjamena

AsiaThe following table provides the Asian time zone settings supported by the Integrated Administrator.

Table J-3 Asian Time Zone Values

Asia:Aden Asia:Dushanbe Asia:Nicosia Asia:Tokyo

Asia:Almaty Asia:Gaza Asia:Novosibirsk Asia:Ujung_Pandang

Asia:Amman Asia:Harbin Asia:Omsk Asia:Ulaanbaatar

Asia:Anadyr Asia:Hong_Kong Asia:Phnom_Penh Asia:Ulan_Bator

Asia:Aqtau Asia:Hovd Asia:Pyongyang Asia:Urumqi

Asia:AqtobeAqtobe Asia:Irkutsk Asia:Qatar Asia:Vientiane

Asia:Ashgabat Asia:Istanbul Asia:Rangoon Asia:Vladivostok

Asia:Ashkhabad Asia:Jakarta Asia:Riyadh Asia:Yakutsk

Asia:Baghdad Asia:Jayapura Asia:Riyadh87 Asia:Yekaterinburg

Asia:Bahrain Asia:Jerusalem Asia:Riyadh88 Asia:Yerevan

Asia:Baku Asia:Kabul Asia:Riyadh89 Hongkong

Asia:Bangkok Asia:Kamchatka Asia:Saigon Iran

Asia:Beirut Asia:Karachi Asia:Samarkand Israel

166 Appendix J Time Zone Settings ENWW

Asia:Bishkek Asia:Kashgar Asia:Seoul Japan

Asia:Brunei Asia:Katmandu Asia:Shanghai Mideast:Riyadh87

Asia:Calcutta Asia:Krasnoyarsk Asia:Singapore Mideast:Riyadh88

Asia:Chungking Asia:Kuala_Lumpur Asia:Taipei Mideast:Riyadh89

Asia:Colombo Asia:Kuching Asia:Tashkent PRC

Asia:Dacca Asia:Kuwait AsiaTbilisi: ROC

Asia:Damascus Asia:Macao Asia:Tehran ROK

Asia:Dhaka Asia:Magadan Asia:Tel_Aviv Singapore

Asia:Dili Asia:Manila Asia:Thimbu Turkey

Asia:Dubai Asia:Muscat Asia:Thimphu

EuropeThe following table provides the European time zone settings supported by the Integrated Administrator.

Table J-4 European Time Zone Values

Eire Europe:Lisbon Europe:Skopje

Europe:Amsterdam Europe:Ljubljana Europe:Sofia

Europe:Andorra Europe:London Europe:Stockholm

Europe:Athens Europe:Luxembourg Europe:Tallinn

Europe:Belfast Europe:Madrid Europe:Tirane

Europe:Belgrade Europe:Malta Europe:Tiraspol

Europe:Berlin Europe:Minsk Europe:Uzhgorod

Europe:Bratislava Europe:Monaco Europe:Vaduz

Europe:Brussels Europe:Moscow Europe:Vatican

Europe:Bucharest Europe:Nicosia Europe:Vienna

Europe:Budapest Europe:Oslo Europe:Vilnius

Europe:Chisinau Europe:Paris Europe:Warsaw

Europe:Copenhagen Europe:Prague Europe:Zagreb

Europe:Dublin Europe:Riga Europe:Zaporozhye

Europe:Gibraltar Europe:Rome Europe:Zurich

Europe:Helsinki Europe:Samara GB

Europe:Istanbul Europe:San_Marino GB-Eire

Europe:Kaliningrad Europe:Sarejevo Poland

Europe:Kiev Europe:Simferopol Portugal

Table J-3 Asian Time Zone Values (continued)

ENWW Europe 167

OceaniaThe following table provides the Oceanic time zone settings supported by the Integrated Administrator.

Table J-5 Oceanic Time Zone Values

Atlantic:Azores Australia:North Kwajalein

Atlantic:Bermuda Australia:NSW NZ

Atlantic:Canary Australia:Perth NZ-CHAT

Atlantic:Cape_Verde Australia:Queensland Pacific:Apia

Atlantic:Faeroe Australia:South Pacific:Auckland

Atlantic:Jan_Mayen Australia:Sydney Pacific:Chatham

Atlantic:Madeira Australia:Tasmania Pacific:Easter

Atlantic:Reykjavik Australia:Victoria Pacific:Efate

Atlantic:South_Georgia Australia:West Pacific:Enderbury

Atlantic:St_Helena Australia:Yancowinna Pacific:Fakaofo

Atlantic:Stanley Iceland Pacific:Fiji

Australia:ACT Indian:Antananarivo Pacific:Funafuti

Australia:Adelaide Indian:Chagos Pacific:Galapagos

Australia:Brisbane Indian:Christmas Pacific:Gambier

Australia:Broken_Hill Indian:Cocos Pacific:Guadalcanal

Australia:Canberra Indian:Comoro Pacific:Guam

Australia:Darwin Indian:Kerguelen Pacific:Honolulu

Australia:Hobart Indian:Mahe Pacific:Johnston

Australia:LHI Indian:Maldives Pacific:Kiritimati

Australia:Lindeman Indian:Mauritius Pacific:Kosrae

Australia:Lord_Howe Indian:Mayotte Pacific:Kwajalein

Australia:Melbourne Indian:Reunion Pacific:Majuro

Pacific:Marquesas Pacific:Pitcairn Pacific:Tongatapu

Pacific:Midway Pacific:Ponape Pacific:Truk

Pacific:Nauru Pacific:Port_Moresby Pacific:Wake

Pacific:Niue Pacific:Rarotonga Pacific:Wallis

Pacific:Norfolk Pacific:Saipan Pacific:Yap

Pacific:Noumea Pacific:Samoa US:Hawaii

Pacific:Pago_Pago Pacific:Tahiti US:Samoa

Pacific:Palau Pacific:Tarawa —


PolarThe following table provides the polar time zone settings supported by the Integrated Administrator.

Table J-6 Polar Time Zone Values

Antarctica:Casey Antarctica:McMurdo Antarctica:Vostok

Antarctica:Davis Antarctica:Palmer Antarctica:Longyearbyen

Antarctica:DumontDUrville Antarctica:South_Pole Antarctica:

Antarctica:Mawson Antarctica:Syowa

AmericasThe following table provides the American time zone settings supported by the Integrated Administrator.

Table J-7 American Time Zone Values

America:Adak America:Chihuahua America:Guatemala

America:Anchorage America:Cordoba America:Guayaquil

America:Anguilla America:Costa_Rica America:Guyana

America:Antigua America:Cuiaba AmericaHalifax

America:Araguaina America:Curacao America:Havana

America:Aruba America:Dawson America:Hermosillo

America:Asuncion America:Dawson_Creek America:Indiana:Indianapolis

America:Atka America:Denver America:Indiana:Knox

America:Barbados America:Detroit America:Indiana:Marengo

America:Belem America:Dominica America:Indiana:Vevay

America:Belize America:Edmonton America:Indianapolis

America:Boa_Vista America:Eirunepe America:Inuvik

America:Bogota America:El_Salvador America:Iqaluit

AmericaBoise: America:Ensenada America:Jamaica

America:Buenos_Aires America:Fort_Wayne America:Jujuy

America:Cambridge_Bay America:Fortaleza America:Juneau

America:Cancun America:Glace_Bay America:Kentucky:Louisville

America:Caracas America:Godthab America:Kentucky:Monticello

America:Catamarca America:Goose_Bay America:Knox_IN

America:Cayenne America:Grand_Turk America:La_Paz

America:Chicago America:Guadeloupe America:Los_Angeles

America:Louisville America:Rainy_River Brazil:DeNoronha

America:Maceio America:Rankin_Inlet Brazil:East

ENWW Polar 169

America:Managua America:Recife Canada:Central

America:Manaus America:Regina Canada:Eastern

America:Martinique America:Rio_Branco Canada:East-Saskatchewan

America:Mazatlan America:Rosario Canada:Mountain

America:Mendoza America:Santiago Canada:Newfoundland

America:Menominee America:Santo_Domingo Canada:Pacific

America:Merida America:Sao_Paulo Canada:Saskatchewan

America:Mexico_City America:Scoresbysund Canada:Yukon

America:Miquelon America:Shiprock Chile:Continental

America:Monterrey America:St_Johns Chile:EasterIsland

America:Montevideo America:St_Kitts Cuba

America:Montreal America:St_Lucia Jamaica

America:Montserrat America:St_Thomas Mexico:BajaNorte

America:Nassau America:St_Vincent Mexico:BajaSur

America:New_York America:Swift_Current Mexico:General

America:Nipigon America:Tegucigalpa US:Alaska

America:Nome America:Thule US:Aleutian

America:Noronha America:Thunder_Bay US:Arizona

America:Panama America:Tijuana US:Central

America:Pangnirtung America:Tortola US:Eastern

America:Paramaribo America:Vancouver US:East-Indiana

America:Phoenix America:Virgin US:Indiana-Starke

America:Port_of_Spain America:Whitehorse US:Michigan

America:Prince America:Winnipeg US:Mountain

America:Porto_Acre America:Yakutat US:Pacific

America:Porto_Velho America:Yellowknife -

America:Puerto_Rico Brazil:Acre -

Table J-7 American Time Zone Values (continued)


K Open Source Availability

The Integrated Administrator is based on embedded Linux and contains numerous Open Sourcecomponents. In compliance with Open Source licensing, HP has made the source code of all OpenSource components used available at the following URL:

http://opensource.hp.com

To locate the Integrated Administrator project, consult the list of all projects.

ENWW 171

http://opensource.hp.com

L Supported SNMP Traps

The following table contains the supported SNMP traps:

NOTE: Please consult HP SNMP MIB file CPQRACK.MIB version 1.12 for additional trap details.

Table L-1 CPQRACK MIB Traps Supported

# Trap Name / Description Severity / State

22001 cpqRackNameChanged

Rack name changed

INFO /OPERATIONAL

22002 cpqRackEnclosureNameChanged

Enclosure name changed

INFO /OPERATIONAL

22005 cpqRackEnclosureTempFailed

Enclosure temperature failed

CRITICAL /NONOPER

22006 cpqRackEnclosureTempDegraded

Enclosure temperature degraded

MAJOR /DEGRADED

22007 cpqRackEnclosureTempOk

Enclosure temperature ok

INFO /OPERATIONAL

22008 cpqRackEnclosureFanFailed

Enclosure fan failed

CRITICAL /NONOPER

22009 cpqRackEnclosureFanDegraded

Enclosure fan degraded

MAJOR /DEGRADED

22010 cpqRackEnclosureFanOk

Enclosure fan ok

INFO /OPERATIONAL

22011 cpqRackEnclosureFanRemoved

Enclosure fan removed

MINOR /DEGRADED

22012 cpqRackEnclosureFanInserted

Enclosure fan inserted

INFO /OPERATIONAL

22013 cpqRackPowerSupplyFailed

Rack power supply failed

CRITICAL /NONOPER

172 Appendix L Supported SNMP Traps ENWW


22014 cpqRackPowerSupplyDegraded

Rack power supply degraded

MAJOR /DEGRADED

22015 cpqRackPowerSupplyOk

Rack power supply ok

INFO /OPERATIONAL

22016 cpqRackPowerSupplyRemoved

Rack power supply removed

MINOR /DEGRADED

22017 cpqRackPowerSupplyInserted

Rack power supply inserted

INFO /OPERATIONAL

22018 cpqRackPowerSubsystemNotRedundant

Rack power subsystem not redundant

MAJOR /DEGRADED

22019 cpqRackPowerSubsystemLineVoltageProblem

Rack power supply input voltage problem

MAJOR /DEGRADED

22020 cpqRackPowerSubsystemOverloadCondition

Rack power subsystem overload condition

MAJOR /DEGRADED

22028 cpqRackServerBladeRemoved

blade removed

INFO /OPERATIONAL

22029 cpqRackServerBladeInserted

blade inserted

INFO /OPERATIONAL

22037 cpqRackEnclosureManagerDegraded

IA health status degraded

MAJOR /DEGRADED

22038 cpqRackEnclosureManagerOK

IA health status repaired

INFO /OPERATIONAL

22052 cpqRackServerBladeStatusRepaired

Blade health status Repaired

INFO /OPERATIONAL

22053 cpqRackServerBladeStatusDegraded

Blade health status Degraded

MAJOR /DEGRADED

22054 cpqRackServerBladeStatusCritical

Blade health status Critical

CRITICAL /OPERATIONAL

22056 cpqRackServerBladeUnexpectedShutdown

Blade unexpected shutdown

INFO /OPERATIONAL

22057 cpqRackServerBladeManagementControllerFWUpdating

Blade management controller firmware updating

INFO /OPERATIONAL

22058 cpqRackServerBladeSystemBIOSFWUpdating

Blade system BIOS firmware updating

INFO /OPERATIONAL

Table L-1 CPQRACK MIB Traps Supported (continued)

ENWW 173


22059 cpqRackServerBladeMangementControllerFirmwareUpdateComplete

Server blade's management controller firmware update has completed

INFO /OPERATIONAL

22060 cpqRackServerBladeSystemBIOSFWUpdateComplete

Blade system BIOS firmware update complete

INFO /OPERATIONAL

22061 cpqRackServerBladeFrontIOBlankingActive

Blade front I/O blanking changed to active

INFO /OPERATIONAL

22062 cpqRackServerBladeRemoteFrontIOBlankingInactive

Blade front I/O blanking changed to inactive

INFO /OPERATIONAL

22063 cpqRackServerBladeDiagnosticAdaptorInserted

Blade diagnostic adaptor inserted

INFO /OPERATIONAL

22064 cpqRackServerBladeDiagnosticAdaptorRemoved

Blade diagnostic adaptor removed

INFO /OPERATIONAL

22065 cpqRackServerBladeEnteredPXEBootMode

Blade entered PXE boot mode

INFO /OPERATIONAL

22066 cpqRackServerBladeExitedPXEBootMode

Blade exited PXE boot mode

INFO /OPERATIONAL

22067 cpqRackServerBladeWarmReset

Blade warm reset occurred

INFO /OPERATIONAL

22068 cpqRackServerBladeBIOSPOSTCompleted

Blade system BIOS POST completed

INFO /OPERATIONAL

22069 cpqRackServerBladePoweredOn

Blade has powered on

INFO /OPERATIONAL

22070 cpqRackServerBladePoweredOff

Blade has powered off

INFO /OPERATIONAL

NOTE: In the State field, NONOPER means NONOPERATIONAL.

Table L-1 CPQRACK MIB Traps Supported (continued)

174 Appendix L Supported SNMP Traps ENWW

Index

Symbols/Numerics802.1Q 7

Aaccessing

remotely 63ROM-Based Setup Utility 111Web-based user interface 15

activity, blade PC 113adding

group 51groups 95trap targets 106user 49users 98

additional tasks 14administration

error messages 144warning messages 143

Administration tab 47administrative tasks 110advanced functions 131African time zones 166AlertMail 4, 101, 164alerts

e-mail 4, 102SNMP 4

American time zones 169Asian time zones 166asset tag 23asset tag number 93authentication 133

Bbays

information 41list 37temperature 40

Bays tab 37bits 10

bits per second 10blade PC

activity 113bay management

commands 80bays 110boot order 134error messages 144identifying 114powering off 113RBSU 111user rights 125warning messages 143

browser, Web 15

Ccertificate request 133certificates, security 12CLI

accessing 63accessing locally 63accessing remotely 63blade PC bay management

commands 80command line interface 62conventions 11enclosure management

commands 74enclosure network configuration

commands 71event messages 83exclusive functions 85general commands 64general management

commands 64operating 64user account commands 68

command line eventmessages 83

command line interface (CLI) 62, 11

commandssupported SOAP

interface 109commands, CLI

blade PC baymanagement 80

enclosure management 74enclosure network

configuration 71general 64general management 64user account 68

community string 105components, rear panel 9configuration

network 26SNMP 30

configuration scripts 54configuring

blade PC boot order 134replication 132SNMP support 105

connectivity, LAN 3connectors 9console

connector 63enabling remote sessions 45local 11log 47opening remote session 110

conventions, CLI 11creating

certificate request 133group 125

customizing enclosuresettings 91

ENWW Index 175

Ddate and time 94deck panel 17default

settings 20values for the Integrated

Administrator 10deleting

group accounts 129user accounts 127, 128

details, event 58device requirements 10DHCP 5diagnostic messages 147disabling

network protocols 136user accounts 127

documents, related to IntegratedAdministrator (IA) 2

downloading securitycertificate 133

Ee-mail alerts 102emulation 10enabling, remote console

sessions 45enclosure

alerts 4customizing settings 91error messages 144identifying 118information 19Integrated Administrator 3management commands 74managing 116maskable event

messages 152maskable log messages 150names 92network configuration

commands 71notifications 4powering off 135problems, notification of 4reviewing activity 116settings 162settings, customizing 91summary 119

system software features 3warning messages 142

Enclosure Self Recovery (ESR) 7Enclosure tab 18encryption 4entering a community string 105error messages

Administration 144blade PC bay 144enclosure 144

ESR (Enclosure Self Recovery) 7European time zones 167event

CLI messages 83details 58icons 58log policy 59maskable enclosure

messages 152notification 6

Event List tab 56

Ffactory settings 20fan status 20features

enclosure system software 3Integrated Administrator 3

firmware, update 53firmware, updating 137flash disaster recovery 139flow control 10functions, advanced 131

Ggeneral commands 64general management

commands 64getting started 8group

adding 51, 95creating 125deleting accounts 129list 48modifying 125settings 164view/modify 53

grouping, Integrated Administrator(IA) processors 6

Hheadless operation 7help 2HP Blade Enclosure Management

System and Utilities 7HP Systems Insight Manager 4,

6, 7HP Systems Insight Manager Web

site 6HP Web site 2HTTP 164hyperlinks 6

IIA firmware, 53icons 58identifying

blade PC 114enclosure 118problem components 116

IEEE 802.1Q VLAN 7initial IP address 9Integrated Administrator (IA)

components 9features 3function 8grouping processors 6hyperlinks 6

Integrated Administrator (IA) (IA)customer advisories Web

site 155related documents 2

integration with HP SAM 6Interconnect tab 59interconnect tray type 24interface

SOAP 5SOAP, disabling 108SOAP, enabling 108supported SOAP

commands 109Internet Explorer 155IP address

initial 9local console 11

IP security 103, 164

JJava Virtual Machine 155

176 Index ENWW

Kkey-based SSH

authentication 133

LLAN connectivity 3launching flash disaster

recovery 139LED 114, 118left panel 17local console 11location, modifying system 106log

Bays tab 47maskable messages 150system 34

Mmanagement

connector 63processor 6system and utilities 7

managingblade PC bays 110enclosure 116users 125

maskableenclosure event

messages 152log messages 150

messagesblade PC diagnostic 147CLI 83enclosure event 152enclosure system 150maskable event 152maskable log 150

modifyingasset tag number 93date and time 94enclosure and rack names 92group 125groups 53system contact

information 106system location 106user rights to blade PC

bays 125users 53

Nnames, enclosure and rack 92navigation 16Netscape 155network

automatic configuration 5configuration 26protocols 136settings 164

Network Time Protocol 5, 104notification, event 6notifications 4NTP 5, 104, 164number of users supported 4

OOceania time zones 168Open Source 171Open Source Web site 171

Pparity 10password, recovering 138permissions, user 90Polar time zones 169policy

event log 59system log 34

power consumptionBays tab 39Enclosure tab 32reporting 5

power management 6power subsystem status 22power supply, redundant 6powering off

blade PC 113enclosure 135

problem components 116ProLiant Essentials Rapid

Deployment Pack 7protocol settings 164protocols 136

Rrack names 92Rapid Deployment Pack 7Rapid Deployment Pack Web

site 7RBSU 6, 111read community 31, 164

rear panel components 9recommended tasks 14recovering password 138redundant power supply 6related documents, Integrated

Administrator (IA) 2remote

access 4, 63console 44control 4opening console session 110sessions 45

removing trap targets 107replicating configuration 132reporting, power consumption 5requirements, local devices 10reviewing

blade PC activity 113configuration tools and

information 8RMON 7ROM-Based Setup Utility 6, 111

Ssafety information 1SAM, integration 6Secure Sockets Layer 4security

certificate 133certificates 12downloading 133setting up IP 103

session, opening remoteconsole 110

setting upAlertMail 101IP security 103NTP 104the system 14user accounts 95Web-based user interface 12

settingsdefault 20factory 20

settings, time zone 25SNMP

alerts 4configuration 30support 105traps 107

ENWW Index 177

SOAPconfiguring support tasks 108interface 5interface, disabling 108interface, enabling 108supported interface

commands 109software

enclosure system features 3tools 6

SSH 164SSH authentication 133SSL 4stop bits 10summary, generating

enclosure 119support and troubleshooting 2Support and Troubleshooting Web

site 2supported users 4symbols equipment 1system

contact information 106location 106log 34log policy 34setup 14

Systems Insight Manager Website 6

Ttabs

Administration 47Bays 37Enclosure 18Event List 56Interconnect 59

targets 106, 107TELNET 164time 94time zone settings 25time zones

Africa 166American 169Asia 166Europe 167Oceania 168Polar 169universal 165

top panel 16

total capacity 22trap targets 106, 107traps, SNMP 107troubleshooting 2, 25

UUnit Identification LED 114, 118universal time 165update IA firmware 53updating firmware 137users

account administration 4account permissions 90account security 4account settings 163adding 49, 98CLI commands 68deleting account 128disabling and deleting

account 127list 47managing 125setting up account 95supported 4view/modify account 53

utilitiesHP Session Allocation

Manager 6HP Systems Insight

Manager 6, 7ROM-Based Setup Utility 6

Vview

group 53user 53

virtual buttonsBays tab 45Enclosure tab 33

Wwarning messages

administration 143blade PC 143enclosure 142

Web browser 15Web sites

HP 2HP Systems Insight

Manager 6

Integrated Administratorcustomer advisories 155

Open Source 171Rapid Deployment Pack 7Support and

Troubleshooting 2Web-based user interface

accessing 15navigation 16setting up 12

write community 31, 164

178 Index ENWW

Administrator's Guide - Hewlett Packardh20628. · 2013-12-23 · HP PC Blade Enclosure Integrated...

Documents

Transcript of Administrator's Guide - Hewlett Packardh20628. · 2013-12-23 · HP PC Blade Enclosure Integrated...