C H A P T E R 2 |
ILOM Notes and Issues |
This chapter describes the Sun Integrated Lights Out Manager (ILOM) service processor notes and issues. It includes the following sections:
The following notes apply to running ILOM on the Sun Blade 6048 modular system.
Sun recommends using the latest released firmware for all Sun Blade 6048 modular system components. The current release, and most recent previous release, are tested and available on the Sun download center:
http://www.sun.com/servers/blades/downloads.jsp
Sun tests each new hardware component and firmware update for existing modules against other chassis components that are using the latest available firmware and the prior revision. Sun recommends that all components use the latest available firmware or the prior version.
For instructions on updating the firmware, refer to the ILOM documentation for the ILOM version that is currently running on your system.
A policy has been added to the CMM to support the Sun Cooling Door that might be used with your chassis.
Note - The CMM must be updated to ILOM version 3.x in order to support a Sun Cooling door. |
Sun supports two types of cooling doors, Sun Cooling Door 5200, and Sun Cooling Door 5600. This section applies to both.
To configure the Sun Cooling Door policy using the web interface, see To Configure the Sun Cooling Door Policy Using the Web Interface.
To configure the Sun Cooling Door policy using the CLI, see To Configure the Sun Cooling Door Policy Using the CLI.
To Configure the Sun Cooling Door Policy Using the Web Interface |
1. Open a browser and enter the IP address of the server.
The ILOM web interface login page appears.
2. Log in to ILOM using the root account.
The default password for the root account is changeme.
The ILOM web interface appears.
3. Select Configuration Policy.
The Policy Configuration page appears.
FIGURE 3-1 Policy Configuration Page
4. Click the radio button next to Sun Cooling Door Installed.
The status changes to indicate your selection.
To Configure the Sun Cooling Door Policy Using the CLI |
1. Log in to ILOM. Open a terminal window and type:
The default password for the root account is changeme.
The ILOM CLI prompt appears (->).
-> set /CMM/policy/COOLING_DOOR_INSTALLED=selection
enabled if your chassis has a cooling door
disabled if your chassis does not have a cooling door
The following display shows the policy settings with the cooling door disabled:
The following issues are related to the ILOM:
ILOM version 3.0.6.11 requires power to both power supplies.
Connect only one power supply; use PSU 1.
Note - This issue was fixed in version 3.1.1 |
The issues in this section are specific to the ILOM 3.0.3.32 on the Sun Blade 6048 modular system.
Sensors were returning invalid readings in the event log, such as:
Readings for these sensors should consist of 0x01 and 0x2 and never return 0x0.
Note - This issue was fixed in release 3.1.2. |
The issues in this section are specific to the ILOM 3.0 on the Sun Blade 6048 modular system.
When updating the CMM ILOM firmware from 2.0.3.10 to 3.0.3.32, the share sensor ID is changed, so a server module running ILOM 2.x cannot read the share sensor correctly.
When the CMM is updated to ILOM 3.0, reset all server module SPs that are running ILOM2.x.
If the CMM is replaced or moved to a different chassis, the first time ILOM boots an incorrect host name or product serial number might be displayed.
After ILOM boots, reset the CMM with one of the following:
The CMM will reboot with the correct product information.
The issues in this section are specific to the ILOM 2.0.3.10 on the Sun Blade 6048 modular system.
If you are running ILOM version 2.0.3.10, you will not be able to set the CMM netmask through the CMM ILOM.
To set the netmask, you can manually edit the /conf/interfaces file via the sunservice account or by using the Linux ifconfig command.
ifconfig eth0 netmask AA.BB.CC.DD
where AA.BB.CC.DD is the desired subnet mask (for example 255.255.0.0).
The issues in this section are specific to the ILOM 2.0.3.3 on the Sun Blade 6048 modular system.
When running ILOM 2.0.3.3, if you press the locate button more than 5 seconds to initiate the lamp LED test, the LED does not turn on and a “transition to degraded” message appears in the SEL log.
The issues in this section are specific to the ILOM 2.0.3.2 on the Sun Blade 6048 modular system.
The following commands have new functionality for ILOM 2.0.3.2:
This command now defaults to graceful shutdown, instead of a forced shutdown, of the system. The CMM will attempt to contact all the server modules and shut them down gracefully. If it cannot shut the server modules down, it reports back an error.
This command causes a forced shutdown, which is the same as the ILOM 2.0.3.1 version of stop /CH.
The following issues are not specific to one ILOM version.
/CH/LOCATE does not turn off when set to ON/Fast_Blink using ipmitool or CLI.
However, when the chassis Locate LED button is pressed, it times out and goes off after 30 minutes as expected.
If you change the CMM IP address in the SP web GUI, you cannot log into the web GUI using the new IP address. You can log into the CLI interface.
If you change the CMM IP address in the web GUI, log into the CLI to reconfigure the IP address again. then log into the web GUI with the new IP address.
For more information on configuring the IP address in the web GUI, refer to the Sun Integrated Lights Out Manager 2.0 User’s Guide.
The SP reports fan module (FM), network express module (NEM), and server module blade (BL) removal and insertion event logs repeatedly, though no insertion or removal has taken place.
When one FM or one PSU is removed from the Sun Blade 6048 chassis, the Tempfail LED on the rear panel turns on while the Service LED on the rear panel is off. The Service LED on the front panel turns on, which is the correct behavior.
When the FM or PSU is reinserted, the Tempfail LED on the rear turns off, and the Service LED on the front turns off.
The following issues have been fixed in ILOM 2.0.3.3:
When using the stop /CH command, the chassis Power/OK LED goes into standby state, and the chassis alert LED is also lights. This will only happen if the stop /CH command is successful. If the graceful shutdown does not occur, the alert LED will not light.
It should be possible to specify, per alert rule, what the destination port of the trap should be. Currently it is hard coded.
Copyright © 2009 Sun Microsystems, Inc. All rights reserved.