Integrated Lights Out Manager (ILOM) 3.0 Feature Updates ......Les produits portant les marques SPARC sont basés sur une architecture développée par Sun Microsystems, Inc. SPARC64

Integrated Lights Out Manager(ILOM) 3.0 Feature Updates

and Release Notes

Manual Code C120-E600-01ENPart No. 875-4572-10June 2009, Revision A

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

FUJITSU LIMITED provided technical input and review on portions of this material.

Sun Microsystems, Inc. and Fujitsu Limited each own or control intellectual property rights relating to products and technology described inthis document, and such products, technology and this document are protected by copyright laws, patents and other intellectual property lawsand international treaties. The intellectual property rights of Sun Microsystems, Inc. and Fujitsu Limited in such products, technology and thisdocument include, without limitation, one or more of the United States patents listed at http://www.sun.com/patents and one or moreadditional patents or patent applications in the United States or other countries.

This document and the product and technology to which it pertains are distributed under licenses restricting their use, copying, distribution,and decompilation. No part of such product or technology, or of this document, may be reproduced in any form by any means without priorwritten authorization of Fujitsu Limited and Sun Microsystems, Inc., and their applicable licensors, if any. The furnishing of this document toyou does not give you any rights or licenses, express or implied, with respect to the product or technology to which it pertains, and thisdocument does not contain or represent any commitment of any kind on the part of Fujitsu Limited or Sun Microsystems, Inc., or any affiliate ofeither of them.

This document and the product and technology described in this document may incorporate third-party intellectual property copyrighted byand/or licensed from suppliers to Fujitsu Limited and/or Sun Microsystems, Inc., including software and font technology.

Per the terms of the GPL or LGPL, a copy of the source code governed by the GPL or LGPL, as applicable, is available upon request by the EndUser. Please contact Fujitsu Limited or Sun Microsystems, Inc.

This distribution may include materials developed by third parties.

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

Sun, Sun Microsystems, the Sun logo, Java, Netra, Solaris, Sun StorEdge, docs.sun.com, OpenBoot, SunVTS, Sun Fire, SunSolve, CoolThreads,J2EE, and Sun are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.

Fujitsu and the Fujitsu logo are registered trademarks of Fujitsu Limited.

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

SPARC64 is a trademark of SPARC International, Inc., used under license by Fujitsu Microelectronics, Inc. and Fujitsu Limited.

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.

United States Government Rights - Commercial use. U.S. Government users are subject to the standard government user license agreements ofSun Microsystems, Inc. and Fujitsu Limited and the applicable provisions of the FAR and its supplements.

Disclaimer: The only warranties granted by Fujitsu Limited, Sun Microsystems, Inc. or any affiliate of either of them in connection with thisdocument or any product or technology described herein are those expressly set forth in the license agreement pursuant to which the productor technology is provided. EXCEPT AS EXPRESSLY SET FORTH IN SUCH AGREEMENT, FUJITSU LIMITED, SUN MICROSYSTEMS, INC.AND THEIR AFFILIATES MAKE NO REPRESENTATIONS OR WARRANTIES OF ANY KIND (EXPRESS OR IMPLIED) REGARDING SUCHPRODUCT OR TECHNOLOGY OR THIS DOCUMENT, WHICH ARE ALL PROVIDED AS IS, AND ALL EXPRESS OR IMPLIEDCONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTY OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THEEXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. Unless otherwise expressly set forth in such agreement, to theextent allowed by applicable law, in no event shall Fujitsu Limited, Sun Microsystems, Inc. or any of their affiliates have any liability to anythird party under any legal theory for any loss of revenues or profits, loss of use or data, or business interruptions, or for any indirect, special,incidental or consequential damages, even if advised of the possibility of such damages.

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, California 95054, Etats-Unis. Tous droits réservés.

Entrée et revue tecnical fournies par FUJITSU LIMITED sur des parties de ce matériel.

Sun Microsystems, Inc. et Fujitsu Limited détiennent et contrôlent toutes deux des droits de propriété intellectuelle relatifs aux produits ettechnologies décrits dans ce document. De même, ces produits, technologies et ce document sont protégés par des lois sur le copyright, desbrevets, d’autres lois sur la propriété intellectuelle et des traités internationaux. Les droits de propriété intellectuelle de Sun Microsystems, Inc.et Fujitsu Limited concernant ces produits, ces technologies et ce document comprennent, sans que cette liste soit exhaustive, un ou plusieursdes brevets déposés aux États-Unis et indiqués à l’adresse http://www.sun.com/patents de même qu’un ou plusieurs brevets ou applicationsbrevetées supplémentaires aux États-Unis et dans d’autres pays.

Ce document, le produit et les technologies afférents sont exclusivement distribués avec des licences qui en restreignent l’utilisation, la copie,la distribution et la décompilation. Aucune partie de ce produit, de ces technologies ou de ce document ne peut être reproduite sous quelqueforme que ce soit, par quelque moyen que ce soit, sans l’autorisation écrite préalable de Fujitsu Limited et de Sun Microsystems, Inc., et de leurséventuels bailleurs de licence. Ce document, bien qu’il vous ait été fourni, ne vous confère aucun droit et aucune licence, expresses ou tacites,concernant le produit ou la technologie auxquels il se rapporte. Par ailleurs, il ne contient ni ne représente aucun engagement, de quelque typeque ce soit, de la part de Fujitsu Limited ou de Sun Microsystems, Inc., ou des sociétés affiliées.

Ce document, et le produit et les technologies qu’il décrit, peuvent inclure des droits de propriété intellectuelle de parties tierces protégés parcopyright et/ou cédés sous licence par des fournisseurs à Fujitsu Limited et/ou Sun Microsystems, Inc., y compris des logiciels et destechnologies relatives aux polices de caractères.

Par limites du GPL ou du LGPL, une copie du code source régi par le GPL ou LGPL, comme applicable, est sur demande vers la fin utilsateurdisponible; veuillez contacter Fujitsu Limted ou Sun Microsystems, Inc.

Cette distribution peut comprendre des composants développés par des tierces parties.

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, Netra, Solaris, Sun StorEdge, docs.sun.com, OpenBoot, SunVTS, Sun Fire, SunSolve, CoolThreads,J2EE, et Sun sont des marques de fabrique ou des marques déposées de Sun Microsystems, Inc. aux Etats-Unis et dans d’autres pays.

Fujitsu et le logo Fujitsu sont des marques déposées de Fujitsu Limited.

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.

SPARC64 est une marques déposée de SPARC International, Inc., utilisée sous le permis par Fujitsu Microelectronics, Inc. et Fujitsu Limited.

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és de Sun qui mettent en place l’interface d’utilisation graphique OPEN LOOK et qui, en outre, se conformentaux licences écrites de Sun.

Droits du gouvernement américain - logiciel commercial. Les utilisateurs du gouvernement américain sont soumis aux contrats de licencestandard de Sun Microsystems, Inc. et de Fujitsu Limited ainsi qu’aux clauses applicables stipulées dans le FAR et ses suppléments.

Avis de non-responsabilité: les seules garanties octroyées par Fujitsu Limited, Sun Microsystems, Inc. ou toute société affiliée de l’une ou l’autreentité en rapport avec ce document ou tout produit ou toute technologie décrit(e) dans les présentes correspondent aux garanties expressémentstipulées dans le contrat de licence régissant le produit ou la technologie fourni(e). SAUF MENTION CONTRAIRE EXPRESSÉMENTSTIPULÉE DANS CE CONTRAT, FUJITSU LIMITED, SUN MICROSYSTEMS, INC. ET LES SOCIÉTÉS AFFILIÉES REJETTENT TOUTEREPRÉSENTATION OU TOUTE GARANTIE, QUELLE QU’EN SOIT LA NATURE (EXPRESSE OU IMPLICITE) CONCERNANT CEPRODUIT, CETTE TECHNOLOGIE OU CE DOCUMENT, LESQUELS SONT FOURNIS EN L’ÉTAT. EN OUTRE, TOUTES LES CONDITIONS,REPRÉSENTATIONS ET GARANTIES EXPRESSES OU TACITES, Y COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE ÀLA QUALITÉ MARCHANDE, À L’APTITUDE À UNE UTILISATION PARTICULIÈRE OU À L’ABSENCE DE CONTREFAÇON, SONTEXCLUES, DANS LA MESURE AUTORISÉE PAR LA LOI APPLICABLE. Sauf mention contraire expressément stipulée dans ce contrat, dansla mesure autorisée par la loi applicable, en aucun cas Fujitsu Limited, Sun Microsystems, Inc. ou l’une de leurs filiales ne sauraient être tenuesresponsables envers une quelconque partie tierce, sous quelque théorie juridique que ce soit, de tout manque à gagner ou de perte de profit,de problèmes d’utilisation ou de perte de données, ou d’interruptions d’activités, ou de tout dommage indirect, spécial, secondaire ouconsécutif, même si ces entités ont été préalablement informées d’une telle éventualité.

LA DOCUMENTATION EST FOURNIE “EN L’ETAT” 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 CONTREFACON.

Contents

Preface xi

1. ILOM 3.0 Feature Set 1

ILOM 3.0 System Requirements and Firmware Compatibility 1

ILOM 3.0 Feature Set Overview 1

ILOM 3.0 Firmware on the SP 2

Server Specific ILOM Features 2

ILOM 3.0 Firmware on the CMM 2

CMM Chassis-Level Management 3

CMM and Server SP CLI Connection 4

CMM and Server SP Address Space on CLI 4

CMM and Server SP Web Interface Connection 5

CMM ILOM Web Interface 5

Server SP ILOM Web Interface 6

ILOM 3.0 Version Numbers 6

Related ILOM 3.0 Documentation 7

2. Updates to the ILOM 3.0.3 Firmware 9

New Features for ILOM 3.0.3 10

Improved Chassis View 11

v

Power Management Metrics 12

Power Consumption History 13

▼ View Power Consumption History Using the CLI 13

▼ View Power Consumption History Using the Web Interface 16

Enhanced Ability to Override BIOS Host Boot Device 19

▼ Configure BIOS Host Boot Device Override Using the CLI 19

▼ Configure BIOS Host Boot Device Override Using the Web Interface20

Clear Faults After Replacement of Faulted Component 22

▼ View and Clear Faults Using the CLI 23

▼ View and Clear Faults Using the Web Interface 24

Jump Links Available on ILOM Web Pages 25

User Management --> Active Directory 25

User Management -->LDAP/SSL 26

Configuration --> System Management Access-->SNMP 26

User Management --> User Accounts 27

Resolved Issues as of ILOM 3.0.3 27

Alt-Graph Key Functionality on International Keyboards 28

Web Interface Does Not Display the Browse Button When Uploading Files28

Newly Generated SSH Keys Are Now Available Immediately WithoutRequiring SSH Server Restart 29

Loading SSH Host Key No Longer Results in Error Message 29

Email Address Using IP Address Is Accepted in Alert Management RuleQuery 30

Known Issues as of ILOM 3.0.3 31

BIOS Upgrade Is Delayed After SP Reboot 31

External Serial Port Settings Do Not Reset to Default Value 32

Hourly Power Average Timestamp Does Not Account for Increments of LessThan One Hour 33

vi Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • June 2009

SSH Keys Fail to Restore After a Backup/Restore 33

Documentation Updates and Errata 34

Targets, Properties, and Values for set Command 35

Some SPARC Systems Support a Maximum of Five Active Sessions 37

Power Policy Not Available for SPARC Systems Using Earlier Version ofILOM 37

▼ Configure Power Policy Using the Web Interface 37

Updating to a Previous ILOM Version Might Not Complete 39

SSH Uses Newly Generated Key Without Restarting the SSH Server 39

ILOM HTTPS SSL Properties Are Not Visible in the ILOM Inventory 40

SNMP Commands to Monitor Power Are Incorrect 40

Rackmount Servers Support Serial Connection to ILOM 41

TFTP Is Not a Supported Transfer Method for the Snapshot Utility 41

CMM Web Interface Provides Download Links to Storage Redirection Serviceand Client CLI Tools 41

Exception to the Rule That available_power Is Greater Thanhwconfig_power 42

3. Updates to the ILOM 3.0.4 Firmware 43

New Features for ILOM 3.0.4 44

Power Management New Web Layout for the SP 45

Power Management New Web Layout for the CMM 46

Power Consumption Thresholds 47

▼ View and Configure Power Thresholds Using the CLI 47

▼ View and Configure Power Thresholds Using the Web Interface 47

Set Timeout Value for a cli Session 48

▼ Set Timeout Value Using the CLI 48

Edit LDAP/SSL Optional User Mapping 49

▼ Edit Optional User Mapping in LDAP/SSL Using the CLI 49

▼ Edit LDAP/SSL Optional User Mapping Using the Web Interface 50

Contents vii

Download SNMP MIBs Directly From ILOM 52

▼ Download SNMP MIBs From ILOM Using the CLI 53

▼ Download SNMP MIBs From ILOM Using the Web Interface 53

View User Roles in Active Session 54

▼ View Roles for Active User Session Using the CLI 54

▼ View Roles for Active User Session Using the Web Interface 55

▼ View and Configure Expanded Search Mode in Active Directory 56

▼ View and Configure Expanded Search Mode in Active DirectoryUsing the CLI 56

▼ View and Configure Expanded Search Mode in Active DirectoryUsing the Web Interface 57

Send Test Email Alert to Specific Alert Destination 59

▼ Send Test Email Alert to Specific Destination Using the CLI 59

▼ Send Test Email Alert to Specific Alert Destination Using the WebInterface 59

ILOM Remote Console Computer Lock 60

Special Considerations When Enabling the ILOM Remote Console LockOption 60

▼ Edit the ILOM Remote Console Lock Option Using the ILOM CLI 61

▼ Edit the ILOM Remote Console Lock Option Using the Web Interface 64

New ILOM SP Network Ports 65

Enhanced Mouse Mode Settings for Remote Host KVMS 65

▼ Edit Mouse Mode Setting for Remote Host Using the CLI 65

▼ Edit Mouse Mode Setting for Remote Host Using the Web Interface 66

Resolved Issues as of ILOM 3.0.4 66

LDAP or RADIUS Commands Do Not Work When Default Role Is Set tonone 67

Difficulty Removing dnslocatorquery Records From Active DirectoryConfiguration 67

When Using the CLI to Set the Time Zone, Certain Time Zones Do NotRecalculate the Clock Correctly 67

viii Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • June 2009

Snapshot Utility Missing Log Files for Debugging 68

ILOM CLI for set /{target}/config dump_uri Does Not ProvideConfirmation Message 69

Role Help Text for Read-Only /SYS Properties Is Incorrrect 69

Help Text for Power Management Properties Is Incorrect 69

Help Output Results for <TARGET> <property> <property> Is Confusing70

Inaccurate Help Text Values for /SP/users/root/ssh/key/1-5 72

ILOM External Serial Port Flow Control Implemented Incorrectly 72

Known Issues as of ILOM 3.0.4 73

ILOM Remote Console Might Hang on Windows Client When Redirecting aCD-ROM Image or Floppy Image 73

Documentation Updates and Errata 74

Allowable Number for DNS Retries Is Incorrect 74

New Web Power Management Layout 74

Power Consumption Thresholds 75

Contents ix

x Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • June 2009

Preface

The Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notesdescribes enhancements that have been made to ILOM firmware since the ILOM 3.0release.

ILOM updated versions are typically released every two to three months. NewILOM 3.x.x features that are common to all servers supporting ILOM are describedin this guide. Specifically, each chapter in the guide documents the new ILOMfeatures and issues for each new ILOM 3.0.x release.

This document is written for system administrators who are familiar withnetworking concepts and basic system management protocols.

Note – The description in this document is limited to the servers which supportILOM. In the description, "all server platforms" refers to all Fujitsu servers whichsupport ILOM. Depending on the server in use, some of the ILOM functions are notsupported. Please confirm the ILOM Supplement manual and the Product Notes ofeach server in advance.

Related DocumentationTo fully understand the information that is presented in this guide, use thisdocument in conjunction with the documents listed in the following table. The latestversions of all the SPARC Enterprise Series manuals are available at the followingWeb sites:

Global Site

xi

http://www.fujitsu.com/sparcenterprise/manual/

Japanese Site

http://primeserver.fujitsu.com/sparcenterprise/manual/

First read the ILOM 3.0 Concepts Guide to learn about ILOM’s features andfunctionality. To set up a new system supported by ILOM, refer to the ILOM 3.0Getting Started Guide, where you will find the procedures for connecting to thenetwork, logging in to ILOM for the first time, and configuring a user account ordirectory service. Then, decide which ILOM interface you want to use to performother ILOM tasks. You can now refer to the appropriate ILOM 3.0 Procedures Guidefor your selected interface.

The following table lists the ILOM 3.0 Documentation Collection.

In addition to the ILOM 3.0 Documentation Collection, associated ILOMSupplement documents present ILOM features and tasks that are specific to theserver platform you are using. Use the ILOM 3.0 Documentation Collection inconjunction with the ILOM Supplement that comes with your server platform.

TABLE P-1 ILOM 3.0 Documentation Collection

Title Content Manual Code

Integrated Lights Out Manager(ILOM) 3.0 Concepts Guide

Information that describes ILOM featuresand functionality

C120-E573

Integrated Lights Out Manager(ILOM) 3.0 Getting Started Guide

Information and procedures for networkconnection, logging in to ILOM for the firsttime, and configuring a user account or adirectory service

C120-E576

Integrated Lights Out Manager(ILOM) 3.0 Web InterfaceProcedures Guide

Information and procedures for accessingILOM functions using the ILOM webinterface

C120-E574

Integrated Lights Out Manager(ILOM) 3.0 CLI Procedures Guide

Information and procedures for accessingILOM functions using the ILOM CLI

C120-E575

Integrated Lights Out Manager(ILOM) 3.0 SNMP and IPMIProcedures Guide

Information and procedures for accessingILOM functions using SNMP or IPMImanagement hosts

C120-E579

xii Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • June 2009

http://primeserver.fujitsu.com/sparcenterprise/manual/


Text Conventions

If you have any comments or requests regarding this document, or if you find anyunclear statements in the document, please state your points specifically on the format the following URL.

For Users in U.S.A., Canada, and Mexicohttps://download.computers.us.fujitsu.com/

For Users in Other Countrieshttp://www.fujitsu.com/global/contact/computing/sparce_index.html

Typeface*

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

Meaning Examples

AaBbCc123 The names of commands, files,and directories; on-screencomputer output

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

AaBbCc123 What you type, when contrastedwith on-screen 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 Concept’s Guide.These are called class options.You must be superuser to do this.To delete a file, type rm filename.

Preface xiii

http://www.fujitsu.com/global/contact/computing/sparce_index.html

http://www.fujitsu.com/global/contact/computing/sparce_index.html

https://download.computers.us.fujitsu.com/

xiv Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • June 2009

CHAPTER 1

ILOM 3.0 Feature Set

This chapter includes the following information about the ILOM 3.0 feature set:

■ “ILOM 3.0 System Requirements and Firmware Compatibility” on page 1

■ “ILOM 3.0 Feature Set Overview” on page 1

■ “ILOM 3.0 Firmware on the SP” on page 2

■ “ILOM 3.0 Firmware on the CMM” on page 2

■ “CMM and Server SP CLI Connection” on page 4

■ “CMM and Server SP Web Interface Connection” on page 5

■ “ILOM 3.0 Version Numbers” on page 6

■ “Related ILOM 3.0 Documentation” on page 7

ILOM 3.0 System Requirements andFirmware CompatibilityTo help you determine system requirements and ILOM firmware compatibility, seethe Product Notes for your server.

ILOM 3.0 Feature Set OverviewThe ILOM 3.0 feature set provides common ILOM functionality that applies to allserver platforms supporting ILOM. These features are built into the ILOM 3.0firmware that is installed on the server service processor (SP) and, if applicable, onthe chassis monitoring module (CMM).

1

Note – CMMs are applicable to blade modular systems. CMMs are not applicable torackmount servers.

ILOM 3.0 Firmware on the SPThe ILOM 3.0 firmware on the SP provides administrators with full lights-outmanagement for a server. This includes the ability to power cycle the server, set up anetwork connection, create and manage user accounts and roles, as well as monitorand maintain the server components locally or remotely.

Server Specific ILOM FeaturesThe ILOM 3.0 SP firmware operates on many server platforms, supporting featuresthat are common to all platforms, as well as other features that are specific to aserver. For additional information about the ILOM 3.0 features that are supportedspecifically for your server, see the ILOM 3.0 Supplement guide that is provided foryour server.

ILOM 3.0 Firmware on the CMMThe ILOM 3.0 firmware on the CMM is configured with an individual IP addressassigned either statically or dynamically using DHCP. The CMM acts as a conduit tothe server module ILOM configuration, enabling settings such as network addressesand administrative user accounts to be configured or viewed.

ILOM on the CMM is the primary point of management for all chassis componentsand functions in a blade modular system chassis. It provides complete monitoringand management functionality for the components, including server modulemanagement, system power management, as well as hot-plug operations ofinfrastructure components such as power supply modules, fan modules, servermodules, and network express modules.

In addition, the CMM supports HTTP and CLI "pass-thru" interfaces that provideaccess to all chassis features through a direct serial port connection or a10/100/1000-BASE-T network management port connection on the CMM.

2 Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • June 2009

CMM Chassis-Level ManagementILOM on the CMM offers a tiered management architecture that enables systemmanagement of individual components or aggregated management of componentsat the chassis level.

A summary of the CMM’s management functions include:

■ Implementation of an IPMI satellite controller, making the chassis environmentalsensors visible to the server module’s BMC functions

■ Direct environmental and inventory management via CLI, web, SNMP, and IPMIinterfaces

■ Firmware management of CMM, network express module (NEM), and servermodule SPs

■ Pass-through management of server modules and HTTP links along withcommand-line interface (CLI) SSH contexts

■ Chassis power control

■ Access to the following components:

■ Chassis

■ Power supplies

■ Fans

■ Network express modules (NEMs)

■ Server module SPs

Chapter 1 ILOM 3.0 Feature Set 3

CMM and Server SP CLI ConnectionYou can use a command-line interface to access ILOM on the CMM or server SPthrough a network connection, or through a direct terminal connection to the serialport on the CMM or server SP.

When the ILOM firmware on the CMM or server SP boots, the login prompt for theCMM or server SP appears, for example:

■ SUNCMMnnnnnnnnnn login:

The first string in the CMM login prompt is the default host name. It consists ofthe prefix SUNCMM and the CMM product serial number.

■ SUNSPnnnnnnnnnnn login:

The first string in the server SP login prompt is the default host name. It consistsof the prefix SUNSP and server product serial number.

CMM and Server SP Address Space on CLIThe following table identifies the CLI address space you can use to interact withILOM.

ILOMManagementComponent Management Address Space

CMM • /CMM is used to manage ILOM on the CMM.• /CH is used to provide inventory, environmental, and hardware

management at the chassis level. The /CH address space replaces /SYSon blade modular systems.

Server SP • /SP is used to configure the server module SP and for viewing logsand consoles.

• /SYS is used to provide inventory, environmental, and hardwaremanagement at the server module level.

Host • /HOST is used to monitor and manage the host operating system.


CMM and Server SP Web Interface ConnectionYou also can access ILOM on the CMM and server SP using a web interfaceconnection. To establish a web interface connection to ILOM, specify the IP addressof the CMM or server SP in the web browser. A welcome page appears promptingyou to enter a user name and password.

CMM ILOM Web InterfaceThe main ILOM web page for the CMM includes a navigation pane that you use tomonitor and manage individual components installed in the chassis. The settingsyou can view or configure are organized in the seven tabs appearing at the top of thepage, as shown in the following example.


Server SP ILOM Web InterfaceThe main ILOM web page for the server SP organizes the settings you can view orconfigure for that server within the six tabs appearing at the top of the page, asshown in the following example:

ILOM 3.0 Version NumbersILOM 3.0 has implemented a new version numbering scheme to help you identifywhich version of ILOM you are running on your system. The numbering schemeincludes a five-field string, for example, a.b.c.d.e, where:

■ a - Represents the major version of ILOM.

■ b - Represents a minor version of ILOM.

■ c - Represents the update version of ILOM.

■ d - Represents a micro version of ILOM. Micro versions are managed perplatform or group of platforms. See your platform Product Notes for details.

■ e - Represents a nano version of ILOM. Nano versions are incrementaliterations of a micro version.

For example, ILOM 3.1.2.1.a would designate:

■ ILOM 3 as the major version of ILOM

■ ILOM 3.1 as a minor version of ILOM 3

■ ILOM 3.1.2 as the second update version of ILOM 3.1

■ ILOM 3.1.2.1 as a micro version of ILOM 3.1.2


■ ILOM 3.1.2.1.a as a nano version of ILOM 3.1.2.1

Related ILOM 3.0 DocumentationThis guide describes new features and issues that are part of a new ILOM 3.x.xrelease. Each chapter in this guide documents new ILOM features and issuesassociated with each new ILOM firmware update.

To fully understand the information that is presented in this guide, use thisdocument in conjunction with the documents listed in “Related Documentation” onpage xi.

First read the ILOM 3.0 Concepts Guide to learn about ILOM’s features andfunctionality. To set up a new system supported by ILOM, refer to the ILOM 3.0Getting Started Guide, where you will find the procedures for connecting to thenetwork, logging in to ILOM for the first time, and configuring a user account ordirectory service. Then, decide which ILOM interface you want to use to performother ILOM tasks. You can now refer to the appropriate ILOM 3.0 Procedures Guidefor your selected interface.

For platform-specific ILOM updates, refer to your ILOM Supplement, whichpresents ILOM features and tasks that are specific to the server platform you areusing. The ILOM Supplement is part of the documentation set for your server.



CHAPTER 2

Updates to the ILOM 3.0.3 Firmware

This chapter describes the new features and functionality that have been added tothe ILOM 3.0.3 firmware release. Procedures to implement the new functionality areexplained. Known issues, resolved issues, and documentation updates are alsodescribed.

Topics in the chapter include:

■ “New Features for ILOM 3.0.3” on page 10

■ “Resolved Issues as of ILOM 3.0.3” on page 27

■ “Known Issues as of ILOM 3.0.3” on page 31

■ “Documentation Updates and Errata” on page 34

9

New Features for ILOM 3.0.3There are several new features integrated into the ILOM 3.0.3 firmware release. Thefollowing table identifies these features and points you to the sections that describethe features.

Topics

Description Links

Updated CMM chassis managementview

• “Improved Chassis View” on page 11

Enhanced CMM power managementmetrics

• “Power Management Metrics” on page 12

Enhanced feature for displaying thehistory of platform-specific powerconsumption

• “Power Consumption History” on page 13• “View Power Consumption History Using the

CLI” on page 13• “View Power Consumption History Using the

Web Interface” on page 16

Enhanced feature to override the bootdevice settings in BIOS using theILOM CLI or web interface

• “Enhanced Ability to Override BIOS Host BootDevice” on page 19

• “Configure BIOS Host Boot Device OverrideUsing the CLI” on page 19

• “Configure BIOS Host Boot Device OverrideUsing the Web Interface” on page 20

Updated information for clearingfaults from the event log after fixinga faulted component

• “Clear Faults After Replacement of FaultedComponent” on page 22

• “View and Clear Faults Using the CLI” onpage 23

• “View and Clear Faults Using the Web Interface”on page 24

Enhanced web pages with jump links • “Jump Links Available on ILOM Web Pages” onpage 25


Improved Chassis ViewIn the ILOM web interface, the chassis view has been modified to include thefollowing enhancements:

■ The navigation pane on the left side of the screen now shows visible entries onlyfor components that are present and manageable.

■ A Chassis Inventory Table now appears in the main body page of the chassisview. The table provides information about name, part number, and serialnumber of all manageable components that are present in the chassis.

Chapter 2 Updates to the ILOM 3.0.3 Firmware 11

Power Management MetricsThe power management feature enables you to monitor power consumption metricsfrom the command-line interface (CLI) or web interface. The following powermanagement metrics are common to all servers supporting ILOM:

■ Actual Power – Represents consumed power for the rackmount server or chassissystem. On a chassis monitoring module (CMM), this is the input powerconsumed by the entire chassis or shelf (all blades, NEMS, fans, and so forth).This value is also made available via the /SYS/VPS sensor.

■ Available Power – For rackmount systems, this value represents the maximuminput power that the power supplies are capable of consuming. For chassissystems, this value represents the available amount of power guaranteed to theserver module (blade) by the chassis.

■ Permitted Power – For rackmount systems, this value represents the maximuminput power that the server guarantees it will consume at any instant. For chassissystems, this value represents the maximum power a server module guarantees itwill consume at any instant.

Special Considerations

Prior to viewing the power management metrics available for your system in ILOM,consider the following information:

■ Some servers supporting ILOM might not provide the values for available power,permitted power, and actual power consumed by the SP, which is typically lessthan 10 watts.

■ Some servers supporting ILOM might provide additional platform-specific powermetrics under the /SP/powermgmt/advanced node in the CLI or the AdvancedPower Metrics table in the System Monitoring --> Power Management page in theweb interface. Each advanced power metric includes a name, a unit, and a value.

For platform-specific power management information, see the ILOM Supplementguide that is available for your server.

For general information about viewing the power management metrics in the CLIand web interface, see the ILOM 3.0 Documentation Collection.


Power Consumption HistoryILOM now displays rolling averages of power consumption in 15-, 30-, and 60-second intervals by leveraging ILOM’s sensor history capability. Power consumptioninformation is retrieved at a rate determined by the individual platform, whichcould range from 1 to 8 seconds, and usually averages around 3 to 5 seconds.

Note – Power consumption history is provided using the ILOM CLI and webinterfaces. This information is not available through IPMI or SNMP.

Before You Begin■ Read Only (o) role is required to view the power consumption history values.

▼ View Power Consumption History Using the CLI1. Log in to ILOM.

2. To display actual power consumption, type the following command:

■ From the server SP:->show /SYS/VPS

■ From the CMM:->show /CH/VPS

For example:


3. To display 15-, 30-, and 60-second rolling power usage average, and to display achoice of targets for average consumption history, type the following command:

■ From the server SP:->show /SYS/VPS/history

■ From the CMM:->show /CH/VPS/history

For example:

->show /CH/VPS

/CH/VPS Targets: history

Properties: type = Power Unit ipmi_name = VPS class = Threshold Sensor value = 1400.000 Watts upper_nonrecov_threshold = N/A upper_critical_threshold = N/A upper_noncritical_threshold = N/A lower_noncritical_threshold = N/A lower_critical_threshold = N/A lower_nonrecov_threshold = N/A alarm_status = cleared

Commands: cd show

->show /CH/VPS/history

/CH/VPS/history Targets: 0 (1 Minute Average, 1 Hour History) 1 (1 Hour Average, 14 Day History)

Properties: 15sec_average = 1210.000 30sec_average = 1400.000 60sec_average = 1800.000

Commands: cd show


4. To display average consumption history by the minute or hour respectively,type the following command with the appropriate target named. In thefollowing example, average per minute is selected.

■ From the server SP:->show /SYS/VPS/history/0

■ From the CMM:->show /CH/VPS/history/0

For example:

5. To display sample set details such as time stamp and power consumed in watts,type:

■ From the server SP:->show /SYS/VPS/history/0/list

->show /CH/VPS/history/0

/CH/VPS/history/ Targets: list

Properties: average = 1500.000 minimum = 1500.000 at Mar 4 08:51:24 maximum = 1500.000 at Mar 4 08:51:23 period = 1 Minute Average depth = 1 Hour History

Commands: cd show


■ From the CMM:->show /CH/VPS/history/0/list

For example:

▼ View Power Consumption History Using the WebInterface1. Log in to ILOM.

2. In the web interface page, click System Monitoring --> Power Management.

The Power Management page appears.

3. In the Power Management page, click the link for Power History.

Two tables appear that show Power Usage Average and Power History.

For example:

■ CMM Power History Example

->show /CH/VPS/history/0/list

/CH/VPS/history/0/list Targets:

Properties: Mar 4 08:52:23 = 1500.000 Mar 4 08:51:24 = 1500.000 Mar 4 08:50:24 = 1500.000 Mar 4 08:49:24 = 1500.000 Mar 4 08:48:24 = 1500.000 Mar 4 08:47:23 = 1500.000

Commands: cd show



■ SP Power History Example

4. To view detailed power history (such as time stamp and power consumed inwatts), select any live entry in the Sample Set column.

The following figure shows the sample set results of the target /CH/VPS/0.


Enhanced Ability to Override BIOS Host BootDeviceYou can now use the CLI and web interface to select a host boot device, overridingthe boot device order settings in BIOS. This ability gives the CLI and web interfaceparity with the existing IPMI interface. Now that this feature is available in the CLIand web interface, a user who has logged in to the SP can quickly and easily changethis value without having to use IPMItool externally.

The primary purpose of the boot device override feature is to allow theadministrator to perform a one-time manual override of the server’s BIOS boot ordersettings. This enables the administrator to quickly configure a machine or group ofmachines to boot from another device, such as the PXE boot environment.

Before You Begin■ The Reset and Host Control (r) role is required to change the host boot device

configuration variable.

▼ Configure BIOS Host Boot Device Override Using theCLI1. Log in to ILOM.

2. Use the cd and show commands to navigate to the host system.

For example:

->cd /HOST/HOST

->show

/HOST Targets: diag

Properties: boot_device = default generate_host_nmi = (Cannot show property)

Commands: cd set show


3. To set the host boot device for the next time the system is powered on, type:

->set boot_device=value

Possible values are:

■ default – Setting the value to default means that there is no override to theBIOS settings. Setting to default will also clear any previously chosenselection.

■ pxe – Setting the value to pxe means that at the next host boot, the BIOS bootorder settings will be temporarily bypassed and instead the host will boot fromthe network, following the PXE boot specification.

■ disk – Setting the value to disk means that at the next host boot, the BIOSboot order settings will be temporarily bypassed and instead the host will bootfrom the first disk as determined by BIOS. The specific disk chosen depends onconfiguration. Typically, hosts use this option by default and the host'sbehavior might not change by selecting this option.

■ diagnostic – Setting the value to diagnostic means that at the next hostboot, the BIOS boot order settings will be temporarily bypassed and insteadthe host will boot into the diagnostic partition, if configured.

■ cdrom – Setting the value to cdrom means that at the next host boot, the BIOSboot order settings will be temporarily bypassed and instead the host will bootfrom the attached CD-ROM or DVD device.

■ bios – Setting the value to bios means that at the next host boot, the BIOSboot order settings will be temporarily bypassed and instead the host will bootinto the BIOS Setup screen.

▼ Configure BIOS Host Boot Device Override Using theWeb Interface1. Log in to ILOM.

2. In the web interface page, click Remote Control --> Host Control.

The Host Control page appears.


3. In the Host Control page, click the Next Boot Device list box and specify a bootdevice option.

Possible boot device options available:

■ default – Setting the value to default means that there is no override to theBIOS settings. Setting to default will also clear any previously chosenselection.

■ pxe – Setting the value to pxe means that at the next host boot, the BIOS bootorder settings will be temporarily bypassed and instead the host will boot fromthe network, following the PXE boot specification.

■ disk – Setting the value to disk means that at the next host boot, the BIOSboot order settings will be temporarily bypassed and instead the host will bootfrom the first disk as determined by BIOS. The specific disk chosen depends onconfiguration. Typically, hosts use this option by default and the host'sbehavior might not change by selecting this option.

■ diagnostic – Setting the value to diagnostic means that at the next hostboot, the BIOS boot order settings will be temporarily bypassed and insteadthe host will boot into the diagnostic partition, if configured.

■ cdrom – Setting the value to cdrom means that at the next host boot, the BIOSboot order settings will be temporarily bypassed and instead the host will bootfrom the attached CD-ROM or DVD device.

■ bios – Setting the value to bios means that at the next host boot, the BIOSboot order settings will be temporarily bypassed and instead the host will bootinto the BIOS Setup screen.

4. Click Save for your changes to take effect.


Clear Faults After Replacement of FaultedComponentThe ILOM-based service processor (SP) receives error telemetry about error eventsthat occur within the major system components on the host (CPU, memory, and I/Ohub) and the environmental subsytems within the chassis (such as fans, powersupplies, and temperature). The components and conditions are then diagnosed asfault events and captured in the ILOM event log.

The steps that are necessary to clear a fault are largely dependent on the type ofserver platform you are using (server module versus rackmount server). Forexample:

■ ILOM-based faults that occur on a server module are NOT persistent once theserver module has been properly prepared for removal and is physically removedfrom the chassis. Therefore, no service actions are required to clear the fault afterthe component is physically replaced. The fault message is captured in the ILOMevent log for historical purposes.

■ ILOM-based faults that occur on a rackmount server ARE persistent and mightrequire service actions to clear the fault after the component is physicallyreplaced, unless the component is a hot-swappable component (such as a fan orpower supply). Hot-swappable components are platform-specific; therefore, referto the platform documentation for a list of the hot-swappable components. Thefault message is captured in the ILOM event log for historical purposes. On arackmount server, you must manually clear the following faults after physicallyreplacing the components, which are not hot-swappable:

■ CPU fault

■ DIMM (memory module) fault

■ PCI card fault

■ Motherboard fault (if the motherboard is not being replaced)

■ ILOM-based faults that occur on components installed in a chassis containingCMM(s) are automatically cleared by the ILOM CMM when the faultedcomponent is replaced. However, if the chassis-level component is not hot-serviceable, then the fault needs to be manually cleared from the ILOM CMM.

In particular, the CMM automatically clears faults on the following chassis-levelcomponents after the faulted components are replaced.

■ CMM fault

■ Fan fault

■ Power supply fault

■ Network express module (NEM) fault

■ PCI express module fault


Note – For more information about the ILOM fault management features offered onyour system, refer to the ILOM 3.0 Documentation Collection and thedocumentation provided with the server platform.

Before You Begin■ The Read Only (o) role is required to view fault information.

■ The Admin (a) role is required to clear faults on system components.

▼ View and Clear Faults Using the CLI1. Log in to ILOM.

2. To view a list of components that have been faulted, type:

■ From a server:->show /SP/faultmgmt

■ From the CMM:->show /CMM/faultmgmt

3. To display fault messages in the ILOM event log, type:

■ From the server:->show /SP/logs/event/list

■ From the CMM:->show /CMM/logs/event/list

4. Fix or replace the faulted component.

5. To clear a fault on a component, type the following command:

Where component_path is one of the following faulted components:

■ Processor

■ Memory

■ Motherboard

■ Fan Module

■ Power Supply

■ CMM fault

->set component_path clear_fault_action=trueAre you sure you want to clear component_path (y/n)? ySet ’clear_fault_action’ to ’true’


■ NEM fault

■ PCI card fault

For example, to clear a processor fault, you would type the following:

▼ View and Clear Faults Using the Web Interface1. Log in to ILOM.

2. To view the status of faulted components detected by ILOM, do the following:

a. In the web interface page, click System Information --> Fault Management.

The Fault Management page appears, listing faulted components by ID, FRU,and TimeStamp.

b. To view additional information about the faulted component, click thefaulted component ID.

Additional information about the faulted component appears in a dialog.

Note – Alternatively, you can view the fault status for a component on theComponent Management page. In the Component Management page, select thecomponent name to view the fault status information.

3. Fix or replace the faulted component in the system.

After fixing or replacing the faulted component, you should clear the fault statusin ILOM.

4. To clear the status of faulted components shown in ILOM, do the following:

a. In the web interface page, click the System Information --> FaultManagement tab.

b. In the Fault Management page, enable the radio button next to the faultedcomponent, then select Clear Fault.

->set /SYS/MB/P0 clear_fault_action=trueAre you sure you want to clear /SYS/MB/P0 (y/n)? ySet ’clear_fault_action’ to ’true’


Jump Links Available on ILOM Web PagesSome ILOM 3.0.3 web interface pages that provide multiple sections now include“jump links” at the top of the web page to improve navigation. Note theinformation, settings, and controls on these pages are unchanged.

The following figures show ILOM web interface pages in which jump links are nowprovided for easier navigation within pages.

User Management --> Active Directory

Topics

Description Links

View changes to Active Directorypage

• “User Management --> Active Directory” onpage 25

View changes to the LDAP/SSL page • “User Management -->LDAP/SSL” on page 26

View changes to the SNMP page • “Configuration --> System Management Access -->SNMP” on page 26

View changes to the User Accountspage

• “User Management --> User Accounts” onpage 27


User Management -->LDAP/SSL

Configuration --> System Management Access-->SNMP


User Management --> User Accounts

Resolved Issues as of ILOM 3.0.3This section describes the issues that have been resolved as of ILOM 3.0.3. Specificchange request (CR) identification numbers and workarounds for the issues areprovided, where available.

Topics

Description Links

ILOM Remote Console resolved issue • “Alt-Graph Key Functionality on InternationalKeyboards” on page 28

User management resolved issue • “Web Interface Does Not Display the BrowseButton When Uploading Files” on page 28

SSH host keys resolved issues • “Newly Generated SSH Keys Are Now AvailableImmediately Without Requiring SSH ServerRestart” on page 29

• “Loading SSH Host Key No Longer Results inError Message” on page 29

Alert management known issue • “Email Address Using IP Address Is Accepted inAlert Management Rule Query” on page 30


Alt-Graph Key Functionality on InternationalKeyboardsWhen running certain versions of the ILOM Remote Console on a client, the Alt-Graph key works incorrectly on international keyboards.

This problem was addressed in two phases:

1. Workaround: A Workaround is provided that adds a short-cut key combination(ALT-z) for toggling on or off the "Right Alt" Keyboard menu item in ILOMRemote Console. This Workaround does not depend on a specific version of theJava Development Kit (JDK). However, this Workaround is limited in that it is notpossible to send the ALT-GR key directly. To use the Workaround, you must berunning a version of ILOM Remote Console that contains the supported short-cutkey (ALT-z).

2. Complete Solution: This solution sends the ALT-GR key directly without anyspecial Remote Console menu options or intervention. However, it requires usinga more recent version of the JDK. To use the Complete Solution, you must berunning a version of ILOM Remote Console that sends the ALT-GR key directly.The following JDK requirements also apply to the Complete Solution:

■ For Windows, use JDK 1.5 or higher.

■ For Solaris and Linux, use JDK 1.6 update 10 or higher.

You can use the ILOM version command to determine which version of ILOM isrunning on a platform.

Note – Linux and Solaris versions of ILOM 3.x contain both the Workaround andComplete Solution. Windows versions of ILOM 3.x contain the functionality asdescribed for the Complete Solution, but not the Workaround.

Web Interface Does Not Display the BrowseButton When Uploading FilesCR 6787083

Issue: In earlier versions of ILOM, a configuration page did not display the Browseoption to upload an SSL certificate in the following situations:

■ When uploading a different SSL certificate and key for HTTPS access

■ When configuring an optional certificate for LDAP/SSL

■ When configuring an optional certificate for Active Directory


■ When configuring user SSH keys

■ When configuring backup and restore operations

Clicking the Upload button to obtain an SSL certificate prompted a new window toappear; however, you were unable to select and upload a file.

Update: This issue is fixed in the ILOM 3.0.3 release. The Browse option to uploadan SSL certificate is now available.

Newly Generated SSH Keys Are Now AvailableImmediately Without Requiring SSH ServerRestartCR 6781487

Issue: When you are generating a new SSH key, you do not need to restart the SSHserver for the new key to take effect. The new SSH key will become immediatelyavailable for new connections.

Update: SSH keys are now available for new connections immediately without aserver restart as a ILOM 3.0.3.

Loading SSH Host Key No Longer Results inError MessageCR 6776200

Issue: In earlier versions of ILOM, using the load command to upload an SSH hostkey might result in a set: Command Failed error message, even when the SSHhost key was uploaded successfully. This error message no longer appears in ILOM3.0.3 and later versions.

Update: This issue is fixed in the ILOM 3.0.3 release.


Email Address Using IP Address Is Accepted inAlert Management Rule QueryCR 6776214

Issue: When using ILOM’s alert management feature, previous versions of ILOMrequired you to use a host name-based email address. You can now send an emailalert using an IP address.

Update: A separate check for IP-based email addresses has been added to the ILOM3.0.3 release so that if the original validation fails, the system will then checkspecifically for an email with an IP address.


Known Issues as of ILOM 3.0.3This section describes the known issues as of ILOM 3.0.3. The following tableidentifies these known issues and points you to the sections that describe the issues.

BIOS Upgrade Is Delayed After SP RebootCR 6813514

Issue: When you upgrade the SP firmware, you can choose to upgrade the BIOSfirmware immediately or to delay the BIOS upgrade until a later time. If you chooseto immediately upgrade the BIOS, the SP firmware is upgraded, the host is forced topower off, and the SP reboots. If you choose to delay the BIOS upgrade, the SPfirmware is upgraded and the SP reboots.

Regardless of your choice, the BIOS is not programmed immediately. Instead, the SPreboots the new 3.x image and waits for the host to power off. The host will bepowered off if you chose the immediate BIOS upgrade option and will begin toprogram the host BIOS. This process can take two to five minutes to complete.

However, two issues can occur:

■ Issue 1: If you chose the immediate BIOS upgrade option, while the host BIOS isbeing programmed, there is no indication that the BIOS upgrade is beingprogrammed. If you power on the host while the BIOS is being programmed, theBIOS will become garbled and the host will not boot. The solution is to power offthe host, wait two to five minutes for the SP to program the BIOS, then power onthe host.

Topics

Description Links

Unexpected BIOS behavior • “BIOS Upgrade Is Delayed After SP Reboot” onpage 31

Unexpected behavior when resettingto defaults

• “External Serial Port Settings Do Not Reset toDefault Value” on page 32

Hourly timestamp behavior • “Hourly Power Average Timestamp Does NotAccount for Increments of Less Than One Hour”on page 33

SSH keys are not loaded • “SSH Keys Fail to Restore After aBackup/Restore” on page 33


■ Issue 2: If you chose the delayed BIOS option and do not power off the host, theBIOS will not be upgraded. The host must be powered off for the SP to programthe BIOS. If you simply reboot the host, the old BIOS will still be present.Mismatched BIOS and SP firmware might result in incorrect system behavior.

Workaround: It is strongly recommended that you power off the host as soon aspossible following an SP firmware upgrade, and wait at least five minutes beforerebooting the system.

External Serial Port Settings Do Not Reset toDefault ValueCR 6676339

Issue: The reset_to_defaults command enables a user to reset the ILOMconfiguration back to the default values. However, external serial port settings arenot reset when reset_to_defaults action is performed.

Workaround: Use the CLI or web interface to set the external port settings to thedesired values before rebooting ILOM. The external serial port settings can beaccessed by typing /SP/serial/external in CLI or by selecting Configuration -->Serial Port in the web interface.


Hourly Power Average Timestamp Does NotAccount for Increments of Less Than One HourCR 6803961

Issue: When logging in to a CMM using the CLI, the hourly power history includesan entry with a timestamp one hour into the future. This entry shows the averagepower from the prior timestamp to the current moment.

For example, a system is set to take power averages every hour, starting at 1:23 a.m.The first hourly power average increment will end at 2:23 a.m. At 1:24 a.m., an entrywith timestamp 2:23 a.m. will be visible and contains the average power from 1:23a.m. to 1:24 a.m. That entry will continue to be updated until 2:23 a.m., at whichpoint, the hourly power average increment concludes, and the new hourly averagetimestamp will display as 3:23 a.m.

Update: This issue will be fixed in a later ILOM release.

SSH Keys Fail to Restore After a Backup/RestoreCR 6808138

Issue: When backing up and restoring an ILOM configuration, RSA and DSA privatekeys that exist under /SP/services/ssh/keys or /CMM/services/ssh/keysfail to restore.

Workaround: When a new key is generated on the SP, it will result in the followingmessage:

Warning: the RSA host key for ’xxx.xxx.xxx.xxx’ differsfrom the key for the IP address ’xxx.xxx.xxx.xxx’Offending key for IP in ~/.ssh/known_hosts:216Matching host key in ~/.ssh/known_hosts:189

Are you sure you want to continue connecting (yes/no)?

Type yes or edit the known_hosts file.

Update: This issue will be fixed in a later ILOM release.


Documentation Updates and ErrataThis section describes errors that have been found in the ILOM 3.0 DocumentationCollection. Specific change request (CR) identification numbers and workarounds forthe issues are provided, where available.

Topics

Description Links

Documentation correction for setcommand targets, properties, andvalues

• “Targets, Properties, and Values for setCommand” on page 35

Documentation update for maximumnumber of active sessions supportedon some SPARC systems

• “Some SPARC Systems Support a Maximum ofFive Active Sessions” on page 37

Documentation update for a featurethat was documented but not yetavailable on SPARC platforms

• “Power Policy Not Available for SPARC SystemsUsing Earlier Version of ILOM” on page 37

Documentation correction fordowngrading firmware

• “Updating to a Previous ILOM Version MightNot Complete” on page 39

Documentation correction for SSHKey functionality

• “SSH Uses Newly Generated Key WithoutRestarting the SSH Server” on page 39

Documentation correction for HTTPSSSL properties

• “ILOM HTTPS SSL Properties Are Not Visible inthe ILOM Inventory” on page 40

Documentation correction for SNMPcommand to monitor available power

• “SNMP Commands to Monitor Power AreIncorrect” on page 40

Documentation correction for serverserial connection to ILOM

• “Rackmount Servers Support Serial Connectionto ILOM” on page 41

Documentation correction forsupported transfer methods for theSnapshot utility

• “TFTP Is Not a Supported Transfer Method forthe Snapshot Utility” on page 41

Documentation update for StorageRedirection

• “CMM Web Interface Provides Download Linksto Storage Redirection Service and Client CLITools” on page 41

Documentation update describingexception to a power managementrule

• “Exception to the Rule That available_powerIs Greater Than hwconfig_power” on page 42


Targets, Properties, and Values for set CommandIssue: In the Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide, there areincorrect entries for properties, values, and default values that correspond with validtargets in the set command. The following information is correct.

Valid Targets Properties Values Default

/SP/clients/activedirectory statedefaultrole

dnslocatormodeaddressportstrictmodetimeoutlogdetail

enabled | disabledadministrator | operator | a| u |c| r | o | senabled | disabled<ip address> or <DNS name><integer between 0-65535>enabled | disabled<integer>none | high | medium | low |trace

disabled(none)

disabled(none)0disabled4none

/SP/clients/activedirectory/cert/

certstatus

clear_actionissuerload_uriserial_numbersubjectvalid_fromvalid_untilversion

<string>

true<string>tftp|ftp|scp<string><string><string><string><string>

certificate notpresent(none)(none)(none)(none)(none)(none)(none)(none)

/SP/clients/activedirectory/alternateservers/nwhere n is 1-5

addressport

<ip address> or <DNS name><integer>

(none)0

/SP/clients/activedirectory/alternateservers/n/certwhere n is 1-5

certstatus


<string>




Update: This information will be included in a future release of the ILOMDocumentation Collection.

/SP/clients/ldapssl statedefaultrole

dnslocatormodeaddressportstrictmodetimeoutlogdetail

enabled | disabledadministrator | operator | a| u |c| r | o | senabled | disabled<ip address> or <DNS name><integer between 0-65535>enabled | disabled<integer>none | high | medium | low |trace

disabled(none)

disabled(none)0disabled4none

/SP/clients/ldapssl/cert/ certstatus


<string>



/SP/clients/ldapssl/alternateservers/n/certwhere n is 1-5

certstatusclear_actionissuerload_uriserial_numbersubjectvalid_fromvalid_untilversion

<string>true<string>tftp|ftp|scp<string><string><string><string><string>

(none)(none)(none)(none)(none)(none)(none)(none)(none)

/SP/clients/ldapssl/customgroups/nwhere n is 1-5

nameroles

<string>administrator | operator | a | u|c | r | o | s

(none)

(none)

/SP/clients/ldapssl/alternateserver/nwhere n is 1-5

addressport

<string><integer>

(none)0

Valid Targets Properties Values Default


Some SPARC Systems Support a Maximum ofFive Active SessionsIssue: In the ILOM 3.0 Documentation Collection, it states that ILOM supports amaximum of 10 active user sessions. This is incorrect for some SPARC systems,which support a maximum of only five user sessions.


Power Policy Not Available for SPARC SystemsUsing Earlier Version of ILOMIssue: Power policy is NOT available to SPARC platforms using ILOM 3.0 or ILOM3.0.2.

Power policy was incorrectly documented as an available feature on SPARCplatforms in the Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide andthe Integrated Lights Out Manager (ILOM) 3.0 SNMP and IPMI Procedures Guide.

Update: Power policy is now available, on some SPARC platforms, in ILOM 3.0.3.

In the next release of the ILOM 3.0 Documentation Collection, the CLI and SNMPProcedures Guides will not change, but the following topic for configuring thepower policy will be added to the Integrated Lights Out Manager (ILOM) 3.0 WebInterface Procedures Guide.

▼ Configure Power Policy Using the Web Interface

Before You Begin■ The Admin (a) role is required to set the Power Policy configuration variable.

■ Refer to your platform ILOM Supplement for information about power policyimplementation on a specific platform.

Note – The power policy described in this section might not be implemented on theplatform that you are using. See the platform-specific ILOM Supplement or ProductNotes for implementation details. You can find the ILOM Supplement and ProductNotes within the documentation set for your system.


Follow these steps to configure the power management policy using the webinterface:

1. Log in to ILOM.

2. In the web interface page, click System Monitoring --> Power Management.

3. In the Power Management page, do the following:

a. In the Power Policy list box and select either Performance or Elastic.

b. Click Save to apply the new setting.


Updating to a Previous ILOM Version Might NotCompleteCR 6808009

Issue: In the Integrated Lights Out Manager 3.0 Concepts Guide, it states that when youare updating the ILOM firmware to a previous version with the PreserveConfiguration option enabled, and if the preserved configuration file is not found,then the configuration will revert to the default settings when the update completes.That information is incorrect. In that scenario, during the update process, thefollowing error message is reported and the update process is stopped:

The configuration matching the version cannot be restored.Please retry without preserving config.

Firmware image update failed

load: Command Failed

->

To proceed, start the update process again and do not choose the PreserveConfiguration option. When the update is complete and the system reboots, theILOM default settings will be used.

Update: This information will be included in a future release of the ILOM 3.0Documentation Collection.

SSH Uses Newly Generated Key WithoutRestarting the SSH ServerCR 6781487

Issue: In the Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide, theIntegrated Lights Out Manager (ILOM) 3.0 Web Interface Procedures Guide, and theIntegrated Lights Out Manager (ILOM) 3.0 SNMP and IPMI Procedures Guide, thedocuments state that when you are generating a new SSH key, you must restart theSSH server for the new key to take effect. That statement is no longer valid. The newSSH key will become immediately available for new connections. The SSH serverdoes not need to be restarted for the new key to take effect.



ILOM HTTPS SSL Properties Are Not Visible inthe ILOM InventoryCR 6749651

Issue: In the Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide, thefollowing properties are listed incorrectly as present in the ILOM inventory. Theseproperties are not part of the ILOM inventory:

■ -> show /SP/services/https/ssl/custom_cert serial_number

■ -> show /SP/services/https/ssl/custom_cert version

■ -> show /SP/services/https/ssl/default_cert issued_by

■ -> show /SP/services/https/ssl/default_cert serial_number

■ -> show /SP/services/https/ssl/default_cert version

Update: This information will be updated in a future release of the ILOMDocumentation Collection.

SNMP Commands to Monitor Power AreIncorrectCR 6766948

Issue: In the Integrated Lights Out Manager (ILOM) 3.0 SNMP and IPMI ProceduresGuide, the commands for monitoring power are incorrect. The following commandsare correct.

● To monitor the available power consumption using SNMP, type this command:

● To monitor the hardware configuration maximum power consumption usingSNMP, type this command:

● To monitor the permitted power consumption using SNMP, type thiscommand:

% snmpget -v2c -cprivate -mALL snmp_agent_ipaddresssunHwCtrlPowerMgmtAvailablePower.0

% snmpget -v2c -cprivate -mALL snmp_agent_ipaddresssunHwCtrlPowerMgmtHWConfigPower.0

% snmpget -v2c -cprivate -mALL snmp_agent_ipaddresssunHwCtrlPowerMgmtPermittedPower.0



Rackmount Servers Support Serial Connection toILOMCR 6792940

Issue: In the Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide, it is statedincorrectly in Table 2-1 that rackmount servers do not support a serial connection toILOM. Rackmount servers do support a serial connection to ILOM.


TFTP Is Not a Supported Transfer Method for theSnapshot UtilityCR 6792940

Issue: In the Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide, TFTP isgiven incorrectly as a supported protocol to use when transferring the Snapshot datato a directory. TFTP is not a supported protocol for Snapshot data transfers. Thesupported transfer protocols are SFTP and FTP.


CMM Web Interface Provides Download Links toStorage Redirection Service and Client CLI ToolsCR 6793269

Issue: In the Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide, it states thatthe Storage Redirection feature is not supported on a chassis monitoring module(CMM) running ILOM 3.0 firmware. The Storage Redirection CLI feature in ILOMconsists of a set of tools (a service and a client) that you run on your machine toconnect to a supporting service processor (SP). The ILOM web interface acts as a“delivery system” for users to download these tools. While it is correct thatredirection is not supported for any CMM, the CMM web interface still provides the


download links to the Storage Redirection service and client CLI tools. Once theservice and client tools are downloaded and running on your machine, they can beused for Storage Redirection to a server module running ILOM 3.0.

Update: This additional information will be added to a future release of the ILOMDocumentation Collection.

Exception to the Rule That available_power IsGreater Than hwconfig_power

CR 6802142

Issue: In the Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide, availablepower is defined as the maximum power that the power supplies in the system candraw from an external source. Typically this number is greater than the hardwareconfiguration maximum. In general, available_power is always greater thanhwconfig_power in all rackmount servers supporting ILOM. An exception existsfor the blade modular systems where hwconfig_power is greater thanavailable_power.

The reason for the exception is because on a chassis system, the maximum powerthat could be consumed by each server module is included in the hwconfig_powernumber. However, the chassis guarantees that the maximum power will never beapplied to all server modules at the same time (and the allowed maximum isdisplayed in permitted_power).



CHAPTER 3

Updates to the ILOM 3.0.4 Firmware

This chapter describes the new features and functionality that have been added tothe ILOM 3.0.4 firmware release. Procedures to implement the new functionality areexplained. Resolved issues, known issues, and documentation updates are alsodescribed.

Topics in the chapter include:

■ “New Features for ILOM 3.0.4” on page 44

■ “Resolved Issues as of ILOM 3.0.4” on page 66

■ “Known Issues as of ILOM 3.0.4” on page 73

■ “Documentation Updates and Errata” on page 74

43

New Features for ILOM 3.0.4There are several new features integrated into the ILOM 3.0.4 release. The followingtable lists those new features and points you to the sections that describe thefeatures.

Topics

Description Links

New power management layout andthreshold control

• “Power Management New Web Layout for theSP” on page 45

• “Power Consumption Thresholds” on page 47

Updated idle time setting for a CLIsession

• “Set Timeout Value for a cli Session” on page 48

New target added for LDAP/SSLauthentication attributes

• “Edit LDAP/SSL Optional User Mapping” onpage 49

New ability to download SNMPMIBs from ILOM

• “Download SNMP MIBs Directly From ILOM”on page 52

New ability to display user roles thatare assigned to a user session

• “View User Roles in Active Session” on page 54

Enhanced expanded search mode inActive Directory

• “View and Configure Expanded Search Mode inActive Directory” on page 56

Enhanced test alert when settingIPMI traps, Email alerts, or SNMPtraps

• “Send Test Email Alert to Specific AlertDestination” on page 59

New locking ability for the ILOMRemote Console

• “ILOM Remote Console Computer Lock” onpage 60

New ILOM SP network ports • “New ILOM SP Network Ports” on page 65

Updated mouse mode setting forremote host KVMS

• “Enhanced Mouse Mode Settings for RemoteHost KVMS” on page 65


Power Management New Web Layout for the SPPower Management has been moved to a top level tab for the SP with the followingthree new sub-level tabs:

■ Allocation – Power Configuration settings have moved to this sub-tab.

■ Settings – Power Policy settings have moved to this sub-tab.

■ History – Power consumption history has moved to this sub-tab.

Note – Some power management features might not be available on all serverssupporting ILOM. Refer to your platform documentation for more informationabout the availability of power management features and functionality for yourserver.


Power Management New Web Layout for theCMMPower Management has been moved to a top level tab for the CMM with thefollowing four new sub-level tabs:


■ Redundancy – Power Policy settings have moved to this sub-tab.


■ Metrics – Power metrics have been moved to this sub-tab.

Note – Some power management functions might not be available on all serverssupporting ILOM. Refer to your platform documentation for more informationabout the availability of power management features and functionality for yourserver.


Power Consumption ThresholdsYou can set two thresholds for power consumption, which generate an ILOM eventif the threshold is exceeded. This event is logged in the ILOM event log. If emailalerts are configured, an email alert is sent. If SNMP traps are enabled, the event willbe delivered via the SUN-HW-TRAP-MIB trap.

Before You Begin

■ The Admin (a) role is required to change power consumption configurationvariables.

■ The Read Only (o) role is required to view power consumption configurationvariables.

▼ View and Configure Power Thresholds Using the CLI1. Log in to ILOM.

2. To view the current settings, type:

->show /SP/powermgmt

3. To set the value for thresholds, type:

-> set threshold1|2=n

Where n represents watts.

Note – The value for threshold 1 and threshold 2 cannot exceed the maximumhwconfig value, which is a variable that is established based on platformrequirements.

▼ View and Configure Power Thresholds Using the WebInterface1. Log in to ILOM.2. In the web interface page, click Power Management --> Allocations.

The Allocations page appears.3. In the Allocations page, set threshold values based on platform requirements.

Note – The value for threshold 1 and threshold 2 cannot exceed the maximumhwconfig value, which is a variable that is established based on platformrequirements.


Set Timeout Value for a cli SessionCR 6280346

You can now set the amount of time a cli session can remain idle before the sessiontimes out and closes. A timeout property has been added for the cli target.Allowable timeout values are between 0 (zero) and 1440 minutes. 0 (zero) indicatesthat the cli session timeout is disabled, so that the cli session will not closeregardless of the amount of time the session is idle.

Before You Begin

■ The Admin (a) role is required to change the cli timeout configurationvariable.

■ The Read Only (o) role is required to view the cli timeout configurationvariable.

▼ Set Timeout Value Using the CLI1. Log in to ILOM.

2. To view the current settings, type:

->show /SP/cli

3. To set the timeout value, type the following command:

-> set /SP/cli timeout=n

Where n is a number between 0 and 1440.

For example, to set the timeout value to 60 minutes, type:

-> set /SP/cli timeout=60

Set ‘timeout’ to ‘60’


Edit LDAP/SSL Optional User MappingCR 6811913

LDAP/SSL now enables the use of attributes other than the Distinguished Name(DN) for user credential validation. Previously, it was difficult to define userdomains used to authenticate users in unconventional environments where theDistinguished Name (DN) does not reflect the user’s login name.

A new target, Optional User Mapping, has been added in ILOM 3.0.4 to enable theuse of alternative attributes for LDAP authentication.

For more information about LDAP/SSL, and for definitions of terms used in thisenhancement, refer to any of the Procedures Guides (CLI, Web, or SNMP) in theILOM Documentation Collection at:http://www.fujitsu.com/sparcenterprise/manual/

Before You Begin

■ The User Management (u) role is required to change LDAP/SSL configurationvariables.

■ The Read Only (o) role is required to view LDAP/SSL configuration variables.

▼ Edit Optional User Mapping in LDAP/SSL Using theCLI1. Log in to ILOM.

1. To view the LDAP/SSL Optional User Mapping, type the following command:

-> show /SP/clients/ldapssl/optionalUserMapping

The following sample output appears.



2. Use the set command to modify any of the properties.

For example:

▼ Edit LDAP/SSL Optional User Mapping Using the WebInterface1. Log in to ILOM.

2. In the web interface page, click User Management --> LDAP/SSL.

The LDAP/SSL Management page appears.

-> cd /SP/clients/ldapssl/optionalUserMapping/SP/clients/ldapssl/optionalUserMapping

-> show

/SP/clients/ldapssl/optionalUserMapping Targets:

Properties: attributeInfo = (&(objectclass=person)(uid=<USERNAME>)) binddn = cn=Manager,dc=sun,dc=com bindpw = (none) searchbase = ou=people,dc=sun,dc=com state = disabled


-> set state=enabledSet ’state’ to ’enabled’


3. In the Optional User Mapping field, click the (edit) link that appears next tothe word “Enabled.”

The Edit dialog box appears.


4. In the Edit LDAP/SSL Optional User Attribute dialog, modify any of theparameters, then click Save to apply your changes.

Download SNMP MIBs Directly From ILOMCR 6691452

A copy of the SNMP MIBs are now part of the ILOM firmware. This enables you todownload the MIBs directly from ILOM rather than being required to retrieve theMIBs from a web site or the platform Tools and Drivers CD/DVD.

Before You Begin

■ The Reset and Host Control (r) role is required to download SNMP MIBs fromILOM.


▼ Download SNMP MIBs From ILOM Using the CLI1. Log in to ILOM.

2. Use the show command to display the SNMP MIBs.

For example:

3. To download the files, type either of the following commands:

-> dump -destination <URI> /SP/services/snmp/mibs

or

-> set /SP/services/snmp/mibs dump_uri=<URI>

Where <URI> specifies the target to which the files are downloaded.

A zip file containing the MIBs is transferred to the destination server.

▼ Download SNMP MIBs From ILOM Using the WebInterface1. Log in to ILOM.

2. In the web interface, click Configuration --> System Management Access -->SNMP.

The SNMP Management page appears.

3. Click the MIBs jump link, or scroll down to the MIBs section.

The MIBs section of the page appears.

-> show /SP/services/snmp/mibs

/SP/services/snmp/mibs Targets:

Properties: dump_uri = (Cannot show property)

Commands: cd dump set show


4. Click Download.

When prompted, enter a destination in which to save the file.

View User Roles in Active SessionCR 6714015

Role information (a | u | c | r | o | s) is now available for all active sessions in theCLI and in the Active Sessions table of the web interface.

Before You Begin

■ The Read Only (o) role is required to view active user session roles.

▼ View Roles for Active User Session Using the CLI1. Log in to ILOM.

2. To display the user session roles, type the following command:

-> show /SP/sessions/n

Where n is the number of the user session.

For example:


▼ View Roles for Active User Session Using the WebInterface1. Log in to ILOM.

2. In the web interface page, click User Management --> Active Sessions.

The Active Sessions table appears.

3. In the Active Session table, view the roles associated with each user session.

-> show sessions/18

/SP/sessions/18 Targets:

Properties: username = root role = aucro starttime = Mon Apr 13 06:25:19 2009 type = web mode = normal

Commands: cd show


▼ View and Configure Expanded Search Mode in ActiveDirectoryCR 6806991

In Active Directory, you can enable or disable an expanded search mode to controlthe search for user entries. The default Active Directory functionality is intentionallyrestrictive to ensure proper security. Search criteria has been expanded toaccommodate specific customer environments.

The expanded search mode is disabled by default, which means theuserPrincipleName is expected to have a fully qualified domain name (FQDN)suffix. When expanded search mode is enabled, different searches are attempted ifthe more specific userPrincipleName search does not immediately succeed.

Before You Begin

■ The User Management (u) role is required to configure Active Directoryconfiguration variables.

■ The Read Only (o) role is required to view Active Direction configurationvariables.

▼ View and Configure Expanded Search Mode in ActiveDirectory Using the CLI1. Log in to ILOM.

2. To view the expanded search mode in Active Directory, type the followingcommand:

-> show /SP/clients/activedirectory

The following sample output appears.

-> show /SP/clients/activedirectory

/SP/clients/activedirectory Targets: admingroups alternateservers cert customgroups dnslocatorqueries opergroups userdomains


3. To enable the expanded search mode in Active Directory, type the followingcommand:

-> set /SP/clients/activedirectory expsearchmode=enabled

For example:

▼ View and Configure Expanded Search Mode in ActiveDirectory Using the Web Interface1. Log in to ILOM.

2. In the web interface page, click User Management --> Active Directory.

The Active Directory Management page appears.

Properties: address = 10.8.123.45 defaultrole = (none) dnslocatormode = disabled expsearchmode = disabled logdetail = none port = 0 state = enabled strictcertmode = disabled timeout = 4


-> set /SP/clients/activedirectory expsearchmode=enabledSet 'expsearchmode' to 'enabled'


3. In the Expanded Search Mode field, select the Enabled box to enable thisoption or clear the Enabled box to disable this option.

4. Click Save to apply your changes.


Send Test Email Alert to Specific Alert DestinationCR 6781900

When editing an IPMI Platform Event Trap (IPMI PET), Email alert, or SNMP trap,you can now send a test alert to the alert rule destination before saving the alert rule.

Before You Begin

■ The Read Only (o) role is required to send a test email alert to a specificdestination.

▼ Send Test Email Alert to Specific Destination Using theCLI1. Log in to ILOM.

2. To send a test email alert, type:

-> set /SP/alertmgmnt/rules/n testrule=true

Where n is the number associated with the alert rule.

▼ Send Test Email Alert to Specific Alert DestinationUsing the Web Interface1. Log in to ILOM.

2. In the web interface page, click Configuration --> Alert Management.

The Alert Settings page appears.

3. In the Alert Settings page, perform the following steps to send a test emailalert:

a. Select the radio button of the alert rule.

b. Click the Test Rule button to send a text email alert to the alert ruledestination.


ILOM Remote Console Computer LockThe Lock feature available for the ILOM Remote Console enhances your systemsecurity by enabling you to lock your computer when terminating a ILOM RemoteConsole session. Specifically, the lock behavior takes place either when youterminate a ILOM Remote Console session or when the managed networkconnection to the server is lost.

If you are running a Windows operating system on your host, you can enable thecomputer lock feature in ILOM by selecting Windows as your option. The Windowslock mode option works in conjunction with the standard Windows keyboardshortcut for locking the Windows operating system (CRTL+ALT+DEL K).

If you are running a Solaris or Linux operating system on your host, you can executethe computer lock behavior when the ILOM Remote Console terminates byimplementing the custom lock mode feature in ILOM.

The custom lock mode feature in ILOM enables you to execute any system behaviorthat is tied to a predefined keyboard shortcut on your host operating system. Toexecute a custom keyboard shortcut behavior in ILOM, you must first define thebehavior you want to take place on your host operating system with a keyboardshortcut. Then, to execute this behavior when the ILOM Remote Console terminates,you must specify the OS keyboard shortcut parameters in the custom KVMS lockmode feature in ILOM.

Special Considerations When Enabling the ILOM RemoteConsole Lock OptionReview the following special considerations in TABLE 3-1 prior to enabling the KVMSlock mode option in ILOM.


▼ Edit the ILOM Remote Console Lock OptionUsing the ILOM CLI1. Log in to the ILOM SP CLI.

Note – Alternatively, you can log in to the ILOM CMM CLI then navigate to the SPtarget where you want to enable or disable the KVMS lock option for the ILOMRemote Console.

2. To view all the possible properties associated with the management of the SPKVMS services, type:

-> help /SP/services/kvms

The following sample output appears:

TABLE 3-1 Special Considerations When Enabling the Remote Console Lock Option

Special Consideration Description

Console user role isrequired to set lockoption.

To enable the ILOM Remote Console Lock option in ILOM, youmust have Console (c) role privileges associated with your useraccount.For more information about setting up a user account in ILOMwith Console privileges, see the User Management section in theILOM 3.0 Documentation Collection.

A predefinedkeyboard shortcuton the OS isrequired to executethe custom lockmode feature.

Prior to enabling a custom keyboard shortcut in ILOM for whenthe ILOM Remote Console connection terminates, you must firstdefine the keyboard shortcut behavior on your host operatingsystem.For instructions for creating a keyboard shortcut on your hostoperating system, see the documentation supplied with youroperating system.

The custom lockmode feature can bedefined with up tofour modifiers andone key.

When you specify the custom lock mode feature in ILOM, you canspecify up to four modifiers and one key. A list of supportedmodifiers and keys that you can use to match your predefined OSkeyboard shortcut appear in both the CLI KVMS help and theweb interface KVMS page.

Lock behavior whenrunning multipleILOM RemoteConsole Sessions.

If more than one ILOM Remote Console session is opened to thesame SP, the Windows lock or custom keyboard shortcut behaviorconfigured in ILOM will only take place when you close the lastSP ILOM Remote Console session.


3. Perform any of the following tasks using either the cd, set, or show commandsto manage the SP KVMS target properties.

/SP/services/kvms : Management of the KVMS service Targets:

Properties: custom_lock_key : KVMS custom lock key custom_lock_key : Possible values = esc, end, tab, ins,del, home, enter, space, break, backspace, pg_up, pg_down,scrl_lck, sys_rq, num_plus, num_minus, f1, f2, f3, f4, f5, f6, f7,f8, f9, f10, f11, f12, a-z, 0-9, !, @, #, $, %, ^, &, *, (, ), -,_, =, +,‚ |, ~, ‘, [, {, ], }, ;, :, ’, ", <, ., >, /, ? custom_lock_key : User role required for set = c

custom_lock_modifiers : KVMS custom lock modifiers custom_lock_modifiers : Possible values = l_alt, r_alt,l_shift, r_shift, l_ctrl, r_ctrl, l_gui, r_gui custom_lock_modifiers : User role required for set = c

lockmode : KVMS lock mode lockmode : Possible values = disabled, windows, custom lockmode : User role required for set = c

mousemode : KVMS mouse mode mousemode : Possible values = absolute, relative mousemode : User role required for set = c

servicestate : KVMS service state servicestate : Possible values = enabled, disabled servicestate : User role required for set = a


Enabled Custom Lock Mode Example

If you, for example, performed the following tasks:

1. Predefined a custom keyboard shortcut in your host OS to log you off theoperating system and this keyboard shortcut was defined with the following keysequences:

<shift><control><backspace>

2. The KVMS properties for the custom lock mode feature in the ILOM CLI wouldlook similar to the properties shown below:

Task Instructions

Navigate to theKVMs target.

• To navigate to the KVMs target, type the following command:-> cd /SP/services/kvms

Note - You must navigate to the KVMs target prior to enabling ordisabling the KVMS lock mode options.

Display theKVMS lockmodeproperties.

• To display the KVMS lock mode properties, type the followingcommand:-> show

The target, properties, and commands that are associated with themanagement of the SP KVMS service appear.

Disable theILOM RemoteConsole lockmode feature.

• To disable the ILOM Remote Console lock mode feature, type thefollowing command:-> set lockmode=disabled

Enable thestandardWindows hostlock modefeature.

• To enable the standard lock mode feature on a Windows system, typethe following command:-> set lockmode=windows

Enable thecustom hostlock modefeature.

• To enable the custom lock mode feature on a Linux, Solaris, orWindows system, type following commands:-> set lockmode=custom

-> set custom_lock_key=<specify a custom lock key>-> set lock_modifiers=<specify up to four custom lock modifiers>

Note - Each custom lock modifier specified must be separated by acomma.


▼ Edit the ILOM Remote Console Lock OptionUsing the Web Interface1. Log in to the ILOM SP web interface.

Note – Alternatively, you can log into the ILOM CMM web interface then navigateto the SP target where you want to enable or disable the KVMS lock option for theILOM Remote Console.

2. In the web interface page, click Remote Console --> KVMS.

The KVMS page appears displaying the options available for KVMS Settings andHost Lock Settings

3. In the Host Lock Settings section of the KVMS page, perform one of thefollowing tasks:

4. Click Save to apply the changes you specified.

/SP/services/kvms Targets:

Properties: custom_lock_key = backspace custom_lock_modifiers = l_shift, l_ctrl lockmode = custom mousemode = absolute servicestate = enabled

Task Instructions

Enable the standard Windowshost lock mode option.

• In the Lock Mode list box, select Windows.

Enable the custom host lockmode feature.

1. In the Lock Mode list box, select Custom.2. In the Custom Lock Modifiers list box, select up to four

custom modifiers that match the keyboard shortcutmodifiers that are predefined in your operating system.

3. In the Custom Lock Key list box, select the key thatmatches the keyboard shortcut key that is predefined inyour operating system.

Disable the host lock modefeature.

• In the Lock Mode list box, select Disabled.


New ILOM SP Network PortsAs of ILOM 3.0.4, support for the following default network ports have been added:

■ 5555 TCP ILOM Remote Console: Encryption

■ 7579 TCP ILOM Remote Console: Serial

■ 6481 TCP ILOM Servicetag Daemon

Support for these SP network ports have been added to ILOM 3.0.4 in addition tothe default network ports that were previously supported in ILOM 3.0.

Note – The Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide lists the defaultnetwork ports for ILOM 3.0. This guide will be updated to include the latest portsavailable as of ILOM 3.0.4.

Enhanced Mouse Mode Settings for Remote HostKVMSAs of ILOM 3.0.4, you can toggle between relative and absolute mouse modesettings for remote KVMS without having to reset the server SP. Changes made tothe mouse mode configuration variable will take effect immediately in the ILOMRemote Console.

Before You Begin

■ The Console (c) role is required to edit the mouse mode configuration variable.

▼ Edit Mouse Mode Setting for Remote HostUsing the CLI1. Log in to ILOM.

2. Use the set command to edit the mouse mode configuration variable, forexample:

-> set /SP/services/kvms mousemode=relative

or

-> set /SP/services/kvms mousemode=absolute


▼ Edit Mouse Mode Setting for Remote HostUsing the Web Interface1. Log in to ILOM.

2. In the web interface page, click Remote Control --> KVMS.

3. In the KVMS page, select Absolute or Relative in the Mouse Mode box.

Resolved Issues as of ILOM 3.0.4This section describes the issues that have been resolved in the ILOM 3.0.4 release.Specific change request (CR) identification numbers and workarounds for the issuesare provided, where available.

Topics

Description Links

User management resolved issues • “LDAP or RADIUS Commands Do Not WorkWhen Default Role Is Set to none” on page 67

• “Difficulty Removing dnslocatorqueryRecords From Active Directory Configuration”on page 67

System clock setting resolved issue • “When Using the CLI to Set the Time Zone,Certain Time Zones Do Not Recalculate theClock Correctly” on page 68

Power management resolved issue • “Help Text for Power Management Properties IsIncorrect” on page 70

Snapshot SP data resolved issue • “Snapshot Utility Missing Log Files forDebugging” on page 69


LDAP or RADIUS Commands Do Not WorkWhen Default Role Is Set to none

CR 6804986

Issue: When you set the LDAP or RADIUS default role to none, the Read Only (o)role is not automatically assigned as it should be.

Update: This issue is fixed in the ILOM 3.0.4 release. Now when you set the LDAPor RADIUS default role to none and log in as an LDAP or RADIUS user, the ReadOnly (o) role is assigned.

Difficulty Removing dnslocatorquery RecordsFrom Active Directory ConfigurationCR 6797346

Issue: dnslocatorquery records cannot be removed during configuration ofActive Directory.

Update: This issue is fixed in ILOM 3.0.4 release. The content and range rules for thednslocatorquery records have been relaxed to allow for the clearing or removalof the entries. This allows an empty string value to be accepted to completelyremove the entry.

ILOM back up CLI feature resolvedissue

• “ILOM CLI for set /{target}/configdump_uri Does Not Provide ConfirmationMessage” on page 69

CLI Help text function resolvedissues

• “Role Help Text for Read-Only /SYS PropertiesIs Incorrrect” on page 70

• “Help Output Results for <TARGET> <property><property> Is Confusing” on page 71

• “Inaccurate Help Text Values for/SP/users/root/ssh/key/1-5” on page 72

Serial port setting in CLI resolvedissue

• “ILOM External Serial Port Flow ControlImplemented Incorrectly” on page 72

Topics

Description Links


When Using the CLI to Set the Time Zone, CertainTime Zones Do Not Recalculate the ClockCorrectlyCR 6798875

Issue: When using the CLI to set the time zone, some time zones either do notrecalculate the clock correctly or make no change to the clock.

Update: You must use valid global time zone nomenclature to set the time zone sothat the clock is recalculated correctly. You can find a list of the valid global timezone nomenclature on the Internet, for example, at:http://en.wikipedia.org/wiki/List_of_tz_zones_by_name

For example, type these commands to set the time zone to either U.S. EasternStandard Time or Central Time:

-> set /SP/clock/ timezone=America/New_York

-> set /SP/clock/ timezone=America/New_YorkSet ’timezone’ to ’America/New_York’

-> show /SP/clock/

/SP/clock Targets:

Properties: datetime = Wed Feb 11 13:22:28 2009 timezone = EST (America/New_York) usentpserver = disabled



http://en.wikipedia.org/wiki/List_of_tz_zones_by_name

Snapshot Utility Missing Log Files for DebuggingCR 6811375

Issue: Missing files from /var/log impairs debug process when collecting data forservice engineers using the Snapshot Utility.

Update: The missing Snapshot Utility /var/log files have been restored in theILOM 3.0.4 release.

ILOM CLI for set /{target}/configdump_uri Does Not Provide ConfirmationMessageCR 6804202

Issue: When you set the dump_uri on /{target}/config, the ILOM CLI does notdisplay a confirmation message to indicate whether the command was successful.

Update: The print confirmation message for set /{target}/config dump_urihas been corrected in the ILOM 3.0.4 release.

-> set /SP/clock/ timezone=America/ChicagoSet ’timezone’ to ’America/Chicago’

-> show /SP/clock/

/SP/clock Targets:

Properties: datetime = Wed Feb 11 12:22:36 2009 timezone = CST (America/Chicago) usentpserver = disabled



Role Help Text for Read-Only /SYS Properties IsIncorrrectCR 6764923, CR 6770180

Issue: The ILOM CLI Help provides misleading user role information for read-only/SYS properties. For example:

-> help /SYS fru_part_number

Properties:

fru_part_number : FRU part number

fru_part_number : User role required for set = r

User role information provided by Help for read-only properties is misleading sincethe read-only properties cannot be configured regardless of user role.

Update: As of ILOM 3.0.4, the ILOM Help function was updated to remove therequired user role value for read-only /SYS properties.

Help Text for Power Management Properties IsIncorrectCR 6770180

Issue: The following properties are read-only and are not configurable; therefore, therole required to view these properties is Read Only (o):

-> help /SP/powermmgmt

Properties:

actual_power : Actual power consumed by the system

actual_power : User role required for set = o

permitted_power : Total power permitted for the system

permitted_power : User role required for set = o

available_power : Available power for the system

available_power : User role required for set = o

Update: This issue is fixed in the ILOM 3.0.4 release. The Help text associated withthe properties now correctly specifies that the required role to view the properties isRead Only (o).


Help Output Results for <TARGET> <property><property> Is ConfusingCR 6770069

Issue: Help function displays confusing text when listing values for multipleproperties, for example:

Help output prints:

Help output should print:

Update: The Help function was updated in the ILOM 3.0.4 release to removeproperty values that were not applicable.

-> help /HOST send_break_action boottimeout statusProperties:send_break_action : Send Break Action to Hostsend_break_action : Possible values = break, dumpcoresend_break_action : User role required for set = cboottimeout : Boot time outsend_break_action : Possible values = break, dumpcoreboottimeout : User role required for set = rstatus : Host Statussend_break_action : Possible values = break, dumpcoreboottimeout : User role required for set = r

-> help /HOST send_break_action boottimeout statusProperties:send_break_action : Send Break Action to Hostsend_break_action : Possible values = break, dumpcoresend_break_action : User role required for set = cboottimeout : Boot time outboottimeout : User role required for set = rstatus : Host Status


Inaccurate Help Text Values for/SP/users/root/ssh/key/1-5

CR 6783032

Issue: The Help text has several inaccuracies for the different properties under/SP/users/root/ssh/keys/.

Update: The Help function for /SP/users/root/ssh/key has been corrected inthe ILOM 3.0.4 release.

ILOM External Serial Port Flow ControlImplemented IncorrectlyCR 6822067

Issue: Writable support (using the set command) for ILOM’s external serial portflow control is not supported on SPARC servers.

Update: As of ILOM 3.0.4, writable support for ILOM’s external serial port flowcontrol is not supported on SPARC servers. Read-only support (using the showcommand) for ILOM’s external serial port flow control is provided for all serverplatforms using ILOM.


Known Issues as of ILOM 3.0.4This section describes known issues and workarounds as of ILOM 3.0.4. Specificchange request (CR) identification numbers and workarounds for these issues areprovided, where available.

ILOM Remote Console Might Hang on WindowsClient When Redirecting a CD-ROM Image orFloppy ImageCR 6806444

Issue: When using a Windows client to redirect a CD-ROM image or floppy imagefrom the ILOM Remote Console, the ILOM Remote Console might not respond.

Affected Software:

■ ILOM 2.0 or later and ILOM 3.0 or later

■ ILOM Remote Console

■ Java Development Kit (JDK) 160

■ Windows operating system installed on client system

Workaround:

● Close the ILOM Remote Console window on the Windows client, then performone of the following workarounds:

■ Using a Linux or Solaris client, launch the ILOM Remote Console to redirectthe CD-ROM image or floppy image.

or

■ Using a Windows, Solaris, or Linux client, launch the Storage RedirectionUtility in ILOM 3.0 to redirect the CD-ROM or floppy image.

Note – The Storage Redirection Utility feature is a command-line utility that is onlyavailable in ILOM 3.0. For instructions about how to use the Storage RedirectionUtility, see the ILOM 3.0 Documentation Collection.


Documentation Updates and ErrataThis section describes errors that have been found in the ILOM 3.0 DocumentationCollection. Specific change request (CR) identification numbers and workarounds forthe issues are provided, where available.

Allowable Number for DNS Retries Is IncorrectCR 6823516

Issue: In the Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide, it isincorrectly stated that the number of allowable retries to configure a DNS setting isbetween 0 and 5.

Update: ILOM allows a total of 5 attempts to contact the DNS server, of which 0-4are retries.

New Web Power Management LayoutPower Management has been moved to a top level tab for the SP with the followingthree new sub-level tabs:


■ Settings – Power Policy settings have moved to this sub-tab.


For more information, see “Power Management New Web Layout for the SP” onpage 45.

Topics

Description Links

Documentation correction forallowable number of DNS retries

• “Allowable Number for DNS Retries IsIncorrect” on page 74

Documentation correction for newweb power management layout

• “New Web Power Management Layout” onpage 74

Documentation correction for powermanagement thresholds

• “Power Consumption Thresholds” on page 75


Power Consumption ThresholdsYou can set two thresholds for power consumption, which generate an ILOM eventif the threshold is exceeded. This event is logged in the ILOM event log. If emailalerts are configured, an email alert is sent. If SNMP traps are enabled, the event willbe delivered via the SUN-HW-TRAP-MIB trap.

For more information, see “Power Consumption Thresholds” on page 47.



Documents

Integrated Lights Out Manager (ILOM) 3.0 Feature Updates ......Les produits portant les marques SPARC sont basés sur une architecture développée par Sun Microsystems, Inc. SPARC64