C H A P T E R 2

Updates to the ILOM 3.0.3 Firmware

This chapter describes the new features and functionality that have been added to the Oracle ILOM 3.0.3 firmware release. Procedures to implement the new functionality are explained. Resolved issues and known issues are also described. In addition, references to the ILOM 3.0 documents in which the new features are described in detail are provided.

Topics in the chapter include:

- New Features for ILOM 3.0.3

- Resolved Issues as of ILOM 3.0.3

- Known Issues as of ILOM 3.0.3

##

New Features for ILOM 3.0.3

The following table identifies new features available in the ILOM 3.0.3 release. References to the appropriate guides in the ILOM 3.0 Documentation Collection that describe the features are also provided.

Topics
Description | Refer To:
--- | ---
Updated CMM chassis management view and documentation | Oracle Integrated Lights Out Manager (ILOM) 3.0 Web Interface Procedures Guide, Web Interface Overview
Enhanced CMM power management metrics | Oracle Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide, Power Monitoring and Management of Hardware Interfaces
Enhanced feature for displaying the history of platform-specific power consumption | Oracle Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide, Power Monitoring and Management of Hardware Interfaces Oracle Integrated Lights Out Manager (ILOM) 3.0 Web Interface Procedures Guide, Power Monitoring and Management of Hardware Interfaces
Enhanced feature to override the boot device settings in BIOS using the ILOM CLI or web interface | Oracle Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide, Remote Host Management Options Oracle Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide, Managing Remote Hosts Power States Oracle Integrated Lights Out Manager (ILOM) 3.0 Web Interface Procedures Guide, Managing Remote Hosts Power States
Updated information for clearing faults from the event log after fixing a faulted component | Oracle Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide, System Monitoring and Alert Management Oracle Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide, Monitoring System Components Oracle Integrated Lights Out Manager (ILOM) 3.0 Web Interface Procedures Guide, Monitoring System Components
Enhanced web pages with jump links | Oracle Integrated Lights Out Manager (ILOM) 3.0 Web Interface Procedures Guide, Web Interface Overview
New data collection options for Snapshot Utility | Oracle Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide, Remote Hosts Diagnostics for x86 and SPARC Systems Oracle Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide, Performing Remote Host System Diagnostics Oracle Integrated Lights Out Manager (ILOM) 3.0 Web Interface Procedures Guide, Performing Remote Host System Diagnostics

##

Resolved Issues as of ILOM 3.0.3

This section describes the issues that have been resolved as of ILOM 3.0.3. Specific change request (CR) identification numbers and workarounds for the issues are provided, where available.

Topics
Description | Links
--- | ---
ILOM Remote Console resolved issue | Alt-Graph Key Functionality on International Keyboards
User management resolved issue | Web Interface Does Not Display the Browse Button When Uploading Files
SSH host keys resolved issues | Newly Generated SSH Keys Require SSH Server Restart Loading SSH Host Key Results in Error Message
Alert management known issue | Email Address Using IP Address Is Accepted in Alert Management Rule Query
System clock setting resolved issue for SPARC servers | When Using the CLI to Set the Time Zone, Certain Time Zones Do Not Recalculate the Clock Correctly (SPARC Servers)

### Alt-Graph Key Functionality on International Keyboards

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

This problem was addressed in two phases:

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

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

- For Windows, use JDK 1.5 or higher.

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

You can use the ILOM `version` command to determine which version of ILOM is running on a platform.

Note - Linux and Solaris versions of ILOM 3.0.x contain both the Workaround and Complete Solution. Windows versions of ILOM 3.0.x contain the functionality as described for the Complete Solution, but not the Workaround.

### Web Interface Does Not Display the Browse Button When Uploading Files

CR 6787083

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

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

- When configuring an optional certificate for LDAP/SSL

- When configuring an optional certificate for Active Directory

- When configuring user SSH keys

- When configuring backup and restore operations

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

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

### Newly Generated SSH Keys Require SSH Server Restart

CR 6781487

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

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

### Loading SSH Host Key Results in Error Message

CR 6776200

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

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

### Email Address Using IP Address Is Accepted in Alert Management Rule Query

CR 6776214

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

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

### When Using the CLI to Set the Time Zone, Certain Time Zones Do Not Recalculate the Clock Correctly (SPARC Servers)

CR 6798875

Issue: When using the CLI to set the time zone, some time zones either do not recalculate the clock correctly or update the time zone setting on the clock.

Update: As of ILOM 3.0.3.20b this issue has been fixed for SPARC servers.

You must use valid global time zone nomenclature to set the time zone to recalculate the clock correctly. You can find a list of the valid global time zone nomenclature on the Internet, for example, at: `http://en.wikipedia.org/wiki/List_of_zoneinfo_time_zones`

Examples:

- To set the SP clock time zone property value to the US standard eastern zone, you would type:

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

or

- To set the SP clock time zone property value to the US central time zone, you would type:

-> `set /SP/clock/ timezone=America/Chicago`

##

Known Issues as of ILOM 3.0.3

This section describes the known issues as of ILOM 3.0.3. The following table identifies the known issues and points you to the sections that describe the issues. Specific change request (CR) numbers and workarounds or updates for the issues are provided, where available.

Topics
Description | Links
--- | ---
Unexpected BIOS behavior | BIOS Upgrade Is Delayed After SP Reboot
Unexpected behavior when resetting to defaults | External Serial Port Settings Do Not Reset to Default Value
Hourly timestamp behavior | Hourly Power Average Timestamp Does Not Account for Increments of Less Than One Hour
SSH keys are not loaded | SSH Keys Fail to Restore After a Backup/Restore

### BIOS Upgrade Is Delayed After SP Reboot

CR 6813514

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

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

However, two issues can occur:

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

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

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

### External Serial Port Settings Do Not Reset to Default Value

CR 6676339

Issue: The `reset_to_defaults` command enables a user to reset the ILOM configuration back to the default values. However, external serial port settings are not reset when `reset_to_defaults` action is performed.

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

### Hourly Power Average Timestamp Does Not Account for Increments of Less Than One Hour

CR 6803961

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

Workaround: None.

The power average timestamp is not a "rolling average" of the last minute or hour. Instead, ILOM selects a starting point in time (call it time 0). At 60 seconds, ILOM records the first minute average. For the next 59 seconds there would be no change, then at time 120, ILOM records the second minute average. The last minute average is the average of the most recent minute, and not the average of the last minute the sensor was readable.

For the hour average, no samples are taken until time 3600 when the first one-hour average is recorded. ILOM records the second hour average at time 7200.

The last 60 one-minute averages will not equal the last one-hour average, unless you compare it with the exact correct time when the most recent hourly average was stored.

Note that the hourly minimum and maximum average can have a later timestamp than the minute averages. This occurs when ILOM does not record data, which only happens if the sensor is no longer readable (power has been turned off, or has dropped too low to measure). In this instance, ILOM records "no data" while the sensor is unreadable to ensure that the historical data is not lost.

### SSH Keys Fail to Restore After a Backup/Restore

CR 6808138

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

Workaround: When a new key is generated on the SP, this message appears:

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

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

Type `yes` or edit the `known_hosts` file.

Copyright © 2010, Oracle and/or its affiliates. All rights reserved.