Академический Документы
Профессиональный Документы
Культура Документы
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
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
Resolved Issues as of ILOM 3.0.3 34
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
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
Resolved Issues as of ILOM 3.0.4 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
Known Issues as of ILOM 3.0.4 73
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
Documentation Updates and Errata 75
Allowable Number for DNS Retries Is Incorrect 75
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
Resolved Issues as of ILOM 3.0.6 112
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
Known Issues as of ILOM 3.0.6 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
Documentation Updates and Errata 115
Serial Port Sharing 115
Contents ix
▼ Switch Serial Port Output Using the CLI 116
▼ Switch Serial Port Output Using the Web Interface 116
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
Resolved Issues as of ILOM 3.0.8 148
Invalid Time Zone Settings in ILOM CLI 148
Snapshot Properties Are Not Persistent After a Reset 148
Known Issues as of ILOM 3.0.8 149
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
Documentation Updates and Errata 151
SP Management Port - Recommended Practice for Spanning Tree
Parameters 152
Renamed ILOM SNMP and IPMI Procedures Guide to Management Protocols
Reference Guide 152
Contents xi
Resolved Issues as of ILOM 3.0.9 165
Unrecoverable ILOM Remote Console Sessions (Fixed) 165
Known Issues as of ILOM 3.0.9 167
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
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
Documentation Updates and Errata 189
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
xv
.
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.
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
Note – CMMs are applicable to Oracle Sun Blade Modular Systems. CMMs are not
applicable to Oracle rackmount servers.
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 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.
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.
4 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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
6 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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.
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:
http://docs.sun.com/app/docs/prod/int.lights.mgr30#hic
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
8 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
CHAPTER 2
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.
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
10 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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.
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 general information about viewing the power management metrics in the CLI
and web interface, see the ILOM 3.0 Documentation Collection.
Note – Power consumption history is provided using the ILOM CLI and web
interfaces. This information is not available through IPMI or SNMP.
12 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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:
■ From the server SP:
->show /SYS/VPS/history
->show /CH/VPS/history
/CH/VPS/history
Targets:
0 (1 Minute Average, 1 Hour History)
1 (1 Hour Average, 14 Day History)
Properties:
15sec_average = 1210.000
30sec_average = 1400.000
60sec_average = 1800.000
Commands:
cd
show
->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
14 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
5. To display sample set details such as time stamp and power consumed in watts,
type:
■ From the server SP:
->show /SYS/VPS/history/0/list
■ 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
2. In the web interface page, click System Monitoring --> Power Management.
The Power Management page appears.
3. In the Power Management page, click the link for Power History.
Two tables appear that show Power Usage Average and Power History.
For example:
■ CMM Power History Example
16 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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.
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.
->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.
18 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
■ cdrom – Setting the value to cdrom means that at the next host boot, the BIOS
boot order settings will be temporarily bypassed and instead the host will boot
from the attached CD-ROM or DVD device.
■ bios – Setting the value to bios means that at the next host boot, the BIOS
boot order settings will be temporarily bypassed and instead the host will boot
into the BIOS Setup screen.
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
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.
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)
20 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
■ 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.
For example, to clear a processor fault, you would type 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.
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.
22 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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.
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.
The following figures show ILOM web interface pages in which jump links are now
provided for easier navigation within pages.
24 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
User Management --> User Accounts
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
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.
26 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
Data Set Options Description
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.
Topics
Description Links
28 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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.
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.
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.
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.
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.
30 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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
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.
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.
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.
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.
32 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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.
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:
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
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
34 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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
Description Links
36 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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.
Update: This information will be included in a future release of the Oracle ILOM
Documentation Collection.
38 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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.
Update: This information will be included in a future release of the Oracle ILOM
Documentation Collection.
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.
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.
1. Log in to ILOM.
2. In the web interface page, click System Monitoring --> Power Management.
a. In the Power Policy list box and select either Performance or Elastic.
40 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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:
->
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
Documentation Collection.
Issue: In the Oracle Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide
(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.
Update: This information will be included in a future release of the Oracle ILOM
Documentation Collection.
Issue: In the Oracle Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide
(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
Documentation Collection.
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:
42 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
Update: This information will be updated in a future release of the Oracle ILOM
Documentation Collection.
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.
Update: This information will be updated in a future release of the Oracle ILOM
Documentation Collection.
Issue: In the Oracle Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide
(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.
Update: This information will be updated in a future release of the Oracle ILOM
Documentation Collection.
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
Update: This additional information will be added to a future release of the ILOM
Documentation Collection.
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).
44 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
CHAPTER 3
This chapter describes the new features and functionality that have been added to
the Oracle ILOM 3.0.4 firmware release. Procedures to implement the new
functionality are explained. Known issues, resolved issues, and documentation
updates are also described.
45
New Features for ILOM 3.0.4
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
46 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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.
Note – Setting the notification threshold value to 0 will disable the notification
threshold option.
48 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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.
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:
http://docs.sun.com/app/docs/prod/int.lights.mgr30#hic
1. To view the LDAP/SSL Optional User Mapping, type the following command:
-> show /SP/clients/ldapssl/optionalUserMapping
The following sample output appears.
50 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
-> 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
52 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
4. In the Edit LDAP/SSL Optional User Attribute dialog, modify any of the
parameters, then click Save to apply your changes.
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.
/SP/services/snmp/mibs
Targets:
Properties:
dump_uri = (Cannot show property)
Commands:
cd
dump
set
show
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.
54 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
4. Click Download, enter the destination to save the file, then click Save.
/SP/sessions/18
Targets:
Properties:
username = root
role = aucro
starttime = Mon Apr 13 06:25:19 2009
type = web
mode = normal
Commands:
cd
show
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.
56 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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.
2. To view the expanded search mode in Active Directory, type the following
command:
-> show /SP/clients/activedirectory
The following sample output appears.
/SP/clients/activedirectory
Targets:
admingroups
alternateservers
cert
customgroups
dnslocatorqueries
opergroups
userdomains
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:
2. In the web interface page, click User Management --> Active Directory.
The Active Directory Management page appears.
58 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
3. In the Expanded Search Mode field, select the Enabled box to enable this
option or clear the Enabled box to disable this option.
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.
3. In the Alert Settings page, perform the following steps to send a test email
alert:
b. Click the Test Rule button to send a text email alert to the alert rule
destination.
60 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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.
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.
62 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
▼ 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:
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
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.
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:
64 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
/SP/services/kvms
Targets:
Properties:
custom_lock_key = backspace
custom_lock_modifiers = l_shift, l_ctrl
lockmode = custom
mousemode = absolute
servicestate = enabled
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.
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.
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.
2. Use the set command to edit the mouse mode configuration variable, for
example:
66 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
▼ Edit Mouse Mode Setting for Remote Host
Using the Web Interface
1. Log in to ILOM.
3. In the KVMS page, select Absolute or Relative in the Mouse Mode box.
Topics
Description Links
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
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.
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.
68 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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
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.
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.
Issue: The ILOM CLI Help provides misleading user role information for read-only
/SYS properties. For example:
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.
Issue: The following properties are read-only and are not configurable; therefore, the
role required to view these properties is Read Only (o):
70 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
actual_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).
Issue: Help function displays confusing text when listing values for multiple
properties, for example:
Issue: The Help text has several inaccuracies for the different properties under
/SP/users/root/ssh/keys/.
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.
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.
72 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
Known Issues as of ILOM 3.0.4
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
provided, where available.
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
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.
■ 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.
74 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
Note – The ILOM Remote Console supports up to three user session connections to
a host system.
Issue: In the Oracle Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide
(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 chapter describes the new features and functionality that have been added to
the Oracle ILOM 3.0.6 firmware release. Procedures to implement the new
functionality are explained. Known issues, resolved issues, and documentation
updates are also described.
77
New Features for ILOM 3.0.6
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
78 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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.
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).
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
80 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
TABLE 4-1 Storage Properties Shown for HDDs and RAID Controllers (Continued)
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.
or
■ /STORAGE/raid to show details for a RAID disk controller
For instructions and examples about how to view the storage monitoring details in
ILOM for HDDs and RAID controllers, see the following procedure.
82 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
▼ Show Property Details in ILOM for HDDs and RAID
Controllers 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 can display the HDD details under /SYS or the RAID disk
controller details under /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:
84 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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:
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
86 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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.
88 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
TABLE 4-5 Server Power Allocated Components (Continued)
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.
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
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.
90 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
TABLE 4-6 CMM Power Allocated Components (Continued)
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
■ “View CMM Component Power Allocations Using the Web Interface” on page 96
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
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.
92 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
▼ View Server Power Allocations for All Components
Using the CLI
1. Log in to the ILOM SP CLI.
2. To view the sum of power allocated to all components in the system, type the
following command:
-> show /SP/powermgmt allocated_power
Note – For each command, the read-only value for the maximum power consumed
by the component is returned, measured in watts.
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
Note – For each command, the read-only value for the maximum power consumed
by the component is returned, measured in watts.
94 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
3. To view the power allocated to a specific component, type the following
command:
-> show /CMM/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 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
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:
Note – To prevent a server module from powering-on, set the permitted power
value for the blade slot to 0.
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).
96 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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.
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.
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.
98 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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.
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.
The most effective way to use the Power Budget feature in ILOM is to:
100 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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.
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.
102 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
TABLE 4-8 Advanced Server Power Budget Properties
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.
For instructions about how to view or configure the server and advanced server
power budget properties in ILOM, see the following procedures:
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
->
104 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
Note – See TABLE 4-7 and TABLE 4-8 to view definitions for each power budget
property.
For example:
Note – To change any server power budget property values in ILOM requires an
Admin (a) role user account.
2. In the ILOM web interface, select the Power Management --> Budget tabs.
The Power Budget Management page appears.
Note – See TABLE 4-7 and TABLE 4-8 to view definitions for each power budget
property.
5. To view the system power limit value that is in effect, do the following:
b. In the Power Management Consumption page, view the property value for
the system power limit.
106 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
■ 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
Note – To change the CMM power supply redundancy policy in ILOM requires an
Admin (a) role user account.
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.
Note – To change the CMM power supply redundancy policy in ILOM requires an
Admin (a) role user account.
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.
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.
108 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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.
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
110 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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.
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
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.
112 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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.
Issue: Power management was not triggering an event after crossing a threshold.
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
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.
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.
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.
Issue: The following console error message might appear after backing up and
restoring the ILOM configuration.
114 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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:
Workaround. None needed. These are expected events and are not indicative of a
problem.
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:
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.
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.
116 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
Note – The serial port sharing setting by default is Service Processor.
This chapter describes the new features and functionality that have been added to
the Oracle ILOM 3.0.8 firmware release. Procedures to implement the new
functionality are explained. Known issues, resolved issues, and documentation
updates are also described.
119
New Features for ILOM 3.0.8
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
120 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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.
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.
122 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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
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.
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.
FIGURE 5-2 Updated Power Management --> Consumption Tab - ILOM SP 3.0.8
124 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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).
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).
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.
126 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
FIGURE 5-4 Power Management --> Limit Tab - ILOM SP 3.0.8
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.
Note – To change any server power limit property values in ILOM requires an
Admin (a) role user account.
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).
128 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
TABLE 5-4 Power Limit Property Descriptions (Continued)
Note – For best power capping performance, the default values are recommended
for all advanced server power limit properties.
For instructions about how to create the banner messages in ILOM, see “Configuring
Banner Messages” on page 132.
130 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
FIGURE 5-6 After Logging In - Banner Message Example - Web Interface
2. Use the show command to display the current banner properties and
supported commands.
For example:
/SP/preferences/banner
Targets:
Properties:
connect_message = (none)
login_message = (none)
login_message_acceptance = disabled
Commands:
cd
set
show
132 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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.
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.
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.
5. Click Save.
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
134 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
FIGURE 5-8 RAID Controller Configuration Details
136 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
FIGURE 5-11 Disk Details - Attached to RAID Controller
138 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
■ “View and Monitor RAID Controller Volume Details Using the Web Interface” on
page 140
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.
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.
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.
140 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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.
2. Use the show command to display the SP Console target, properties, and
commands.
For example:
/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:
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
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:
142 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
■ 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.
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.
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
144 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
▼ 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:
/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:
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
146 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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.
2. In the ILOM web interface, click the Remote Control --> TPM tab.
The TPM Settings page appears.
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
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.
148 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
Known Issues as of ILOM 3.0.8
This section describes known issues and workarounds as of ILOM 3.0.8. Specific
change request (CR) identification numbers and workarounds for these issues are
provided, where available.
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
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
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.
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.
150 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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
Update: This information will be updated in a future release of the Oracle ILOM
Documentation Collection.
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.
152 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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
Update: This information will be updated in a future release of the Oracle ILOM
Documentation Collection.
This chapter describes the new features and functionality that have been added to
the Oracle ILOM 3.0.9 firmware release. Procedures to implement the new
functionality are explained. Known issues, resolved issues, and documentation
updates are also described.
155
New Features for ILOM 3.0.9
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
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:
156 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
• 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
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
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
158 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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.
2. In the ILOM web interface, click the System Information --> Components tab.
The Components page appears.
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.
160 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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:
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.
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).
162 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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
/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
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.
164 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
Resolved Issues as of ILOM 3.0.9
This section describes the issues that have been resolved in the ILOM 3.0.9 release.
Specific change request (CR) identification number and workaround for the issues
are provided, where available.
Topics
Description Links
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
166 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
Known Issues as of ILOM 3.0.9
This section describes known issues and workarounds as of ILOM 3.0.9. Specific
change request (CR) identification numbers and workarounds for these issues are
provided, where available.
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
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.
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.
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:
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).
168 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
CHAPTER 7
This chapter describes the new features and functionality that have been added to
the Oracle ILOM 3.0.10 firmware release. Procedures to implement the new
functionality are explained. Known issues, resolved issues, and documentation
updates are also described.
169
New Features for ILOM 3.0.10
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
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.
170 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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
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.
172 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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.
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.
Note – To change any power 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 --> Allocation tabs.
The CMM Power Allocation page appears.
174 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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.
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
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
176 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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
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:
-> show /CMM/powermgmt/powerconf/bladeslots
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
178 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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:
/CMM/powermgmt/powerconf/bladeslots/BL1
Targets:
Properties:
granted_power = 0
grant_limit = 800
Commands:
cd
set
show
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).
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.
180 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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
provided, where available.
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
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.
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:
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
182 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
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:
2. Create a new directory as the mount point or use the existing directory.
For example:
/mnt
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.
ii. Select the check box for Do this automatically for files like
this from now on.
184 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
■ 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.
b. In the Windows Explorer dialog, select Tools --> Folder Options then
select the Files Types tab.
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)
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.
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.
ii. Select the check box for Do this automatically for files like
this from now on.
186 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
■ 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.
b. In the Windows Explorer dialog, select Tools --> Folder Options then
select the Files Types tab.
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)
Issue. Due to increased SSL security in ILOM, Internet Explorer 6 is unable to launch
the ILOM SP web interface over HTTPS.
188 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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
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
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:
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.
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.
190 Oracle Integrated Lights Out Manager (ILOM) 3.0 Feature Updates and Release Notes • May 2010
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.