Ilom 3.0

Oracle Integrated Lights Out
Manager (ILOM) 3.0
Feature Updates and Release Notes
Part No. 820-7329-16

May 2010, Revision A
Copyright © 2009, 2010, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are
protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy,
reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any
means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report
them to us in writing.
If this is software or related software documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S.
Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS. Programs, software, databases, and related documentation and technical data delivered to U.S. Government
customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and
agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the
restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government
contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500
Oracle Parkway, Redwood City, CA 94065.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for
use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software or
hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to
ensure the safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in
dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. Intel and Intel
Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or
registered trademarks of SPARC International, Inc. UNIX is a registered trademark licensed through X/Open Company, Ltd.
This software or hardware and documentation may provide access to or information on content, products, and services from third parties.
Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content,
products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access
to or use of third-party content, products, or services.
Copyright © 2009, 2010, Oracle et/ou ses affiliés. Tous droits réservés.
Ce logiciel et la documentation qui l’accompagne sont protégés par les lois sur la propriété intellectuelle. Ils sont concédés sous licence et
soumis à des restrictions d’utilisation et de divulgation. Sauf disposition de votre contrat de licence ou de la loi, vous ne pouvez pas copier,
reproduire, traduire, diffuser, modifier, breveter, transmettre, distribuer, exposer, exécuter, publier ou afficher le logiciel, même partiellement,
sous quelque forme et par quelque procédé que ce soit. Par ailleurs, il est interdit de procéder à toute ingénierie inverse du logiciel, de le
désassembler ou de le décompiler, excepté à des fins d’interopérabilité avec des logiciels tiers ou tel que prescrit par la loi.
Les informations fournies dans ce document sont susceptibles de modification sans préavis. Par ailleurs, Oracle Corporation ne garantit pas
qu’elles soient exemptes d’erreurs et vous invite, le cas échéant, à lui en faire part par écrit.
Si ce logiciel, ou la documentation qui l’accompagne, est concédé sous licence au Gouvernement des Etats-Unis, ou à toute entité qui délivre la
licence de ce logiciel ou l’utilise pour le compte du Gouvernement des Etats-Unis, la notice suivante s’applique :
U.S. GOVERNMENT RIGHTS. Programs, software, databases, and related documentation and technical data delivered to U.S. Government
customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and
agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the
restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government
contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500
Oracle Parkway, Redwood City, CA 94065.
Ce logiciel ou matériel a été développé pour un usage général dans le cadre d’applications de gestion des informations. Ce logiciel ou matériel
n’est pas conçu ni n’est destiné à être utilisé dans des applications à risque, notamment dans des applications pouvant causer des dommages
corporels. Si vous utilisez ce logiciel ou matériel dans le cadre d’applications dangereuses, il est de votre responsabilité de prendre toutes les
mesures de secours, de sauvegarde, de redondance et autres mesures nécessaires à son utilisation dans des conditions optimales de sécurité.
Oracle Corporation et ses affiliés déclinent toute responsabilité quant aux dommages causés par l’utilisation de ce logiciel ou matériel pour ce
type d’applications.
Oracle et Java sont des marques déposées d’Oracle Corporation et/ou de ses affiliés.Tout autre nom mentionné peut correspondre à des
marques appartenant à d’autres propriétaires qu’Oracle.
AMD, Opteron, le logo AMD et le logo AMD Opteron sont des marques ou des marques déposées d’Advanced Micro Devices. Intel et Intel
Xeon sont des marques ou des marques déposées d’Intel Corporation. Toutes les marques SPARC sont utilisées sous licence et sont des marques
ou des marques déposées de SPARC International, Inc. UNIX est une marque déposée concédée sous licence par X/Open Company, Ltd.
Please
Recycle
Contents
Using This Documentation xv
1. ILOM 3.0 Feature Set 1

ILOM 3.0 System Requirements and Firmware Compatibility 2
ILOM 3.0 Feature Set Overview 2
ILOM 3.0 Firmware on the SP 2
Server Specific ILOM Features 3
ILOM 3.0 Firmware on the CMM 3
CMM Chassis-Level Management 3
CMM and Server SP CLI Connection 4
CMM and Server SP Address Space on CLI 5
CMM and Server SP Web Interface Connection 5
CMM ILOM Web Interface 6
Server SP ILOM Web Interface 6
ILOM 3.0 Version Numbers 7
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
iii
Power Management Metrics 11
Power Consumption History 12
▼ View Power Consumption History Using the CLI 12
▼ View Power Consumption History Using the Web Interface 15
Enhanced Ability to Override BIOS Host Boot Device 17
▼ Configure BIOS Host Boot Device Override Using the CLI 18
▼ Configure BIOS Host Boot Device Override Using the Web Interface
19
Clear Faults After Replacement of Faulted Component 20
▼ View and Clear Faults Using the CLI 21
▼ View and Clear Faults Using the Web Interface 22
Jump Links Available on ILOM Web Pages 23
User Management --> Active Directory 23
User Management -->LDAP/SSL 24
Configuration --> System Management Access
-->SNMP 24
User Management --> User Accounts 25
Snapshot FRUID Data Set Option for Service 25
▼ Creating a Snapshot Data Collection Using the CLI 25
▼ Creating a Snapshot Data Collection Using the Web Interface 26
Resolved Issues as of ILOM 3.0.3 28
Alt-Graph Key Functionality on International Keyboards 28
Web Interface Does Not Display the Browse Button When Uploading Files
29
Newly Generated SSH Keys Are Now Available Immediately Without
Requiring SSH Server Restart 30
Loading SSH Host Key No Longer Results in Error Message 30
Email Address Using IP Address Is Accepted in Alert Management Rule
Query 30
Known Issues as of ILOM 3.0.3 31
iv Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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 32
SSH Keys Fail to Restore After a Backup/Restore 33
When Using the CLI to Set the Time Zone, Certain Time Zones Do Not
Recalculate the Clock Correctly (SPARC Servers) 34
Documentation Updates and Errata 35
Targets, Properties, and Values for set Command 37
Some SPARC Systems Support a Maximum of Five Active Sessions 39
Power Policy Is Not Available for SPARC Systems Using Earlier Version of
ILOM 39
▼ Configure Power Policy Using the Web Interface 39
Updating to a Previous ILOM Version Might Not Complete 41
SSH Uses Newly Generated Key Without Restarting the SSH Server 41
ILOM HTTPS SSL Properties Are Not Visible in the ILOM Inventory 42
SNMP Commands to Monitor Power Are Incorrect 42
Rackmount Servers Support Serial Connection to ILOM 43
TFTP Is Not a Supported Transfer Method for the Snapshot Utility 43
CMM Web Interface Provides Download Links to Storage Redirection Service
and Client CLI Tools 43
Exception to the Rule That available_power Is Greater Than
hwconfig_power 44

Power Management New Web Layout for the SP 47
Power Consumption Thresholds 47
Before You Begin 48
▼ View and Configure Notification Thresholds Using the CLI 48
Contents v
▼ View and Configure Notification Thresholds Using the Web
Interface 48
Set Timeout Value for a CLI Session 49
Before You Begin 49
▼ Set Timeout Value Using the CLI 49
Edit LDAP/SSL Optional User Mapping 50
Before You Begin 50
▼ Edit Optional User Mapping in LDAP/SSL Using the CLI 50
▼ Edit LDAP/SSL Optional User Mapping Using the Web Interface 51
Download SNMP MIBs Directly From ILOM 53
Before You Begin 53
▼ Download SNMP MIBs From ILOM Using the CLI 54
▼ Download SNMP MIBs From ILOM Using the Web Interface 54
View User Roles in Active Session 55
Before You Begin 55
▼ View Roles for Active User Session Using the CLI 55
▼ View Roles for Active User Session Using the Web Interface 56
View and Configure Expanded Search Mode in Active Directory 57
Before You Begin 57
▼ View and Configure Expanded Search Mode in Active Directory
Using the CLI 57
▼ View and Configure Expanded Search Mode in Active Directory
Using the Web Interface 58
Send Test Email Alert to Specific Alert Destination 60
Before You Begin 60
▼ Send Test Email Alert to Specific Destination Using the CLI 60
▼ Send Test Email Alert to Specific Alert Destination Using the Web
Interface 60
ILOM Remote Console Computer Lock 61
vi Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
Special Considerations When Enabling the ILOM Remote Console Lock
Option 61
▼ Edit the ILOM Remote Console Lock Option Using the CLI 63
Enabled Custom Lock Mode Example 64
▼ Edit the ILOM Remote Console Lock Option Using the Web Interface 65
New ILOM SP Network Ports 66
Enhanced Mouse Mode Settings for Remote Host KVMS 66
Before You Begin 66
▼ Edit Mouse Mode Setting for Remote Host Using the CLI 66
▼ Edit Mouse Mode Setting for Remote Host Using the Web Interface 67
LDAP or RADIUS Commands Do Not Work When Default Role Is Set to
none 68
Difficulty Removing dnslocatorquery Records From Active Directory
Configuration 68
When Using the CLI to Set the Time Zone, Certain Time Zones Do Not
Recalculate the Clock Correctly (x86 Servers) 69
Snapshot Utility Missing Log Files for Debugging 69
ILOM CLI for set /{target}/config dump_uri Does Not Provide
Confirmation Message 70
Role Help Text for Read-Only /SYS Properties Is Incorrect 70
Help Text for Power Management Properties Is Incorrect 70
Help Output Results for <TARGET> <property> <property> Is Confusing
71
Inaccurate Help Text Values for /SP/users/root/ssh/key/1-5 72
ILOM External Serial Port Flow Control Implemented Incorrectly 72
CLI Auto Completion for Read-Only Properties Does Not Work on Sun Fire
X4140, X4240, and X4440 Servers 72
ILOM Remote Console Might Hang on Windows Client When Redirecting a
CD-ROM Image or Floppy Image 73
Contents vii
Unrecoverable ILOM Remote Console Sessions 74
Allowable Number for DNS Retries Is Incorrect 75

Storage Monitoring for HDDs and RAID Controllers 79
Storage Properties Shown for HDDs and RAID Controllers 80
RAID Status Definitions for Physical and Logical Drives 81
View and Monitor Storage Details for HDDs and RAID Controllers 82
▼ Show Property Details in ILOM for HDDs and RAID Controllers
Using the CLI 83
Power Management Features in ILOM 86
Summary of Power Management Features Prior to ILOM 3.0.6 87
New or Enhanced Power Management Features as of ILOM 3.0.6 87
Component Allocation Power Distribution 88
Monitoring Server Power Allocated Components 88
Monitoring CMM Power Allocated Components 90
Component Power Allocation Special Considerations 91
Component Power Allocation CLI and Web Procedures 92
▼ View Server Power Allocations for All Components Using the CLI
93
▼ View Server Component Power Allocations Using the CLI 93
▼ View CMM Power Allocations for All Chassis Components Using the
CLI 94
▼ View CMM Component Power Allocations Using the CLI 94
▼ Configure Permitted Power for Blade Slots Using the CLI 95
▼ View Server Component Power Allocations Using the Web Interface
96
▼ View CMM Component Power Allocations Using the Web Interface
96
viii Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
▼ Configure Permitted Power for Blade Slots in CMM Using the Web
Interface 98
Power Budget 100
Why Use a Power Budget? 100
Server Power Budget Properties 101
Advanced Server Power Budget Features 102
▼ Configure Server Power Budget Properties Using the CLI 104
▼ Configure Server Power Budget Properties Using the Web Interface
105
Power Supply Redundancy for CMM Systems 106
▼ View or Configure CMM Power Supply Redundancy Properties Using the
CLI 107
▼ View or Configure CMM Power Supply Redundancy Properties Using the
Web Interface 108
Platform-Specific CMM Power Metrics 109
Root Factory Default Password Warning Message 110
New ILOM SP Network Port 111
Ability to Send SMTP Test Alert Email Notification 112
Drill-Down Ability to Server Module From CMM After Disabling ssh 113
Ability to Record Power Management Events in Log File 113
Unable to Retrieve Host Power State After Upgrading ILOM Firmware From
2.0 to 3.0 114
Access Page Error Appears After Configuring Unknown Sensor LED Status
When Monitoring System From IPMItool 114
Console Error Appears After Performing Backup and Restore 114
Windows Server 2008 R2 Generates System Event Log Warning Messages
When Power Is Being Limited by ILOM Power Management 115
Serial Port Sharing 115
Contents ix
▼ Switch Serial Port Output Using the CLI 116
▼ Switch Serial Port Output Using the Web Interface 116
5. Updates to ILOM 3.0.8 Firmware 119

New System Summary Information
(Overview Tab) 121
Power Management New Terminology and Web Layout for the Server SP
122
New Web Layout and Terminology for the Server SP 123
Updated Power Allocation and Power Limit Procedures 127
▼ View Server Power Allocation Plan Using the Web Interface 127
▼ Configure Server Power Limit Properties Using the Web Interface
128
New System Banner Message Capability 130
Configuring Banner Messages 132
▼ Configure Banner Messages Using the CLI 132
▼ Configure Banner Messages Using the Web Interface 133
New Storage Monitoring Web Interface 134
RAID Controller Details 134
Disks Attached to RAID Controllers Details 136
RAID Controller Volume Details 138
View and Monitor Storage Details Using the Web Interface 139
▼ View and Monitor RAID Controller Details Using the Web Interface
139
▼ View and Monitor Details for Disks That Are Attached to RAID
Controllers Using the Web Interface 140
▼ View and Monitor RAID Controller Volume Details Using the Web
Interface 140
New WS-Management and CIM Support for Managing Sun Hardware 140
New SP Console History Log Available on x86 Servers 141
x Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
View and Manage SP Console History Log Entries Using the ILOM CLI
141
New TPM Support for SPARC Servers 144
▼ Control TPM State on SPARC Servers Using the CLI 145
▼ Control TPM State on SPARC Server Using the Web Interface 147
Invalid Time Zone Settings in ILOM CLI 148
Snapshot Properties Are Not Persistent After a Reset 148
Storage Redirection Not Supported With 64-bit JRE 149
5-Minute Delay to View Storage Monitoring Information 150
ILOM Version Not Shown When Using SIA to Upgrade ILOM From an Inband
Management Interface 150
SP Management Port - Recommended Practice for Spanning Tree
Parameters 152
Renamed ILOM SNMP and IPMI Procedures Guide to Management Protocols
Reference Guide 152

New NEM Firmware Management Capability for Oracle Modular Chassis
Systems 156
▼ Update NEM Firmware Using the CLI 157
▼ Update NEM Firmware Using the Web Interface 159
New International Keyboard Support for ILOM Remote Console 162
New System Uptime Display in ILOM CLI and Web Interface 163
▼ View System Uptime Using the CLI 163
▼ View System Uptime Using the Web Interface 164
ILOM Remote Console Supports Microsoft Windows 7 and Internet Explorer
8 Clients 164
Contents xi
Unrecoverable ILOM Remote Console Sessions (Fixed) 165
DIMM FRU Data Fields Are Null After Downgrading or Upgrading SP
Firmware Between 3.0.3 and 3.0.9 167
Invalid Help Command (help /SP system_contact=test) Results in
Garbage Output 168
Service Snapshot Utility Unable to Collect SP Data When IE Web Browser
Security Option Is Enabled 168

Power Management Updated Terminology, Web Layout, and CLI Properties
for the CMM 170
New Web Layout and Terminology for the CMM 171
▼ Configure Grant Limit for Blade Slots in CMM Using the Web Interface
174
New CLI Properties and Terminology for the CMM 176
▼ View Blade Slots Granted Power or Reserved Power Using the CLI 177
▼ View Granted Power or Grant Limit For Blade Using the CLI 178
▼ Configure Grant Limit For A Blade Using the CLI 179
Centralized Firmware Upgrade Management Interface for Chassis
Components 180
SAS-2 Zoning Manager Feature Available in ILOM for Chassis Modular
Systems 180
Ability to Change CLI Prompt on CMM to Differentiate Between CMM and
Server Module (Blade) 180
Resolved Issue as of ILOM 3.0.10 181
Invalid Help Command (help /SP system_contact=test) Results in
Garbage Output 181
IPMItool sunoem CLI Might Be Denied If All Session Slots Are Busy 182
xii Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
DVD Redirection From Solaris Client to RHEL Host Requires Manual
Mount 183
Storage Redirection CLI Service Requires 32-bit JDK to Successfully Start 184
ILOM Remote Console Requires 32-bit JDK to Successfully Launch 186
ILOM Web Interface Unable to Connect to SP When Using Internet Explorer
6 188
force Command Omitted from IPMI CLI Command Documentation 189
BIOS Default Settings Loaded After Updating SP Firmware 190
Update Storage Redirection Content to Include 32-bit JDK File Requirement
190
Update ILOM Remote Console Content to Include 32-bit JDK File
Requirement 191
Contents xiii
xiv Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
Using This Documentation
The feature updates and release notes guide describes enhancements that have been
made to Oracle 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 rackmount servers and server modules (blades)
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.
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. These
documents are available online at:
http://docs.sun.com/app/docs/prod/int.lights.mgr30#hic
The following table lists the ILOM 3.0 Documentation Collection
Note – Documentation Collection, and the documents comprising the collection

were referred to as Sun Integrated Lights Out Manager (ILOM) 3.0 guides. The
document titles will change at the next release of the Oracle ILOM 3.0
Documentation Collection.
xv
.
TABLE P-1 ILOM 3.0 Documentation Collection
Title Content Part Number Format
Oracle Integrated Lights Out Information that describes 820-6410 PDF

Manager (ILOM) 3.0 Concepts ILOM features and HTML
Guide functionality
Oracle Integrated Lights Out Information and procedures 820-5523 PDF
Manager (ILOM) 3.0 Getting for network connection, HTML
Started Guide logging in to ILOM for the first
time, and configuring a user
account or a directory service
Manager (ILOM) 3.0 Web for accessing ILOM functions HTML
Interface Procedures Guide using the ILOM web interface
Manager (ILOM) 3.0 CLI for accessing ILOM functions HTML
Procedures Guide using the ILOM CLI
Manager (ILOM) 3.0 for accessing ILOM functions HTML
Management Protocols using SNMP, IPMI, or
Reference Guide* WS-Man and CIM
Manager (ILOM) for accessing CMM specific HTML
CMM Administration Guide ILOM functions.
for Sun Blade 6000 and Sun
Blade 6048 Modular Systems
Oracle Integrated Lights Out Platform-specific ILOM See the platform PDF
(ILOM) 3.0 Manager supplement document that documentation HTML
Supplement identifies the support for collection for
common or platform-specific your server
features in ILOM 3.0
* As of ILOM 3.0.8, the procedures guide for SNMP and IPMI was renamed to Oracle Integrated
Lights Out Manager (ILOM) 3.0 Management Protocols Reference Guide.
Documentation, Support, and Training

■ Documentation: http://docs.sun.com/
■ Support: http://www.sun.com/support/
xvi Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
■ Training: http://www.sun.com/training/
Documentation Comments
Submit comments about this document by clicking the Feedback[+] link at
http://docs.sun.com. :
Please include the title and part number of your document with your feedback:
Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes,
part number 820-7329-16.
Using This Documentation xvii

xviii Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
CHAPTER 1
ILOM 3.0 Feature Set
This chapter includes the following information about the Oracle ILOM 3.0 feature
set:
■ “ILOM 3.0 System Requirements and Firmware Compatibility” on page 2
■ “ILOM 3.0 Feature Set Overview” on page 2
■ “ILOM 3.0 Firmware on the SP” on page 2
■ “ILOM 3.0 Firmware on the CMM” on page 3
■ “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 7
■ “Related ILOM 3.0 Documentation” on page 7
1
ILOM 3.0 System Requirements and
Firmware Compatibility
To determine the system requirements and ILOM firmware compatibility for your
server, as well as download the latest version of ILOM, go to the following site:
http://www.sun.com/systemmanagement/ilom_platforms.jsp
ILOM 3.0 Feature Set Overview

The Oracle ILOM 3.0 feature set provides common ILOM functionality that applies
to all Oracle Sun Blade Modular Systems and rackmount servers. 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).
Note – CMMs are applicable to Oracle Sun Blade Modular Systems. CMMs are not
applicable to Oracle 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 an Oracle 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.
2 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
Server Specific ILOM Features
The ILOM 3.0 SP firmware operates on many Oracle server platforms, supporting
features that are common to all platforms, as well as other features that are specific
to an Oracle 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 Sun 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-through" 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.
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
Chapter 1 ILOM 3.0 Feature Set 3

■ Access to the following components:
■ Chassis
■ Power supplies
■ Fans
■ Network express modules (NEMs)
■ Server module SPs
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 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 /SYS
on Sun Blade Modular Systems.
Server SP • /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 • /HOST is used to monitor and manage the host operating system.
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 six tabs appearing at the top of the
page, as shown in the following example.
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 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 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 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 xv. These documents are available online at:
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 2
Updates to the ILOM 3.0.3 Firmware
This chapter describes the new features and functionality that have been added to
the Oracle ILOM 3.0.3 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 3.0.3” on page 10
■ “Resolved Issues as of ILOM 3.0.3” on page 28
■ “Known Issues as of ILOM 3.0.3” on page 31
■ “Documentation Updates and Errata” on page 35
9
New Features for ILOM 3.0.3
There are several new features integrated into the Oracle ILOM 3.0.3 firmware
release. The following table identifies these features and points you to the sections
that describe the features.
Topics
Description Links
Updated CMM chassis management • “Improved Chassis View” on page 11

view
Enhanced CMM power management • “Power Management Metrics” on page 11
metrics
Enhanced feature for displaying the • “Power Consumption History” on page 12
history of platform-specific power
consumption
Enhanced feature to override the • “Enhanced Ability to Override BIOS Host Boot
boot device settings in BIOS using Device” on page 17
the ILOM CLI or web interface • “Configure BIOS Host Boot Device Override
Using the CLI” on page 18
• “Configure BIOS Host Boot Device Override
Using the Web Interface” on page 19
Updated information for clearing • “Clear Faults After Replacement of Faulted
faults from the event log after fixing a Component” on page 20
faulted component • “View and Clear Faults Using the CLI” on
page 21
• “View and Clear Faults Using the Web Interface”
on page 22
Enhanced web pages with jump links • “Jump Links Available on ILOM Web Pages” on
page 23
New data collection options for • “Snapshot FRUID Data Set Option for Service”
Snapshot Utility on page 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.
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 Sun servers:
■ 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.
Chapter 2 Updates to the ILOM 3.0.3 Firmware 11

■ 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 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 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.
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

■ The 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:
->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
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:
->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 = 1210.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 the
following example, average per minute is selected.
->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 = 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
5. To display sample set details such as time stamp and power consumed in watts,
type:
->show /SYS/VPS/history/0/list
■ 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 = 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
▼ 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

■ 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.
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
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
from the attached CD-ROM or DVD device.
■ bios – Setting the value to bios means that at the next host boot, the BIOS
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.
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
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
from the attached CD-ROM or DVD device.
■ bios – Setting the value to bios means that at the next host boot, the BIOS
into the BIOS Setup screen.
4. Click Save for your changes to take effect.
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 subsystem 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 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-level
components 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 on
your system, refer to the ILOM 3.0 Documentation Collection and the
documentation provided with your Oracle 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)? y
Set ’clear_fault_action’ to ’true’
Where component_path is one of the following faulted components:

■ Processor
■ Memory
■ Motherboard
■ Fan Module
■ Power Supply
■ CMM
■ NEM
■ PCI card
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)? y
Set ’clear_fault_action’ to ’true’
▼ 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.
Jump Links Available on ILOM Web Pages

Some 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 the
information, settings, and controls on these pages are unchanged
The following figures show ILOM web interface pages in which jump links are now
provided for easier navigation within pages.
User Management --> Active Directory

User Management -->LDAP/SSL
Configuration --> System Management Access

-->SNMP
User Management --> User Accounts
Snapshot FRUID Data Set Option for Service

As of ILOM 3.0.3, a FRUID data set option is available from the Snapshot utility.
Specifically, this option enables Service personnel to analyze data in a binary format
about field-replaceable hardware installed on a server. This FRUID option is not for
customer use, unless Service personnel instructs the customer to use this option.
Caution – The purpose of the ILOM Service Snapshot utility is to collect data for
use by Service personnel to diagnose system problems. Customers should not run
the Snapshot utility unless requested to do so by Service personnel.
The following ILOM CLI and web interface procedures for using the Snapshot utility
have been updated to include information about the new FRUID data set option.
■ “Creating a Snapshot Data Collection Using the CLI” on page 25
■ “Creating a Snapshot Data Collection Using the Web Interface” on page 26
Before You Begin

■ To collect SP data using the Service Snapshot utility, you need the Admin(a)
role enabled.
▼ Creating a Snapshot Data Collection Using the CLI

1. Log in to the ILOM CLI.
2. Type the following commands:

->set /SP/diag/snapshot dataset=data
->set /SP/diag/snapshot dump_uri=URI

Where data and URI are one of the following:
Variable Options Description
data Normal Requests ILOM to collect operating system and

system hardware information.
FRUID Requests ILOM to collect information about FRUs
currently configured on your server in addition to
the data collected by the "Normal" option.
Full Requests ILOM to collect all data about the server.
Selecting Full might reset the system.
• normal- Specifies the collection of only the log files from the
logonly respective data set option.
• fruid-logonly
• full-logonly
URI Any valid Specifies the URI of the target directory. The URI
target directory format is as follows:
location • protocol://username:password@host/directory
Where protocol can be one of these transfer methods:
SFTP and FTP.
For example, to store the snapshot information in the
directory named data on the host, define the URI as
follows:
• ftp://joe:mypasswd@host_ip_address/data
The directory data is relative to the user’s login, so
the directory would probably be /home/joe/data
▼ Creating a Snapshot Data Collection Using the Web

Interface
1. Log in to the ILOM web interface.
2. In the ILOM web interface, select the Maintenance --> Snapshot tabs.
The Snapshot Utility page appears.
3. In the Snapshot Utility page, select the desired Data Set: Normal, FRUID, Full,
or Custom.
A description of these options follow.
Data Set Options Description
Normal Requests ILOM to collect operating system and system hardware

information.
FRUID Requests ILOM to collect information about FRUs currently configured
on your server in addition to the data collected by the "Normal" data set
option.
Full Requests ILOM to collect all data about the server.
Selecting Full might reset the system.
Custom Enables you to specify one or more of the following data sets to be
collected by ILOM:
• ILOM Data
• Hardware Data
• Basic OS Data
• Diagnostic Data
• FRUID Data
4. Specify one or more of the following output options:

■ Collect only log files from data set. Enable this option if you want to collect
log file information only and not information about normal files or commands.
■ Encrypt output file. Enable this option if you want to encrypt the output file.
5. Specify a method you want to use to transfer the output file (Browser, SFTP, or
FTP).
6. Click Run and specify where to save the file, then click OK.

Resolved Issues as of ILOM 3.0.3
This section describes the issues that have been resolved as of ILOM 3.0.3. Specific
change request (CR) identification numbers and workarounds for the issues are
provided, where available.
Topics
Description Links
ILOM Remote Console resolved issue • “Alt-Graph Key Functionality on International

Keyboards” on page 28
User management resolved issue • “Web Interface Does Not Display the Browse
Button When Uploading Files” on page 29
SSH host keys resolved issues • “Newly Generated SSH Keys Are Now Available
Immediately Without Requiring SSH Server
Restart” on page 30
• “Loading SSH Host Key No Longer Results in
Error Message” on page 30
Alert management known issue • “Email Address Using IP Address Is Accepted in
Alert Management Rule Query” on page 30
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 6787083
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
■ 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 3.0.3 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 6781487
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 3.0.3.
Loading SSH Host Key No Longer Results in

Error Message
CR 6776200
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
3.0.3 and later versions.
Update: This issue is fixed in the ILOM 3.0.3 release.
Email Address Using IP Address Is Accepted in

Alert Management Rule Query
CR 6776214
Issue: When using ILOM’s alert management feature, previous versions of ILOM
required you to use a host name-based email address. You can now send an email
alert using an IP address.
Update: A separate check for IP-based email addresses has been added to the ILOM
3.0.3 release so that if the original validation fails, the system will then check
specifically for an email with an IP address.
Known Issues as of ILOM 3.0.3
This section describes the known issues as of ILOM 3.0.3. The following table
identifies the known issues and points you to the sections that describe the issues.
Specific change request (CR) numbers and workarounds or updates for the issues
are provided, where available.
Topics
Description Links
Unexpected BIOS behavior • “BIOS Upgrade Is Delayed After SP Reboot” on

page 31
Unexpected behavior when resetting • “External Serial Port Settings Do Not Reset to
to defaults Default Value” on page 32
Hourly timestamp behavior • “Hourly Power Average Timestamp Does Not
Account for Increments of Less Than One Hour”
on page 32
SSH keys are not loaded • “SSH Keys Fail to Restore After a
Backup/Restore” on page 33
BIOS Upgrade Is Delayed After SP Reboot

CR 6813514
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.
■ 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 6676339
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 the CLI or by selecting
Configuration --> Serial Port in the web interface.
Hourly Power Average Timestamp Does Not

Account for Increments of Less Than One Hour
CR 6803961
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.
Workaround: None.
The power average timestamp is not a "rolling average" of the last minute or hour.
Instead, ILOM selects a starting point in time (call it time 0). At 60 seconds, ILOM
records the first minute average. For the next 59 seconds there would be no change,
then at time 120, ILOM records the second minute average. The last minute average
is the average of the most recent minute, and not the average of the last minute the
sensor was readable.
For the hour average, no samples are taken until time 3600 when the first one-hour
average is recorded. ILOM records the second hour average at time 7200.
The last 60 one-minute averages will not equal the last one-hour average, unless you
compare it with the exact correct time when the most recent hourly average was
stored.
Note that the hourly minimum and maximum average can have a later timestamp
than the minute averages. This occurs when ILOM doesn’t record data, which only
happens if the sensor is no longer readable (power has been turned off, or has
dropped too low to measure). In this instance, ILOM records "no data" while the
sensor is unreadable to ensure that the historical data is not lost.
SSH Keys Fail to Restore After a Backup/Restore

CR 6808138
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.

This section describes the issues that have been resolved in the ILOM 3.0.3 release.
Specific change request (CR) identification numbers and workarounds for the issues
Topics
Description Links
System clock setting resolved issue • “When Using the CLI to Set the Time Zone,
for SPARC servers Certain Time Zones Do Not Recalculate the
Clock Correctly (SPARC Servers)” on page 34
When Using the CLI to Set the Time Zone, Certain

Time Zones Do Not Recalculate the Clock
Correctly (SPARC Servers)
CR 6798875
Issue: When using the CLI to set the time zone, some time zones either do not
recalculate the clock correctly or update the time zone setting on the clock.
Update: As of ILOM 3.0.3.20b this issue has been fixed for SPARC servers.
You must use valid global time zone nomenclature to set the time zone to recalculate
the clock correctly. You can find a list of the valid global time zone nomenclature on
the Internet, for example, at:
http://en.wikipedia.org/wiki/List_of_zoneinfo_time_zones
Examples:
■ To set the SP clock time zone property value to the US standard eastern zone, you
would type:
-> set /SP/clock/ timezone=America/New_York
or
■ To set the SP clock time zone property value to the US central time zone, you
would type:
-> set /SP/clock/ timezone=America/Chicago
Documentation Updates and Errata
This section describes errors that have been found in the Oracle ILOM 3.0
Documentation Collection. Specific change request (CR) identification numbers and
workarounds for the issues are provided, where available.

Topics
Description Links
Documentation correction for set • “Targets, Properties, and Values for set
command targets, properties, and Command” on page 37
values
Documentation update for maximum • “Some SPARC Systems Support a Maximum of
number of active sessions supported Five Active Sessions” on page 39
on some SPARC systems
Documentation update for a feature • “Power Policy Is Not Available for SPARC
that was documented but not yet Systems Using Earlier Version of ILOM” on
available on SPARC platforms page 39
Documentation correction for • “Updating to a Previous ILOM Version Might
downgrading firmware Not Complete” on page 41
Documentation correction for SSH • “SSH Uses Newly Generated Key Without
Key functionality Restarting the SSH Server” on page 41
Documentation correction for HTTPS • “ILOM HTTPS SSL Properties Are Not Visible in
SSL properties the ILOM Inventory” on page 42
Documentation correction for SNMP • “SNMP Commands to Monitor Power Are
command to monitor available power Incorrect” on page 42
Documentation correction for server • “Rackmount Servers Support Serial Connection
serial connection to ILOM to ILOM” on page 43

Topics
Description Links
Documentation correction for • “TFTP Is Not a Supported Transfer Method for

supported transfer methods for the the Snapshot Utility” on page 43
Snapshot utility
Documentation update for Storage • “CMM Web Interface Provides Download Links
Redirection to Storage Redirection Service and Client CLI
Tools” on page 43
Documentation update describing • “Exception to the Rule That available_power
exception to a power management Is Greater Than hwconfig_power” on page 44
rule
Targets, Properties, and Values for set Command
Issue: In the Oracle Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide
(820-6412-10), 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 | (none)
c| r | o | s
dnslocatormode enabled | disabled disabled
address <ip address> or <DNS name> (none)
port <integer between 0-65535> 0
strictmode enabled | disabled disabled
timeout <integer> 4
logdetail none | high | medium | low | none
trace
/SP/clients/activedirectory/ certstatus <string> certificate not
cert/ 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/ address <ip address> or <DNS name> (none)
alternateservers/n port <integer> 0
where n is 1-5
/SP/clients/activedirectory/ certstatus <string> certificate not
alternateservers/n/cert present
where n is 1-5 clear_action true (none)

Valid Targets Properties Values Default
/SP/clients/ldapssl state enabled | disabled disabled

defaultrole administrator | operator | a| u | (none)
c| r | o | s
dnslocatormode enabled | disabled disabled
address <ip address> or <DNS name> (none)
port <integer between 0-65535> 0
strictmode enabled | disabled disabled
timeout <integer> 4
logdetail none | high | medium | low | none
trace
/SP/clients/ldapssl/cert/ certstatus <string> certificate not
present
clear_action true (none)
/SP/clients/ldapssl/ certstatus <string> (none)
alternateservers/n/cert clear_action true (none)
where n is 1-5 issuer <string> (none)
/SP/clients/ldapssl/customgr name <string> (none)
oups/n roles administrator | operator | a | u|
where n is 1-5 c|r|o|s (none)
/SP/clients/ldapssl/ address <string> (none)
alternateserver/n port <integer> 0
where n is 1-5
Update: This information will be included in a future release of the Oracle ILOM
Some SPARC Systems Support a Maximum of
Five Active Sessions
Issue: In the Oracle 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.
Power Policy Is 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
3.0.2.
Power policy was incorrectly documented as an available feature on SPARC

platforms in the Oracle Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide
(820-6412-10) and the Oracle Integrated Lights Out Manager (ILOM) 3.0 Management
Protocols Reference Guide (820-6413).
Update: Power policy is now available, on some SPARC platforms, in ILOM 3.0.3.
In a future release of the ILOM 3.0 Documentation Collection, the following topic for
configuring the power policy will be added to the Oracle 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.

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.
Updating to a Previous ILOM Version Might Not
Complete
CR 6808009
Issue: In the Oracle Integrated Lights Out Manager 3.0 Concepts Guide (820-6410-10), 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 Oracle ILOM 3.0
SSH Uses Newly Generated Key Without

Restarting the SSH Server
CR 6781487
(820-6412-10), the Oracle Integrated Lights Out Manager (ILOM) Web Interface
Procedures Guide (820-6411-10), and the Oracle Integrated Lights Out Manager (ILOM)
3.0 Management Protocols Reference Guide (820-6413), 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.

ILOM HTTPS SSL Properties Are Not Visible in
the ILOM Inventory
CR 6749651
(820-6412-10), 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 Oracle ILOM
SNMP Commands to Monitor Power Are

Incorrect
CR 6766948
Issue: In the Oracle Integrated Lights Out Manager (ILOM) 3.0 Management Protocols
Reference Guide (820-6413), 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:

sunHwCtrlPowerMgmtHWConfigPower.0
● To monitor the permitted power consumption using SNMP, type this

command:

sunHwCtrlPowerMgmtPermittedPower.0
Rackmount Servers Support Serial Connection to

ILOM
CR 6792940
Issue: In the Oracle Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide (820-
6410-10), 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.
TFTP Is Not a Supported Transfer Method for the

Snapshot Utility
CR 6792940
(820-6412-10), 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.
CMM Web Interface Provides Download Links to

Storage Redirection Service and Client CLI Tools
CR 6793269
Issue: In the Oracle Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide (820-
6410-10), 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 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
Exception to the Rule That available_power Is

Greater Than hwconfig_power
CR 6802142
Issue: In the Sun Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide (820-6410-
10), 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 Oracle rackmount servers. An exception exists
for the Oracle 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

CHAPTER 3

45
There are several new features integrated into the ILOM 3.0.4 release. The following
table lists those new features and points you to the sections that describe the
features.
Topics
Description Links
New power management layout and • “Power Management New Web Layout for the
threshold control SP” on page 47
Updated idle time setting for a CLI • “Set Timeout Value for a CLI Session” on page 49
session
New target added for LDAP/SSL • “Edit LDAP/SSL Optional User Mapping” on
authentication attributes page 50
New ability to download SNMP • “Download SNMP MIBs Directly From ILOM”
MIBs from ILOM on page 53
New ability to display user roles that • “View User Roles in Active Session” on page 55
are assigned to a user session
Enhanced expanded search mode in • “View and Configure Expanded Search Mode in
Active Directory Active Directory” on page 57
Enhanced test alert when setting • “Send Test Email Alert to Specific Alert
IPMI traps, Email alerts, or SNMP Destination” on page 60
traps
New locking ability for the Sun • “ILOM Remote Console Computer Lock” on
ILOM Remote Console page 61
New ILOM SP network ports • “New ILOM SP Network Ports” on page 66
Updated mouse mode setting for • “Enhanced Mouse Mode Settings for Remote
remote host KVMS Host KVMS” on page 66
Power Management New Web Layout for the SP
Power Management has been moved to a top level tab for the SP with the following
two new second level tabs:
■ Consumption– The power configuration settings have moved to the Power
Management -- > Consumption tab.
■ History – The power consumption history information has moved to the Power
Management -- > History tab.
Note – Some power management features might not be available on all Oracle
servers. Refer to your platform ILOM Supplement documentation for more
information about the availability of power management features and functionality
for your server.
FIGURE 3-1 Updated Power Management --> Consumption tab
Power Consumption Thresholds

You can set two notification thresholds for power consumption, which generate
ILOM events if the thresholds are exceeded. These events are logged in the ILOM
event log. If email alerts are configured, an email 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.
▼ View and Configure Notification 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 notification thresholds, type:

-> set threshold1|2=n
Where n represents watts.
Note – Setting the notification threshold value to 0 will disable the notification
threshold option.
▼ View and Configure Notification Thresholds Using the

Web Interface
1. Log in to ILOM.
2. In the web interface page, click Power Management --> Consumption.
The Power Consumption page appears.
3. In the Power Consumption page, do the following:
a. In the Notification Threshold field, select the Enabled check box.
b. Based on your platform requirements, specify a notification threshold value

in the Watts text box.
c. Click Save to apply these changes.
Set Timeout Value for a CLI Session
CR 6280346
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 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 Mapping
CR 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 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 3.0.4 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.
-> 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.

3. In the Optional User Mapping field, click the (edit) link that appears next to
the word “Enabled.”
The Edit dialog box appears.
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 6691452
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 sun.com 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.

▼ 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 are 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.
4. Click Download, enter the destination to save the file, then click Save.
View User Roles in Active Session

CR 6714015
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:

-> 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 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 page appears.
3. In the Active Session table, view the roles associated with each user session.
View and Configure Expanded Search Mode in
Active Directory
CR 6806991
In Active Directory, you can enable or disable an expanded search mode to control
the search for user entries. The default Active Directory functionality is intentionally
restrictive to ensure proper security. Search criteria have been expanded to
accommodate specific customer environments.
The expanded search mode is disabled by default, which means the

userPrincipleName is expected to have a fully qualified domain name (FQDN)
suffix. When expanded search mode is enabled, different searches are attempted if
the more specific userPrincipleName search does not immediately succeed.
Before You Begin

■ The User Management (u) role is required to configure Active Directory
configuration variables.
■ The Read Only (o) role is required to view Active Direction configuration
variables.
▼ View and Configure Expanded Search Mode in Active

Directory Using the CLI
1. Log in to ILOM.
2. To view the expanded search mode in Active Directory, type the following
command:
-> show /SP/clients/activedirectory
The following sample output appears.
-> show /SP/clients/activedirectory
/SP/clients/activedirectory
Targets:
admingroups
alternateservers
cert
customgroups
dnslocatorqueries
opergroups
userdomains

Properties:
address = 10.8.123.45
defaultrole = (none)
dnslocatormode = disabled
expsearchmode = disabled
logdetail = none
port = 0
state = enabled
strictcertmode = disabled
timeout = 4
Commands:
cd
set
show
3. To enable the expanded search mode in Active Directory, type the following
command:
-> set /SP/clients/activedirectory expsearchmode=enabled
For example:
-> set /SP/clients/activedirectory expsearchmode=enabled

Set 'expsearchmode' to 'enabled'
▼ View and Configure Expanded Search Mode in Active

Directory Using the Web Interface
1. Log in to ILOM.
2. In the web interface page, click User Management --> Active Directory.
The Active Directory Management page appears.
3. In the Expanded Search Mode field, select the Enabled box to enable this
option or clear the Enabled box to disable this option.
4. Click Save to apply your changes.

Send Test Email Alert to Specific Alert Destination
CR 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 specific
destination.
▼ Send Test Email Alert to Specific Destination Using the

CLI
1. 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 Destination

Using the Web Interface
1. 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 email
alert:
a. Select the radio button of the alert rule.
b. Click the Test Rule button to send a text email alert to the alert rule
destination.
ILOM Remote Console Computer Lock
The Lock feature available for the ILOM Remote Console enhances your system
security by enabling you to lock your computer when terminating a ILOM Remote
Console session. Specifically, the lock behavior takes place either when you
terminate an ILOM Remote Console session or when the managed network
connection to the server is lost.
If you are running a Windows operating system on your host, you can enable the
computer lock feature in ILOM by selecting Windows as your option. The Windows
lock mode option works in conjunction with the standard Windows keyboard
shortcut 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 execute
the computer lock behavior when the ILOM Remote Console terminates by
implementing the custom lock mode feature in ILOM.
The custom lock mode feature in ILOM enables you to execute any system behavior
that is tied to a predefined keyboard shortcut on your host operating system. To
execute a custom keyboard shortcut behavior in ILOM, you must first define the
behavior you want to take place on your host operating system with a keyboard
shortcut. Then, to execute this behavior when the ILOM Remote Console terminates,
you must specify the OS keyboard shortcut parameters in the custom KVMS lock
mode feature in ILOM.
Special Considerations When Enabling the ILOM Remote

Console Lock Option
Review the following special considerations in TABLE 3-1 prior to enabling the KVMS
lock mode option in ILOM.

TABLE 3-1 Special Considerations When Enabling the Remote Console Lock Option
Special Consideration Description
Console user role is To enable the ILOM Remote Console Lock option in ILOM, you
required to set lock must have Console (c) role privileges associated with your user
option. account.
For more information about setting up a user account in ILOM
with Console privileges, see the User Management section in the
ILOM 3.0 Documentation Collection.
A predefined Prior to enabling a custom keyboard shortcut in ILOM for when
keyboard shortcut the ILOM Remote Console connection terminates, you must first
on the OS is define the keyboard shortcut behavior on your host operating
required to execute system.
the custom lock For instructions for creating a keyboard shortcut on your host
mode feature. operating system, see the documentation supplied with your
operating system.
The custom lock When you specify the custom lock mode feature in ILOM, you can
mode feature can be specify up to four modifiers and one key. A list of supported
defined with up to modifiers and keys that you can use to match your predefined OS
four modifiers and keyboard shortcut appear in both the CLI KVMS help and the
one key. web interface KVMS page.
Lock behavior when If more than one ILOM Remote Console session is opened to the
running multiple same SP, the Windows lock or custom keyboard shortcut behavior
ILOM Remote configured in ILOM will only take place when you close the last
Console Sessions. SP ILOM Remote Console session.
▼ Edit the ILOM Remote Console Lock Option
Using the CLI
1. Log in to the ILOM SP CLI.
Note – Alternatively, you can log in to the ILOM CMM CLI then navigate to the SP
target where you want to enable or disable the KVMS lock option for the ILOM
Remote Console.
2. To view all the possible properties associated with the management of the SP
KVMS services, type:
-> help /SP/services/kvms
The following sample output appears:
/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

3. Perform any of the following tasks using either the cd, set, or show commands
to manage the SP KVMS target properties.
Task Instructions
Navigate to the • To navigate to the KVMS target, type the following command:
KVMS target. -> cd /SP/services/kvms
Note - You must navigate to the KVMS target prior to enabling or
disabling the KVMS lock mode options.
Display the • To display the KVMS lock mode properties, type the following
KVMS lock command:
mode -> show
properties. The target, properties, and commands that are associated with the
management of the SP KVMS service appear.
Disable the • To disable the ILOM Remote Console lock mode feature, type the
ILOM Remote following command:
Console lock -> set lockmode=disabled
mode feature.
Enable the • To enable the standard lock mode feature on a Windows system, type
standard the following command:
Windows host -> set lockmode=windows
lock mode
feature.
Enable the • To enable the custom lock mode feature on a Linux, Solaris, or
custom host Windows system, type following commands:
lock mode -> set lockmode=custom
feature. -> 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 a
comma.
Enabled Custom Lock Mode Example
In this example, you have defined, in your host OS, the following custom keyboard
shortcut sequence to log you off the operating system:
<shift><control><backspace>
To implement the above custom keyboard shortcut sequence while exiting a Remote
Console session, the following KVMS properties would be set in the ILOM CLI:
/SP/services/kvms
Targets:
Properties:
custom_lock_key = backspace
custom_lock_modifiers = l_shift, l_ctrl
lockmode = custom
mousemode = absolute
servicestate = enabled
▼ Edit the ILOM Remote Console Lock Option

1. Log in to the ILOM SP web interface.
Note – Alternatively, you can log in to the ILOM CMM web interface then navigate
to the SP target where you want to enable or disable the KVMS lock option for the
ILOM Remote Console.
2. In the web interface page, click Remote Console --> KVMS.

The KVMS page appears displaying the options available for KVMS Settings and
Host Lock Settings.
3. In the Host Lock Settings section of the KVMS page, perform one of the
following tasks:
Task Instructions
Enable the standard Windows • In the Lock Mode list box, select Windows.
host lock mode option.
Enable the custom host lock 1. In the Lock Mode list box, select Custom.
mode feature. 2. In the Custom Lock Modifiers list box, select up to four
custom modifiers that match the keyboard shortcut
modifiers that are predefined in your operating system.
3. In the Custom Lock Key list box, select the key that
matches the keyboard shortcut key that is predefined in
your operating system.
Disable the host lock mode • In the Lock Mode list box, select Disabled.
feature.
4. Click Save to apply the changes you specified.

New ILOM SP Network Ports
As 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 to
the default network ports that were previously supported in ILOM 3.0.
Note – The Oracle Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide (820-
6410) lists the default network ports for ILOM 3.0. This guide will be updated to
include the latest ports available as of ILOM 3.0.4.
Enhanced Mouse Mode Settings for Remote Host

KVMS
As of ILOM 3.0.4, you can toggle between relative and absolute mouse mode
settings for remote KVMS without having to reset the server SP. Changes made to
the mouse mode configuration variable will take effect immediately in the ILOM
Remote Console.
Before You Begin

■ The Console (c) role is required to edit the mouse mode configuration variable.
▼ Edit Mouse Mode Setting for Remote Host

Using the CLI
1. Log in to ILOM.
2. Use the set command to edit the mouse mode configuration variable, for
example:
-> set /SP/services/kvms mousemode=relative

or
-> set /SP/services/kvms mousemode=absolute
▼ Edit Mouse Mode Setting for Remote Host
1. 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.
4. To apply the changes, click Save.

Topics
Description Links
User management resolved issues • “LDAP or RADIUS Commands Do Not Work

When Default Role Is Set to none” on page 68
• “Difficulty Removing dnslocatorquery
Records From Active Directory Configuration”
on page 68
System clock setting resolved issue • “When Using the CLI to Set the Time Zone,
Certain Time Zones Do Not Recalculate the
Clock Correctly (x86 Servers)” on page 69
Power management resolved issue • “Help Text for Power Management Properties Is
Incorrect” on page 70
Snapshot SP data resolved issue • “Snapshot Utility Missing Log Files for
Debugging” on page 69
ILOM back up CLI feature resolved • “ILOM CLI for set /{target}/config
issue dump_uri Does Not Provide Confirmation
Message” on page 70

Topics
Description Links
CLI Help text function resolved • “Role Help Text for Read-Only /SYS Properties
issues Is Incorrect” 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 resolved • “ILOM External Serial Port Flow Control
issue Implemented Incorrectly” on page 72
CLI read-only properties resolved • “CLI Auto Completion for Read-Only Properties
issue Does Not Work on Sun Fire X4140, X4240, and
X4440 Servers” on page 72
LDAP or RADIUS Commands Do Not Work

When 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 LDAP
or RADIUS default role to none and log in as an LDAP or RADIUS user, the Read
Only (o) role is assigned.
Difficulty Removing dnslocatorquery Records

From Active Directory Configuration
CR 6797346
Issue: dnslocatorquery records cannot be removed during configuration of

Active Directory.
Update: This issue is fixed in the ILOM 3.0.4 release. The content and range rules for
the dnslocatorquery records have been relaxed to allow for the clearing or
removal of the entries. This allows an empty string value to be accepted to
completely remove the entry.
When Using the CLI to Set the Time Zone, Certain
Time Zones Do Not Recalculate the Clock
Correctly (x86 Servers)
CR 6798875
Issue: When using the CLI to set the time zone, some time zones either do not
recalculate the clock correctly or update the time zone setting on the clock.
Update: As of ILOM 3.0.4 this isuse has been fixed for x86 servers.
You must use valid global time zone nomenclature to set the time zone to recalculate
the clock correctly. You can find a list of the valid global time zone nomenclature on
the Internet, for example, at:
http://en.wikipedia.org/wiki/List_of_zoneinfo_time_zones
Examples:
■ To set the SP clock time zone property value to the US standard eastern zone, you
would type:
-> set /SP/clock/ timezone=America/New_York
or
■ To set the SP clock time zone property value to the US central time zone, you
would type:
-> set /SP/clock/ timezone=America/Chicago
Snapshot Utility Missing Log Files for Debugging

CR 6811375
Issue: Missing files from /var/log impairs debug process when collecting data for
Service personnel using the Snapshot Utility.
Update: The missing Snapshot Utility /var/log files have been restored in the
ILOM 3.0.4 release.

ILOM CLI for set /{target}/config
dump_uri Does Not Provide Confirmation
Message
CR 6804202
Issue: When you set the dump_uri on /{target}/config, the ILOM CLI does not
display a confirmation message to indicate whether the command was successful.
Update: The print confirmation message for set /{target}/config dump_uri

has been corrected in the ILOM 3.0.4 release.
Role Help Text for Read-Only /SYS Properties Is

Incorrect
CR 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 since
the 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 the
required user role value for read-only /SYS properties.
Help Text for Power Management Properties Is

Incorrect
CR 6770180
Issue: The following properties are read-only and are not configurable; therefore, the
role 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 with
the properties now correctly specifies that the required role to view the properties is
Read Only (o).
Help Output Results for <TARGET> <property>

<property> Is Confusing
CR 6770069
Issue: Help function displays confusing text when listing values for multiple
properties, for example:
Help output prints:
-> help /HOST send_break_action boottimeout status

Properties:
send_break_action : Send Break Action to Host
send_break_action : Possible values = break, dumpcore
send_break_action : User role required for set = c
boottimeout : Boot time out
boottimeout : User role required for set = r
status : Host Status
Help output should print:
-> help /HOST send_break_action boottimeout status

Properties:
send_break_action : Send Break Action to Host
send_break_action : User role required for set = c
boottimeout : Boot time out
status : Host Status

Update: The Help function was updated in the ILOM 3.0.4 release to remove
property values that were not applicable.
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 in

the ILOM 3.0.4 release.
ILOM External Serial Port Flow Control

Implemented Incorrectly
CR 6822067
Issue: Writable support (using the set command) for ILOM’s external serial port
flow control is supported only on Oracle’s AST2000 server-based platforms.
Update: As of ILOM 3.0.4, writable support for ILOM’s external serial port flow
control is provided on all Oracle AST2000 server-based platforms. Read-only
support (using the show command) for ILOM’s external serial port flow control is
provided for all other Oracle server platforms.
CLI Auto Completion for Read-Only Properties

Does Not Work on Sun Fire X4140, X4240, and
X4440 Servers
CR 6729108
Issue: CLI does not recognize read-only properties when using the show command.
Update: Support was added to the ILOM 3.0.4 release to recognize read-only
properties while using the show command.
This section describes known issues and workarounds as of ILOM 3.0.4. Specific
change request (CR) identification numbers and workarounds for these issues are
Topics
Description Links
ILOM Remote Console known issues • “ILOM Remote Console Might Hang on
Windows Client When Redirecting a CD-ROM
Image or Floppy Image” on page 73
• “Unrecoverable ILOM Remote Console Sessions”
on page 74
ILOM Remote Console Might Hang on Windows

Client When Redirecting a CD-ROM Image or
Floppy Image
CR 6806444
Issue: When using a Windows client to redirect a CD-ROM image or floppy image
from 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
■ JDK 160
■ Windows operating system installed on client system.
Workaround:
● Close the ILOM Remote Console window on the Windows client, then perform
one of the following workarounds:
■ Using a Linux or Solaris client, launch the ILOM Remote Console to redirect
the CD-ROM image or floppy image.
or
■ Using a Windows, Solaris, or Linux client, launch the Storage Redirection
Utility in ILOM 3.0 to redirect the CD-ROM image or floppy image.

Note – The Storage Redirection Utility feature is a command-line utility that is only
available in ILOM 3.0. For instructions about how to use the Storage Redirection
Utility, see the Oracle ILOM 3.0 Documentation Collection.
Unrecoverable ILOM Remote Console Sessions

CR 6867870
Issue: Unrecoverable ILOM Remote Console sessions can occur when:

■ The ILOM Remote Console client has multiple tabs showing connections to three
different hosts while the state of the ILOM Remote Console client is in sleep mode
(or network cable is disconnected).
■ A second and third ILOM Remote Console client have the same connections
established to the same three hosts while the state of these Remote Console clients
are also in sleep mode (or network cable is disconnected).
When one (or more) of the ILOM Remote Console clients returns from sleep mode
(or the network cable is reconnected) and is unable to restart an inactive session,
the following occurs:
■ A system dialog appears stating the “Connection with SP is down, try
redirection later.” Click OK to dismiss the dialog.
■ A second dialog appears stating “The maximum number of connections
have been reached.” Click OK to dismiss the dialog.
Workaround: To recover the inactive ILOM Remote Console sessions on the first two
hosts, you must reset the SP (reset /SP) on both systems. For the third host, the
inactive ILOM Remote Console sessions typically recover within five minutes after
resetting the SPs on the first two hosts. However, if the state of the third ILOM
Remote Console client is in hibernation mode or screen saver mode, the inactive
Remote Console sessions on the third host might not recover. Should this occur, you
will need to reset the SP on the third host to recover the inactive ILOM Remote
Console sessions.
Note – The ILOM Remote Console supports up to three user session connections to
a host system.


Allowable Number for DNS Retries Is Incorrect

CR 6823516
(820-6412-10), it is incorrectly stated that the number of allowable retries to configure
a DNS setting is between 0 and 5.
Update: ILOM allows a total of 5 attempts to contact the DNS server, of which 0-4
are retries.
This information will be updated in a future release of the Oracle ILOM


CHAPTER 4

77
The following table identifies the new features available in ILOM 3.0.6.
Topics
Description Links
New storage monitoring properties • “Storage Monitoring for HDDs and RAID
for HDDs and RAID configurations Controllers” on page 79
Enhancements to power management • “Power Management Features in ILOM” on
page 86
• “New or Enhanced Power Management Features
as of ILOM 3.0.6” on page 87
New root password warning message • “Root Factory Default Password Warning
Message” on page 110
Updated list of network ports used • “New ILOM SP Network Port” on page 111
by ILOM
Storage Monitoring for HDDs and RAID
Controllers
As of version 3.0.6, ILOM supports additional storage monitoring functions for
viewing and monitoring storage details that are associated with system hard disk
drives (HDDs) and RAID controllers. These enhanced storage property details are
available in ILOM from the ILOM CLI.
Topics described in this section, include:

■ “Storage Properties Shown for HDDs and RAID Controllers” on page 80
■ “RAID Status Definitions for Physical and Logical Drives” on page 81
■ “View and Monitor Storage Details for HDDs and RAID Controllers” on page 82
Note – Some Oracle servers might not enable support for the storage monitoring
functions that are described in this chapter. To determine whether storage
monitoring support on your server has been enabled, see the ILOM Supplement
guide for your server.
For Oracle servers supporting the Storage Monitoring feature in ILOM, a system
management pack must be installed to use the Storage Monitoring features. For
information about how to download this management pack, see Oracle Server
Hardware Management Pack User’s Guide (821-1609).

Storage Properties Shown for HDDs and RAID
Controllers
Using the ILOM CLI, you can view the following properties (TABLE 4-1) that are
associated with your system server HDDs and RAID controller options.
Note – The storage properties appearing in TABLE 4-1 might not be available for all
storage configurations.
TABLE 4-1 Storage Properties Shown for HDDs and RAID Controllers
HDD Storage Properties (shown in ILOM CLI under /SYS)
• Disk type (SATA or SAS) • OK to remove status • HBA ID for controller

• FRU type (hard disk) • Service fault state • HBA ID for disk
• FRU name • Present device state • RAID status (online,
offline, failed, missing, and
so on)
• FRU part number • Disk capacity • RAID dedicated hot-spare
(for disk)
• FRU serial number • Device name • RAID global hot-spare
(disk group)
• FRU manufacturer • World Wide Name (WWN) • RAID ID list that is
applicable to the HDD
• FRU version • FRU description
RAID Controller Properties (shown in ILOM CLI under /STORAGE/raid)
• FRU manufacturer • PCI subdevice • Maximum global hot

spares (allowed number of
global hot spares for
controller)
• FRU model • RAID levels supported • Minimum stripe size
(supported size in
kilobytes)
• PCI vendor ID • Maximum disks (allowed • Maximum stripe size
disks for controller) (supported size in
kilobytes)
• PCI device ID • Maximum RAIDs (allowed
logical volumes for
controller)
• PCI subvendor ID • Maximum hot spares
(allowed dedicated hot
spares for single RAID)
TABLE 4-1 Storage Properties Shown for HDDs and RAID Controllers (Continued)
RAID Controller Disk Properties (shown in ILOM CLI under /STORAGE/raid)
• FRU name • FRU version • World Wide Name (WWN)

• FRU part number • RAID status (offline, online, • Dedicated hot spare (for
failed, missing, initializing) disk)
• FRU serial number • Disk capacity (supported • Global hot spare (for disk
size in byte) group)
• FRU manufacturer • Device name • RAID IDs (list for this
device)
• FRU description • Disk type (SAS or SATA • System drive slot
known by host operating (corresponding internal
system) hard drive NAC name for
RAID)
RAID Controller Volume Properties (shown in ILOM CLI under /STORAGE/raid)
• RAID level • Mounted status • Stripe size

• RAID volume status (OK, • Device name, known by host • Targets for child member of
degraded, failed, missing) operating system RAID ID
• Disk capacity • Resync status
For instructions about how to view the storage properties in ILOM for HDDs and
RAID controllers, see “View and Monitor Storage Details for HDDs and RAID
Controllers” on page 82.
RAID Status Definitions for Physical and Logical Drives

When a physical disk is configured as part of a volume and is attached to a
powered-on controller, ILOM reports one of the following status values for
configured physical (TABLE 4-2) and logical (TABLE 4-3) drives.
TABLE 4-2 RAID Status Definitions for Physical RAID Disks
Physical RAID Disk ID Status
OK The disk is online.

Offline The disk is offline per host request or for another reason such as disk is not
compatible for use in volume.
Failed The disk has failed.

TABLE 4-2 RAID Status Definitions for Physical RAID Disks (Continued)
Physical RAID Disk ID Status
Initializing The disk is being initialized or rebuilt.

Missing The disk is missing or not responding.
Unknown The disk is not recognized.
TABLE 4-3 Status Definitions for Logical RAID Volumes
Logical RAID Volume Status
OK The volume is running at optimal level.

Degraded The volume is running in degraded mode. An additional disk loss could
result in permanent data loss.
Failed The volume has too many failed disks and is not running.
Missing The volume is not found or not available.
Unknown The volume is not recognized or is not defined.
View and Monitor Storage Details for HDDs and RAID

Controllers
To view and monitor storage details related to the HDDs and RAID controllers that
are configured on your system, log in to the ILOM CLI and drill down the following
target properties under:
■ /SYS/ to show details for HDDs
or
■ /STORAGE/raid to show details for a RAID disk controller
Before You Begin

■ Ensure that the Storage Monitoring feature is supported on your Oracle server.
For details, see the ILOM Supplement guide for your server.
■ For Oracle servers supporting the Storage Monitoring features, you must
download and install a system management pack prior to using the Storage
Monitoring features in ILOM. For information about how to download this
management pack, see Oracle Server Hardware Management Pack User’s Guide (821-
1609).
For instructions and examples about how to view the storage monitoring details in
ILOM for HDDs and RAID controllers, see the following procedure.
▼ Show Property Details in ILOM for HDDs and RAID
Controllers Using the CLI
Note – Alternatively, you can log in to the ILOM CMM CLI then navigate to the SP
target where you can display the HDD details under /SYS or the RAID disk
controller details under /STORAGE/raid.
2. Use the cd command to navigate to the /SYS or /STORAGE/raid target.

For example:
■ ->cd /SYS
or
■ ->cd /STORAGE/raid
3. To display property details for an HDD installed on your server, use the show
command.
For example:
■ To view storage details for a specific HDD configured on your system, you
might type:
-> show /SYS/DBP/HDD0
Where 0 is the HDD slot location on the server where the HDD is installed.
Sample CLI output:

4. To display property details associated with a RAID controller and its associated
disk IDs, use the show command:
For example:
a. To list the RAID controller target(s) configured, you would type:

-> show /STORAGE/raid
Sample CLI storage raid target output:
b. To show the property details associated with a controller, as well as to list

the raid_id targets configured, you would type:
-> show /STORAGE/raid/controller@od:00.0
Where od:00.0 is the ID that corresponds to the PCI address of the controller.
Sample CLI RAID controller targets and properties output:
c. To list the available disk_id targets, as well as to view the properties
associated with a controller raid_id, you would type:
-> show /STORAGE/raid/controller@od:00.0/raid_id0
■ Where od:00.0 is the PCI address for the controller that was found installed
on your server.
■ Where raid_id0 is the target RAID disk that is configured on the
controller.
Sample CLI RAID controller output for raid_id:
d. To view the property details for a disk_id that is associated with a raid_id on
the controller, you would type:
-> show /STORAGE/raid/controller@od:00.0/raid_id0/disk_id0
■ Where od:00.0 is the PCI address for the controller that was found installed
on your server.
■ Where raid_id0 is the target RAID disk that is configured on the
controller.
■ Where disk_id0 is the target disk that is associated with the raid_id.
Sample CLI RAID controller output for raid_id and disk_id:

5. Type exit to exit the CLI.
Power Management Features in ILOM

The power management features in ILOM enable you to monitor and manage your
system’s power consumption.
For further details about the common power management features available in
ILOM, see the following sections.
■ “Summary of Power Management Features Prior to ILOM 3.0.6” on page 87
■ “New or Enhanced Power Management Features as of ILOM 3.0.6” on page 87
Summary of Power Management Features Prior to
ILOM 3.0.6
TABLE 4-4 identifies the common power management features available in ILOM
prior to ILOM version 3.0.6.
TABLE 4-4 Common Power Management Features Prior to ILOM 3.0.6
Feature Description Detailed Information
Power From the ILOM CLI or web • “Power Management Metrics” on

Consumption interface, you can monitor page 11
Metrics power consumption metrics for • Oracle Integrated Lights Out Manager
your server and, if applicable, (ILOM) 3.0 Concepts Guide (820-6410)
chassis system when a CMM is • Oracle Integrated Lights Out Manager
present. (ILOM) 3.0 CLI Procedures Guide (820-
6411)
• Oracle Integrated Lights Out Manager
(ILOM) 3.0 Web Interface Procedures
Guide (820-6412)
Power From the ILOM CLI or web • “Power Consumption History” on
Consumption interface, you can monitor the page 12
History power usage average and
power history for all power
consumption sensors.
Power From the ILOM CLI or web • “Power Consumption Thresholds” on
Consumption interface, you can configure an page 47
Notification alert threshold to notify you of
Threshold when the system’s power
consumption reaches or
exceeds the threshold value
specified.
New or Enhanced Power Management

Features as of ILOM 3.0.6
As of version 3.0.6, ILOM supports the following new or enhanced common power
management features:
■ “Component Allocation Power Distribution” on page 88
■ “Power Budget” on page 100
■ “Power Supply Redundancy for CMM Systems” on page 106

■ “Platform-Specific CMM Power Metrics” on page 109
Component Allocation Power Distribution
Note – The Component Allocation Power Distribution interfaces described in this

section might change in the future.
The Component Allocation Power Distribution feature in ILOM enables you to

monitor, in real-time, the amount of power that is allocated to server components
and, if applicable, CMM components.
Topics described in this section:

■ “Monitoring Server Power Allocated Components” on page 88
■ “Monitoring CMM Power Allocated Components” on page 90
■ “Component Power Allocation Special Considerations” on page 91
■ “Component Power Allocation CLI and Web Procedures” on page 92
Monitoring Server Power Allocated Components

TABLE 4-5 identifies the components that are allocated power in ILOM by your Oracle
server. For each component listed in TABLE 4-5, ILOM provides an allocated server
power value in wattage that represents the sum of the maximum power consumed
by either a single server component (such as a memory module), a category of server
components (all memory modules), or all server power-consuming components.
TABLE 4-5 Server Power Allocated Components
Server Power Allocated Allocated Power Applicable to Applicable to

Component (Watts) Rackmount Server Sun Blade Server Module
All server power-consuming X X X

components
CPUs X X X
Memory modules, such as X X X
DIMMs
I/O modules, such as HDDs, X X X
PEMs, REMs*, RFEMs*
* These I/O modules apply only to Sun Blade server modules.
** These devices for server modules are allocated power by the CMM. See TABLE 4-6 for details.
TABLE 4-5 Server Power Allocated Components (Continued)
Server Power Allocated Allocated Power Applicable to Applicable to

Component (Watts) Rackmount Server Sun Blade Server Module
Motherboard (MB) X X X
Power Supply Units (PSUs) X X Does not apply**
Fans (FM) X X Does not apply**
* These I/O modules apply only to Sun Blade server modules.
** These devices for server modules are allocated power by the CMM. See TABLE 4-6 for details.
You can monitor the server power allocated components from the Power
Management --> Distribution page in the ILOM SP web interface or from the
SP/powermgmt/powerconf CLI target in the ILOM SP CLI. An example of the
Power Management --> Distribution page is shown FIGURE 4-1.
FIGURE 4-1 Power Management --> Distribution Tab - ILOM SP 3.0.6
For more details about how to view the server or CMM power allocation, see:
■ “View Server Component Power Allocations Using the CLI” on page 93
■ “View CMM Component Power Allocations Using the Web Interface” on page 96

Monitoring CMM Power Allocated Components
TABLE 4-6 identifies the components that are allocated power in ILOM by the CMM
in your Sun system chassis. For each component listed in TABLE 4-6, ILOM provides
an allocated CMM power value in wattage that represents the sum of the maximum
power consumed by either a single CMM component (a blade), a category of CMM
components (all blades), or all CMM power-consuming components. It also provides
a permitted CMM power value in wattage that represents the guaranteed maximum
power the CMM component (or component category) can consume.
Note – The Permitted Power value in ILOM is derived from the Power Supply
Redundancy Policy and the Redundant Power available (for details see,“Power Supply
Redundancy for CMM Systems” on page 106). The CMM continuously monitors and
tracks all the Allocated Power to the system, as well as the Allocatable Power
remaining and it ensures that the sum for these numbers (allocated and allocatable)
never exceeds the chassis Permitted Power value.
Note – Power to a Sun Blade server module is allocated by the CMM when a
request for power is made by the server module. The server module requests power
whenever it is powered on, and releases power back to the CMM whenever it is
powered off. The CMM allocates power to the server module if the remaining
allocatable power is sufficient to meet the server module’s request. The CMM also
checks whether there is a limit set to the amount of power that it is permitted to a
server module (which is known as the Blade Slot Permitted Power in the web interface
or CMM/powermgmt/powerconf/bladeslots/BLn permitted_power in the
CLI). The CMM only allocates power to the server module if the requested power is
less than or equal to this property.
TABLE 4-6 CMM Power Allocated Components
Allocated Power Permitted Power Allocatable Power

CMM Power Allocated Component (Watts) (Watts) (Watts)
All CMM power-consuming X X X

components (aggregate value
for all powered entities listed)
Blade slots (BL#) X X* Does not apply
CMM X Does not apply Does not apply
* The permitted power allocated to blade slots is user configurable.
TABLE 4-6 CMM Power Allocated Components (Continued)
Allocated Power Permitted Power Allocatable Power

CMM Power Allocated Component (Watts) (Watts) (Watts)
Network Express Modules X Does not apply Does not apply

(NEMs)
Power Supply Units (PSUs) X Does not apply Does not apply
Fans (FM) X Does not apply Does not apply
* The permitted power allocated to blade slots is user configurable.
You can monitor the power allocated CMM components from the Power
Management --> Distribution page in the ILOM CMM web interface or from the
CMM/powermgmt/powerconf CLI target in the ILOM CMM CLI. For more details,
see:
■ “View CMM Component Power Allocations Using the CLI” on page 94
In addition to monitoring the power allocation for each CMM power allocated
component, you can modify the permitted (maximum) power the CMM allocates to
blade slots within the chassis. For details, see:
■ “Configure Permitted Power for Blade Slots Using the CLI” on page 95
■ “Configure Permitted Power for Blade Slots in CMM Using the Web Interface” on
page 98
Component Power Allocation Special Considerations

When monitoring the server or CMM power allocated components, consider the
following information:
■ Power allocation for component categories. For component categories that
include multiple components, such as fans, you will be able to monitor the total
sum of power consumed by all components (fans), as well as the total sum of
power consumed by an individual component (fan).
■ Hot-pluggable component power allocation. ILOM automatically displays a pre-
allocated maximum power value for any known component that can be placed in
a hot-plug component location either on a server or on a system chassis. For
example:
■ A hot-pluggable component location on an Oracle server could include storage
slots for hard disk drives (HDDs). In this case, ILOM will display a maximum
power value for the HDD to be placed in the storage slot.
■ A hot-pluggable component location on a system chassis (with a CMM) can
include blade slots for server modules or I/O server modules. In this case,
ILOM will display a maximum power value for any I/O server module that

could be placed in the blade slots. However, if I/O server modules are not
supported in the system chassis, then ILOM will display a maximum power
value for a server module (and not an I/O server module).
For more information about which locations or components on your server or
CMM chassis system are hot-pluggable, refer to the platform documentation
shipped with your system.
■ Power supply power allocation. ILOM automatically allocates power to the
power supply to account for power losses between the wall outlet and the
component.
■ Troubleshooting Sun Blade server module power-on issues. If the Sun Blade
server module is unable to power on, verify that the SP permitted power
property value (/SP/powermgmt permitted_power) is not more than the
CMM blade slot permitted power property value
(/CMM/powermmgt/powerconf/bladeslots/BLn permitted_power).
Note – ILOM 3.x server modules negotiate with the CMM and honor the
permitted power restriction. Pre-3.x ILOM server modules will power on as long
as there is enough allocatable power. Therefore, the permitted power constraint is
only honored by server modules running ILOM 3.x or subsequent release.
Component Power Allocation CLI and Web Procedures

This section provides instructions for the following component power allocation
tasks.
For the ILOM CLI:

■ “View Server Power Allocations for All Components Using the CLI” on page 93
■ “View Server Component Power Allocations Using the CLI” on page 93
■ “View CMM Power Allocations for All Chassis Components Using the CLI” on
page 94
■ “View CMM Component Power Allocations Using the CLI” on page 94
■ “Configure Permitted Power for Blade Slots Using the CLI” on page 95
For the ILOM web interface:

■ “View Server Component Power Allocations Using the Web Interface” on page 96
■ “Configure Permitted Power for Blade Slots in CMM Using the Web Interface” on
page 98
▼ View Server Power Allocations for All Components
Using the CLI
2. To view the sum of power allocated to all components in the system, type the
following command:
-> show /SP/powermgmt allocated_power
▼ View Server Component Power Allocations Using the

CLI
2. To view power allocated to a component category (fans, CPUs, and so forth),

type the following command:
-> show /SP/powermgmt/powerconf/component_type
Where component_type is the name of the component category.
For example, to view the power allocated to all CPUs (component category), you
would type:
-> show /SP/powermgmt/powerconf/CPUs
Note – For each command, the read-only value for the maximum power consumed
by the component is returned, measured in watts.
3. To view the power allocated to a specific component, type the following

command:
-> show /SP/powermgmt/powerconf/component_type/component_name
■ Where component_type is the name of the component category.
■ Where component_name is the name of the component.
For example, to view the power allocated to a specific CPU, you would type:
-> show /SP/powermgmt/powerconf/CPUs/CPUn
Where n is the installed location number of the CPU.
Other rackmount server components can include:
■ /SP/powermgmt/powerconf/Fans/FB0_FMn
■ /SP/powermgmt/powerconf/PSUs/PSn
■ /SP/powermgmt/powerconf/CPUs/MB_Pn
■ /SP/powermgmt/powerconf/memory/MB_P0_Dn

■ /SP/powermgmt/powerconf/IO/DBP_HDDn
Other server module components can include:
■ /SP/powermgmt/powerconf/CPUs/MB_Pn
■ /SP/powermgmt/powerconf/memory/MB_P0_Dn
■ /SP/powermgmt/powerconf/IO/DBP_HDDn
▼ View CMM Power Allocations for All Chassis

Components Using the CLI
1. Log in to the ILOM CMM CLI.
2. To view the sum of power allocated to all chassis system components, type the
following command:
-> show /CMM/powermgmt allocated_power
3. To view the remaining power available to allocate to blade slots, type the
following command:
-> show /CMM/powermgmt allocatable_power
▼ View CMM Component Power Allocations Using the

CLI
2. To view power allocated to a component category (fans, blade slots, and so

forth), type the following command:
-> show /CMM/powermgmt/powerconf/component_type
For example, to view the power allocated to all blade slots (component category),
you would type:
-> show /CMM/powermgmt/powerconf/bladeslots
Note – For each command, the read-only value for the maximum power consumed
by the component is returned, measured in watts.
3. To view the power allocated to a specific component, type the following
command:
-> show /CMM/powermgmt/powerconf/component_type/component_name
Where component_name is the name of the component.
For example, to view the power allocated to a specific blade slot, you would type:
-> show /CMM/powermgmt/powerconf/bladeslots/BLn
Where n is the location number of the blade slot.
Other CMM components can include:
■ /CMM/powermgmt/powerconf/NEMs/NEMn
■ /CMM/powermgmt/powerconf/Fans/FMn
■ /CMM/powermgmt/powerconf/PSUs/PSn
▼ Configure Permitted Power for Blade Slots Using the

CLI
Note – To change any permitted_power property value for blade slots in ILOM
requires an Admin (a) role user account.
2. To configure the permitted (maximum) power that the CMM will allocate to a
blade slot, type the following command:
-> set /CMM/powermgmt/powerconf/bladeslots/bladeslotn
permitted_power=watts
Where bladeslotn represents the blade slot that you want to configure.
For example:
-> set /CMM/powermgmt/powerconf/bladeslots/bladeslot1

permitted_power=1200
Set 'permitted_power' to '1200'
Note – To prevent a server module from powering-on, set the permitted power
value for the blade slot to 0.

▼ View Server Component Power Allocations Using the
Web Interface
2. Select the Power Management --> Distribution tabs.

The SP Power Distribution page appears.
3. In the SP Power Distribution page, view the power management values for:
■ Allocated Power – Total power allocated value in wattage for all power-
consuming components on the server.
■ Distribution Details – The allocated power wattage value for each server
component category (for example, memory) and each server component (for
example ME_PO_D0).
▼ View CMM Component Power Allocations Using the

Web Interface
1. Log in to the ILOM CMM web interface.
2. In the left pane of the CMM web interface page, select CMM then in the right
pane of the web interface page, select the Power Management --> Distribution
tabs.
The CMM Power Distribution page appears.

3. In the CMM Power Distribution page, view the power management values for:
■ Allocated Power – Total power allocated value in wattage for all power-
consuming CMM components in the system chassis.
■ Allocatable Power – Total remaining power (watts) available from CMM to
allocate to blade slots.
■ Blade Slot Power Distribution – View power allocation values for:
■ Allocated Power – Total power (watts) allocated to the server module
(blade) in this slot. The CMM always allocates enough power to handle an
unmanaged I/O server module, whether or not an I/O server module is
present.
■ Permitted Power – Maximum power allocation permitted for a server
module in this blade slot.
Note – To modify the Permitted Power allocated to a server module slot, see
“Configure Permitted Power for Blade Slots in CMM Using the Web Interface” on
page 98 or “Configure Permitted Power for Blade Slots Using the CLI” on page 95.
■ Component Power Distribution – View allocated power for each non-blade

component in the system.
▼ Configure Permitted Power for Blade Slots in CMM

Note – To change any power allocation property value for blade slots in ILOM
requires an Admin (a) role user account.
2. In the left pane of the web interface page, select CMM then in the right pane of
the web interface page, select the Power Management --> Distribution tabs.
The CMM Power Distribution page appears.
3. Scroll down to the Blade Slot Power Distribution table.
4. In the Blade Slot Power Distribution table, do the following.
a. Select the radio button for the blade slot Permitted Power allocation that you
want to modify.
b. Click Edit.
A dialog appears listing information about the Allocated and Permitted Power
value.
c. In the dialog, modify the Permitted Power value, then click Save.
Note – To prevent server module from powering-on, you can set the Permitted
Power value to 0.

Power Budget
Note – The Power Budget interfaces described in this section are unstable, and
might change in the future.
Some Oracle server platforms support a power budget. A power budget sets a limit
on the system’s power consumption. The system applies power capping when
power consumption exceeds the power limit and guarantees that the maximum
power consumption will not exceed the system’s Permitted Power.
You can configure a power budget and then, at a later time, enable or disable the
configuration properties that are set. After a power budget is enabled, the ILOM SP
monitors the power consumption and applies power capping when needed. Power
capping is achieved by limiting the maximum frequency at which the CPUs run. The
ILOM SP coordinates this process with the operating system (OS) to ensure that the
OS can continue applying its own power management policies within the set limit.
Power budget settings in ILOM are saved across all SP reboots and host power-off
and power-on states. During an SP reboot, the applied power capping budget that is
in effect will remain. After the SP completes the reboot process, power capping is
then automatically adjusted, as needed, by the system.
ILOM’s ability to achieve a power budget depends on the workload running on the
system. For example, if the workload is causing the system to operate near the
maximum power consumption, ILOM will be unable to achieve a budget that is
close to the minimum power consumption. If ILOM is unable to achieve the set
Power Limit, it will automatically generate a violation notification.
Power Budget topics described in this section include:

■ “Why Use a Power Budget?” on page 100
■ “Server Power Budget Properties” on page 101
■ “Advanced Server Power Budget Features” on page 102
■ “Configure Server Power Budget Properties Using the CLI” on page 104
■ “Configure Server Power Budget Properties Using the Web Interface” on page 105
Why Use a Power Budget?

The Power Budget feature in ILOM helps you to better plan and manage the power
required for your data center. Typically the power allocated to a server is based on
the nameplate power, as provided by the /SP/powermgmt allocated_power
property.
The most effective way to use the Power Budget feature in ILOM is to:
1. Determine the workload that will operate on the Oracle server.
2. Set the Power Limit property in ILOM that is near (for example, at or slightly
above) to the workload’s normal operating power consumption.
3. Use the Power Limit property value to help plan the amount of power that will
need to be allocated in your data center for this system.
Server Power Budget Properties

TABLE 4-7 identifies the server power budget properties that you can view or
configure from the CLI or web interface in ILOM.
TABLE 4-7 Server Power Budget Properties
Power Budget Property Description
Activation State Enable this property to enable the power budget

configuration.
Status The Status reports one of the following current power budget
states:
• OK – The OK status appears when the system is able to
achieve the power limit, or when the power budget is not
enabled.
• Violation – The Violation status occurs when the system is
not able to reduce power to the power limit.
If the power consumption falls below the Power Limit, the
violation is cleared and the status returns to ok.
The budget status is also reported through a system sensor:
/SYS/PWRBS. This is a discreet sensor which is set to 1
(deasserted) when the budget is ok, and to 2 (asserted)
when the budget has been violated.
Power Limit Set a Power Limit in watts or as a percentage of the range
between minimum and maximum system power.
Note - The minimum system power is viewable in the CLI
under the target /SP/powermgmt/budget
min_powerlimit. The maximum system power is viewable
from the Allocated Power property in the web interface or
from the CLI under the target /SP/powermgmt
allocated_power.

Advanced Server Power Budget Features
The advanced server power budget features in ILOM include properties for Time
Limit and Violation Actions. These property settings (see TABLE 4-8) enable you
to control the aggressiveness of power capping, and to configure a system action in
response to a violated budget.
The server power budget is designed to ensure that power capping is not applied
until the Power Limit is exceeded. The Time Limit property specifies the grace
period for capping power to within the Power Limit, if exceeded. The system
provides a default grace period that is set to achieve responsiveness at the least cost
to the system performance. When the default grace period is enabled for the Time
Limit property, anomalous spikes are ignored and power capping is applied only
when power consumption remains above the Power Limit. If you specify a
different grace period than the default grace period provided, the user-modified
grace period could cause ILOM to increase or decrease the power cap severity in
response to exceeding the Power Limit.
Server modules are allocated power by the chassis CMM, and must guarantee to not
exceed this allocated amount. It might be necessary to reduce the server module's
guaranteed maximum power to allow the server module to power on, or there might
be some other administrative reason for requiring that the server power never
exceeds a watts value. Setting the budget grace period to None instructs ILOM to
permanently apply power capping to ensure that the Power Limit is never
exceeded, at the cost of limited performance. If ILOM can guarantee the Power
Limit with a grace period of None, it reduces the value of the Permitted Power
property to reflect the new guaranteed maximum power. If the power limit or grace
period is later increased, the Permitted Power value on a rackmount server is
increased. However, the Permitted Power value for a Sun Blade server module
will only increase if the chassis CMM is able to provide the server module with
additional power.
TABLE 4-8 identifies the advanced server power budget property settings that you can
view or configure from the ILOM CLI or web interface.
TABLE 4-8 Advanced Server Power Budget Properties
Power Budget Property Description
Time Limit Specify one of the following grace periods for capping the
power usage to the limit:
• Default – Platform selected optimum grace period.
• None – No grace period. Power capping is permanently
applied.
• Custom – User-specified grace period.
Violation Actions The actions that the system will take if the power limit cannot
be achieved within the grace period. This option can be set to
None or Hard Power Off.
This setting, by default, is set to None.
Note – For best power capping performance, the default values are recommended
for all advanced server power budget properties.
An example of the web interface Power Management --> Budget properties is shown
in FIGURE 4-2.
FIGURE 4-2 SP - Power Management Budget Tab - ILOM 3.0.6
For instructions about how to view or configure the server and advanced server
power budget properties in ILOM, see the following procedures:

■ “Configure Server Power Budget Properties Using the CLI” on page 104
■ “Configure Server Power Budget Properties Using the Web Interface” on page 105
▼ Configure Server Power Budget Properties Using the

CLI
Note – To change any server power budget property values in ILOM requires an
Admin (a) role user account.
2. To view the current power budget settings, type the following command:
-> show /SP/powermgmt/budget
/SP/powermgmt/budget
Targets:
Properties:
activation_state = enabled
status = ok
powerlimit = 600 (watts)
timelimit = default (30 seconds)
violation_actions = none
min_powerlimit = 150
pendingpowerlimit = 600 (watts)
pendingtimelimit = default
pendingviolation_actions = none
commitpending = (Cannot show property)
Commands:
cd
show
->
3. To configure power budget settings, type the following command:

-> set /SP/powermgmt/budget property=value
Where property=value represents one of the following:
■ activation_state=[enabled|disabled]
■ pendingpowerlimit=[wattsw|percent%]
■ pendingtimelimit=[default|none|seconds]
■ pendingviolation_actions=[none|poweroff]
■ commitpending=true
Note – See TABLE 4-7 and TABLE 4-8 to view definitions for each power budget
property.
Note – To set the powerlimit, timelimit and violation_action in the ILOM

CLI, you must set the matching pending properties and then commit these three
pending properties as a group. After these properties are committed by typing set
/SP/powermgmt/budget commitpending=true, the new values will apply
whenever the budget activation_state is set to enabled.
For example:
-> set /SP/powermgmt/budget activation_state=enabled

Set 'activation_state' to 'enabled'
▼ Configure Server Power Budget Properties Using the

Web Interface
Note – To change any server power budget property values in ILOM requires an
2. In the ILOM web interface, select the Power Management --> Budget tabs.
The Power Budget Management page appears.

3. In the Power Budget Management page, view or modify any of the power
budget properties listed.
Note – See TABLE 4-7 and TABLE 4-8 to view definitions for each power budget
property.
4. To apply power budget changes, click Save.
5. To view the system power limit value that is in effect, do the following:
a. Select the Power Management --> Consumption tabs.

The Power Management Consumption page appears.
b. In the Power Management Consumption page, view the property value for
the system power limit.
Power Supply Redundancy for CMM Systems

From the ILOM CMM CLI or web interface you can view and configure the
following power supply redundancy options:
■ Power Supply Redundancy Policy – This policy controls the number of power
supplies that are currently allocating power in addition to the number of power
supplies that are reserved to handle power supply failures. Values for this
redundancy policy property can be set to:
■ None – Reserves no power supplies.
■ n+n – Reserves half of the power supplies to handle power supply failures.
■ Redundant Power – This value is provided by the system. It represents the
available power that is not allocated.
To view or configure the CMM power supply redundancy options in the ILOM CLI
or web interface, see:
■ “View or Configure CMM Power Supply Redundancy Properties Using the CLI”
on page 107
■ “View or Configure CMM Power Supply Redundancy Properties Using the Web
Interface” on page 108
▼ View or Configure CMM Power Supply

Redundancy Properties Using the CLI
Note – To change the CMM power supply redundancy policy in ILOM requires an
2. To configure power management settings, type the following command:

-> set /CMM/powermgmt property=value
Where property=value represents the redundancy [none|n+n]
For example:
-> set /CMM/powermgmt redundancy=none

Set 'redundancy' to 'none'
Note – When you change the redundancy policy, this change affects the amount of
power the CMM is permitted to allocate to server modules (blades). The chassis
Permitted Power is set to the power that the available power supplies can
provide minus the redundant power that is available. In addition, when there is no
redundant power available to the system, a loss of a power supply will cause the
system to reduce the Permitted Power. If the system reduces the Permitted
Power below the power that had already been allocated, you should immediately
take steps to turn off the server modules to reduce the allocated power.

▼ View or Configure CMM Power Supply
Redundancy Properties Using the Web Interface
Note – To change the CMM power supply redundancy policy in ILOM requires an
2. In the left pane of the CMM web interface, select CMM then in the right pane
of the web interface page, select the Power Management --> Redundancy tabs.
The Power Management Redundancy page appears.
3. In the Redundancy page, view or configure the properties.:

■ Power Supply Redundancy Policy – Select the number of power supplies to
allocate for redundancy.
■ None – To reserve no power supplies.
■ N+N – To reserve half of the power supplies.
Note – When you change the redundancy policy, this change affects the amount of
power the CMM is permitted to allocate to server modules (blades). The chassis
Permitted Power is set to the power that the available power supplies can provide
minus the redundant power available. In addition, when there is no redundant
power available to the system, a loss of a power supply will cause the system to
reduce the Permitted Power. If the system reduces the Permitted Power below
the power that had already been allocated, you should immediately take steps to
turn off the server modules to reduce the allocated power.
■ Redundant Power – This value is provided by the system. It represents the

available power that is not allocated.
4. Click Save to apply any changes made.
Platform-Specific CMM Power Metrics
Note – The Platform-Specific CMM Power Metric interfaces described in this section
are unstable, and might change in the future.
As of ILOM version 3.0.6, advanced power metrics are available in some Oracle
systems from the ILOM CMM CLI or web interface. These metrics represent the
maximum allocated power value for each blade slot. For empty slots or slots with
I/O server modules, the value presented by ILOM represents the maximum power
that an I/O server module could consume.
To determine whether your CMM system supports this ILOM 3.0.6 feature, refer to
the platform ILOM Supplement for your server or CMM.
For Oracle systems supporting the CMM advanced power metrics, you can view the
power metrics in the Power Management --> Metrics page of the ILOM web
interface (FIGURE 4-3) or from the ILOM CLI under the target
/CMM/powermgmt/advanced/BLn.
FIGURE 4-3 Sample Power Management Metrics Page

Root Factory Default Password Warning
Message
When the root password in ILOM is set to factory default, a warning will appear on
the ILOM CLI and web interface.
For example:
■ In the ILOM web interface, a warning link will appear in the page header. Placing
your mouse over the link will display the warning message or clicking the
warning link will display the warning message in a dialog.
■ In the ILOM CLI, the following factory default warning message appears after
logging in to ILOM.
Password:
Waiting for daemons to initialize...
Daemons ready
Oracle(TM) Integrated Lights Out Manager
Version 3.0.0.0 r46636

Copyright 2009 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Warning: password is set to factory default.
New ILOM SP Network Port
As of ILOM 3.0.6, a new SP network port (5556) is available for configuring the
ILOM Remote Console Session Manager behind a firewall.
TABLE 4-9 identifies the updated list of the default network ports used by ILOM.
TABLE 4-9 ILOM Network Ports
Port Protocol Application
Common Network Ports

22 SSH over TCP SSH - Secure Shell
69 TFTP over UDP TFTP - Trivial File Transfer Protocol (outgoing)
80 HTTP over TCP Web (user-configurable)
123 NTP over UDP NTP - Network Time Protocol (outgoing)
161 SNMP over UDP SNMP - Simple Network Management Protocol (user-
configurable)
162 IPMI over UDP IPMI - Platform Event Trap (PET) (outgoing)
389 LDAP over LDAP - Lightweight Directory Access Protocol
UDP/TCP (outgoing; user-configurable)
443 HTTPS over TCP Web (user-configurable))
514 Syslog over UDP Syslog - (outgoing)
623 IPMI over UDP IPMI - Intelligent Platform Management Interface
546 DHCP over UDP DHCP - Dynamic Host Configuration Protocol (client)
1812 RADIUS over UDP RADIUS - Remote Authentication Dial In User Service
(outgoing; user-configurable)
SP Network Ports
5120 TCP ILOM Remote Console: CD
5121 TCP ILOM Remote Console: Keyboard and Mouse
5123 TCP ILOM Remote Console: Diskette
5555 TCP ILOM Remote Console: Encryption
5556 TCP ILOM Remote Console: Authentication
6481 TCP ILOM Remote Console: Servicetag Daemon
7578 TCP ILOM Remote Console: Video

TABLE 4-9 ILOM Network Ports (Continued)
Port Protocol Application
7579 TCP ILOM Remote Console: Serial

CMM Network Ports
8000 - 8023 HTTP over TCP ILOM drill-down (blades)
8400 - 8423 HTTPS over TCP ILOM drill-down (blades)
8200 - 8219 HTTP over TCP ILOM drill-own (NEMs)
8600 - 8619 HTTPS over TCP ILOM drill-down (NEMs)

This section describes the issues that have been resolved as of the ILOM 3.0.6.
Specific change request (CR) identification numbers for these fixed issues are
Topics
Description Links
Unexpected SMTP test email • “Ability to Send SMTP Test Alert Email
notification behavior Notification” on page 112
Unexpected behavior drill-down • “Drill-Down Ability to Server Module From
behavior from CMM to blade CMM After Disabling ssh” on page 113
Unexpected power management • “Ability to Record Power Management Events in
event behavior Log File” on page 113
Ability to Send SMTP Test Alert Email

Notification
CR 6850298
Issue: After pressing Test (on SMTP page) the test email notification was not sent
and there was no entry found in event log for this event.
Update: This issue has been resolved as of ILOM 3.0.6.
Drill-Down Ability to Server Module From CMM
After Disabling ssh
CR 6837359
Issue: After disabling ssh on a server module it was impossible to drill-down to the
server module from the CMM.
Ability to Record Power Management Events in

Log File
CR 6831492
Issue: Power management was not triggering an event after crossing a threshold.

TABLE 4-10 Known Issues as of ILOM 3.0.6
Known Issue CR(s) For Description and Workaround, See:
ILOM web interface • 6858008 • “Unable to Retrieve Host Power State After
known issues • 6853118 Upgrading ILOM Firmware From 2.0 to 3.0” on
page 114
• “Access Page Error Appears After Configuring
Unknown Sensor LED Status When Monitoring
System From IPMItool” on page 114
IPMI interface • 6848980 • “Access Page Error Appears After Configuring
known issue Unknown Sensor LED Status When Monitoring
System From IPMItool” on page 114
Back up and restore • 6847309 • “Console Error Appears After Performing Backup
known issue and Restore” on page 114

Unable to Retrieve Host Power State After
Upgrading ILOM Firmware From 2.0 to 3.0
CR 6858008
Issue: When the SP firmware is updated from ILOM 2.0 to 3.0, the ILOM web
interface might not be able to retrieve the remote host power state after the upgrade
completes. If this occurs, a blank page appears on the Remote Power Control tab.
Workaround: Perform one of the following actions:

■ Clear your browser cache and refresh your browser after completing the upgrade.
or
■ In the header area of the ILOM web page, click the Refresh button (on the ILOM
web interface page) to correct the browser caching issue.
Access Page Error Appears After Configuring

Unknown Sensor LED Status When Monitoring
System From IPMItool
CR 6848980
Issue: Unknown sensor LED statuses are shown in the ILOM web interface when
using IPMItool to monitor Oracle servers. This issue is likely to occur when
concurrently running the SP and the IPMI KCS interface from the operating system
(OS). As a result of this configuration, the IPMI messages are overloaded to the SP.
Workaround: To enable the ILOM web interface sufficient time to read the IPMI
sensors, you should limit the rate of KCS message responses to the host OS by
inserting the command sleep 1 between commands in your host IPMItool script.
Console Error Appears After Performing Backup

and Restore
CR 6847309
Issue: The following console error message might appear after backing up and
restoring the ILOM configuration.
bind (udp): Address already in use
Workaround: None. This is a benign error message.
Windows Server 2008 R2 Generates System Event
Log Warning Messages When Power Is Being
Limited by ILOM Power Management
CR 6881284
Issue: When power is being limited by the ILOM Power Management feature, the
Windows Server 2008 R2 operating system will generate warning messages in the
System Event Log informing the user that the processor(s) are being restricted.
Example Event:
The Speed of Processor xx in group x is being limited by system firmware. The

processor has been in this reduced performance state for xxxx seconds since last
report.
Workaround. None needed. These are expected events and are not indicative of a
problem.

This section describes updates or errors that have been found in the Oracle ILOM 3.0

Serial Port Sharing

As of version 3.0, ILOM supports the ability on some Sun servers to switch the serial
port output from the server between the SP console (NET MGT) and the host console
(COM1) By default, the SP console is connected to the system serial port. This
feature is beneficial for Windows kernel debugging, as it enables you to view non-
ASCII character traffic from the host console.
You can switch serial port output using either the ILOM web interface or the ILOM
command-line interface (CLI). For instructions, see the following sections:

■ “Switch Serial Port Output Using the Web Interface” on page 116
■ “Switch Serial Port Output Using the CLI” on page 116
Note – To determine whether serial port sharing is supported for your server in
ILOM 3.0, refer to the platform ILOM Supplement guide provided for your server.
Caution – You should set up the network on the SP before attempting to switch the
serial port owner to the host server. If a network is not set up, and you switch the
serial port owner to the host server, you will be unable to connect using the CLI or
web interface to change the serial port owner back to the SP. To return the serial port
owner setting to the SP, you will need to restore access to the serial port on the
server. For more details about restoring access to the server port on your server, see
the platform documentation supplied with your server.
▼ Switch Serial Port Output Using the CLI

1. Log in to the ILOM CLI.
2. To set the serial port owner, type:

-> set /SP/serial/portsharing /owner=host
Note – The serial port sharing value by default is owner=SP.
3. Use a dongle cable to connect a serial host to the server.

For details on how to use a dongle cable to attach devices to the server, see the
platform documentation supplied with your server.
▼ Switch Serial Port Output Using the Web

Interface
1. Log in to the ILOM web interface.
2. In the ILOM web interface, select the Configuration --> Serial Port tabs.
The Serial Port Settings page appears.
3. In the Serial Port Settings page, select Host Server as the serial port owner.
Note – The serial port sharing setting by default is Service Processor.
4. Click Save for the changes to take effect.
5. Use a dongle cable to connect the serial host to the server.

For details on how to use a dongle cable to attach devices to the server, see the
platform documentation supplied with your server.

CHAPTER 5
Updates to ILOM 3.0.8 Firmware

119
There are several new features integrated into the Oracle ILOM 3.0.8 release. The
following table lists those new features and points you to the sections that describe
the features.
Topics
Description Links
Enhanced web interface page that • “New System Summary Information (Overview
enables you to view and manage Tab)” on page 121
system summary information and
power-on settings from one page
New power management • “Power Management New Terminology and Web
terminology and web layout for SP Layout for the Server SP” on page 122
New IPMI power capping (Power • Oracle Integrated Lights Out Manager (ILOM) 3.0
Limit) capability and new IPMI Management Protocols Reference Guide
procedures for: (820-6413-11)
• Set Power-Limit Budget Activation
State
• Get Power-Limit Budget Wattage
• Set Power Limit Budget Wattage
New power capping (Power Limit) • Oracle Integrated Lights Out Manager (ILOM) 3.0
capability for SNMP Management Protocols Reference Guide
implementations. (820-6413-11)
For more information, see the
Hardware Control MIB for power
management data objects
New functionality added in ILOM for • “New System Banner Message Capability” on
system banner messages page 130
New ILOM web interface support for • “New Storage Monitoring Web Interface” on
Storage Monitoring page 134
New functionality added in ILOM to • “New WS-Management and CIM Support for
support WS-Management and CIM Managing Sun Hardware” on page 140
as a standard management interface
New SP History Log functionality • “New SP Console History Log Available on x86
added in ILOM for Oracle x86 servers Servers” on page 141
Note - This content is applicable to
Oracle SPARC servers as well.
New TPM management for SPARC • “New TPM Support for SPARC Servers” on
servers page 144
New System Summary Information
(Overview Tab)
Within the ILOM web interface, the System Information tab has been updated to
include a new Overview tab, which provides summary information about your
system properties and settings.
As of ILOM version 3.0.8, you can access the Overview tab to view the following
information about your system.
System Information: The system information fields identify the product name, part
number, and serial number of the Oracle system.
Status: The following status fields indicate the power and operational
state of your system.
• Power State – This field indicates the current power state of
your system and offers you the ability to control the system
power state from this tab. Alternatively, you can control the
system power state from the Remote Control Power tab.
• System Status – This field indicates the operational state of
your system and offers you the ability to view information
about faulted hardware components. Alternatively, you can use
the Fault Management tab to view components in a faulted
state.
SysFW Information: The SysFW information field indicates the system firmware
version embedded on a SPARC server. This field only applies to
SPARC servers.
ILOM Information: The ILOM information fields identify the IP address and host
name that are assigned to the SP and the current ILOM version
that is installed.
An example of the Overview tab is shown in FIGURE 5-1.
Chapter 5 Updates to ILOM 3.0.8 Firmware 121

FIGURE 5-1 Overview Tab Example - CMM ILOM Web Interface
Power Management New Terminology and Web

Layout for the Server SP
As of ILOM version 3.0.8, some of the Power Management terminology and settings
have changed on the web interface for the ILOM server SP. For more details about
these changes, see the following topics:
■ “New Web Layout and Terminology for the Server SP” on page 123
■ “Updated Power Allocation and Power Limit Procedures” on page 127
Note – The SP Power Management CLI terminology and targets have not changed
in ILOM 3.0.8. For details about using the SP Power Management CLI properties, see
Chapter 4.
Note – The CMM Power Management terminology and properties have not
changed in ILOM 3.0.8. For more information about using the CMM Power
Management properties, see Chapter 4.
New Web Layout and Terminology for the Server SP
A summary of the SP changes that were made in ILOM 3.0.8 to the Power
Management web interface tabs and settings is provided in TABLE 5-1.
TABLE 5-1 New Power Management Server SP Web Layout and Terminology for ILOM 3.0.8
Power Management
Tab Changes Made in ILOM 3.0.8 For details, see:
Consumption tab Some Power Management --> “Consumption Tab Changes Made in ILOM
Consumption tab settings for the server SP 3.0.8 for the Server SP” on page 123
have been renamed in ILOM 3.0.8.
Allocation tab A new Power Allocation tab and settings “Allocation Tab Changes in ILOM 3.0.8 for
are available for the server SP in ILOM the Server SP” on page 125
3.0.8.
The Power Allocation tab replaces the
Distribution tab that was previously
available in ILOM 3.0.6.
Limit tab A new Limit tab and settings are available “Limit Tab Changes in ILOM 3.0.8 for the
for the server SP in ILOM 3.0.8. Server SP” on page 125
The Limit tab settings replace the Budget
tab settings that were previously available
in ILOM 3.0.6
Consumption Tab Changes Made in ILOM 3.0.8 for the Server SP

Some of the server SP power management properties on the Consumption tab were
changed as of ILOM 3.0.8. For more information about these changes, see TABLE 5-2.
TABLE 5-2 Consumption Tab Server SP Settings Changes in ILOM 3.0.8
Consumption Tab Changes Details
Target Limit A new read-only property for Target Limit is available on the Power
(new property) Management --> Consumption tab as of ILOM 3.0.8.
The Target Limit (shown in FIGURE 5-2) property represents the
power consumption limit value that was configured for the server.
Note - The configuration options for the Target Limit property appear
on the Power Management --> Limit tab. For more details about the
Target Limit configuration options, see “Limit Tab Changes in ILOM
3.0.8 for the Server SP” on page 125.

TABLE 5-2 Consumption Tab Server SP Settings Changes in ILOM 3.0.8 (Continued)
Peak Permitted The Permitted Power property on the Power Management -->
(renamed property) Consumption tab in ILOM 3.0.4 (shown in FIGURE 3-1) was renamed to
Peak Permitted in ILOM 3.0.8.
The Peak Permitted read-only property (shown in FIGURE 5-2)
represents the maximum power the system can consume.
Note - For servers, the Peak Permitted value in ILOM is derived from the
System Allocated power and the Target Limit. For more details, see
“Advanced Server Power Budget Features” on page 102.
Allocated Power The read-only property for Allocated Power (shown in FIGURE 3-1)
(removed) was removed from the Power Management --> Consumption tab as of
ILOM 3.0.8 (shown in FIGURE 5-2).
Note - In ILOM 3.0.8, you can view Allocated Power values for the
system and for each component on the Power Allocation Plan page. For
more details, see “Allocation Tab Changes in ILOM 3.0.8 for the Server
SP” on page 125.
An example of the updated Power Management Consumption tab that is available

for the SP as of ILOM version 3.0.8 is shown in FIGURE 5-2.
FIGURE 5-2 Updated Power Management --> Consumption Tab - ILOM SP 3.0.8
Allocation Tab Changes in ILOM 3.0.8 for the Server SP
The Distribution tab that was previously available for the SP in ILOM 3.06 was
renamed in ILOM 3.0.8 to the Allocation tab (shown in FIGURE 5-3).
FIGURE 5-3 Power Management --> Allocation Tab - ILOM SP 3.0.8
The Allocation tab, in ILOM 3.0.8, provides all the same power requirement
information previously available on the Distribution tab in ILOM 3.0.6 (shown in
FIGURE 4-1). However, the Allocation tab uses two tables to separate the system
power requirements from the component power requirements (shown in FIGURE 5-3).
Limit Tab Changes in ILOM 3.0.8 for the Server SP

The Budget tab that was previously available for the SP in ILOM 3.0.6 was renamed
in ILOM 3.0.8 to the Limit tab (shown in FIGURE 5-4).

The Limit tab in ILOM 3.0.8 provides all the same SP power capping information
that was previously available on the Budget tab. However, some of the previous
power capping properties have been renamed on the Power Management --> Limit
tab in ILOM 3.0.8. For more details about the property changes made to the Limit
tab, see TABLE 5-3.
TABLE 5-3 Limit Tab Server SP Setting Changes in ILOM 3.0.8
Limit Tab Property Changes Details
Power Limiting The Activation State property on the Budget tab in ILOM 3.0.6
(renamed property) (shown in FIGURE 4-2) was renamed to Power Limiting on the Power
Management --> Limit tab in ILOM 3.0.8.
The Powering Limiting [] enable property (shown in FIGURE 5-4)
when selected enables the power limit configuration.
Status Error Message The Status read-only property previously available on the Budget tab
(replaces Status property) in ILOM 3.0.6 (shown in FIGURE 4-2) was replaced by a new Status
Error Message on the Power Management --> Limit tab or
Consumption tab in ILOM 3.0.8.
The new Status Error Message only appears on your system when
ILOM fails to achieve the power limit that was configured.
Target Limit The Power Limit property on the Budget tab in ILOM 3.0.6 (shown in
(renamed property) FIGURE 4-2) was renamed to Target Limit on the Power Management
--> Limit tab in ILOM 3.0.8.
The Target Limit property (shown in FIGURE 5-4) enables you to
specify the a target limit value in watts or as a percentage. This value
must be a range between the minimum and maximum system power.
Policy The Time Limit property on the Budget tab in ILOM 3.0.6 (shown in
(renamed advanced property) FIGURE 4-2) was renamed to Policy on the Power Management -->
Limit tab in ILOM 3.0.8.
The Policy property (shown in FIGURE 5-4) enables you to specify the
type of power capping to apply:
• Soft - Only cap if actual power exceeds Target Limit – If you
enabled the soft cap option, you can configure the grace period for
capping Actual Power to within the Target Limit.
- System Default – Platform selected optimum grace period.
or
- Custom – User-specified grace period.
• Hard - Fixed cap keeps Peak Permitted power under Target
Limit – If you enabled this option, power capping is permanently
applied without a grace period.
An example of the new Power Management --> Limit tab properties that are
available for the SP as of ILOM version 3.0.8 is shown in FIGURE 5-4.
FIGURE 5-4 Power Management --> Limit Tab - ILOM SP 3.0.8
Updated Power Allocation and Power Limit Procedures

The following procedures were updated to reflect the new power management
terminology and web layout changes made for the server SP in ILOM 3.0.8.
■ “View Server Power Allocation Plan Using the Web Interface” on page 127
■ “Configure Server Power Limit Properties Using the Web Interface” on page 128
▼ View Server Power Allocation Plan Using the Web

Interface
2. Select the Power Management --> Allocation tabs.

The Power Allocation Plan page appears (see FIGURE 5-3).
3. In the Power Allocation Plan page, view the following system power
requirements for power capacity planning:
■ System Power Map – This table reflects the total power allocated value in
wattage for the following system power properties: Allocated Power,
Installed Hardware Minimum, Peak Permitted Power, and Target
Limit.

■ Per Component Power Map – This table reflects the allocated power wattage
value for each server component category (for example, memory) and each
server component (for example ME_PO_D0). It also identifies whether the
allocated power value can be capped.
▼ Configure Server Power Limit Properties Using the

Web Interface
Note – To change any server power limit property values in ILOM requires an
2. In the ILOM web interface, select the Power Management --> Limit tabs.
The Power Limit page appears (see FIGURE 5-4).
3. In the Power Limit page, view or modify any of the following power limit
properties (see TABLE 5-4).
TABLE 5-4 Power Limit Property Descriptions
Power Limit Property Description
Power Limiting Enable this property to enable the power limit

configuration.
Target Limit Set a Target Limit in watts or as a percentage. This
value should reflect a range between the Installed
Hardware Minimum Power and the Allocated Power.
Note - You can view the Installed Hardware Minimum
Power value and the Allocated Power value on the
Power Management --> Allocation tab. For more details,
see “Allocation Tab Changes in ILOM 3.0.8 for the Server
SP” on page 125.
TABLE 5-4 Power Limit Property Descriptions (Continued)
Power Limit Property Description
Policy The Policy property enables you to configure the power

capping policy. In the Policy property, specify which of
the following types of power capping you want to apply:
• Soft - Only cap if actual power exceeds Target
Limit. – If you enabled the soft cap option, you can
configure the grace period for capping Actual Power
to within the Target Limit.
- System Default – Platform selected optimum grace
period.
or
- Custom – User-specified grace period.
• Hard - Fixed cap keeps Peak Permitted power
under Target Limit. – If you enable this option,
power capping is permanently applied without a grace
period.
Violation Actions The Violation Actions property enables you to specify the
settings you want ILOM to take if the power limit cannot
be achieved within the set grace period.
You can choose to specify one of the following actions:
• None – If you enable this option and the power limit
cannot be achieved, ILOM will display a Status
Error Message to notify you that ILOM is unable to
achieve the power capping limit specified.
or
• Hard-Power-Off – If this option is chosen and the
power limit cannot be achieved, ILOM takes the
following actions:
* Display a Status Error Message.
* Hard-power-off the server.
Note - The default option for Violation Actions is None.
Note – For best power capping performance, the default values are recommended
for all advanced server power limit properties.
4. To apply the power limit property changes, click Save.

New System Banner Message Capability
System administrators, as of ILOM 3.0.8, can create banner messages and display
them on the Login page or immediately after logging in to ILOM.
Creating and displaying banner messages in ILOM is optional. However, system

administrators can use this capability whenever there is a need to share information
about system updates, system policies, or other important announcements.
Examples of where (Login page or after login) the banner messages appear in ILOM
after they have been created are shown in FIGURE 5-5, FIGURE 5-6, and FIGURE 5-7.
For instructions about how to create the banner messages in ILOM, see “Configuring
Banner Messages” on page 132.
FIGURE 5-5 Login Page – Connect Banner Example – Web Interface
FIGURE 5-6 After Logging In - Banner Message Example - Web Interface
FIGURE 5-7 Banner Message Example - CLI

Configuring Banner Messages
Use one of the following procedures to configure a banner message in ILOM:
■ “Configure Banner Messages Using the CLI” on page 132
■ “Configure Banner Messages Using the Web Interface” on page 133
Before You Begin

■ To configure a banner message in ILOM requires an Admin (a) role user account.
▼ Configure Banner Messages Using the CLI

1. Log in to the ILOM SP or CMM CLI.
2. Use the show command to display the current banner properties and
supported commands.
For example:
-> show /SP/preferences/banner
/SP/preferences/banner
Targets:
Properties:
connect_message = (none)
login_message = (none)
login_message_acceptance = disabled
Commands:
cd
set
show
3. To create a banner message, perform any of the following tasks:
Tasks Instructions
To create a Type:
banner -> set /SP/preferences/banner connect_message=message
message to Where message equals the content you want to appear on the
appear on the Login page.
Login page
To create Type:
banner -> set /SP/preferences/banner login_message=message
message to Where message equals the content you want to appear after
appear in a logging in to ILOM.
dialog box
after logging
in to ILOM.
Note - Messages are limited to a 1000 characters. To create a new line within the message,
use the following CLI characters: /r or /n.
4. To enable the system to display the banner messages, type:
-> set /SP/preferences/banner/ login_message_acceptance=enabled
5. To disable the system from displaying the banner messages type:
-> set /SP/preferences/banner/ login_message_acceptance=disabled
▼ Configure Banner Messages Using the Web Interface

Note – Alternatively, you can create banner messages for a CMM by logging in to
the CMM ILOM web interface.
2. In the ILOM web interface, click System Information --> Banner Messages.
3. In the Banner Message page, do the follow:
Task Instructions
To create a banner message to appear Enter the message in the Connect Message text
on the Login page box.
To create banner message to appear in Enter the message in the Login Message text
a dialog box after logging in to ILOM. box.

4. In the Login Message Acceptance check box, select the check box to enable the
system to display the banner message(s).
5. Click Save.
New Storage Monitoring Web Interface

The Storage Monitoring features in ILOM enable you to view and monitor storage
details that are associated with system hard disk drives (HDDs) and RAID
controllers. As of ILOM version 3.0.8, you can access these features from the ILOM
web interface. Prior to ILOM 3.0.8, these features were only accessible, in ILOM
3.0.6, through the ILOM CLI.
Note – For more information about using the ILOM CLI to monitor storage details
about HDDs and RAID controllers, see “Show Property Details in ILOM for HDDs
and RAID Controllers Using the CLI” on page 83.
The type of storage details that you can monitor from the ILOM web interface are
explained in the following sections:
■ “RAID Controller Details” on page 134
■ “Disks Attached to RAID Controllers Details” on page 136
■ “RAID Controller Volume Details” on page 138
RAID Controller Details

From the Storage --> RAID --> Controller tab in ILOM, you can access configuration
information about each RAID controller installed on your system. This information
includes:
■ RAID controller configuration details that describe the RAID levels, maximum
number of disks, and the maximum number of RAIDs that can be configured on
each installed RAID controller. For example, see FIGURE 5-8.
■ RAID controller FRU properties and values for each installed RAID controller. For
example, see FIGURE 5-9.
■ RAID controller topology details that display information about attached disks,
configured RAID volumes, and disks that are part of a RAID. For example, see
FIGURE 5-10.
FIGURE 5-8 RAID Controller Configuration Details
FIGURE 5-9 RAID Controller FRU Properties and Values

FIGURE 5-10 RAID Controller Topology Details
Disks Attached to RAID Controllers Details

From the Storage --> RAID --> Disks tab in ILOM, you can access configuration
information about the disks that are attached to your RAID controllers. This
information includes:
■ Disk configuration details for each disk attached to a RAID controller. These
details include the disk name, status, serial number, capacity, and device name.
For example, see FIGURE 5-11.
■ Disk FRU properties and values for each disk attached to a RAID controller. For
example, see FIGURE 5-12.
FIGURE 5-11 Disk Details - Attached to RAID Controller
FIGURE 5-12 Disk FRU Properties and Values
RAID Controller Volume Details

From the Storage --> RAID --> Volume tab in ILOM, you can access configuration
information about the RAID volumes that are configured on RAID controllers. This
information includes:

■ Volume configuration details for each volume configured on a RAID controller.
These details include the volume name, status, RAID level, capacity, and device
name. For example, see FIGURE 5-13.
■ Volume properties and values for each volume configured on a RAID controller.
For example, see FIGURE 5-14.
FIGURE 5-13 RAID Volume Configuration Details
FIGURE 5-14 RAID Volume Properties and Values
View and Monitor Storage Details Using the Web

Interface
Refer to the following procedures to view and monitor details about the following
storage components:
■ “View and Monitor RAID Controller Details Using the Web Interface” on
page 139
■ “View and Monitor Details for Disks That Are Attached to RAID Controllers
Using the Web Interface” on page 140
■ “View and Monitor RAID Controller Volume Details Using the Web Interface” on
page 140
Before You Begin

■ Ensure that the Storage Monitoring feature is supported on your Oracle server.
For details, see the ILOM Supplement guide for your server.
■ For Oracle servers supporting the Storage Monitoring feature, you must
download and install a system management pack prior to using the Storage
Monitoring features in ILOM. For information about how to download this
management pack, see Sun Server Hardware Management Pack Users Guide (821-
1609).
▼ View and Monitor RAID Controller Details Using the

Web Interface
1. Log in to the ILOM SP or CMM web interface.
2. In the ILOM web interface, click the Storage --> RAID --> Controllers tab.
The Controller Monitoring page appears listing the configuration details for the
RAID controllers installed on your system. For example, see FIGURE 5-8 - “RAID
Controller Configuration Details” on page 135.
3. To access additional details about an installed RAID controller, do the

following:
■ To access FRU properties and values, click the RAID Controller name.
A dialog appears listing the RAID Controller FRU properties and values. For
example, see FIGURE 5-9 - “RAID Controller FRU Properties and Values” on
page 135.
■ To access topology information about a RAID controller, select the radio button
next to the RAID controller name, then click Show Topology.
The topology details for that RAID controller appear. For example, see
FIGURE 5-10 - “RAID Controller Topology Details” on page 136.

▼ View and Monitor Details for Disks That Are Attached
to RAID Controllers Using the Web Interface
2. In the ILOM web interface, click the Storage --> RAID --> Disks tab.
The Disks Monitoring page appears listing the configuration details for the disks
attached to RAID controllers. For example, see FIGURE 5-11 - “Disk Details -
Attached to RAID Controller” on page 137.
3. To view the FRU properties and values associated with a disk, click the disk
name.
A dialog appears listing the disk FRU properties and values. For example, see
FIGURE 5-12 - “Disk FRU Properties and Values” on page 137.
▼ View and Monitor RAID Controller Volume Details

2. In the ILOM web interface, click the Storage --> RAID --> Volumes tab.
The Volume Monitoring page appears listing the configuration details for the
RAID volumes configured on the RAID controllers. For example, see FIGURE 5-13 -
“RAID Volume Configuration Details” on page 138.
3. To view the FRU properties and values associated with a volume, click the
volume name.
A dialog appears listing the volume properties and values. For example, see
FIGURE 5-14 - “RAID Volume Properties and Values” on page 138.
New WS-Management and CIM Support for

Managing Sun Hardware
As of ILOM version 3.0.8, support for managing Sun hardware using
WS-Management and Common Information Model (CIM) is available. For more
information about WS-Management and CIM, see the Oracle Integrated Lights Out
Manager (ILOM) 3.0 Management Protocols Reference Guide (820-6413-11).
New SP Console History Log Available on x86
Servers
The SP Console History Log enables you to view system console messages that are
stored by ILOM within a 1-Mbyte persistent log file.
As of ILOM version 3.0.8, you can display the console messages stored in the SP
Console History Log file from the ILOM CLI on all Oracle x86 servers. Prior to ILOM
3.0.8, the SP Console History Log file was only viewable in ILOM on Oracle SPARC
servers.
Note – The SP Console History Log feature is not available for use from the ILOM
web interface.
For instructions about how to display log entries in the SP Console History Log file,
see the following procedure.
Before You Begin

■ You must have Console (c) role user account to display the entries stored in the
SP Console History Log file.
View and Manage SP Console History Log Entries Using

the ILOM CLI
1. Log in to the SP ILOM CLI.
2. Use the show command to display the SP Console target, properties, and
commands.
For example:

-> show /SP/console
/SP/console
Targets:
history
Properties:
line_count = 0
pause_count = 0
start_from = end
Commands:
cd
show
start
stop
->
3. Use the help command to view details about the SP Console target and
properties.
For example:
-> help /SP/console
/SP/console: Redirection of console stream to SP

Targets:
history: console history
Properties:
line_count: total number of lines to display
line_count: Possible values = 0-2048 where 0 means no limit
line_count: User role required for set = c
pause_count: number of lines to display before each pause

pause_count: Possible values = 0-2048 where 0 means no limit
pause_count: User role required for set = c
start_from: from which end of the available history to list

start_from: Possible values = beginning,end
start_from: User role required for set = c
4. Use the set command to specify the property values that you want ILOM to
use when displaying the entries in the SP Console History Log file.
For example:
■ set command usage:
set [target] <property>=<value> [<property>=<value>...]
■ At the prompt, you would type the SP console target and one or more display
property values as follows:
-> set /SP/console property=value
-> set /SP/console property=value property=value
-> set /SP/console property=value property=value property=value
Where property and value can be any of the following parameters specified in the
following table.
Property Values Example
line_count Accepts a line value To specify ILOM to display four lines of the SP Console History Log,
within the range of 0 you would type:
to 2048, where 0 -> set /SP/console line_count=4
means no limit.
Note - The default
value for
line_count is 0.
pause_count Accepts a pause To specify ILOM to display four lines of the SP Console History Log
value within the and pause the display after displaying two lines, you would type:
range of 0 to 2048, -> set /SP/console line_count=4 pause_count=2
where 0 means not to
pause the display.
Note - The default
value for
pause_count is 0.
start_from Values include: To specify ILOM to display the first four lines of the SP Console History
• end – The last line Log and pause the display after displaying two lines, you would type:
(most recent) in -> set /SP/console line_count=4 pause_count=2
the history log. start_from=beginning
• beginning - The
first line in the
history log.
Note - The default
value for
start_from is end.
The UTC timestamps recorded in the SP Console History Log reflect the local time
configured on the server.

New TPM Support for SPARC Servers
From the ILOM CLI or web interface, you can manage the support of the TPM
(Trusted Platform Module) state on an Oracle Solaris TPM-enabled SPARC server.
Note – The TPM feature in ILOM is available as of ILOM version 3.0.8 for SPARC
servers only.
For instructions on how to enable or disable the TPM state in ILOM for a Solaris
TPM-enabled SPARC server, see the following topics:
■ “Control TPM State on SPARC Servers Using the CLI” on page 145
■ “Control TPM State on SPARC Server Using the Web Interface” on page 147
Before You Begin

■ The SPARC server should be running a version of Oracle Solaris that supports
TPM.
For more information about configuring TPM support in Solaris, see the Solaris
documentation or the platform documentation shipped with your server.
■ ILOM version 3.0.8 (or subsequent version) is required to be installed on the
SPARC server SP.
■ You need to have the Reset and Host Control (r) user account to modify the TPM
settings in ILOM.
▼ Control TPM State on SPARC Servers Using the
CLI
1. Log in to the SP ILOM CLI.
2. Use the show command to display the TPM target, properties, and commands.
For example:
-> show /HOST/tpm
/HOST/tpm
Targets:
Properties:
activate = false
enable = false
forceclear = false
Commands:
cd
set
show
->
3. Use the help command to view details about the TPM target and properties.
For example:

-> help /HOST/tpm
/HOST/tpm : Host TPM (Trusted Platform Module) Knobs

Targets:
Properties:
activate : TPM Activate Property. If set to TRUE, then TPM
will be activated if the 'enable' property is also set to TRUE.
activate : Possible values = true, false
activate : User role required for set = r
enable : TPM Enable Property. If not enabled, then TPM

configuration changes can not be made.
enable : Possible values = true, false
enable : User role required for set = r
forceclear : TPM Forceclear Property. If set to TRUE, then

TPM state will be purged on the next power on event if and only if
the 'enable' property is set to TRUE.
forceclear : Possible values = true, false
forceclear : User role required for set = r
4. Use the set command to specify the TPM property values.

For example:
■ set command usage:
set [target] <property>=<value> [<property>=<value>]
■ At the prompt, you would type the TPM target and one or more property
values as follows:
-> set /SP/console property=value
-> set /SP/console property=value property=value
Where property and value can be any of the following parameters specified in the
following table:
Property Values Example
enable Accepts true or false. To enable the TPM state, you would type:
Note - The default value -> set /HOST/tpm enable=true
for enable is false. Note - To apply the enabled TPM state on the SPARC server the next
time the server powers on, you must activate it. For more details, see
activate property.
activate Accepts true or false. To enable the TPM state and activate this enabled state on the
Note - The default value SPARC server the next time the server powers on, you would type:
for activate is false. -> set /HOST/tpm enable=true activate=true
forceclear Accepts true or false. To purge (disable) an enabled TPM state on the SPARC server the
Note - The default value next time the server powers on, you would type:
for forceclear is -> set /HOST/tpm forceclear=true
false. Note - forceclear will only set to true, if enable and activate
are also set to true.
▼ Control TPM State on SPARC Server Using the

Web Interface
2. In the ILOM web interface, click the Remote Control --> TPM tab.
The TPM Settings page appears.
3. In the TPM Settings page, do one of the following:

■ To enable the TPM state and activate this enabled state on the SPARC server
the next time it is powered on, select True for the following TPM settings:
■ Enable – Select the Enable True check box to enable the TPM state on the
SPARC server.
■ Activate – Select Activate True check box to activate the configuration
change on the SPARC server the next time the server powers on.
or
■ To purge (disable) an enabled TPM state on the SPARC server the next time the
server powers on, select True for following three TPM settings:
■ Enable – Select the Enable True check box to disable the TPM state on the
SPARC.
■ Activate – Select the Activate True check box to activate the configuration
change on the SPARC server.

■ Forceclear – Select Forceclear True check box to purge the enabled TPM
state from the SPARC server the next time the server powers on.

Topics
Description Links
Time zone CLI setting issue resolved • “Invalid Time Zone Settings in ILOM CLI” on
page 148
Snapshot properties are not • “Snapshot Properties Are Not Persistent After a
persistent after resetting the SP Reset” on page 148
Invalid Time Zone Settings in ILOM CLI

CR 6871128
Issue: Incomplete time zone names were accepted by ILOM for the CLI target:
SP/clock/timezone. An incomplete time zone name could cause the system to
use the time zone for Greenwich Mean Time (GMT).
Update: This issue is fixed in the ILOM 3.0.8 release. The ILOM CLI only accepts
and validates complete time zone names.
Snapshot Properties Are Not Persistent After a

Reset
Issue: If you use the CLI to change the Snapshot property values and then reset the
SP, the Snapshot property values revert to their default property values.
Update: The Snapshot feature in ILOM is working as designed. The Snapshot

properties are not persistent after resetting the SP.
Topics
Description Links
The 64-bit JRE is not supported for • “Storage Redirection Not Supported With 64-bit
Storage Redirection JRE” on page 149
Long delay populating storage • “5-Minute Delay to View Storage Monitoring
monitoring devices after performing Information” on page 150
upgrade
ILOM version not shown when • “ILOM Version Not Shown When Using SIA to
upgrading ILOM using SIA and an Upgrade ILOM From an Inband Management
inband management interface Interface” on page 150
Storage Redirection Not Supported With 64-bit

JRE
CR 6800702 and CR 6805732
Issue: An attempt to start Storage Redirection might fail when using a 64-bit Java
runtime environment (JRE). Since the 64-bit JRE is the default on a 64-bit system,
you will need to have the 32-bit JRE installed as well. When using a 64-bit JRE to
start Storage Redirection, the following error message appears:
"Unsupported platform"
Workaround: Install a 32-bit JRE on the 64-bit system. JREs can be downloaded from
this site: http://java.com/en/download/index.jsp

5-Minute Delay to View Storage Monitoring
Information
CR 6870530
Issue: You might experience up to a 5-minute delay before storage monitoring

information is present or up to date in the ILOM CLI or the web interface. This delay
typically occurs after:
■ Upgrading to ILOM 3.0.6 (or later) and installing the required System
Management Pack.
or
■ Querying the system after updates were made to the RAID or disk information.
Note – The Storage Monitoring feature is not available on all Oracle servers. To
determine whether your server is enabled to support this feature, refer to the ILOM
Supplement guide for your server.
Note – If the Storage Monitoring feature is available on your server, a System

Management Pack is required to be installed prior to using the Storage Monitoring
feature. For more information about the System Management pack required for your
server, refer to the ILOM Supplement guide for your server.
Workaround: There is no workaround. This 5-minute delay only occurs after

installation of the required System Management Pack or after RAID or disk updates
have been made to the system.
ILOM Version Not Shown When Using SIA to

Upgrade ILOM From an Inband Management
Interface
CR 6867109
Issue: When upgrading ILOM from the Sun Installation Assistant (SIA) using the
inband interface, SIA might not (on some Oracle servers) display the running
version of ILOM.
Workaround:Use the ILOM web interface to determine the running version of

ILOM.

Topics
Description Links
Documentation update describing • “SP Management Port - Recommended Practice

recommended settings for spanning for Spanning Tree Parameters” on page 152
tree settings
Documentation update to describe • “New ILOM SP Network Port” on page 111
the latest default network ports used
by ILOM as of ILOM version 3.0.6
Documentation update for new • “Snapshot FRUID Data Set Option for Service”
FRUID data set option available in on page 25
the Snapshot Utility as of ILOM
version 3.0.3.
Renamed ILOM IPMI and SNMP • “Renamed ILOM SNMP and IPMI Procedures
Procedures Guide (820-6413-10) to Guide to Management Protocols Reference
ILOM Management Protocols Guide” on page 152
Reference Guide (820-6413-11)

SP Management Port - Recommended Practice for
Spanning Tree Parameters
Since the SP management network port is not designed to behave like a switch port,
the SP management port does not support switch port features like spanning-tree
portfast.
When configuring spanning tree parameters, consider these recommendations:

■ The port used to connect the SP management network port to the adjacent
network switch should always treat the SP management network port as a host
port.
■ The spanning tree option on the port connecting to the adjacent network switch
should either be disabled entirely or at a minimum configured with the following
parameters:
Spanning Tree Parameter Recommended Setting
portfast Enable this interface to immediately move to a forwarding state.

bpdufilter Do not send or receive BPDUs on this interface.
bpduguard Do not accept BPDUs on this interface.
cdp Do not enable the discovery protocol on this interface.
Renamed ILOM SNMP and IPMI Procedures

Guide to Management Protocols Reference Guide
As of ILOM version 3.0.8, the guide for the Oracle Integrated Lights Out Manager
(ILOM) 3.0 SNMP and IPMI Procedures Guide (820-6413-10) has been renamed to the
Oracle Integrated Lights Out Manager (ILOM) 3.0 Management Protocols Reference Guide
(820-6413-11).
The guide was renamed in ILOM version 3.0.8 to include information about
monitoring Oracle hardware from other industry standard interfaces like
WS-Management and CIM.
As of ILOM version 3.0.8, the Oracle Integrated Lights Out Manager (ILOM) 3.0
Management Protocols Reference Guide (820-6413-11) includes information about:
■ IPMI
■ SNMP
■ WS-Management and CIM

CHAPTER 6

155
There are several new features integrated into the ILOM 3.0.9 release. The following
table lists those new features and points you to the sections that describe the
features.
Topics
Description Links
New NEM firmware update • “New NEM Firmware Management Capability

capability for modular chassis for Oracle Modular Chassis Systems” on
systems page 156
New international keyboard support • “New International Keyboard Support for ILOM
for ILOM Remote Console Remote Console” on page 162
New system uptime display available • “New System Uptime Display in ILOM CLI and
in ILOM CLI and web interface Web Interface” on page 163
Support for Microsoft Windows 7 • “ILOM Remote Console Supports Microsoft
and Internet Explorer 8 Clients Windows 7 and Internet Explorer 8 Clients” on
page 164
New NEM Firmware Management Capability for

Oracle Modular Chassis Systems
As of ILOM 3.0.9, some of the Oracle modular chassis systems will support a new
firmware capability that enables you to manage firmware updates for Network
Express Modules (NEMs). Prior to ILOM 3.0.9, NEM firmware updates were not
supported from ILOM.
Note – For more information about which Oracle modular chassis systems and
NEMs support the new NEM firmware update functionality in ILOM, refer to the
Oracle Integrated Lights Out Manager (ILOM) CMM Administration Guide for Sun Blade
6000 and Sun Blade 6048 Modular Systems (820-0052).
You can perform a NEM firmware update directly from the ILOM CLI or web
interface. Supported file transfer methods for uploading the firmware package to the
NEM include:
• TFTP • HTTPS
• FTP • SFTP
• SCP • Browser*
• HTTP
Note - * The Browser local file transfer option is only available from the ILOM web
interface.
For more information about how to perform the NEM firmware update from the
ILOM web interface or CLI, see the following topics:
■ “Before You Begin” on page 157
■ “Update NEM Firmware Using the CLI” on page 157
■ “Update NEM Firmware Using the Web Interface” on page 159
Before You Begin

■ From the NEM’s vendor product download web site, download the NEM
firmware update package to a system on your network where you can later gain
access to it from ILOM.
■ To update the NEM firmware in ILOM, you need the Admin (a) role enabled.
▼ Update NEM Firmware Using the CLI

Note – If your Oracle system is an SMP server that uses a modular system chassis
without a CMM, you will need to connect to the ILOM SP CLI. All other Oracle Sun
Modular 6000 Series Chassis Systems that have CMMs must connect to the ILOM
CMM CLI.
2. Use the cd command to navigate to the NEM requiring the firmware update.
For example:
cd /SYS/NEM#
Where # is the slot location where the NEM is installed in the chassis.
If your chassis system does not support multiple NEMs and one NEM is
supported, the NEM location would equal 0. For this example, you would type:
cd /SYS/NEM0

3. Type the show command to view the NEM properties and the firmware version
presently installed on the NEM.
For example, see the NEM show property output below for the Sun Fire 4800
System.
Note – The fru_extra_1= property field identifies the firmware version presently
installed on the NEM.
-> cd /SYS/NEM0
/SYS/NEM0
-> show
/SYS/NEM0
Targets:
PRSNT
STATE
ERR
OK
SERVICE
OK2RM
LOCATE
Properties:
type = Network Express Module
ipmi_name = NEM0
fru_manufacturer = VENDOR_Name
fru_part_number = 511-1056-04
fru_extra_1 = FW 5.3.1.0
fault_state = OK
load_uri = (none)
clear_fault_action = (none)
power_state = On
Commands:
cd
load
reset
set
show
start
stop
4. Use the load command to upload and install the firmware update package on
the NEM.
For example, you would type:
load_uri=uri
Where uri equals the URI transfer method and location of the firmware package.
See the following CLI load examples for each supported file transfer method
Transfer
Method CLI load Command Examples
TFTP load_uri=tftp://ip_address/rom_nem.pkg
FTP load_uri=ftp://username:password@ip_address/rom_nem.pkg
SCP load_uri=scp://username:password@ip_address/rom_nem.pkg
HTTP load_uri=http://username:password@ip_address/rom_nem.pkg
HTTPS load_uri=https://username:password@ip_address/rom_nem.pkg
SFTP load_uri=sftp://username:password@ip_address/rom_nem.pkg
Where:
■ ip_address is the IP address of the system where the file is stored.
■ username is the login user name to the system where the file is stored.
■ password is the login password to the system where the file is stored.
■ rom_nem.pkg is the name of the firmware update package.
The user name and password for HTTP and HTTPS are optional.
Note – Alternatively, you can use the set and load commands in the ILOM CLI to
specify the path of the NEM location, as well as the location of the firmware update
package to upload. For example: set /SYS/NEM#/load_uri=uri
5. Wait a few moments for ILOM to confirm the completion of the firmware
update process.
A success or failure status appears.
6. Use the show command to view and confirm the firmware version that is
installed on the NEM.
▼ Update NEM Firmware Using the Web Interface


Note – If your Oracle system is an SMP server that uses a modular system chassis
without a CMM, you will need to connect to the ILOM SP web interface. All other
Oracle Sun Modular 6000 Series Chassis Systems that have CMMs must connect to
the ILOM CMM web interface.
2. In the ILOM web interface, click the System Information --> Components tab.
The Components page appears.
3. In the Component Status table, do the following:
a. Select the radio button for the NEM that you want to update.
b. Click the NEM name appearing in the Component Name column to view the
firmware version presently installed on the NEM, then click Close to dismiss
the dialog.
c. In the Actions drop-down list box, select Update Firmware to initiate the
firmware update process for the NEM.
The Upload Firmware dialog appears.
4. In the Upload Firmware dialog, do the following:
a. Select the Upload Transfer Method from the drop-down list box.
b. Specify the required fields for the selected transfer method as follows:
Transfer Method Option Required Field Instructions
Browser Select File Use the Browse button to

specify the location of the
NEM firmware update
package.
FTP, SCP, HTTP, HTTPS, Host Specify the IP address of the
TFTP, SFTP host system where the NEM
firmware update package is
stored.

Transfer Method Option Required Field Instructions
FTP, SCP, HTTP, HTTPS, Filepath Specify the complete path to

TFTP, SFTP where the NEM firmware
update package is stored.
FTP, SCP, HTTP, HTTPS, Username Specify the login user name
SFTP to the system where the
NEM firmware update
package is stored.
FTP, SCP, HTTP, HTTPS, Password Specify the login password
SFTP to the system where the
NEM firmware update
package is stored.
5. Wait a few moments for ILOM to confirm the completion of the firmware
update process.
A success or failure status appears in the Upload Firmware dialog.
New International Keyboard Support for ILOM

Remote Console
As of ILOM 3.0.9, the ILOM Remote Console fully supports the use of all characters
on the following international keyboards.
■ Swedish Keyboard
■ Swiss-French Keyboard
■ Finnish Keyboard
Note – Prior to ILOM 3.0.9, the ILOM Remote Console did not support the use of all
the international characters on the Swedish, Swiss-French, and Finnish keyboards.
(CR 6781995, CR 673081, CR 6824306).
New System Uptime Display in ILOM CLI and
Web Interface
As of ILOM 3.0.9, ILOM provides a new capability in the CLI and web interface that
enables you to determine the amount of time your system has been up and running
since it last powered-on or restarted.
For instructions for viewing the system Uptime display in ILOM, see the following
procedures:
■ “View System Uptime Using the CLI” on page 163
■ “View System Uptime Using the Web Interface” on page 164
▼ View System Uptime Using the CLI

2. To display the properties associated with the system clock, type:

-> show /SP/clock
For example:
-> show /SP/clock
/SP/clock
Targets:
Properties:
datetime = Thu Oct 22 10:19:46 2009
timezone = GMT (GMT)
uptime = 5 days, 22:55:16
usentpserver = disabled
Commands:
cd
set
show

▼ View System Uptime Using the Web Interface
2. In the ILOM web interface, click the System Information --> Overview tab.
The System Overview page appears displaying the Uptime value in the third field
from the bottom of the page.
ILOM Remote Console Supports Microsoft

Windows 7 and Internet Explorer 8 Clients
As of ILOM 3.0.9, the Remote Console feature in ILOM supports Microsoft Windows
7 and Internet Explorer 8 operating system clients.
Specific change request (CR) identification number and workaround for the issues
Topics
Description Links
Remote Console resolved issue • “Unrecoverable ILOM Remote Console Sessions

(Fixed)” on page 165
Unrecoverable ILOM Remote Console Sessions

(Fixed)
CR 6867870
Issue: Prior to ILOM 3.0.6, some users experienced problems when recovering an
inactive ILOM Remote Console session to a host and were required, as a
workaround, to reboot the host server SP to recover the session. For further details
about this problem and the workaround, see “Unrecoverable ILOM Remote Console
Sessions” on page 74 in the Known Issues section of Chapter 3.
Update: A fix that no longer requires the rebooting of the SP to recover an inactive
Remote Console session is available for all Oracle server systems shipping with (or
supporting) one of the following ILOM firmware releases:
■ ILOM 3.0.6
■ ILOM 3.0.8
■ ILOM 3.0.9
If your server has ILOM 3.0.6 or later installed, the Oracle ILOM Remote Console
could take up to five minutes to release and recover an inactive session. However, if
the host server is powered off, the recovery time for the Remote Console session can
take approximately 15 minutes. Note that the recovery time for the Remote Console

session is dependent on the amount of video traffic that is present. The following
table provides a guideline for how long the ILOM Remote Console might take to
release and recover a session.
Estimated Recovery Time

for Remote Console
Video Screen Traffic Session Console or Host Scenario
Extremely High Approximately 10 Remote Console has an xterm

(>30KB per seconds of seconds window running “ls -R /”
video traffic between host
system and SP)
High (1KB per seconds Approximately 3 Remote Console display is dynamic.
between host system and minutes For example: blinking mouse cursor
SP)
Regular (500 bytes per Approximately 5 Remote Console display is static. For
seconds between host minutes example, it has no keyboard, mouse
system and SP) activity or any real-time graphical
display.
Low (100 bytes per seconds Approximately 11 Remote Console has a black or blank
between host system and minutes display.
SP)
Very Low (7 bytes per Approximately 15 Host is powered off.
seconds between host minutes
system and SP)
None (0 bytes between host Approximately 6 Remote Console session is in
system and SP) minutes suspend mode (inactive tab).
Topics
Description Links
ILOM displays null FRU data fields • “DIMM FRU Data Fields Are Null After
Downgrading or Upgrading SP Firmware
Between 3.0.3 and 3.0.9” on page 167
Garbage output appears for invalid • “Invalid Help Command (help /SP
Help command syntax system_contact=test) Results in Garbage
Output” on page 168
Unable to collect SP data with • “Service Snapshot Utility Unable to Collect SP
Snapshot Utility when web browser Data When IE Web Browser Security Option Is
security setting is enabled Enabled” on page 168
DIMM FRU Data Fields Are Null After

Downgrading or Upgrading SP Firmware
Between 3.0.3 and 3.0.9
CR 691359, 6850456, and 6916007
Issue: On some platform servers, ILOM displays null DIMM FRU data fields after
upgrading or downgrading the ILOM SP firmware (between 3.0.3 and 3.0.9) with the
Delay BIOS Update option enabled.
Workaround: Perform the following steps:
1. Power off the host before downgrading or upgrading the firmware between
ILOM 3.0.3 and 3.0.9.
2. Do not enable the firmware option to Delay BIOS Update when downgrading
or updating the ILOM firmware.

Invalid Help Command (help /SP
system_contact=test) Results in Garbage
Output
CR 6884556 and 6923383
Issue: Using an invalid help command such as help /SP system_contact=test

results in garbage output displayed.
Workaround: Use the correct syntax for "help /SP system_contact.
Service Snapshot Utility Unable to Collect SP Data

When IE Web Browser Security Option Is Enabled
CR 6877868
Issue: If the Internet Explorer (IE) web browser Security option for Save
Encrypted Pages To Disk is enabled, the following error message appears when
attempting to collect SP data with the Service Snapshot Utility:
Internet Explorer cannot download mdccvm02i -

spanshot.cgi?dataset=ioh. Internet Explorer was not able to
open this Internet site. The requested site is either
unavailable or cannot be found. Please try again later.
Workaround: Prior to using the Service Snapshot Utility to collect SP data, disable
the Internet Explorer web browser Security option for Save Encrypted Pages
To Disk (Tools -->Internet Options-->Advanced tab).
CHAPTER 7

■ “Resolved Issue as of ILOM 3.0.10” on page 181
169
There are several new features integrated into the Oracle ILOM 3.0.10 release. The
following table lists those new features and points you to the sections that describe
the features.
Topics
Description Links
Updates made to Power Management • “Power Management Updated Terminology, Web

CMM terminology, web layout and Layout, and CLI Properties for the CMM” on
CLI properties page 170
New centralized interface for • “Centralized Firmware Upgrade Management
managing chassis component Interface for Chassis Components” on page 180
firmware
New SAS-2 zoning management • “SAS-2 Zoning Manager Feature Available in
feature available for ILOM CMM ILOM for Chassis Modular Systems” on page 180
3.0.10
Ability to make CMM CLI prompt • “Ability to Change CLI Prompt on CMM to
specific to CMM or blade Differentiate Between CMM and Server Module
(Blade)” on page 180
Power Management Updated Terminology, Web

Layout, and CLI Properties for the CMM
As of ILOM version 3.0.10, some of the CMM Power Management terminology and
settings have changed on the ILOM CLI and web interface. For more details about
these changes, see the following topics:
■ “New Web Layout and Terminology for the CMM” on page 171
■ “New CLI Properties and Terminology for the CMM” on page 176
Note – The SP Power Management CLI terminology and targets have not changed
in ILOM 3.0.6. For details about using the SP Power Management CLI properties, see
Chapter 4.
New Web Layout and Terminology for the CMM
A summary of the CMM changes that were made in ILOM 3.0.10 to the Power
Management web interface tabs and settings is provided in TABLE 7-1.
TABLE 7-1 New Power Management CMM Web Layout and Terminology for ILOM 3.0.10
CMM Power
Management Tab Changes Made in ILOM 3.0.10 For details, see:
Consumption tab Some Power Management --> “Consumption Tab Changes Made in ILOM
Consumption tab settings for the CMM 3.0.10 for the CMM” on page 171
have been renamed in ILOM 3.0.10.
Allocation tab A new Power Allocation tab and settings “Allocation Tab Changes in ILOM 3.0.10 for
are available for the CMM in ILOM 3.0.10. the CMM” on page 172
The Power Allocation tab replaces the
Distribution tab that was previously
available for the CMM in ILOM 3.0.6.
Metrics The Power Management Metrics tab was “Power Management Metrics Tab Removed
removed for the CMM in ILOM 3.0.10. in ILOM 3.0.10 for CMM” on page 176
The Metrics values that were available in
ILOM 3.0.6 were moved to the Allocation
tab in ILOM 3.0.10
Consumption Tab Changes Made in ILOM 3.0.10 for the CMM

Some of the CMM power management properties on the Consumption tab were
changed as of ILOM 3.0.10. For more information about these changes, see TABLE 7-2.
TABLE 7-2 Consumption Tab CMM Settings Changes in ILOM 3.0.10
Peak Permitted The Permitted Power property on the CMM Power Management -->
(renamed property) Consumption tab was renamed to Peak Permitted in ILOM 3.0.10.
The Peak Permitted read-only property (shown in FIGURE 7-1)
represents the maximum power the system is permitted to use.
Available Power The read-only property for Available Power was removed from the
(renamed and moved property) CMM Power Management --> Consumption tab as of ILOM 3.0.10
(shown in FIGURE 7-1).
The reade-only property for Available Power was renamed to
Grantable Power in ILOM 3.0.10 and moved to the Power Summary
table on the Allocation tab. For more details, see “Allocation Tab
Changes in ILOM 3.0.10 for the CMM” on page 172.
An example of the updated Power Management Consumption tab that is available

for the CMM as of ILOM version 3.0.10 is shown in FIGURE 7-1.

FIGURE 7-1 Updated Power Management --> Consumption Tab - ILOM CMM 3.0.10
Allocation Tab Changes in ILOM 3.0.10 for the CMM

The Distribution tab that was previously available for the CMM in ILOM 3.0.6 was
renamed in ILOM 3.0.10 to the Allocation tab (shown in FIGURE 7-2).
FIGURE 7-2 Power Management --> Allocation Tab - ILOM CMM 3.0.10
The Allocation tab, in ILOM 3.0.10, provides all the same power requirement
information previously available on the CMM Power Distribution tab in ILOM 3.0.6.
However, the new CMM Allocation tab in ILOM 3.0.10 provides two additional
tables that identify the System Power Specifications and the Blade Power Grants (as
shown in FIGURE 7-2).
A summary of other property changes made to the CMM Allocation tab in ILOM
3.0.10 are described in TABLE 7-3.

TABLE 7-3 New or revised property names on CMM Allocation tab
Updated Property
Name Details
Grantable Power Allocatable Power in ILOM 3.0.6 was renamed to Grantable Power in
(renamed ILOM 3.0.10.
property) Grantable Power indicates the total remaining power (watts) available
from the CMM to allocate to blade slots without exceeding grant limit.
Grant Limit Permitted Power in ILOM 3.0.6 was renamed to Grant Limit in ILOM
(renamed 3.0.10.
property) Grant Limit represents the maximum power the system will grant to a
blade slot. For instructions for setting the grant limit on a blade see,
“Configure Grant Limit for Blade Slots in CMM Using the Web Interface”
on page 7-174
Granted Power Allocated Power in ILOM 3.0.6 was renamed to Granted Power in ILOM
(renamed 3.0.10.
property) Granted Power represents the sum of the maximum power consumed by
either a single server component (such as a memory module), a category
of server components (all memory modules), or all server power-
consuming components.
▼ Configure Grant Limit for Blade Slots in CMM

Note – To change any power property value for blade slots in ILOM requires an
2. In the left pane of the web interface page, select CMM then in the right pane of
the web interface page, select the Power Management --> Allocation tabs.
The CMM Power Allocation page appears.
3. Scroll down to the Blade Slot Grants table.
4. In the Blade Slot Grants table, do the following.
a. Select the radio button for the blade slot that you want to modify.
b. Click Edit.
A dialog appears listing power configuration information for the blade.
c. In the dialog, modify the Grant Limit value by selecting Custom and
specifying a value for the wattage, then click Save.
Note – To prevent the blade from powering-on, you can set the Grant Limit
value to 0.

Power Management Metrics Tab Removed in ILOM 3.0.10 for CMM
The CMM Metrics tab previously described in ILOM 3.0.6 (“Platform-Specific CMM
Power Metrics” on page 109) was removed from the Power Management web
interface in ILOM 3.0.10. The information previously appearing in the CMM Metrics
tab was moved to the Allocation tab -->Blade Power Grants table (shown in
FIGURE 7-2).
Note – The Power Management Metrics CLI property has not changed. You can
access the power management metrics in the ILOM 3.0.10 CLI under the target
/CMM/powermgmt/advanced/BLn
New CLI Properties and Terminology for the

CMM
A summary of the CMM changes that were made in ILOM 3.0.10 to the Power
Management CLI and settings is provided in TABLE 7-1.
TABLE 7-4 New Power Management CLI Properties in ILOM 3.0.10
Renamed CLI
Properties Details For updated CLI procedure, see:
allocated_power The following CLI allocated_power • “View Blade Slots Granted Power or
renamed to property for all blade slots in ILOM 3.0.6: Reserved Power Using the CLI” on
granted_power for /CMM/powermgmt/powerconf/bladeslot page 7-177
blade slots allocated_power
changed in ILOM 3.0.10 to granted_power:
/CMM/powermgmt/powerconf/bladeslot
granted_power
allocated_power The following CLI allocated_power • “View Granted Power or Grant Limit
renamed property for blades in ILOM 3.0.6: For Blade Using the CLI” on
granted_power for /CMM/powermgmt/powerconf/bladeslot/ page 7-178
blades BLn allocated_power ->
granted_power
changed in ILOM 3.0.10 to granted_power:
/CMM/powermgmt/powerconf/bladeslot/
BLn granted_power
TABLE 7-4 New Power Management CLI Properties in ILOM 3.0.10 (Continued)
Renamed CLI
Properties Details For updated CLI procedure, see:
permitted_power The following CLI permitted_power • “View Granted Power or Grant Limit
renamed property for blades in ILOM 3.0.6: For Blade Using the CLI” on
grant_limit for /CMM/powermgmt/powerconf/bladeslot/ page 7-178
blades BLn permitted_power • “Configure Grant Limit For A Blade
changed in ILOM 3.0.10 to grant_limit: Using the CLI” on page 7-179
/CMM/powermgmt/powerconf/bladeslot/
BLn grant_limit
▼ View Blade Slots Granted Power or Reserved

Power Using the CLI
2. To view the sum of power granted to all blade slots or the sum of power
reserved for all auto-powered I/O blade slots, type the following command:
The granted_power value and reserved power value allocated to all blade slots
appears, for example:

/CMM/powermgmt/powerconf/bladeslots
Targets:
BL0
BL1
BL2
BL3
BL4
BL5
BL6
BL7
BL8
BL9
Properties:
granted_power = 952
reserved_power = 876
Commands:
cd
show
▼ View Granted Power or Grant Limit For Blade

Using the CLI
1. Log into the ILOM CMM CLI.
2. To view the sum of power granted to an individual blade or to the grant limit
value set for a blade, type the following command:
-> show /CMM/powermgmt/powerconf/bladeslot/BLn
Where n represents the slot location for the blade.
For example:
-> show /CMM/powermgmt/powerconf/bladeslots/BL1
/CMM/powermgmt/powerconf/bladeslots/BL1
Targets:
Properties:
granted_power = 0
grant_limit = 800
Commands:
cd
set
show
▼ Configure Grant Limit For A Blade Using the

CLI
Note – To change the grant power limit for any blade in ILOM requires an Admin
(a) role user account.
2. To configure the permitted (maximum) power that the CMM will allocate to a
blade, type the following command:
-> set /CMM/powermgmt/powerconf/bladeslots/BLn grant_limit=watts
Note – To prevent a server module from powering-on, set the grant limit value for
the blade to 0.
Note – The grant limit value cannot be less than any amount already granted
(granted_power).

Centralized Firmware Upgrade Management
Interface for Chassis Components
As of ILOM 3.0.10, a new centralized interface on the CMM is available to manage
firmware updates for Oracle Sun Modular System chassis components. From this
interface, users will be able to view, update, or recover the firmware for each
firmware chassis device. For more information about how to use this feature, see the
Oracle Integrated Lights Out Manager (ILOM) CMM Administration Guide for Sun Blade
6000 and Sun Blade 6048 Modular Systems (820-0052).
SAS-2 Zoning Manager Feature Available in

ILOM for Chassis Modular Systems
As of ILOM 3.0.10, a new zoning management feature is available for SAS-2 storage
devices that are installed in Oracle Sun Blade 6000 or Sun Blade 6048 Modular
Systems. For more information about how to manage SAS-2 chassis storage devices
from ILOM, see the Oracle Integrated Lights Out Manager (ILOM) CMM Administration
Guide for Sun Blade 6000 and Sun Blade 6048 Modular Systems (820-0052).
Note – The zoning manager feature will not be documented in the Oracle Integrated
Lights Out Manager (ILOM) CMM Administration Guide for Sun Blade 6000 and Sun
Blade 6048 Modular Systems (820-0052) until the SAS-2 storage devices are available.
Ability to Change CLI Prompt on CMM to

Differentiate Between CMM and Server Module
(Blade)
As of ILOM 3.0.10, you can change the CLI prompt on the CMM to differentiate
between a CMM CLI prompt and a blade CLI prompt. For more information about
the new CLI prompt properties and how to make the CLI prompt specific to a CMM
or a blade, see the Oracle Integrated Lights Out Manager (ILOM) CMM Administration
Guide for Sun Blade 6000 and Sun Blade 6048 Modular Systems (820-0052).
Resolved Issue as of ILOM 3.0.10
This section describes the issue that have been resolved in the ILOM 3.0.10 release.
Specific change request (CR) identification number and workaround for the issue is
Topics
Description Links
Display output for invalid CLI help • “Invalid Help Command (help /SP
command syntax fixed system_contact=test) Results in Garbage
Output” on page 181
Force option made available for • “IPMItool sunoem CLI Might Be Denied If All
IPMItool sunoem CLI Session Slots Are Busy” on page 182
Invalid Help Command (help /SP

system_contact=test) Results in Garbage
Output
CR 6884556
Issue: Using an invalid CLI help command such as help /SP system_contact=
test results in garbage output displayed.
Update: The CLI help feature in ILOM 3.0.10 has been updated. When invalid
syntax for the help command is entered in the CLI, the following message and
usage information appears.
help: Invalid command syntax

Usage: help [-o|-output terse|verbose]
[<command>|legal|targets|<target>|<target> <property>]

IPMItool sunoem CLI Might Be Denied If All
Session Slots Are Busy
CR 6884556
Issue: IPMItool sunoem CLI could be denied because all session slots appear to be
busy.
Update: The IPMItool sunoem CLI has been updated as of ILOM 3.0.10 to offer a
force command that closes any currently running IPMI sunoem CLI session in
favor of the new one that is being invoked. You can invoke the force command by
including the word force as part of the argument to invoke the CLI, for example:
ipmitool -I open sunoem cli force version

This section describes the known issues and workarounds as of ILOM 3.0.10. Specific
Topics
Description Links
Unable to view DVD content from • “DVD Redirection From Solaris Client to RHEL
Solaris client redirection Host Requires Manual Mount” on page 183
ILOM CLI Storage Redirection fails to • “Storage Redirection CLI Service Requires 32-bit
launch with 64 -bit JDK JDK to Successfully Start” on page 184
ILOM Remote Console fails to launch • “ILOM Remote Console Requires 32-bit JDK to
with 64-bit JDF Successfully Launch” on page 186
Internet Explorer 6 unable to launch • “ILOM Web Interface Unable to Connect to SP
ILOM 3.0 web interface When Using Internet Explorer 6” on page 188
DVD Redirection From Solaris Client to RHEL
Host Requires Manual Mount
CR 6876387
Issue: When you redirect a DVD (physical driver or image file) from Oracle Solaris
to Red Hat Enterprise Linux (RHEL), the floppy and CD-ROM icon will appear in
RHEL, but when you click the CD-ROM icon you are unable to see the content of the
DVD.
Update: You need to manually mount the DVD device to see the content of the DVD.
To manually mount the DVD device, follow these steps:
1. Use the lsscsi command to check the device name of DVD.

For example, the lsscsi output might look like:
[5:0:0:0] cd/dvd AMI Virtual CDROM 1.00 /dev/scd1
Where the device name is: /dev/scd1
2. Create a new directory as the mount point or use the existing directory.
For example:
/mnt
3. Mount the DVD device.

For example:
# mount /dev/scd1 /mnt
mount: block device /dev/scd1 is write-protected, mounting
read-only
The contents the DVD appears under /mnt.

Storage Redirection CLI Service Requires 32-bit
JDK to Successfully Start
CR 6938720
Issue: The service for the Storage Redirection CLI feature in ILOM fails to start if the
64-bit JDK file type is specified to start the service.
Workaround: Specify the 32-bit JDK file type to start the Storage Redirection Service.
Instructions for specifying the 32-bit JDK file type when using either the Firefox web
browser or Internet Explorer web browser follow:
■ Firefox web browser. Perform these steps to specify the 32-bit JDK when starting
the service for the Storage Redirection CLI feature in ILOM.
a. In the ILOM web browser, start the service for Storage Redirection.
For example, click Remote Console --> Redirection then in the Launch
Redirection page, click Launch Service.
Note – For details about how to start the Storage Redirection Service, see the
procedure “Start Storage Redirection Service” in the Integrated Lights Out Manager
(ILOM) 3.0 CLI Procedures Guide (820-6412).
A dialog appears indicating the file type chosen to start the service.
b. In the dialog (see example dialog below), do the following:
i. Click Open with... to specify the 32-bit JDK file.
ii. Select the check box for Do this automatically for files like
this from now on.
■ Internet Explorer (IE) web browser. Perform the following steps prior to starting
the service for the Storage Redirection CLI feature in ILOM. These steps describe
how to register the 32-bit JDK file type for the Storage Redirection Service in
ILOM using Windows Explorer.
a. On the Windows client, open Windows Explorer (not Internet Explorer).
b. In the Windows Explorer dialog, select Tools --> Folder Options then
select the Files Types tab.
c. In the Files Types tab, do the following:
i. In the registered file type list, select the JNLP file type and click Change.
ii. In the Open With... dialog, click Browse to select the 32-bit JDK file.
iii. Select the checkbox for Always use the selected program to open
this kind of file.
iv. Click OK, then start the service for Storage Redirection in the ILOM web
interface.
For details, see the procedure “Start Storage Redirection Service” in the
Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide (820-6412)

ILOM Remote Console Requires 32-bit JDK to
Successfully Launch
CR 6938720
Issue: The ILOM Remote Console feature in ILOM fails to launch if the 64-bit JDK
file type is specified by the web browser.
Workaround: Specify the 32-bit JDK file type to launch the ILOM Remote Console.
Instructions for specifying the 32-bit JDK file type when using either the Firefox web
browser or Internet Explorer web browser follow:
■ Firefox web browser. Perform these steps to specify the 32-bit JDK when
launching the ILOM Remote Console feature in ILOM.
a. In the ILOM web browser, launch the ILOM Remote Console.

For example, click Remote Console --> Redirection then in the Launch
Redirection page, click Launch Remote Console.
Note – For details about how to launch the ILOM Remote Console, see the
procedure “Launch the ILOM Remote Console” in the Integrated Lights Out Manager
(ILOM) 3.0 CLI Web Interface Procedures Guide (820-6410).
A dialog appears indicating the file type chosen to launch the program.
b. In the dialog (see example dialog below), do the following:
i. Click Open with... to specify the 32-bit JDK file.
ii. Select the check box for Do this automatically for files like
this from now on.
■ Internet Explorer (IE) web browser. Perform the following steps prior to
launching the ILOM Remote Console feature in ILOM. These steps describe how
to register the 32-bit JDK file type for the ILOM Remote Console feature in ILOM
using Windows Explorer.
a. On the Windows client, open Windows Explorer (not Internet Explorer).
b. In the Windows Explorer dialog, select Tools --> Folder Options then
select the Files Types tab.
c. In the Files Types tab, do the following:
i. In the registered file type list, select the JNLP file type and click Change.
ii. In the Open With... dialog, click Browse to select the 32-bit JDK file.
iii. Select the checkbox for Always use the selected program to open
this kind of file.
iv. Click OK, then start the service for Storage Redirection in the ILOM web
interface.
For details, see the procedure “Launch the ILOM Remote Console” in the
Integrated Lights Out Manager (ILOM) 3.0 Web Interface Procedures Guide (820-
6410)

ILOM Web Interface Unable to Connect to SP
When Using Internet Explorer 6
CR 6934155
Issue. Due to increased SSL security in ILOM, Internet Explorer 6 is unable to launch
the ILOM SP web interface over HTTPS.
Workarounds: Perform any of the following workarounds:

■ Upgrade Internet Explorer to a later version and launch the ILOM SP web
interface
■ Use a different web browser such as FireFox 2.0 to launch the ILOM SP web
interface.
■ Enable the weak_ciphers setting in the ILOM SP CLI, then launch the ILOM SP
web interface using Internet Explorer 6.
To enable the setting for weak_ciphers in the ILOM CLI, type:
set /SP/services/https weak_ciphers=enabled
■ Launch the ILOM SP web interface over HTTP from Internet Explorer (IE) 6.
To launch the ILOM SP web interface over HTTP from IE 6, you must first in the
ILOM SP CLI enable HTTP and disable redirection.
To enable HTTP and disable redirection in the ILOM SP CLI, type:
set /SP/services/http secureredirect=disabled servicestate=
enabled

Topics
Description Links
Description about IPMItool force • “force Command Omitted from IPMI CLI
command omitted is from Command Documentation” on page 189
documentation
BIOS settings are not preserved after • “BIOS Default Settings Loaded After Updating
updating firmware SP Firmware” on page 190
Update 32-bit JDK file type for • “Update Storage Redirection Content to Include
starting the Storage Redirection CLI 32-bit JDK File Requirement” on page 190
Service
Update 32-bit JDK file type for • “Update ILOM Remote Console Content to
launching the ILOM Remote Console Include 32-bit JDK File Requirement” on
page 191
force Command Omitted from IPMI CLI

Command Documentation
CR 6904246
Issue: A description about the IPMItool force command was omitted from the
Oracle Integrated Lights Out Manager 3.0 Management Protocols Reference Guide (820-
6413-11).
Update: As of ILOM 3.0.10, the IPMItool sunoem CLI command has a force option
that can be invoked by simply adding the word force as the first argument to the
CLI. For example:
ipmitool -I open sunoem cli force version

BIOS Default Settings Loaded After Updating SP

Firmware
CR 6936327
Issue: A description about the BIOS default settings being loading after updating the
SP firmware was omitted from the Firmware Update procedures documented in the
following guides:
■ Oracle Integrated Lights Out Manager (ILOM) 3.0 Web Interface Procedures Guide
(820-6411)
■ Oracle Integrated Lights Out Manager (ILOM 3.0 CLI Procedures Guide (820-6412)
Update: BIOS default settings cannot be preserved when updating the SP firmware.
After updating the SP firmware, the default settings are automatically loaded for the
new BIOS image.

Update Storage Redirection Content to Include

32-bit JDK File Requirement
CR 6938720
Issue: A 32-bit JDK file must be installed on client and specified by the web browser
to start the service for the Storage Redirection CLI feature in ILOM.
Update: For instructions for specifying the 32-bit JDK file, see “Storage Redirection
CLI Service Requires 32-bit JDK to Successfully Start” on page 184.

Update ILOM Remote Console Content to Include
32-bit JDK File Requirement
CR 6938720
Issue: A 32-bit JDK file must be installed on client and specified by the web browser
to launch the ILOM Remote Console feature in ILOM.
Update: For instructions for specifying the 32-bit JDK file, see “ILOM Remote
Console Requires 32-bit JDK to Successfully Launch” on page 186.



Ilom 3.0

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ilom 3.0

Uploaded by

Copyright:

Available Formats

Oracle Integrated Lights Out

Manager (ILOM) 3.0

Feature Updates and Release Notes

Part No. 820-7329-16

Using This Documentation xv

1. ILOM 3.0 Feature Set 1

2. Updates to the ILOM 3.0.3 Firmware 9

3. Updates to the ILOM 3.0.4 Firmware 45

4. Updates to the ILOM 3.0.6 Firmware 77

5. Updates to ILOM 3.0.8 Firmware 119

6. Updates to ILOM 3.0.9 Firmware 155

7. Updates to ILOM 3.0.10 Firmware 169

The following table lists the ILOM 3.0 Documentation Collection

Note – Documentation Collection, and the documents comprising the collection

TABLE P-1 ILOM 3.0 Documentation Collection

Title Content Part Number Format

Oracle Integrated Lights Out Information that describes 820-6410 PDF

Documentation, Support, and Training

Using This Documentation xvii

ILOM 3.0 Feature Set

ILOM 3.0 Feature Set Overview

ILOM 3.0 Firmware on the SP

ILOM 3.0 Firmware on the CMM

CMM Chassis-Level Management

A summary of the CMM’s management functions include:

Chapter 1 ILOM 3.0 Feature Set 3

CMM and Server SP CLI Connection

CMM • /CMM is used to manage ILOM on the CMM.

CMM and Server SP Web Interface Connection

Chapter 1 ILOM 3.0 Feature Set 5

Server SP ILOM Web Interface

For example, ILOM 3.1.2.1.a would designate:

Related ILOM 3.0 Documentation

Chapter 1 ILOM 3.0 Feature Set 7

For platform-specific ILOM updates, refer to your ILOM Supplement, which

Updates to the ILOM 3.0.3 Firmware

Topics in the chapter include:

Updated CMM chassis management • “Improved Chassis View” on page 11

Power Management Metrics

Chapter 2 Updates to the ILOM 3.0.3 Firmware 11

For platform-specific power management information, see the ILOM Supplement

Power Consumption History

Before You Begin

▼ View Power Consumption History Using the CLI

Chapter 2 Updates to the ILOM 3.0.3 Firmware 13

4. To display average consumption history by the minute or hour respectively,

▼ View Power Consumption History Using the Web

Chapter 2 Updates to the ILOM 3.0.3 Firmware 15

Enhanced Ability to Override BIOS Host Boot

Before You Begin

Chapter 2 Updates to the ILOM 3.0.3 Firmware 17

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

▼ Configure BIOS Host Boot Device Override Using the

Chapter 2 Updates to the ILOM 3.0.3 Firmware 19

4. Click Save for your changes to take effect.

Clear Faults After Replacement of Faulted

Before You Begin

▼ View and Clear Faults Using the CLI

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

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

4. Fix or replace the faulted component.

Chapter 2 Updates to the ILOM 3.0.3 Firmware 21