Manual Code C120-E600-01EN Part No June 2009, Revision A. Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes

Transcription

1 Manual Code C120-E600-01EN Part No June 2009, Revision A Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes

2 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 in this document, and such products, technology and this document are protected by copyright laws, patents and other intellectual property laws and international treaties. The intellectual property rights of Sun Microsystems, Inc. and Fujitsu Limited in such products, technology and this document include, without limitation, one or more of the United States patents listed at and one or more additional 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 prior written authorization of Fujitsu Limited and Sun Microsystems, Inc., and their applicable licensors, if any. The furnishing of this document to you does not give you any rights or licenses, express or implied, with respect to the product or technology to which it pertains, and this document does not contain or represent any commitment of any kind on the part of Fujitsu Limited or Sun Microsystems, Inc., or any affiliate of either of them. This document and the product and technology described in this document may incorporate third-party intellectual property copyrighted by and/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 End User. 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 trademark in 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 acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun s licensees who implement OPEN LOOK 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 of Sun 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 this document or any product or technology described herein are those expressly set forth in the license agreement pursuant to which the product or 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 SUCH PRODUCT OR TECHNOLOGY OR THIS DOCUMENT, WHICH ARE ALL PROVIDED AS IS, AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING WITHOUT LIMITATION 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. Unless otherwise expressly set forth in such agreement, to the extent allowed by applicable law, in no event shall Fujitsu Limited, Sun Microsystems, Inc. or any of their affiliates have any liability to any third 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.

3 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 et technologies décrits dans ce document. De même, ces produits, technologies et ce document sont protégés par des lois sur le copyright, des brevets, 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 plusieurs des brevets déposés aux États-Unis et indiqués à l adresse de même qu un ou plusieurs brevets ou applications breveté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 quelque forme 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 type que 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 par copyright et/ou cédés sous licence par des fournisseurs à Fujitsu Limited et/ou Sun Microsystems, Inc., y compris des logiciels et des technologies 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 utilsateur disponible; 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 marque dé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 Sun Microsystems, 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. Sun reconnaît les efforts de pionniers de Xerox pour la recherche et le développement du concept des interfaces d utilisation visuelle ou graphique pour l industrie de l informatique. Sun détient une license non exclusive de Xerox sur l interface d utilisation graphique Xerox, cette licence couvrant également les licenciés de Sun qui mettent en place l interface d utilisation graphique OPEN LOOK et qui, en outre, se conforment aux licences écrites de Sun. Droits du gouvernement américain - logiciel commercial. Les utilisateurs du gouvernement américain sont soumis aux contrats de licence standard 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 autre entité en rapport avec ce document ou tout produit ou toute technologie décrit(e) dans les présentes correspondent aux garanties expressément stipulées dans le contrat de licence régissant le produit ou la technologie fourni(e). SAUF MENTION CONTRAIRE EXPRESSÉMENT STIPULÉE DANS CE CONTRAT, FUJITSU LIMITED, SUN MICROSYSTEMS, INC. ET LES SOCIÉTÉS AFFILIÉES REJETTENT TOUTE REPRÉSENTATION OU TOUTE GARANTIE, QUELLE QU EN SOIT LA NATURE (EXPRESSE OU IMPLICITE) CONCERNANT CE PRODUIT, 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, SONT EXCLUES, DANS LA MESURE AUTORISÉE PAR LA LOI APPLICABLE. Sauf mention contraire expressément stipulée dans ce contrat, dans la mesure autorisée par la loi applicable, en aucun cas Fujitsu Limited, Sun Microsystems, Inc. ou l une de leurs filiales ne sauraient être tenues responsables 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 ou consé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 EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L APTITUDE A UNE UTILISATION PARTICULIERE OU A L ABSENCE DE CONTREFACON.

4

5 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 Firmware 9 New Features for ILOM Improved Chassis View 11 v

6 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 Interface 20 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 Alt-Graph Key Functionality on International Keyboards 28 Web Interface Does Not Display the Browse Button When Uploading Files 28 Newly Generated SSH Keys Are Now Available Immediately Without Requiring SSH Server Restart 29 Loading SSH Host Key No Longer Results in Error Message 29 Address Using IP Address Is Accepted in Alert Management Rule Query 30 Known Issues as of ILOM 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 Less Than One Hour 33 vi Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes June 2009

7 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 of ILOM 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 Service and Client CLI Tools 41 Exception to the Rule That available_power Is Greater Than hwconfig_power Updates to the ILOM Firmware 43 New Features for ILOM 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

8 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 Directory Using the CLI 56 View and Configure Expanded Search Mode in Active Directory Using the Web Interface 57 Send Test Alert to Specific Alert Destination 59 Send Test Alert to Specific Destination Using the CLI 59 Send Test Alert to Specific Alert Destination Using the Web Interface 59 ILOM Remote Console Computer Lock 60 Special Considerations When Enabling the ILOM Remote Console Lock Option 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 LDAP or RADIUS Commands Do Not Work When Default Role Is Set to none 67 Difficulty Removing dnslocatorquery Records From Active Directory Configuration 67 When Using the CLI to Set the Time Zone, Certain Time Zones Do Not Recalculate the Clock Correctly 67 viii Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes June 2009

9 Snapshot Utility Missing Log Files for Debugging 68 ILOM CLI for set /{target}/config dump_uri Does Not Provide Confirmation 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 Confusing 70 Inaccurate Help Text Values for /SP/users/root/ssh/key/ ILOM External Serial Port Flow Control Implemented Incorrectly 72 Known Issues as of ILOM ILOM Remote Console Might Hang on Windows Client When Redirecting a CD-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

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

11 Preface The Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes describes enhancements that have been made to ILOM firmware since the ILOM 3.0 release. ILOM updated versions are typically released every two to three months. New ILOM 3.x.x features that are common to all servers supporting ILOM are described in this guide. Specifically, each chapter in the guide documents the new ILOM features and issues for each new ILOM 3.0.x release. This document is written for system administrators who are familiar with networking concepts and basic system management protocols. Note The description in this document is limited to the servers which support ILOM. In the description, "all server platforms" refers to all Fujitsu servers which support ILOM. Depending on the server in use, some of the ILOM functions are not supported. Please confirm the ILOM Supplement manual and the Product Notes of each server in advance. Related Documentation To fully understand the information that is presented in this guide, use this document in conjunction with the documents listed in the following table. The latest versions of all the SPARC Enterprise Series manuals are available at the following Web sites: Global Site xi

12 Japanese Site First read the ILOM 3.0 Concepts Guide to learn about ILOM s features and functionality. To set up a new system supported by ILOM, refer to the ILOM 3.0 Getting Started Guide, where you will find the procedures for connecting to the network, logging in to ILOM for the first time, and configuring a user account or directory service. Then, decide which ILOM interface you want to use to perform other ILOM tasks. You can now refer to the appropriate ILOM 3.0 Procedures Guide for your selected interface. The following table lists the ILOM 3.0 Documentation Collection. TABLE P-1 ILOM 3.0 Documentation Collection Title Content Manual Code Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide Integrated Lights Out Manager (ILOM) 3.0 Getting Started Guide Integrated Lights Out Manager (ILOM) 3.0 Web Interface Procedures Guide Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide Integrated Lights Out Manager (ILOM) 3.0 SNMP and IPMI Procedures Guide Information that describes ILOM features and functionality Information and procedures for network connection, logging in to ILOM for the first time, and configuring a user account or a directory service Information and procedures for accessing ILOM functions using the ILOM web interface Information and procedures for accessing ILOM functions using the ILOM CLI Information and procedures for accessing ILOM functions using SNMP or IPMI management hosts C120-E573 C120-E576 C120-E574 C120-E575 C120-E579 In addition to the ILOM 3.0 Documentation Collection, associated ILOM Supplement documents present ILOM features and tasks that are specific to the server platform you are using. Use the ILOM 3.0 Documentation Collection in conjunction with the ILOM Supplement that comes with your server platform. xii Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes June 2009

13 Text Conventions Typeface * AaBbCc123 AaBbCc123 AaBbCc123 Meaning The names of commands, files, and directories; on-screen computer output What you type, when contrasted with on-screen computer output Book titles, new words or terms, words to be emphasized. Replace command-line variables with real names or values. Examples Edit your.login file. Use ls -a to list all files. % You have mail. % su Password: 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. * The settings on your browser might differ from these settings. If you have any comments or requests regarding this document, or if you find any unclear statements in the document, please state your points specifically on the form at the following URL. For Users in U.S.A., Canada, and Mexico For Users in Other Countries l Preface xiii

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

15 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 and Firmware Compatibility To help you determine system requirements and ILOM firmware compatibility, see the Product Notes for your server. ILOM 3.0 Feature Set Overview The ILOM 3.0 feature set provides common ILOM functionality that applies to all server platforms supporting ILOM. These features are built into the ILOM 3.0 firmware that is installed on the server service processor (SP) and, if applicable, on the chassis monitoring module (CMM). 1

16 Note CMMs are applicable to blade modular systems. CMMs are not applicable to rackmount servers. ILOM 3.0 Firmware on the SP The ILOM 3.0 firmware on the SP provides administrators with full lights-out management for a server. This includes the ability to power cycle the server, set up a network connection, create and manage user accounts and roles, as well as monitor and maintain the server components locally or remotely. Server Specific ILOM Features The ILOM 3.0 SP firmware operates on many server platforms, supporting features that are common to all platforms, as well as other features that are specific to a server. For additional information about the ILOM 3.0 features that are supported specifically for your server, see the ILOM 3.0 Supplement guide that is provided for your server. ILOM 3.0 Firmware on the CMM The ILOM 3.0 firmware on the CMM is configured with an individual IP address assigned either statically or dynamically using DHCP. The CMM acts as a conduit to the server module ILOM configuration, enabling settings such as network addresses and administrative user accounts to be configured or viewed. ILOM on the CMM is the primary point of management for all chassis components and functions in a blade modular system chassis. It provides complete monitoring and management functionality for the components, including server module management, system power management, as well as hot-plug operations of infrastructure components such as power supply modules, fan modules, server modules, and network express modules. In addition, the CMM supports HTTP and CLI "pass-thru" interfaces that provide access to all chassis features through a direct serial port connection or a 10/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

17 CMM Chassis-Level Management ILOM on the CMM offers a tiered management architecture that enables system management of individual components or aggregated management of components at the chassis level. A summary of the CMM s management functions include: Implementation of an IPMI satellite controller, making the chassis environmental sensors visible to the server module s BMC functions Direct environmental and inventory management via CLI, web, SNMP, and IPMI interfaces Firmware management of CMM, network express module (NEM), and server module SPs Pass-through management of server modules and HTTP links along with command-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

18 CMM and Server SP CLI Connection You can use a command-line interface to access ILOM on the CMM or server SP through a network connection, or through a direct terminal connection to the serial port on the CMM or server SP. When the ILOM firmware on the CMM or server SP boots, the login prompt for the CMM or server SP appears, for example: SUNCMMnnnnnnnnnn login: The first string in the CMM login prompt is the default host name. It consists of the 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 consists of the prefix SUNSP and server product serial number. CMM and Server SP Address Space on CLI The following table identifies the CLI address space you can use to interact with ILOM. ILOM Management Component CMM Server SP Host Management Address Space /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 /SYS on blade modular systems. /SP is used to configure the server module SP and for viewing logs and consoles. /SYS is used to provide inventory, environmental, and hardware management at the server module level. /HOST is used to monitor and manage the host operating system. 4 Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes June 2009

19 CMM and Server SP Web Interface Connection You also can access ILOM on the CMM and server SP using a web interface connection. To establish a web interface connection to ILOM, specify the IP address of the CMM or server SP in the web browser. A welcome page appears prompting you to enter a user name and password. CMM ILOM Web Interface The main ILOM web page for the CMM includes a navigation pane that you use to monitor and manage individual components installed in the chassis. The settings you can view or configure are organized in the seven tabs appearing at the top of the page, as shown in the following example. Chapter 1 ILOM 3.0 Feature Set 5

20 Server SP ILOM Web Interface The main ILOM web page for the server SP organizes the settings you can view or configure for that server within the six tabs appearing at the top of the page, as shown in the following example: ILOM 3.0 Version Numbers ILOM 3.0 has implemented a new version numbering scheme to help you identify which version of ILOM you are running on your system. The numbering scheme includes 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 per platform or group of platforms. See your platform Product Notes for details. e - Represents a nano version of ILOM. Nano versions are incremental iterations of a micro version. For example, ILOM a would designate: ILOM 3 as the major version of ILOM ILOM 3.1 as a minor version of ILOM 3 ILOM as the second update version of ILOM 3.1 ILOM as a micro version of ILOM Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes June 2009

21 ILOM a as a nano version of ILOM Related ILOM 3.0 Documentation This guide describes new features and issues that are part of a new ILOM 3.x.x release. Each chapter in this guide documents new ILOM features and issues associated with each new ILOM firmware update. To fully understand the information that is presented in this guide, use this document in conjunction with the documents listed in Related Documentation on page xi. First read the ILOM 3.0 Concepts Guide to learn about ILOM s features and functionality. To set up a new system supported by ILOM, refer to the ILOM 3.0 Getting Started Guide, where you will find the procedures for connecting to the network, logging in to ILOM for the first time, and configuring a user account or directory service. Then, decide which ILOM interface you want to use to perform other ILOM tasks. You can now refer to the appropriate ILOM 3.0 Procedures Guide for your selected interface. For platform-specific ILOM updates, refer to your ILOM Supplement, which presents ILOM features and tasks that are specific to the server platform you are using. The ILOM Supplement is part of the documentation set for your server. Chapter 1 ILOM 3.0 Feature Set 7

22 8 Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes June 2009

23 CHAPTER 2 Updates to the ILOM Firmware This chapter describes the new features and functionality that have been added to the ILOM firmware release. Procedures to implement the new functionality are explained. Known issues, resolved issues, and documentation updates are also described. Topics in the chapter include: New Features for ILOM on page 10 Resolved Issues as of ILOM on page 27 Known Issues as of ILOM on page 31 Documentation Updates and Errata on page 34 9

24 New Features for ILOM There are several new features integrated into the ILOM firmware release. The following table identifies these features and points you to the sections that describe the features. Topics Description Updated CMM chassis management view Enhanced CMM power management metrics Enhanced feature for displaying the history of platform-specific power consumption Enhanced feature to override the boot device settings in BIOS using the ILOM CLI or web interface Updated information for clearing faults from the event log after fixing a faulted component Enhanced web pages with jump links Links Improved Chassis View on page 11 Power Management Metrics on page 12 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 Ability to Override BIOS Host Boot Device on page 19 Configure BIOS Host Boot Device Override Using the CLI on page 19 Configure BIOS Host Boot Device Override Using the Web Interface on page 20 Clear Faults After Replacement of Faulted Component on page 22 View and Clear Faults Using the CLI on page 23 View and Clear Faults Using the Web Interface on page 24 Jump Links Available on ILOM Web Pages on page Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes June 2009

25 Improved Chassis View In the ILOM web interface, the chassis view has been modified to include the following enhancements: The navigation pane on the left side of the screen now shows visible entries only for components that are present and manageable. A Chassis Inventory Table now appears in the main body page of the chassis view. The table provides information about name, part number, and serial number of all manageable components that are present in the chassis. Chapter 2 Updates to the ILOM Firmware 11

26 Power Management Metrics The power management feature enables you to monitor power consumption metrics from the command-line interface (CLI) or web interface. The following power management metrics are common to all servers supporting ILOM: Actual Power Represents consumed power for the rackmount server or chassis system. On a chassis monitoring module (CMM), this is the input power consumed 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 maximum input power that the power supplies are capable of consuming. For chassis systems, this value represents the available amount of power guaranteed to the server module (blade) by the chassis. Permitted Power For rackmount systems, this value represents the maximum input power that the server guarantees it will consume at any instant. For chassis systems, this value represents the maximum power a server module guarantees it will 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 less than 10 watts. Some servers supporting ILOM might provide additional platform-specific power metrics under the /SP/powermgmt/advanced node in the CLI or the Advanced Power Metrics table in the System Monitoring --> Power Management page in the web interface. Each advanced power metric includes a name, a unit, and a value. For platform-specific power management information, see the ILOM Supplement guide that is available for your server. For general information about viewing the power management metrics in the CLI and web interface, see the ILOM 3.0 Documentation Collection. 12 Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes June 2009

27 Power Consumption History ILOM now displays rolling averages of power consumption in 15-, 30-, and 60- second intervals by leveraging ILOM s sensor history capability. Power consumption information is retrieved at a rate determined by the individual platform, which could 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 web interfaces. 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 CLI 1. 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: Chapter 2 Updates to the ILOM Firmware 13

28 ->show /CH/VPS /CH/VPS Targets: history Properties: type = Power Unit ipmi_name = VPS class = Threshold Sensor value = 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 3. To display 15-, 30-, and 60-second rolling power usage average, and to display a choice 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/history /CH/VPS/history Targets: 0 (1 Minute Average, 1 Hour History) 1 (1 Hour Average, 14 Day History) Properties: 15sec_average = sec_average = sec_average = Commands: cd show 14 Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes June 2009

29 4. To display average consumption history by the minute or hour respectively, type the following command with the appropriate target named. In the following 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: ->show /CH/VPS/history/0 /CH/VPS/history/ Targets: list Properties: average = minimum = at Mar 4 08:51:24 maximum = at Mar 4 08:51:23 period = 1 Minute Average depth = 1 Hour History Commands: cd show 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 Chapter 2 Updates to the ILOM Firmware 15

30 From the CMM: ->show /CH/VPS/history/0/list For example: ->show /CH/VPS/history/0/list /CH/VPS/history/0/list Targets: Properties: Mar 4 08:52:23 = Mar 4 08:51:24 = Mar 4 08:50:24 = Mar 4 08:49:24 = Mar 4 08:48:24 = Mar 4 08:47:23 = Commands: cd show View Power Consumption History Using the Web Interface 1. 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 16 Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes June 2009

31 Chapter 2 Updates to the ILOM Firmware 17

32 SP Power History Example 4. To view detailed power history (such as time stamp and power consumed in watts), select any live entry in the Sample Set column. The following figure shows the sample set results of the target /CH/VPS/0. 18 Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes June 2009

33 Enhanced Ability to Override BIOS Host Boot Device You can now use the CLI and web interface to select a host boot device, overriding the boot device order settings in BIOS. This ability gives the CLI and web interface parity with the existing IPMI interface. Now that this feature is available in the CLI and web interface, a user who has logged in to the SP can quickly and easily change this value without having to use IPMItool externally. The primary purpose of the boot device override feature is to allow the administrator to perform a one-time manual override of the server s BIOS boot order settings. This enables the administrator to quickly configure a machine or group of machines 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 the CLI 1. 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 Chapter 2 Updates to the ILOM Firmware 19

34 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 the BIOS settings. Setting to default will also clear any previously chosen selection. pxe Setting the value to pxe means that at the next host boot, the BIOS boot order settings will be temporarily bypassed and instead the host will boot from the network, following the PXE boot specification. disk Setting the value to disk means that at the next host boot, the BIOS boot order settings will be temporarily bypassed and instead the host will boot from the first disk as determined by BIOS. The specific disk chosen depends on configuration. Typically, hosts use this option by default and the host's behavior might not change by selecting this option. diagnostic Setting the value to diagnostic means that at the next host boot, the BIOS boot order settings will be temporarily bypassed and instead the host will boot into the diagnostic partition, if configured. cdrom Setting the value to cdrom means that at the next host boot, the BIOS boot order settings will be temporarily bypassed and instead the host will boot from the attached CD-ROM or DVD device. bios Setting the value to bios means that at the next host boot, the BIOS boot order settings will be temporarily bypassed and instead the host will boot into the BIOS Setup screen. Configure BIOS Host Boot Device Override Using the Web Interface 1. Log in to ILOM. 2. In the web interface page, click Remote Control --> Host Control. The Host Control page appears. 20 Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes June 2009

35 3. In the Host Control page, click the Next Boot Device list box and specify a boot device option. Possible boot device options available: default Setting the value to default means that there is no override to the BIOS settings. Setting to default will also clear any previously chosen selection. pxe Setting the value to pxe means that at the next host boot, the BIOS boot order settings will be temporarily bypassed and instead the host will boot from the network, following the PXE boot specification. disk Setting the value to disk means that at the next host boot, the BIOS boot order settings will be temporarily bypassed and instead the host will boot from the first disk as determined by BIOS. The specific disk chosen depends on configuration. Typically, hosts use this option by default and the host's behavior might not change by selecting this option. diagnostic Setting the value to diagnostic means that at the next host boot, the BIOS boot order settings will be temporarily bypassed and instead the host will boot into the diagnostic partition, if configured. cdrom Setting the value to cdrom means that at the next host boot, the BIOS boot order settings will be temporarily bypassed and instead the host will boot from the attached CD-ROM or DVD device. bios Setting the value to bios means that at the next host boot, the BIOS boot order settings will be temporarily bypassed and instead the host will boot into the BIOS Setup screen. 4. Click Save for your changes to take effect. Chapter 2 Updates to the ILOM Firmware 21

36 Clear Faults After Replacement of Faulted Component The ILOM-based service processor (SP) receives error telemetry about error events that occur within the major system components on the host (CPU, memory, and I/O hub) and the environmental subsytems within the chassis (such as fans, power supplies, and temperature). The components and conditions are then diagnosed as fault events and captured in the ILOM event log. The steps that are necessary to clear a fault are largely dependent on the type of server platform you are using (server module versus rackmount server). For example: ILOM-based faults that occur on a server module are NOT persistent once the server module has been properly prepared for removal and is physically removed from the chassis. Therefore, no service actions are required to clear the fault after the component is physically replaced. The fault message is captured in the ILOM event log for historical purposes. ILOM-based faults that occur on a rackmount server ARE persistent and might require service actions to clear the fault after the component is physically replaced, unless the component is a hot-swappable component (such as a fan or power supply). Hot-swappable components are platform-specific; therefore, refer to the platform documentation for a list of the hot-swappable components. The fault message is captured in the ILOM event log for historical purposes. On a rackmount server, you must manually clear the following faults after physically replacing 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 containing CMM(s) are automatically cleared by the ILOM CMM when the faulted component is replaced. However, if the chassis-level component is not hotserviceable, then the fault needs to be manually cleared from the ILOM CMM. In particular, the CMM automatically clears faults on the following chassis-level components after the faulted components are replaced. CMM fault Fan fault Power supply fault Network express module (NEM) fault PCI express module fault 22 Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes June 2009

37 Note For more information about the ILOM fault management features offered on your system, refer to the ILOM 3.0 Documentation Collection and the documentation 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 CLI 1. 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: ->set component_path clear_fault_action=true Are you sure you want to clear component_path (y/n)? Set clear_fault_action to true y Where component_path is one of the following faulted components: Processor Memory Motherboard Fan Module Power Supply CMM fault Chapter 2 Updates to the ILOM Firmware 23

38 NEM fault PCI card fault For example, to clear a processor fault, you would type the following: ->set /SYS/MB/P0 clear_fault_action=true Are you sure you want to clear /SYS/MB/P0 (y/n)? Set clear_fault_action to true y View and Clear Faults Using the Web Interface 1. 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 the faulted component ID. Additional information about the faulted component appears in a dialog. Note Alternatively, you can view the fault status for a component on the Component Management page. In the Component Management page, select the component 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 status in 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 --> Fault Management tab. b. In the Fault Management page, enable the radio button next to the faulted component, then select Clear Fault. 24 Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes June 2009

39 Jump Links Available on ILOM Web Pages Some ILOM web interface pages that provide multiple sections now include jump links at the top of the web page to improve navigation. Note the information, settings, and controls on these pages are unchanged. Topics Description Links View changes to Active Directory page User Management --> Active Directory on page 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 Accounts page User Management --> User Accounts on page 27 The following figures show ILOM web interface pages in which jump links are now provided for easier navigation within pages. User Management --> Active Directory Chapter 2 Updates to the ILOM Firmware 25

40 User Management -->LDAP/SSL Configuration --> System Management Access -->SNMP 26 Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes June 2009

41 User Management --> User Accounts Resolved Issues as of ILOM This section describes the issues that have been resolved as of ILOM Specific change request (CR) identification numbers and workarounds for the issues are provided, where available. Topics Description ILOM Remote Console resolved issue User management resolved issue SSH host keys resolved issues Alert management known issue Links Alt-Graph Key Functionality on International Keyboards on page 28 Web Interface Does Not Display the Browse Button When Uploading Files on page 28 Newly Generated SSH Keys Are Now Available Immediately Without Requiring SSH Server Restart on page 29 Loading SSH Host Key No Longer Results in Error Message on page 29 Address Using IP Address Is Accepted in Alert Management Rule Query on page 30 Chapter 2 Updates to the ILOM Firmware 27

42 Alt-Graph Key Functionality on International Keyboards When 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 ILOM Remote Console. This Workaround does not depend on a specific version of the Java Development Kit (JDK). However, this Workaround is limited in that it is not possible to send the ALT-GR key directly. To use the Workaround, you must be running a version of ILOM Remote Console that contains the supported short-cut key (ALT-z). 2. Complete Solution: This solution sends the ALT-GR key directly without any special Remote Console menu options or intervention. However, it requires using a more recent version of the JDK. To use the Complete Solution, you must be running 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 is running on a platform. Note Linux and Solaris versions of ILOM 3.x contain both the Workaround and Complete Solution. Windows versions of ILOM 3.x contain the functionality as described for the Complete Solution, but not the Workaround. Web Interface Does Not Display the Browse Button When Uploading Files CR Issue: In earlier versions of ILOM, a configuration page did not display the Browse option 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 28 Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes June 2009

43 When configuring user SSH keys When configuring backup and restore operations Clicking the Upload button to obtain an SSL certificate prompted a new window to appear; however, you were unable to select and upload a file. Update: This issue is fixed in the ILOM release. The Browse option to upload an SSL certificate is now available. Newly Generated SSH Keys Are Now Available Immediately Without Requiring SSH Server Restart CR Issue: When you are generating a new SSH key, you do not need to restart the SSH server for the new key to take effect. The new SSH key will become immediately available for new connections. Update: SSH keys are now available for new connections immediately without a server restart as a ILOM Loading SSH Host Key No Longer Results in Error Message CR Issue: In earlier versions of ILOM, using the load command to upload an SSH host key might result in a set: Command Failed error message, even when the SSH host key was uploaded successfully. This error message no longer appears in ILOM and later versions. Update: This issue is fixed in the ILOM release. Chapter 2 Updates to the ILOM Firmware 29

44 Address Using IP Address Is Accepted in Alert Management Rule Query CR Issue: When using ILOM s alert management feature, previous versions of ILOM required you to use a host name-based address. You can now send an alert using an IP address. Update: A separate check for IP-based addresses has been added to the ILOM release so that if the original validation fails, the system will then check specifically for an with an IP address. 30 Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes June 2009

45 Known Issues as of ILOM This section describes the known issues as of ILOM The following table identifies these known issues and points you to the sections that describe the issues. Topics Description Unexpected BIOS behavior Unexpected behavior when resetting to defaults Hourly timestamp behavior SSH keys are not loaded Links BIOS Upgrade Is Delayed After SP Reboot on page 31 External Serial Port Settings Do Not Reset to Default Value on page 32 Hourly Power Average Timestamp Does Not Account for Increments of Less Than One Hour on page 33 SSH Keys Fail to Restore After a Backup/Restore on page 33 BIOS Upgrade Is Delayed After SP Reboot CR Issue: When you upgrade the SP firmware, you can choose to upgrade the BIOS firmware immediately or to delay the BIOS upgrade until a later time. If you choose to immediately upgrade the BIOS, the SP firmware is upgraded, the host is forced to power off, and the SP reboots. If you choose to delay the BIOS upgrade, the SP firmware is upgraded and the SP reboots. Regardless of your choice, the BIOS is not programmed immediately. Instead, the SP reboots the new 3.x image and waits for the host to power off. The host will be powered off if you chose the immediate BIOS upgrade option and will begin to program 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 is being programmed, there is no indication that the BIOS upgrade is being programmed. If you power on the host while the BIOS is being programmed, the BIOS will become garbled and the host will not boot. The solution is to power off the host, wait two to five minutes for the SP to program the BIOS, then power on the host. Chapter 2 Updates to the ILOM Firmware 31

46 Issue 2: If you chose the delayed BIOS option and do not power off the host, the BIOS will not be upgraded. The host must be powered off for the SP to program the 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 as possible following an SP firmware upgrade, and wait at least five minutes before rebooting the system. External Serial Port Settings Do Not Reset to Default Value CR Issue: The reset_to_defaults command enables a user to reset the ILOM configuration back to the default values. However, external serial port settings are not reset when reset_to_defaults action is performed. Workaround: Use the CLI or web interface to set the external port settings to the desired values before rebooting ILOM. The external serial port settings can be accessed by typing /SP/serial/external in CLI or by selecting Configuration --> Serial Port in the web interface. 32 Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes June 2009

47 Hourly Power Average Timestamp Does Not Account for Increments of Less Than One Hour CR Issue: When logging in to a CMM using the CLI, the hourly power history includes an entry with a timestamp one hour into the future. This entry shows the average power 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 entry with timestamp 2:23 a.m. will be visible and contains the average power from 1:23 a.m. to 1:24 a.m. That entry will continue to be updated until 2:23 a.m., at which point, the hourly power average increment concludes, and the new hourly average timestamp 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/Restore CR Issue: When backing up and restoring an ILOM configuration, RSA and DSA private keys that exist under /SP/services/ssh/keys or /CMM/services/ssh/keys fail to restore. Workaround: When a new key is generated on the SP, it will result in the following message: Warning: the RSA host key for xxx.xxx.xxx.xxx differs from the key for the IP address xxx.xxx.xxx.xxx Offending key for IP in ~/.ssh/known_hosts:216 Matching 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. Chapter 2 Updates to the ILOM Firmware 33

48 Documentation Updates and Errata This section describes errors that have been found in the ILOM 3.0 Documentation Collection. Specific change request (CR) identification numbers and workarounds for the issues are provided, where available. Topics Description Documentation correction for set command targets, properties, and values Documentation update for maximum number of active sessions supported on some SPARC systems Documentation update for a feature that was documented but not yet available on SPARC platforms Documentation correction for downgrading firmware Documentation correction for SSH Key functionality Documentation correction for HTTPS SSL properties Documentation correction for SNMP command to monitor available power Documentation correction for server serial connection to ILOM Documentation correction for supported transfer methods for the Snapshot utility Documentation update for Storage Redirection Documentation update describing exception to a power management rule Links Targets, Properties, and Values for set Command on page 35 Some SPARC Systems Support a Maximum of Five Active Sessions on page 37 Power Policy Not Available for SPARC Systems Using Earlier Version of ILOM on page 37 Updating to a Previous ILOM Version Might Not Complete on page 39 SSH Uses Newly Generated Key Without Restarting the SSH Server on page 39 ILOM HTTPS SSL Properties Are Not Visible in the ILOM Inventory on page 40 SNMP Commands to Monitor Power Are Incorrect on page 40 Rackmount Servers Support Serial Connection to ILOM on page 41 TFTP Is Not a Supported Transfer Method for the Snapshot Utility on page 41 CMM Web Interface Provides Download Links to Storage Redirection Service and Client CLI Tools on page 41 Exception to the Rule That available_power Is Greater Than hwconfig_power on page Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes June 2009

49 Targets, Properties, and Values for set Command Issue: In the Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide, there are incorrect entries for properties, values, and default values that correspond with valid targets in the set command. The following information is correct. Valid Targets Properties Values Default /SP/clients/activedirectory state enabled disabled disabled defaultrole administrator operator a u c r o s (none) dnslocatormode enabled disabled disabled address <ip address> or <DNS name> (none) port <integer between > 0 strictmode enabled disabled disabled timeout <integer> 4 logdetail none high medium low trace none /SP/clients/activedirectory/ cert/ certstatus <string> certificate not present clear_action true (none) issuer <string> (none) load_uri tftp ftp scp (none) serial_number <string> (none) subject <string> (none) valid_from <string> (none) valid_until <string> (none) version <string> (none) /SP/clients/activedirectory/ alternateservers/n where n is 1-5 address port <ip address> or <DNS name> <integer> (none) 0 /SP/clients/activedirectory/ alternateservers/n/cert certstatus <string> certificate not present where n is 1-5 clear_action true (none) issuer <string> (none) load_uri tftp ftp scp (none) serial_number <string> (none) subject <string> (none) valid_from <string> (none) valid_until <string> (none) version <string> (none) Chapter 2 Updates to the ILOM Firmware 35

50 Valid Targets Properties Values Default /SP/clients/ldapssl state enabled disabled disabled defaultrole administrator operator a u c r o s (none) dnslocatormode enabled disabled disabled address <ip address> or <DNS name> (none) port <integer between > 0 strictmode enabled disabled disabled timeout <integer> 4 logdetail none high medium low trace none /SP/clients/ldapssl/cert/ certstatus <string> certificate not present clear_action true (none) issuer <string> (none) load_uri tftp ftp scp (none) serial_number <string> (none) subject <string> (none) valid_from <string> (none) valid_until <string> (none) version <string> (none) /SP/clients/ldapssl/ alternateservers/n/cert where n is 1-5 certstatus clear_action issuer <string> true <string> (none) (none) (none) load_uri tftp ftp scp (none) serial_number <string> (none) subject <string> (none) valid_from <string> (none) valid_until <string> (none) version <string> (none) /SP/clients/ldapssl/customgr oups/n where n is 1-5 name roles <string> administrator operator a u c r o s (none) (none) /SP/clients/ldapssl/ alternateserver/n where n is 1-5 address port <string> <integer> (none) 0 Update: This information will be included in a future release of the ILOM Documentation Collection. 36 Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes June 2009

51 Some SPARC Systems Support a Maximum of Five Active Sessions Issue: In the ILOM 3.0 Documentation Collection, it states that ILOM supports a maximum of 10 active user sessions. This is incorrect for some SPARC systems, which support a maximum of only five user sessions. Update: This information will be included in a future release of the ILOM Documentation Collection. Power Policy Not Available for SPARC Systems Using Earlier Version of ILOM Issue: Power policy is NOT available to SPARC platforms using ILOM 3.0 or ILOM Power policy was incorrectly documented as an available feature on SPARC platforms in the Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide and the Integrated Lights Out Manager (ILOM) 3.0 SNMP and IPMI Procedures Guide. Update: Power policy is now available, on some SPARC platforms, in ILOM In the next release of the ILOM 3.0 Documentation Collection, the CLI and SNMP Procedures Guides will not change, but the following topic for configuring the power policy will be added to the Integrated Lights Out Manager (ILOM) 3.0 Web Interface 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 policy implementation on a specific platform. Note The power policy described in this section might not be implemented on the platform that you are using. See the platform-specific ILOM Supplement or Product Notes for implementation details. You can find the ILOM Supplement and Product Notes within the documentation set for your system. Chapter 2 Updates to the ILOM Firmware 37

52 Follow these steps to configure the power management policy using the web interface: 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. 38 Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes June 2009

53 Updating to a Previous ILOM Version Might Not Complete CR Issue: In the Integrated Lights Out Manager 3.0 Concepts Guide, it states that when you are updating the ILOM firmware to a previous version with the Preserve Configuration 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, the following 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 Preserve Configuration option. When the update is complete and the system reboots, the ILOM default settings will be used. Update: This information will be included in a future release of the ILOM 3.0 Documentation Collection. SSH Uses Newly Generated Key Without Restarting the SSH Server CR Issue: In the Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide, the Integrated Lights Out Manager (ILOM) 3.0 Web Interface Procedures Guide, and the Integrated Lights Out Manager (ILOM) 3.0 SNMP and IPMI Procedures Guide, the documents state that when you are generating a new SSH key, you must restart the SSH server for the new key to take effect. That statement is no longer valid. The new SSH key will become immediately available for new connections. The SSH server does not need to be restarted for the new key to take effect. Update: This information will be included in a future release of the ILOM Documentation Collection. Chapter 2 Updates to the ILOM Firmware 39

54 ILOM HTTPS SSL Properties Are Not Visible in the ILOM Inventory CR Issue: In the Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide, the following properties are listed incorrectly as present in the ILOM inventory. These properties 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 ILOM Documentation Collection. SNMP Commands to Monitor Power Are Incorrect CR Issue: In the Integrated Lights Out Manager (ILOM) 3.0 SNMP and IPMI Procedures Guide, the commands for monitoring power are incorrect. The following commands are correct. To monitor the available power consumption using SNMP, type this command: % snmpget -v2c -cprivate -mall snmp_agent_ipaddress sunhwctrlpowermgmtavailablepower.0 To monitor the hardware configuration maximum power consumption using SNMP, type this command: % snmpget -v2c -cprivate -mall snmp_agent_ipaddress sunhwctrlpowermgmthwconfigpower.0 To monitor the permitted power consumption using SNMP, type this command: % snmpget -v2c -cprivate -mall snmp_agent_ipaddress sunhwctrlpowermgmtpermittedpower.0 40 Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes June 2009

55 Update: This information will be updated in a future release of the ILOM Documentation Collection. Rackmount Servers Support Serial Connection to ILOM CR Issue: In the Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide, it is stated incorrectly in Table 2-1 that rackmount servers do not support a serial connection to ILOM. Rackmount servers do support a serial connection to ILOM. Update: This information will be updated in a future release of the ILOM Documentation Collection. TFTP Is Not a Supported Transfer Method for the Snapshot Utility CR Issue: In the Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide, TFTP is given incorrectly as a supported protocol to use when transferring the Snapshot data to a directory. TFTP is not a supported protocol for Snapshot data transfers. The supported transfer protocols are SFTP and FTP. Update: This information will be updated in a future release of the ILOM Documentation Collection. CMM Web Interface Provides Download Links to Storage Redirection Service and Client CLI Tools CR Issue: In the Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide, it states that the Storage Redirection feature is not supported on a chassis monitoring module (CMM) running ILOM 3.0 firmware. The Storage Redirection CLI feature in ILOM consists of a set of tools (a service and a client) that you run on your machine to connect 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 that redirection is not supported for any CMM, the CMM web interface still provides the Chapter 2 Updates to the ILOM Firmware 41

56 download links to the Storage Redirection service and client CLI tools. Once the service and client tools are downloaded and running on your machine, they can be used for Storage Redirection to a server module running ILOM 3.0. Update: This additional information will be added to a future release of the ILOM Documentation Collection. Exception to the Rule That available_power Is Greater Than hwconfig_power CR Issue: In the Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide, available power is defined as the maximum power that the power supplies in the system can draw from an external source. Typically this number is greater than the hardware configuration maximum. In general, available_power is always greater than hwconfig_power in all rackmount servers supporting ILOM. An exception exists for the blade modular systems where hwconfig_power is greater than available_power. The reason for the exception is because on a chassis system, the maximum power that could be consumed by each server module is included in the hwconfig_power number. However, the chassis guarantees that the maximum power will never be applied to all server modules at the same time (and the allowed maximum is displayed in permitted_power). Update: This information will be updated in a future release of the ILOM Documentation Collection. 42 Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes June 2009

57 CHAPTER 3 Updates to the ILOM Firmware This chapter describes the new features and functionality that have been added to the ILOM firmware release. Procedures to implement the new functionality are explained. Resolved issues, known issues, and documentation updates are also described. Topics in the chapter include: New Features for ILOM on page 44 Resolved Issues as of ILOM on page 66 Known Issues as of ILOM on page 73 Documentation Updates and Errata on page 74 43

58 New Features for ILOM There are several new features integrated into the ILOM release. The following table lists those new features and points you to the sections that describe the features. Topics Description New power management layout and threshold control Updated idle time setting for a CLI session New target added for LDAP/SSL authentication attributes New ability to download SNMP MIBs from ILOM New ability to display user roles that are assigned to a user session Enhanced expanded search mode in Active Directory Enhanced test alert when setting IPMI traps, alerts, or SNMP traps New locking ability for the ILOM Remote Console Links Power Management New Web Layout for the SP on page 45 Power Consumption Thresholds on page 47 Set Timeout Value for a cli Session on page 48 Edit LDAP/SSL Optional User Mapping on page 49 Download SNMP MIBs Directly From ILOM on page 52 View User Roles in Active Session on page 54 View and Configure Expanded Search Mode in Active Directory on page 56 Send Test Alert to Specific Alert Destination on page 59 ILOM Remote Console Computer Lock on page 60 New ILOM SP network ports New ILOM SP Network Ports on page 65 Updated mouse mode setting for remote host KVMS Enhanced Mouse Mode Settings for Remote Host KVMS on page Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes June 2009

59 Power Management New Web Layout for the SP Power Management has been moved to a top level tab for the SP with the following three 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 servers supporting ILOM. Refer to your platform documentation for more information about the availability of power management features and functionality for your server. Chapter 3 Updates to the ILOM Firmware 45

60 Power Management New Web Layout for the CMM Power Management has been moved to a top level tab for the CMM with the following four new sub-level tabs: Allocation Power Configuration settings have moved to this sub-tab. Redundancy Power Policy settings have moved to this sub-tab. History Power consumption history has 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 servers supporting ILOM. Refer to your platform documentation for more information about the availability of power management features and functionality for your server. 46 Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes June 2009

61 Power Consumption Thresholds You can set two thresholds for power consumption, which generate an ILOM event if the threshold is exceeded. This event is logged in the ILOM event log. If alerts are configured, an alert is sent. If SNMP traps are enabled, the event will be delivered via the SUN-HW-TRAP-MIB trap. Before You Begin The Admin (a) role is required to change power consumption configuration variables. The Read Only (o) role is required to view power consumption configuration variables. View and Configure Power Thresholds Using the CLI 1. 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 maximum hwconfig value, which is a variable that is established based on platform requirements. View and Configure Power Thresholds Using the Web Interface 1. 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 maximum hwconfig value, which is a variable that is established based on platform requirements. Chapter 3 Updates to the ILOM Firmware 47

62 Set Timeout Value for a cli Session CR You can now set the amount of time a cli session can remain idle before the session times 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) indicates that the cli session timeout is disabled, so that the cli session will not close regardless of the amount of time the session is idle. Before You Begin The Admin (a) role is required to change the cli timeout configuration variable. The Read Only (o) role is required to view the cli timeout configuration variable. Set Timeout Value Using the CLI 1. 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 For example, to set the timeout value to 60 minutes, type: -> set /SP/cli timeout=60 Set timeout to Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes June 2009

63 Edit LDAP/SSL Optional User Mapping CR LDAP/SSL now enables the use of attributes other than the Distinguished Name (DN) for user credential validation. Previously, it was difficult to define user domains used to authenticate users in unconventional environments where the Distinguished Name (DN) does not reflect the user s login name. A new target, Optional User Mapping, has been added in ILOM to enable the use of alternative attributes for LDAP authentication. For more information about LDAP/SSL, and for definitions of terms used in this enhancement, refer to any of the Procedures Guides (CLI, Web, or SNMP) in the ILOM Documentation Collection at: Before You Begin The User Management (u) role is required to change LDAP/SSL configuration variables. The Read Only (o) role is required to view LDAP/SSL configuration variables. Edit Optional User Mapping in LDAP/SSL Using the CLI 1. 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. Chapter 3 Updates to the ILOM Firmware 49

64 -> 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 Commands: cd set show 2. Use the set command to modify any of the properties. For example: -> set state=enabled Set state to enabled Edit LDAP/SSL Optional User Mapping Using the Web Interface 1. Log in to ILOM. 2. In the web interface page, click User Management --> LDAP/SSL. The LDAP/SSL Management page appears. 50 Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes June 2009

65 3. In the Optional User Mapping field, click the (edit) link that appears next to the word Enabled. The Edit dialog box appears. Chapter 3 Updates to the ILOM Firmware 51

66 4. In the Edit LDAP/SSL Optional User Attribute dialog, modify any of the parameters, then click Save to apply your changes. Download SNMP MIBs Directly From ILOM CR A copy of the SNMP MIBs are now part of the ILOM firmware. This enables you to download the MIBs directly from ILOM rather than being required to retrieve the MIBs 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 from ILOM. 52 Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes June 2009

67 Download SNMP MIBs From ILOM Using the CLI 1. Log in to ILOM. 2. Use the show command to display the SNMP MIBs. For example: -> show /SP/services/snmp/mibs /SP/services/snmp/mibs Targets: Properties: dump_uri = (Cannot show property) Commands: cd dump set show 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 Web Interface 1. 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. Chapter 3 Updates to the ILOM Firmware 53

68 4. Click Download. When prompted, enter a destination in which to save the file. View User Roles in Active Session CR Role information (a u c r o s) is now available for all active sessions in the CLI 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 CLI 1. 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: 54 Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes June 2009

69 -> show sessions/18 /SP/sessions/18 Targets: Properties: username = root role = aucro starttime = Mon Apr 13 06:25: type = web mode = normal Commands: cd show View Roles for Active User Session Using the Web Interface 1. 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. Chapter 3 Updates to the ILOM Firmware 55