C H A P T E R  1

Features and Issues From 10-2008 to 02-2009

This chapter describes the new features that have been implemented and issues that have been addressed in the ILOM 2.0 releases between October 2008 and February 2009.


New Features and Issues

ILOM 2.0.x Cross-Platform Features From 10-2008 to 02-2009

TABLE 3-1 summarizes the ILOM features that were introduced into the firmware between October 2008 and February 2009. Refer to your platform ILOM Supplement, platform Product Notes, or other platform documentation to determine which of the features applies to a specific platform and specific ILOM firmware release.

The table also includes the Sun internal tracking number (CR) for each feature. Sun Service personnel should refer to the CR number for more information about the feature


TABLE 3-1 New ILOM 2.0.x Cross-Platform Feature

ILOM Features

Sun Internal Tracking Number (CR)

Alt-Graph Key Functionality on International Keyboards

None


Alt-Graph Key Functionality on International Keyboards

CR: None

Description: When running certain versions of the Sun Remote Console application (JavaRConsole) 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 Sun 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 Sun 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 Sun 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 Sun ILOM Remote Console that sends the ALT-GR key directly. The following JDK requirements also apply to the Complete Solution:

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

Use the information in the following table to determine the ILOM versions for each platform, then associate the version with the Workaround Solution or the Complete Solution.


Platform

ILOM Revisions With Workaround

Release Vehicles With Workaround

ILOM Revisions With Complete Solution

Release Vehicles With Complete Solution

Sun Fire X2250

All versions

All

2.0.2.12 or later

Tools&Drivers CD 1.1.1 or later

Sun Fire X4100 M2/X4200 M2

2.0.2.1 r27740 or later

SW 1.4 or later

2.0.2.10 r35249 or later

SW 2.1 or later

Sun Fire X4600 M2

2.0.2.5 r29771 or later

SW 2.0 or later

2.0.2.10 r38791

SW 2.2 or later

Sun Fire X4500

2.0.2.1 r26849 or later

SW 1.5

No versions with fix

No release with fix

Sun Fire X4540

All versions

All

No versions with fix

No release with fix

Sun Fire X4150

All versions

All

2.0.2.5 r37049 or later

Tools&Drivers CD 2.2 or later

Sun Fire X4250

All versions

All

2.0.2.10 r39321 or later

Tools&Drivers CD 2.2 or later

Sun Fire X4450

All versions

All

2.0.2.10 r39321 or later

Tools&Drivers CD 2.3 or later

Sun Fire X4140

None

None

None

None

Sun Fire X4240

None

None

None

None

Sun Fire X4440

None

None

None

None

Sun Blade X6220

2.0.3.3 r34514 or later

SW 2.0 or later

2.0.3.10 r36968 or later

SW 2.1

Sun Blade X6240

All versions

All

2.0.3.11 or later

SW 1.2.0 or later

Sun Blade X6440

All versions

All

2.0.3.11 or later

SW 1.1.0 or later

Sun Blade X6250

All versions

All

2.0.3.6 or later

SW 2..0.2 or later

Sun Blade X6450

All versions

All

2.0.3.6 or later

SW 2..0.2 or later

Sun Fire X4170

All versions

All

All versions

All

Sun Fire X4270

All versions

All

All versions

All

Sun Fire X4275

All versions

All

All versions

All

Sun Blade X6270

All versions

All

All versions

All

Sun Fire X2270

All versions

All

All versions

All




Note - This table does not list platforms that have announced end-of-life plans or products that are not applicable, such as Sun Blade chassis systems.


ILOM 2.0.x Cross-Platform Issues From 10-2008 to 02-2009

TABLE 3-2 summarizes the ILOM issues reported between October 2008 and February 2009. The table also includes the Sun internal tracking number (CR) for each issue. Sun Service personnel should refer to the CR number for more information about the issue.

Refer to your platform ILOM Supplement, platform Product Notes, or other platform documentation to determine which of the issues applies to a specific platform and specific ILOM firmware release.


TABLE 3-2 ILOM 2.0.x Cross-Platform Issues

ILOM Issue

Sun Internal Tracking Number (CR)

Timeout for IPMI LAN Session Is Too Long

6756693

Incorrect Traps Were Returned for Assertion/Deassertion of Power Sensors

6580094

Backslash and Double Quotation Mark (\”) Required in setfru -c Command

6538946

ILOM 2.0 User’s Guide Needs Update for Redirection of Console Input Using Solaris Operating Environment

6770175

Non-Alphanumeric Characters Are Not Allowed in SNMP Community Name String

6698177

After Editing an IP Address in Web Interface, Cannot Log In Again to ILOM Using New IP Address

6745118

locate LED Continues Blinking After LED Test

6652152

Serial Port Owner Is Blank for Operator and There Is No Save Button

6794235


Timeout for IPMI LAN Session Is Too Long

CR: 6756993

Description: IPMI LAN sessions should time out after 3 minutes of inactivity. However, due to incorrect settings for the LAN timer interval, the IPMI LAN session was set to time out after 30 minutes of inactivity.

Resolution: The IPMI LAN idle session timeout has been corrected to time out after 3 minutes of inactivity.

Incorrect Traps Were Returned for Assertion/Deassertion of Power Sensors

CR: 6580094

Description: The following incorrect traps were returned during assertion and deassertion of power sensors:

/SYS/PWRGOOD "State Asserted" returned the following trap:
sunHwTrapComponentError

/SYS/PWRGOOD "State Deasserted" returned the following trap: sunHwTrapComponentOk

Resolution: "State asserted" now returns an OK trap, and "State Deasserted" now returns an Error trap.

Backslash and Double Quotation Mark (\”) Required in
setfru -c Command

CR: 6538946

Description: If a double quotation mark is used in a string that is set with the
setfru -c command, the double quote needs to be preceded by a backslash character. Note that \” counts as two characters.

Resolution: Strings with double quotes must include backslash characters. For example:


sc> setfru -c \”1234567890123456789012345678901234567890123456789012345678901234567890123456\”
Updating Customer_DataR in /SYS/MB
Updating Customer_DataR in /SYS/PDB
Updating Customer_DataR in /SYS/SASBP
Updating Customer_DataR in /SYS/FANBD0
Updating Customer_DataR in /SYS/FANBD1
 
sc> showfru
...
/Customer_DataR
/Customer_DataR/UNIX_Timestamp32: Mon Mar 26 18:41:54 GMT 2007
/Customer_DataR/Cust_Data: "1234567890123456789012345678901234567890123456789012345678901234567890123456"
SEGMENT: PS

ILOM 2.0 User’s Guide Needs Update for Redirection of Console Input Using Solaris Operating Environment

CR: 6770175

Description: The Sun ILOM Remote Console is a remote management graphical user interface tool that enables you to redirect devices on a remote host server from a local client. Remote Console supports two methods of redirection--video and serial console--enabling the devices on your local client to behave as if they were directly attached to the remote host server. Video redirection is supported on all Sun x64 servers and some SPARC servers. Serial console redirection is not supported on Sun x64 servers.

Redirection of video and serial console for users of the Solaris operating environment is not adequately described in the Sun Integrated Lights Out Manager 2.0 User’s Guide (820-1188).

Resolution: Use the following instructions to redirect the console input/output to the video and serial ports using the Solaris operating environment.


procedure icon  Redirect Console Input/Output to Video Port Using the Solaris Operating Environment



Note - This procedure is supported on Sun x64 systems running the Solaris operating environment. Refer to your platform documentation for more information.


1. Log in to Solaris as root.

2. To redirect the console input/output to video, type the following:


# eeprom console=text


3. To reboot Solaris, type:


# reboot



procedure icon  Redirect Console Input/Output to Serial Console Using Solaris Operating Environment

1. Log in to Solaris as root.

2. To redirect the console input/output to the serial console, type the following:


# eeprom console=ttya




Note - This procedure is only supported on Sun x64 systems running the Solaris operating environment. After the console is configured in this manner, the only way to access the Solaris console will be from the ILOM command line interface.


3. To reboot Solaris, type:


# reboot


Non-Alphanumeric Characters Are Not Allowed in SNMP Community Name String

CR: 6698177

Description: ILOM did not allow community strings containing non-alphanumeric characters (underscore and hyphen).

Resolution: You can now use a hyphen or an underscore character to create an SNMP community name. If you use the ILOM web interface to create the community name or to specify the community name for SNMP traps, you can start the community name with a hyphen. However, you cannot use a hyphen as the first character when creating a community name using the ILOM command-line interface (CLI). The CLI shell interprets the hyphen character as the start of a parameter.

After Editing an IP Address in Web Interface, Cannot Log In Again to ILOM Using New IP Address

CR: 6745118

Description: If you change the chassis monitoring module (CMM) static IP address to a new static IP address using the ILOM web interface, you might be unable to log in again to the ILOM web interface using the new IP address.

Resolution: This is the expected behavior of changing the static IP address while logged in. Wait approximately 1 to 2 minutes after changing the IP address, then reconnect to ILOM with the new IP address.

locate LED Continues Blinking After LED Test

CR: 6652152

Description: At the conclusion of a system-wide LED test (Push-to-Test), all LEDs are restored to pre-LED-test state, except the Locate LED. The Locate LED continues to fast blink.

Resolution: The behavior of the Locate LED before initiating the Push-to-Test procedure is a fast blink, so the Locate LED will continue to fast blink after the Push-to-Test process is complete.

Serial Port Owner Is Blank for Operator and There Is No Save Button

CR: 6794235

Description: When logging in to a host server with Operator permissions using the ILOM web interface (Configuration --> Serial Port), you might experience the following errors:

Because of these errors, a user with Operator permissions might assume incorrectly that changes can be made to the serial settings on the web.

Resolution: Only users with Administrator privileges can change the serial port settings.

Documentation Updates and Errata

This section describes errors that have been found in the Sun Integrated Lights Out Manager 2.0 User’s Guide (820-1188). Specific change request (CR) identification numbers and workarounds for the issues are provided, where available.


Documentation Issue

Sun Internal Tracking Number (CR)

Corrections to ILOM Target Tree Illustration

none

Targets, Properties, and Values for set and show Commands

none


Corrections to ILOM Target Tree Illustration

Issue: In the Sun Integrated Lights Out Manager 2.0 User’s Guide (820-1188), Figure 3-1 incorrectly illustrates the target structure of ILOM 2.0.

Resolution: The following figure is correct.


ILOM 2.0 Target Tree

Targets, Properties, and Values for set and show Commands

Issue: In the Sun Integrated Lights Out Manager 2.0 User’s Guide (820-1188), there are incorrect entries for properties, values, and default values that correspond with valid targets in the set and show commands. The following information is correct.


Valid Targets

Properties

Values

Default

/SP/clients/activedirectory

logdetail

none | high | medium | low |
trace

none


Update: This information will be included in a future release of the User’s Guide.