sun integrated lights out manager (ilom) 3.0 …people.tuke.sk/dezider.guspan/sun...

Sun Microsystems, Inc.www.sun.com

Submit comments about this document at: http://www.sun.com/hwdocs/feedback

Sun Integrated Lights Out Manager (ILOM)3.0 Supplement for Sun Blade™ 6000 and

Sun Blade 6048 Modular System

Part No. 820-7603-10May 2009, Revision A

PleaseRecycle

Copyright 2009 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved.

Sun Microsystems, Inc. has intellectual property rights relating to technology that is described in this document. In particular, and withoutlimitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one ormore additional patents or pending patent applications in the U.S. and in other countries.

This document and the product to which it pertains are distributed under licenses restricting their use, copying, distribution, anddecompilation. No part of the product or of this document may be reproduced in any form by any means without prior written authorization ofSun and its licensors, if any.

Third-party software, including font technology, is copyrighted and licensed from Sun suppliers.

Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark inthe U.S. and in other countries, exclusively licensed through X/Open Company, Ltd.

Sun, Sun Microsystems, the Sun logo, Java, AnswerBook2, docs.sun.com, Sun Blade , and Solaris are trademarks or registered trademarks ofSun Microsystems, Inc. in the U.S. and in other countries.

All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and in othercountries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc.

AMD Opteron is a trademark or registered trademark of Advanced Microdevices, Inc.

The OPEN LOOK and Sun™ Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledgesthe pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sunholds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPENLOOK GUIs and otherwise comply with Sun’s written license agreements.

U.S. Government Rights—Commercial use. Government users are subject to the Sun Microsystems, Inc. standard license agreement andapplicable provisions of the FAR and its supplements.

DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES,INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.

Copyright 2009 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, Californie 95054, Etats-Unis. Tous droits réservés.

Sun Microsystems, Inc. a les droits de propriété intellectuels relatants à la technologie qui est décrit dans ce document. En particulier, et sans lalimitation, ces droits de propriété intellectuels peuvent inclure un ou plus des brevets américains énumérés à http://www.sun.com/patents etun ou les brevets plus supplémentaires ou les applications de brevet en attente dans les Etats-Unis et dans les autres pays.

Ce produit ou document est protégé par un copyright et distribué avec des licences qui en restreignent l’utilisation, la copie, la distribution, et ladécompilation. Aucune partie de ce produit ou document ne peut être reproduite sous aucune forme, par quelque moyen que ce soit, sansl’autorisation préalable et écrite de Sun et de ses bailleurs de licence, s’il y en a.

Le logiciel détenu par des tiers, et qui comprend la technologie relative aux polices de caractères, est protégé par un copyright et licencié par desfournisseurs de Sun.

Des parties de ce produit pourront être dérivées des systèmes Berkeley BSD licenciés par l’Université de Californie. UNIX est une marquedéposée aux Etats-Unis et dans d’autres pays et licenciée exclusivement par X/Open Company, Ltd.

Sun, Sun Microsystems, le logo Sun, Java, AnswerBook2, docs.sun.com, Sun Blade , et Solaris sont des marques de fabrique ou des marquesdéposées de Sun Microsystems, Inc. aux Etats-Unis et dans d’autres pays.

Toutes les marques SPARC sont utilisées sous licence et sont des marques de fabrique ou des marques déposées de SPARC International, Inc.aux Etats-Unis et dans d’autres pays. Les produits portant les marques SPARC sont basés sur une architecture développée par SunMicrosystems, Inc.

AMD Opteron est une marque de fabrique ou une marque deposee de Advanced Microdevices, Inc.

L’interface d’utilisation graphique OPEN LOOK et Sun™ a été développée par Sun Microsystems, Inc. pour ses utilisateurs et licenciés. Sunreconnaît les efforts de pionniers de Xerox pour la recherche et le développement du concept des interfaces d’utilisation visuelle ou graphiquepour l’industrie de l’informatique. Sun détient une license non exclusive de Xerox sur l’interface d’utilisation graphique Xerox, cette licencecouvrant également les licenciées de Sun qui mettent en place l’interface d ’utilisation graphique OPEN LOOK et qui en outre se conformentaux licences écrites de Sun.

LA DOCUMENTATION EST FOURNIE “EN L’ÉTAT” ET TOUTES AUTRES CONDITIONS, DECLARATIONS ET GARANTIES EXPRESSESOU TACITES SONT FORMELLEMENT EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENTTOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L’APTITUDE A UNE UTILISATION PARTICULIERE OU AL’ABSENCE DE CONTREFAÇON.

Contents

Preface v

1. Introduction 1

Document Overview 1

New Features List 2

Key Updates for the CMM ILOM 3.0 3

Activating CMM Ethernet Ports 5

To Enable Ethernet Ports Through the CLI 6

To Enable Ethernet Ports Through the Web Interface 7

2. Firmware Update Procedures 9

Obtaining the Service Processor’s IP Address 10

Determining Your Current Firmware Versions 10

Downloading Firmware Files 13

Flashing the ILOM Firmware 14

Resetting the CMM 17

3. Sensors 19

Types of Sensors 19

Discrete Sensors 20

Threshold Sensors 20

iii

Displaying Sensors 21

Sensor Information 22

NEM Sensors 22

Power Supply Sensors 23

Fan Sensors 28

Blade Module Sensors 30

Chassis Sensors 31

ILOM 3.0 for Specific Sun Blade 6048 Cases 32

ILOM Behavior With Two Power Cord Configuration 32

ILOM Readings for Specific Power Supply States 35

iv Sun Integrated Lights Out Manager (ILOM) 3.0 Supplement for Sun Blade 6000 and 6048 Modular System • May

Preface

The Sun Sun Integrated Lights Out Manager (ILOM) 3.0 Supplement for Sun Blade 6000and 6048 Modular System contains information about Integrated Lights Out Manager(ILOM) 3.0 that is specific to the Sun Blade™ 6000 modular system.

For a complete discussion of ILOM 3.0 and its capabilities along with userprocedures, see the ILOM 3.0 documentation collection at:

http://docs.sun.com/app/docs/coll/ilom3.0

Related DocumentationThe document set for the Sun Blade 6000 modular system is described in the WhereTo Find Sun Blade 6000 Modular System Documentation sheet that is packed with yoursystem. You can also find the documentation at http://docs.sun.com.

Translated versions of some of these documents are available athttp://docs.sun.com. Select a language from the drop-down list and navigate tor document collection using the Product category link. Available translations includeFrench, Simplified Chinese, Traditional Chinese, Korean, and Japanese.

English documentation is revised more frequently and might be more up-to-datethan the translated documentation. For all Sun documentation, go tohttp://docs.sun.com.

v


http://docs.sun.com

http://docs.sun.com

http://docs.sun.com

Typographic Conventions

Third-Party Web SitesSun is not responsible for the availability of third-party web sites mentioned in thisdocument. Sun does not endorse and is not responsible or liable for any content,advertising, products, or other materials that are available on or through such sitesor resources. Sun will not be responsible or liable for any actual or alleged damageor loss caused by or in connection with the use of or reliance on any such content,goods, or services that are available on or through such sites or resources.

Sun Welcomes Your CommentsSun is interested in improving its documentation and welcomes your comments andsuggestions. You can submit your comments by going tohttp://www.sun.com/hwdocs/feedback.

Please include the title and part number of your document with your feedback:

Sun Sun Integrated Lights Out Manager (ILOM) 3.0 Supplement for Sun Blade 6000 and6048 Modular System, part number 820-7603-10.

Typeface*

* The settings on your browser might differ from these settings.

Meaning Examples

AaBbCc123 The names of commands, files,and directories; onscreencomputer output

Edit your.login file.Use ls -a to list all files.% You have mail.

AaBbCc123 What you type, when contrastedwith onscreen computer output

% su

Password:

AaBbCc123 Book titles, new words or terms,words to be emphasized.Replace command-line variableswith real names or values.

Read Chapter 6 in the User’s Guide.These are called class options.You must be superuser to do this.To delete a file, type rm filename.

vi Sun Integrated Lights Out Manager (ILOM) 3.0 Supplement for Sun Blade 6000 and 6048 Modular System • May

http://www.sun.com/hwdocs/feedback

CHAPTER 1

Introduction

This supplement provides platform-specific information related to ILOM 3.0 runningon the Sun Blade 6000 or Sun Blade 6048 modular system CMM.

The following topics are covered in this chapter:

■ “Document Overview” on page 1

■ “New Features List” on page 2

■ “Key Updates for the CMM ILOM 3.0” on page 3

■ “Activating CMM Ethernet Ports” on page 5

Document OverviewThis document is a supplement that contains information specific to the Sun Blade6000 and Sun Blade 6048 modular system CMM ILOM 3.0. For more detailedinformation on setting up and using the ILOM 3.0, refer to the documentation in theILOM 3.0 Documentation Collection at:


This document contains information on new features for ILOM 3.0 (in this chapter),instructions for updating the ILOM firmware in “Firmware Update Procedures” onpage 9 and information on chassis sensors in “Sensors” on page 19.

Note – The term blade module is used to refer to a module that could be either aserver module or a storage module.

1


New Features ListILOM 3.0 is enhanced with many new features and functions that were not availablein ILOM 2.x, including improved security, improved usability, and easier integrationinto your data center environment ILOM.

TABLE 1-1 lists new features for ILOM 3.0. These features are described more fully inthe ILOM 3.0 Documentation Collection.

TABLE 1-1 ILOM 3.0 New Features

Category Feature

General Functionality

DNS support

Timezone support

Configuration backup and restore

Restore to factory defaults

Enhanced LDAP and LDAP/SSL support

Power management capabilities

Ability to generate new SSH keys

Scalability and Usability

User-configurable filtering of hardware monitoringinformation in CLI and web interface

Use host name to access other services by name, such asLDAP, Active Directory, LDAP/SSL

Security

More granular user roles

Predefined root and default accounts

User SSH key authentication

Ability to disable the network management port when youare using only the serial port

Ability to disable individual services, such as IPMI, SSH,and KVMS, so that the port is closed

Serviceability

Data collection utility to diagnose system problems

2 Sun Integrated Lights Out Manager (ILOM) 3.0 Supplement for Sun Blade 6000 and 6048 Modular System • May

Key Updates for the CMM ILOM 3.0The following are key updates that are specific to the CMM ILOM 3.0:

■ “Updates to the ILOM 3.0 Web Interface” on page 3

■ “Changes in Power Allocated to the Blade Modules” on page 5

■ “Fan Speed Control Improvements” on page 5

Updates to the ILOM 3.0 Web Interface

Chassis View on Main Page

The following items are new in the chassis view that you see when you first log intothe ILOM web interface:

■ Down the left side, there are hyperlinks to blade modules (and possibly NEMs)that are installed in the chassis that have SP Web interfaces. ILOM 2.0 shows allblade modules, even if those blade modules are absent.

■ There is a new Chassis Inventory table right on the chassis view, which shows thevarious blade module and NEM components, their part numbers and serialnumbers.

System Information Tab

On the System Information tab, there is now a Fault Management sub-tab that isnew for the CMM.

If the CMM decides a component is faulty, the fault is displayed on this tab. TheCMM determines that a blade module or NEM is faulty if the blade module has itsamber SERVICE LED turned on. Clicking on the fault will display more details.

Chapter 1 Introduction 3

System Monitoring Tab

In the System Monitoring tab, Power Management sub-tab, there are a few newitems. They include the following:

■ Power History: Many blade module platforms record their power usage history(those that are able to measure power usage). The CMM records the chassispower history (called /CH/VPS), but also records the blade module power usagehistory (/CH/BLx/VPS) for server module blades that are capable of measuringtheir own power and are running ILOM 3.0.

■ Advanced Power Metrics: This existed in ILOM 2.0, but is greatly expanded inILOM 3.0 to help customers understand the power allocation within the chassis.TABLE 1-2 describes the available power metrics.

TABLE 1-2 Advanced Power Metrics

Metric Description

BLx HW Config Power Given the blade module’s hardware configuration of processors and memory, this isthe maximum power the blade module could possibly draw.

BLx Allocated Power This is the maximum power allocated to the blade module slot. For blade modulesrunning ILOM 2.0, this will match the "BLx HW Config Power". For blade modulesrunning ILOM 3.0, if the blade module is powered off, no power is allocated to theslot, which allows that power to be used to power on other blade modules.

NEMx AllocatedPower

Maximum power allocated to the NEM.

PSx Allocated Power Maximum power allocated to the power supply (the difference between AC inputpower and DC out power).

PSx/FAN AllocatedPower

Maximum power allocated for the power supply fans.

FMx Allocated Power Maximum power allocated to the fan module.

CMM Allocated Power Maximum power allocated to the CMM service processor.

Available Power Input power available to the system; the sum of the maximum AC input to all powersupplies.

Permitted Power The maximum power that the chassis is permitted to use. If "Reserve Power Supplies"is 0, this will match "Available Power". If "Reserve Power Supplies" is 1, this will behalf of "Available Power".

Redundant Power This is the power held in reserve in case of a power supply failure. Its value is"Available Power" minus "Permitted Power".

Allocated Power The sum of all of the allocated power numbers above. This can not exceed permittedpower.

Allocatable Power The power still available to be allocated to blade modules; Its value is "PermittedPower" minus "Allocated Power".


Changes in Power Allocated to the Blade ModulesThere is a big change in ILOM 3.0 power allocation to the blade modules. In ILOM2.0, a blade module determines if there is enough Permitted Power for all blademodules to power on; if there is not enough power, the blade module does notpower on. For a rack with many high-powered blade modules, this results in noblade modules powering on.

In ILOM 3.0 (with ILOM 3.0 on both the CMM and on the blade modules), the blademodule is allocated 0 Watts when it is powered off. When a blade module wants topower on, it contacts the CMM and requests some amount of power to be allocatedto the slot. The CMM then allocates power to the slot and allows the blade moduleto power on. When a blade module powers off, it releases the power back to theCMM.

As a result, even if you have a rack full of high-powered blade modules, you can stillpower on some subset of blade modules. Once all permitted power is used up, youcannot power on any more blade modules until a running blade module is poweredoff. But once you power off one blade module, you’ll be able to power on anotherblade module.

Fan Speed Control ImprovementsThere are some fan speed control improvements in ILOM 3.0 for CMM, when ILOM3.0 is running on both the CMM and blade modules. In ILOM 2.0, the CMM sets thefan speed based on ambient temperature. In ILOM 3.0, the CMM uses feedback fromthe blade modules to determine the lowest fan speed that will maintain appropriatetemperature for the blade modules.

This new fan speed control feature is only available if the CMM and all blademodules in the chassis are running ILOM 3.0.

Activating CMM Ethernet PortsBy default, Ethernet Port 0 is enabled on the CMM. You can enable Port 1 or enableboth ports through the CLI or the web interface.


Caution – You can cause Ethernet networking problem and bring down the externalnetwork if you activate both Ethernet ports on the CMM. Before you activate bothports, make sure the external switch supports trunk mode. The upstream Ethernetswitch needs to be configured correctly, so that no Ethernet traffic loop is created.This is done usually by the spanning tree algorithm.

To Enable Ethernet Ports Through the CLITo enable port 1 via the CLI:

1. Log in to the ILOM CLI:

2. Type:

ssh root@networkaddress

cd /CMM/network


3. Type show to view the switchconf variable setting.

For example:

In this example, the switchconf variable is set to port0.

■ To activate port 1 and disable port 0, type: switchconf=port1

■ To activate port 1 and keep port 0 active, type switchconf=trunk

4. Remove the CMM and reinstall it into the chassis.

See the chassis Service Manual for instructions on removing and replacing theCMM in the chassis.

The active port is now NET MGT port 1 or both NET MGT ports.

To Enable Ethernet Ports Through the WebInterfaceTo enable an Ethernet port using the web interface:

1. Open a web browser and type the IP address of the server SP or CMM.

The Login page for the ILOM web interface appears.

show/CMM/network Targets:

Properties: commitpending = (Cannot show property) ipaddress = 10.6.153.71 ipdiscovery = dhcp ipgateway = 10.6.152.1 ipnetmask = 255.255.252.0 macaddress = 00:14:4F:6B:6F:C1 pendingipaddress = 10.6.153.71 pendingipdiscovery = dhcp pendingipgateway = 10.6.152.1 pendingipnetmask = 255.255.252.0 switchconf = port0

Commands: cd set show


2. In the ILOM Login page, enter a user name and password then click OK.

The ILOM web interface appears.

3. Click on CMM in the left panel.

4. Click the Configuration tab, then the Network tab.

FIGURE 1-1 ILOM Web Interface Network Screen

In the CMM Management Network Switch drop down list, select the port thatyou want to activate or Trunking (Link Aggregation) to activate both ports.

5. Remove the CMM and reinstall it into the chassis.

See the chassis Service Manual for instructions on removing and replacing theCMM in the chassis.

The active port is now NET MGT port 1 or both NET MGT ports.


CHAPTER 2

Firmware Update Procedures

This section describes how to use the service processor to update the CMM ILOM.This information is covered in more detail in the ILOM 3.0 DocumentationCollection at:


Use the following sections, in order:

1. Obtain the IP address of the CMM. See “Obtaining the Service Processor’s IPAddress” on page 10.

2. Log on to the CMM to check the versions of firmware you have. See“Determining Your Current Firmware Versions” on page 10.

3. Use ILOM to download the new versions of firmware. See “DownloadingFirmware Files” on page 13.

4. Use ILOM to install the new firmware. See “Flashing the ILOM Firmware” onpage 14.

5. Reset the CMM. See “Resetting the CMM” on page 17.

Note – For information on backup and restoring the ILOM configuration, refer tothe Sun Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide or the SunIntegrated Lights Out Manager (ILOM) 3.0 Web Interface Procedures Guide.

9


Obtaining the Service Processor’s IP AddressYou must use the CMM IP address to access to the ILOM. If you do not alreadyknow the Service Processor’s IP address, you must determine it.

Refer to Sun Integrated Lights Out Manager (ILOM) 3.0 Getting Started Guide forinstructions on how to determine the IP address of the CMM.

Determining Your Current Firmware VersionsThere are three alternate procedures in this section that you can use:

■ “Using the CLI Through the Management Ethernet Port” on page 10

■ “Using the CLI Through the Serial Management Port” on page 11

■ “Using the Web Interface” on page 12

Using the CLI Through the Management Ethernet PortSee the Sun Integrated Lights Out Manager (ILOM) 3.0 Getting Started Guide for moredetailed information on this procedure.

1. Connect an RJ-45 Ethernet cable to the NET MGT Ethernet port on the chassisCMM by establishing an SSH connection using the following command:

# ssh -l root cmm_ip

where cmm_ip is the IP address of the CMM.

2. The login prompt is displayed:

/hostname/login:

Where hostname could be SUNCMM followed by the product serial number, or if thecustomer has enabled hostnames in DHCP, it will be the assigned host name.

3. Enter the default password when you are prompted:

/hostname/login: root

password: changeme

4. After you have successfully logged in, the CMM displays its default commandprompt:

->


5. Type the version command, which returns output similar to the following:

The ILOM (CMM) firmware version and build number are listed in the output.

Using the CLI Through the Serial Management Port1. Configure your terminal device or the terminal emulation software running on

a laptop or PC to the following settings:

2. Connect a serial cable from the RJ-45 SER MGT port on the CMM to yourterminal device or PC.

3. Press Enter on the terminal device to establish a connection between thatterminal device and the CMM.

The CMM displays a login prompt.

/hostname/login:

Where hostname could be SUNCMM followed by the product serial number, or if thecustomer has enabled hostnames in DHCP, it will be the assigned hostname.

4. Log in to the ILOM CMM and type the default user name (root) with thedefault password (changeme).

After you have successfully logged in, the CMM displays its default commandprompt:

->

-> versionCMM firmware version: 3.0.3.32CMM firmware build number: 42331CMM firmware date: Wed Feb 18 11:46:55 PST 2009CMM filesystem version: 0.1.22

8N1: eight data bits, no parity, one stop bit9600 baudDisable hardware flow control (CTS/RTS)Disable software flow control (XON/XOFF)

Chapter 2 Firmware Update Procedures 11

5. Type the version command, which returns output similar to the following:

The ILOM firmware version and build number are listed in the output.

Using the Web Interface1. Connect to the ILOM Web interface by entering the IP address of the server’s

CMM in your browser’s address field. For example:

https://129.146.53.150

2. Log in to the ILOM CMM and type the default user name (root) with thedefault password (changeme).

The first Web page presented is the Chassis View page, which includes shows animage of the chassis front and back with installed modules, along with a chassisinventory.

FIGURE 2-1 ILOM Chassis View Page

-> versionCMM firmware version: 3.0.3.32CMM firmware build number: 42331CMM firmware date: Wed Feb 18 11:46:55 PST 2009CMM filesystem version: 0.1.22


3. To view the ILOM version, click on CMM in the upper left corner.

The System Information -> Versions page is displayed, which includesthe firmware version and build number.

FIGURE 2-2 ILOM Versions Window

Downloading Firmware FilesDownload the flash image .ima file using these steps:

1. Browse to http://www.sun.com/download/

2. Click View by Category.

3. Click X64 Servers and Workstations in the Hardware Drivers area.

4. Click the link for Sun Blade 6000 chassis.

5. Enter your Username and Password.

If you do not have a Username and Password, you can register free of charge byclicking Register Now.

6. Click Accept License Agreement.


7. Click the appropriate firmware image file name:

ILOM-version-Sun_Blade_6000.ima or

ILOM-version-Sun_Blade_6048.ima

For example:

ILOM-3_0_3_32-Sun_Blade_6048.ima or

ILOM-3_0_3_32-Sun_Blade_6000.ima

Flashing the ILOM Firmware

Caution – ILOM enters a special mode to load new firmware. No other tasks can beperformed in ILOM until the firmware upgrade is complete and the ILOM is reset.

This is the procedure that actually flashes the firmware, replacing the existingimages with the new images from the .pkg file you downloaded previously.

This section describes two methods of flashing the ILOM/BIOS firmware:

■ “Updating the Firmware with the ILOM GUI” on page 14

■ “Updating the Firmware With the ILOM CLI” on page 16

Updating the Firmware with the ILOM GUI1. Log into the ILOM GUI by pointing your browser at the IP address of the

Service Processor. For example:

https://10.6.78.144

2. Select the Maintenance tab.

3. Select the Firmware Upgrade tab.


FIGURE 2-3 Firmware Upgrade Tab

4. Click the Enter Upgrade Mode button.

An Upgrade Verification dialog appears, indicating that other users who arelogged in will lose their session when the update process completes.

5. In the Upgrade verification dialog, click OK to continue.

The Firmware Upgrade page appears.

6. Browse for the flash image file.

7. Click the Upload button.

Wait for the file to upload and validate.

The Firmware Verification page appears.

8. (Optional) In the Firmware Verification page, enable the PreserveConfiguration.

Enable this option if you want to save your existing configuration in ILOM andrestore that existing configuration after the update process completes.

9. Click Start Upgrade to start the upgrade process or click Exit to cancel theprocess.

When you click Start Upgrade the upload process will start and a prompt tocontinue the process appears.


10. At the prompt, click OK to continue.

The Update Status page appears providing details about the update progress.When the update indicates 100%, the firmware upload is complete.

When the upload completes, the system automatically reboots.

Note – The ILOM web interface might not refresh properly after the updatecompletes. If the ILOM web is missing information or displays an error message,you might be viewing a cached version of the page from the version previous to theupdate. Clear your browser cache and refresh your browser before continuing.

11. Reconnect to the CMM ILOM web interface.

12. Select System Information --> Version to verify that the firmware version onthe CMM corresponds to the firmware image you installed.

Note – If you did not preserve the ILOM configuration before the firmware update,you will need to perform the initial ILOM setup procedures to reconnect to ILOM.

Updating the Firmware With the ILOM CLI1. Log onto the ILOM CLI through the Management Ethernet Port (see “Using the

CLI Through the Management Ethernet Port” on page 10) or the serial port (see“Using the CLI Through the Serial Management Port” on page 11).

2. From the ILOM CLI, use the following command:

load -source tftp://tftpserver/ILOM-version-Sun_Blade_60x0.ima

where tftpserver is the trivial file-transfer protocol (TFTP) server that contains theupdate and ILOM-version-Sun_Blade_60x0.ima is the firmware image file, forexample:

ILOM-3_0_3_32-Sun_Blade_6000.ima or

ILOM-3_0_3_32-Sun_Blade_6048.ima


Resetting the CMMTo reset the ILOM CMM, you can do any of the following:

■ From the ILOM CMM graphical Web interface:

a. Click the Maintenance tab.

b. Click the Reset Components sub-tab.

c. Select /CH/CMM, then click Reset.

FIGURE 2-4 ILOM Reset Service Processor Window

■ From the ILOM CLI, use the following command:

reset /CMM

■ Shut down the chassis power, remove the AC power cords, then reinstall thepower cords.


CHAPTER 3

Sensors

This chapter contains ILOM sensor information for both the Sun Blade 6000 and SunBlade 6048 chassis. The information in this section is specific for ILOM 3.0.

For sensor information for previous versions of ILOM, see the Integrated Lights OutManager (ILOM) Administration Guide for the Sun Blade 6000 Modular System for SunBlade 6000 and the Sun Blade 6048 Modular System Service Manual for the Sun Blade6048.

This chapter contains the following sections:

■ “Types of Sensors” on page 19

■ “Displaying Sensors” on page 21

■ “Sensor Information” on page 22

■ “ILOM 3.0 for Specific Sun Blade 6048 Cases” on page 32

Types of SensorsThere are two types of CMM sensors:

■ Discrete sensors display information about the CMM components.

■ Threshold sensors show analog values, such as temperature readings or voltagelevels.

19

Discrete SensorsDiscrete sensors display a single value from a set of possible values.

Discrete sensors are displayed in the following format:

Where the following variables are used:

■ POSSIBLE_SUB_SENSORS: A list of sensors below this sensor. Examples includefault or warning sensors. Using the cd command, you can navigate to the sub-sensor node.

■ SENSOR_TYPE: The type of sensor.

■ SENSOR_VALUE: The sensor value.

Threshold SensorsThreshold sensors display analog readings, such as temperature or voltage levels,and associated thresholds for that reading. These can be configured to generatesystem events when they exceed specified thresholds.

In general, these sensors are displayed in the following format:

/PATH/TO/SENSOR Targets: $(POSSIBLE_SUB_SENSORS) Properties: type = $(SENSOR_TYPE) class = Discrete value = $(SENSOR_VALUE)

/PATH/TO/SENSOR Targets: $(POSSIBLE_SUB_SENSORS) Properties: type = $(SENSOR_TYPE) class = Threshold value = $(SENSOR_VALUE) $(SENSOR_UNITS) upper_nonrecov_threshold = $(UNR_THRESH) $(SENSOR_UNITS) upper_critical_threshold = $(UC_THRESH) $(SENSOR_UNITS)

upper_noncritical_threshold = $(UNC_THRESH) $(SENSOR_UNITS) lower_nonrecov_threshold = $(LNR_THRESH) $(SENSOR_UNITS) lower_critical_threshold = $(LC_THRESH) $(SENSOR_UNITS)

lower_noncritical_threshold = $(LNC_THRESH) $(SENSOR_UNITS)


■ POSSIBLE_SUB_SENSORS: A list of sensors below this sensor. Examples includefault or warning sensors. Use the CD command to navigate to the sub-sensor.

■ SENSOR_TYPE: The type of sensor.

■ SENSOR_VALUE: The near real-time analog reading from the sensor.

■ SENSOR_UNITS: The units describing the SENSOR_VALUE reading.

■ UNR_THRESH, UC_THRESH UNC_THRESH, LNR_THRESH, LC_THRESH,LNC_THRESH: These values may generate a system event if theSENSOR_VALUE crosses their thresholds.

If the CLI has no access to threshold values, for example if a component is notpresent, the corresponding sensor is displayed as “0.000”.

Displaying SensorsAll sensors are located in the /CH namespace. To display the sensors using the CLI,separate the fields into targets and navigate using the cd and show commands.

For example, the speed for fan 0 in fan module 3 can be viewed by entering:

-> show /CH/FM3/F0/TACH

Note – If the chassis slot does not contain a server module, or if a power supply isnot present, the corresponding target might not appear. For example, if slot 3 isempty, the target BL3 might not appear.

Chapter 3 Sensors 21

Sensor InformationAll sensors listed in this section can be accessed through the ILOM CLI or webinterface by placing /CH in front of the sensor path shown here. For example, toaccess the NEMn/PRSNT, use the path /CH/NEMn/PRSNT.

The following sensors are described in this section:

■ “NEM Sensors” on page 22

■ “Power Supply Sensors” on page 23

■ “Fan Sensors” on page 28

■ “Blade Module Sensors” on page 30

■ “Chassis Sensors” on page 31

■ “ILOM 3.0 for Specific Sun Blade 6048 Cases” on page 32

NEM SensorsThere are two network express module (NEM) slots available in the chassis. NEMsare numbered from 0 to 1.

NEMn/PRSNT

These sensors report whether the NEMs are present.

TABLE 3-1 NEMn/PRSNT Readings

Reading State Event Description

0x0001 Device Absent Yes NEM is absent.

0x0002 Device Present Yes NEM is present.


NEMn/STATE

These sensors report the state of any multi-fabric NEMs that are installed in thechassis.

NEMn/ERR

These sensors report whether any multi-fabric NEMs have failed.

Power Supply SensorsThere are two power supply modules in the chassis. Each power supply modulecontains two power supplies or “sides” for the Sun Blade 6000 chassis and threepower supply sides for the Sun Blade 6048 chassis. Power supply modules arenumbered from 0 to 1 and power supply sides are numbered from 0 to 1.

PSn/PRST

Reports the presence of the power supply module.

TABLE 3-2 NEMn/STATE Readings


0x0001 Running Yes NEM is running.

0x0004 Powered Off Yes NEM is powered off.

0x0040 Degraded Yes NEM needs to be serviced

TABLE 3-3 NEMn/ERR Readings


0x0001 Predictive Failure Asserted Yes NEM has failed.

0x0002 Predictive Failure Deasserted Yes NEM has not failed.

TABLE 3-4 PSn/PRST Readings


0x0001 Device Absent Yes Power supply is absent.

0x0002 Device Present Yes Power supply is present.


PSn/IN_POWER

These threshold sensors report the input (AC) power to the power supplies in Watts.

The power sensors are only accurate when the chassis is drawing a significantamount of power. Under low power conditions, the chassis cannot accuratelymeasure power, so it will report "no reading". Typically, accurate power cannot bereported if the Sun Blade 6000 chassis is drawing less than 1500 Watts or if the SunBlade 6048 chassis is drawing less than 2200 Watts.

PSn/OUT_POWER

These threshold sensors report the output (DC) power from the power supplies inWatts.


PSn/T_AMB

These threshold sensors report the ambient temperature of the power supplymodules.

PSn/V_12V

These threshold sensors report the power supply module 12V voltage reading.

PSn/V_3V3

These threshold sensors report the power supply module 3_3V voltage reading.

PSn/I_3V3

These threshold sensors report the power supply module 3_3V current rating.


PSn/V_3V3_ERR

Reports a power supply module 3_3V sensor fault.

PSn/TEMP_WRN

Reports that ambient temperature reaches the following range: 50o to 60o C.

PSn/TEMP_ERR

Reports presence of a power supply temperature error.

TABLE 3-5 PSn/V_3V3_ERR Readings


0x0001 Predictive FailureDeasserted

No This state indicates that a power supply 3_3Vfault has not occurred.

0x0002 Predictive FailureAsserted

Yes This state indicates that a power supply 3_3Vfault has occurred.

TABLE 3-6 PSn/TEMP_WRN Readings



No This state indicates that a power supply ambienttemperature has not reached the 50o to 60o Crange.


Yes This state indicates that a power supply ambienttemperature has reached the 50o to 60o C range.

TABLE 3-7 PSn/TEMP_ERR Readings



No This state indicates that a power supplytemperature fault has not occurred.


Yes This state indicates that a power supplytemperature fault has occurred.


PSn/FAN_ERR

Reports presence of a power supply fan error.

PSn/FANn/TACH

These threshold sensors report the speed of the two fans in the power supply.

PSn/Sn/V_OUT_OK

Reports the state of a power supply side.

PSn/Sn/I_12V

These threshold sensors report the power supply side 12V voltage reading.

TABLE 3-8 PSn/FAN_ERR Readings



No This state indicates that a power supply fan faulthas not occurred.


Yes This state indicates that a power supply fan faulthas occurred.

TABLE 3-9 PSn/Sn/V_12V_ERR Readings



No This state indicates that a power supply side faulthas not occurred.


Yes This state indicates that a power supply side faulthas occurred.


PSn/Sn/V_IN_ERR

Reports a power supply side fault.

PSn/Sn/V_12V_ERR

Reports a power supply side 12V voltage sensor fault.

PSn/Sn/I_12V_ERR

Reports a power supply side 12V voltage sensor fault.




No This state indicates that a power supply side faulthas not occurred.


Yes This state indicates that a power supply side faulthas occurred.




No This state indicates that a power supply side 12Vvoltage fault has not occurred.


Yes This state indicates that a power supply side 12Vvoltage fault has occurred.




No This state indicates that a power supply side 12Vvoltage fault has not occurred.


Yes This state indicates that a power supply side 12Vvoltage fault has occurred.


PSn/Sn/I_12V_WRN

Reports that power supply side 12V output current exceeds 240A for 100 msec.

VPS

VPS is the virtual power sensors and reports the total power used by the chassis(typically the sum of PS0/IN_POWER and PS1/IN_POWER).


Fan SensorsThe Sun Blade 6000 chassis contains six fan modules and the Sun Blade 6048 chassiscontains eight fan modules. Each module contains two fans. Fan modules arenumbered from 0 to 5 for Sun Blade 6000 and 0 to 7 for Sun Blade 6048. Fans arenumbered from 0 to 1.

TABLE 3-13 PSn/Sn/I_12V_WRN Readings



No This state indicates that a power supply side 12Vcurrent does not exceed 240A for 100 msec.


Yes This state indicates that a power supply side 12Vcurrent exceeds 240A for 100 msec.


FMn/Fn/TACH

These sensors report individual fan speeds. All fan speed sensors are configured togenerate the same events and all faults are handled in the same way. They are notmonitored when the chassis is powered off.

FMn/ERR

These sensors report fan module failure status.

TABLE 3-14 FMn/Fn/TACH Readings

Threshold Direction Event Description

Lower Non-Recoverable

Assert Yes Fan speed has decreased below lower non-recoverablethreshold.This indicates that the fan has failed or has beenremoved.

Lower Non-Recoverable

Deassert Yes Fan speed has returned to normal from lower non-recoverable.This indicates that the fan has returned to normal orhas been replaced.

TABLE 3-15 FMn/ERR Readings



No This state indicates that the fan module has notfailed.


Yes This state indicates that the fan module hasfailed.


Blade Module SensorsThe Sun Blade 6000 chassis has 10 blade slots for server or storage modules (blademodules) and blade slots are numbered from 0 to 9.

The Sun Blade 6048 chassis has 12 blade slots for server or storage modules (blademodules) and blade slots are numbered from 0 to 11.

BLn/PRSNT

These sensors report whether server modules are present in the specified slots.

BLn/STATE

These sensors report the state of the server modules.

BLn/ERR

These sensors report whether there is a fault on the server module.

TABLE 3-16 BLn/PRSNT Readings


0x0001 Device Absent No Server module is not present.

0x0002 State Present No Server module is present.

TABLE 3-17 BLn/STATE Readings


0x0001 Running No Server module is running.

0x0004 Power Off No Server module is not powered off.

0x0020 Off Duty No Server module is ready to remove.

TABLE 3-18 BLn/ERR Readings


0x0001 Predictive Failure Asserted Yes Server module has failed.

0x0002 Predictive Failure Deasserted Yes Server module has not failed.


BLn/VPS

These sensors report the virtual power for the server modules. This sensor shouldmatch the /SYS/VPS sensor reading on the server module. Slots are numbered from0 to 9 for Sun Blade 6000 and 0 to 11 for Sun Blade 6048.

This sensor is only available on some server modules, and only if the server moduleis running ILOM 3.0. Otherwise, BLn/VPS will report "no reading". Refer to theserver module documentation to determine whether or not this sensor is available.

Chassis SensorsThe following sensors are for the Sun Blade 6000 and Sun Blade 6048 chassis.

HOT

This sensor reports if any blade is requesting full fan speed due to high temperature.

T_AMBO

T_AMB0 reports ambient temperature in the chassis midplane. This sensor is formonitoring only; no threshold is defined.

TABLE 3-19 HOT Readings


0x0001 State Deasserted No This state indicates that no blade is requestingfull fan speed.

0x0002 State Asserted No This state indicates that one ore more bladesis requesting full fan speed.


P_OVER_WARN

Reports power supply oversubscription state.

ILOM 3.0 for Specific Sun Blade 6048CasesThis section covers the following topics:

■ “ILOM Behavior With Two Power Cord Configuration” on page 32

■ “ILOM Readings for Specific Power Supply States” on page 35

ILOM Behavior With Two Power CordConfigurationThis section specifies how CMM and server module firmware behave when only twoof the three power plugs are connected to an A231 power supply module.

There are three plugs on the back of each A231 PSU. These plugs are named AC0,AC1, and AC2. Each allow connection of a 220V power cord.When only two of theavailable three plugs is connected to the A231 PSUs, this will provide 5600 watts tothe entire chassis.

If you connect only two of the total three plugs, connect them to AC0 and AC1. AC2should not be connected.

The following topics are addressed:

■ “Configuring the CMM for Two Power Cords” on page 33

■ “CMM IPMITool Readings” on page 34

■ “Server Module IPMITool Readings” on page 34

TABLE 3-20 P_OVER_WARN Readings


0x0001 State Deasserted No Power supplies are not oversubscribed; blademodules are allowed to turn on.

0x0002 State Asserted No Power supplies are oversubscribed; someblade modules might not turn on.


For details on ILOM 3.0, refer to the Sun Integrated Lights Out Manager 3.0 User’sGuide.

Configuring the CMM for Two Power CordsTo set up a two power cord configuration, disable the power supply side to in theCMM ILOM with the following commands:

To view the disabled power cord side 2 configuration:

-> set /CMM/policy MONITOR_PS0_SIDE2=disabled-> set /CMM/policy MONITOR_PS1_SIDE2=disabled

-> show /CMM/policy//CMM/policy Targets: Properties: COOLING_DOOR_INSTALLED = disabled MONITOR_PS0_SIDE0 = enabled MONITOR_PS0_SIDE1 = enabled MONITOR_PS0_SIDE2 = disabled MONITOR_PS1_SIDE0 = enabled MONITOR_PS1_SIDE1 = enabled MONITOR_PS1_SIDE2 = disabled PS_FANS_HIGH = disabled Commands: cd set show->


ILOM Readings for Specific Power Supply StatesThis section shows some of the sensor readings for the SEL in cases that are specificto the Sun Blade 6048 modular system.

AC Cables Are DisconnectedWhen an AC cable gets disconnected, the SEL displays the readings as shown theexample for power supply module 0, side 0 in TABLE 3-21.

Note – The order of the events might not match the real time event exactly, becausethat is based on how the sensors are being scanned.

AC Cables Gets Disconnected, Then Plugged Back InWhen an AC cable gets disconnected, then plugged back in, the SEL displays thereadings as shown for power supply module 0, side 0 in TABLE 3-22.

TABLE 3-21 AC Cable Disconnect SEL Readings

Event ID Device State Description

8 Voltage PS0/S0/V_OUT_OK State Deasserted PSU 0 side 0 DC output isout (because AC isunplugged).

9 Voltage PS0/S0/V_IN_ERR Predictive FailureAsserted

PSU 0 side 1 AC isdisconnected.

TABLE 3-22 AC Cables Re-inserted SEL Readings


8 Voltage PS0/S0/V_OUT_OK State Deasserted PSU 0 side 0 DC output isout (because AC isunplugged).

9 Voltage PS0/S0/V_IN_ERR PredictiveFailure Asserted

PSU 0 side 0 AC isdisconnected.

a Voltage PS0/S0/V_OUT_OK State Asserted PSU 0 side 0 DC output isOK (because AC is pluggedin).

b Voltage PS0/S0/V_IN_ERR PredictiveFailure Deasserted

PSU 0 side 0 is connected.


Stop /CHWhen the stop /CH command is applied, the SEL displays the readings as shown inthe example in TABLE 3-23. This example describes a two power cord configuration.

Start /CHWhen the start /CH command is applied, the SEL displays the readings as shown inthe example in TABLE 3-24. This example describes a two power cord configuration.

TABLE 3-23 Stop /CH SEL Readings


29 Module/BoardNEM1/STATE

Transition toPower Off

Not enough power for theNEM 1, since the PSU shutsoff.

2a VoltagePS0/S0/V_OUT_OK

State Deasserted PSU 0 side 0 is out.

2b VoltagePS0/S1/V_OUT_OK


2c Module/BoardNEM0/STATE

Transition toPower Off

Not enough power for theNEM 0, since the PSU shutsoff.

2d VoltagePS1/S0/V_OUT_OK


2e VoltagePS1/S1/V_OUT_OK


TABLE 3-24 Start /CH SEL Readings


2f Module/Board NEM1/STATE Transition toRunning

NEM 1 is powering on.

30 OEM BL7/ERR Predictive FailureDeasserted

Blade module does not havean error.

31 Module/Board NEM0/STATE Transition toRunning

NEM 0 is powering on.

32 Voltage PS1/S0/V_OUT_OK State Asserted PSU 1 side 0 is on.



One PSU Is RemovedWhen one PSU is removed, and there is too much power consumption in the chassisto support PSU redundancy, the SEL displays the readings shown in TABLE 3-25.

34 OEM BL1/ERR Predictive FailureDeasserted

Blade module does not havean error.



TABLE 3-25 PSU Removed SEL Readings


1 Entity Presence PS0/PRSNT Device Absent PS0 is absent from thesystem.

2 Voltage PS0/S0/V_OUT_OK State Deasserted PSU 0 side 0 DC power isout.



TABLE 3-24 Start /CH SEL Readings (Continued)



PSU Is Re-insertedTABLE 3-26 shows the SEL readings as a PSU is reinserted into the system and thesystem recognizes that power has been re-applied.

TABLE 3-26 PSU Re-inserted SEL Readings


5 Entity Presence PS0/PRSNT Device Present PS0 is present in the system.

6 Voltage PS0/S0/V_OUT_OK State Asserted PSU 0 side 0 DC power ison.




sun integrated lights out manager (ilom) 3.0 …people.tuke.sk/dezider.guspan/sun...

Documents