Service Processor Issues

C H A P T E R 6

This chapter describes the service processor issues.

It is divided into the following sections:

General Service Processor Issues- Issues that affect systems with both ILOM and ELOM service processors.

CMM Service Processor Issues - Issues that affect the Chassis Management Module (CMM).

ELOM Service Processor Issues- Issues that affect systems with ELOM service processors only.

ILOM Service Processor Issues - Issues that affect systems with ILOM service processors only.

General Service Processor Issues

This section describes service processor issues that affect systems regardless of the type of service processor.

ILOM Does Not Recognize Message From BIOS Warning of Unsupported DIMM (6764365)

The ILOM does not recognize messages from the BIOS warning that unsupported DIMMs are installed.

This is fixed in SW3.1.

Floppy Image Does Not Appear During Redirection With RHEL Host (6828797)

The contents of the floppy drive do not appear during redirection with a RHEL host.

Workaround

1. Enter the following commands:

$ echo 2 >/sys/module/scsi_mod/max_luns

$ cat /sys/module/scsi_mod/max_luns

2. Try to select the floppy contents again.

The floppy contents appear.

Image Does Not Appear During Redirection of DVD from Solaris to RHEL (6876387)

If you redirect a physical DVD or image file from Solaris to RHEL, when you select the CDROM icon, it appears empty.

Workaround

1. Use the lsscsi command to check the device name of the DVD.

The system displays output similar to this:

[5:0:0:0] cd/dvd AMI Virtual CDROM 1.00 /dev/scd1

Note the device name, /dev/scd1.

2. Mount the device on a new or existing directory. For example:

# mount /dev/scd1 /mnt

The DVD contents appear under /mnt.

CLI Command `stop/SYS` Does Not Work After Upgrade to SW3.0 (687471)

After upgrading to SW3.0, the CLI command stop/SYS does not work.

Workaround

Use the GUI or the stop -f /SYS command.

JavaRConsole Does Not Support Swedish or Finnish Keyboards (6781995 and 6824306)

Remote JavaRconsole sessions do not support Swedish or Finnish keyboards.

Workaround

Upgrade to SW3.1.

JavaRconsole Does Not Support Swiss-French Keyboards (6753081)

Remote JavaRconsole sessions do not support Swiss-French keyboards.

Workaround 1

Upgrade to SW3.1

Workaround 2

Use a French keyboard.

‘Upgrade Succeeded’ Message Does Not Appear In Event Log (6875008)

After upgrading (flashing) the SP image to 3.0.6.13, the message that the upgrade succeeded does not appear in the event log.

This is fixed in SW3.1.

Exiting BIOS while Preserving BIOS Options Causes JRC To Lose Connection (6878636)

During a Java Remote Console session, if you configure the BIOS, then select Save Changes and Exit, the JRC session might be disconnected.

This is fixed in SW3.1.

Can Not Set Locate LED To Blink Using ipmitool (6876420)

Using ipmitool ... chassis identify 0 should cause the locate LED to blink, but it does not.

This is fixed in SW3.1.

Default User Can’t Login to SP When check_physical_presence Is True (6875869)

The default user can’t login to the SP when check_physical_presence is true.

This is fixed in SW3.1

SEL Log Incorrectly Reports “Correctable ECC Logging Limit Reached” (6855049)

The SEL log incorrectly reports “Correctable ECC logging limit reached” when it encounters a single correctable error. It also lights the fault LED, indicating incorrectly that a DIMM has failed.

Workaround

Upgrade to SW3.0 or later. It continues to report correctable errors when they occur, but it does not report that the logging limit is reached until it encounters 24 correctable errors in 24 hours, which is normal behavior.

Delaying BIOS Upgrade During Firmware Update Can Corrupt BIOS (CR 6813514)

The ILOM SP firmware upgrade procedure includes an option to delay the BIOS update until the host is reset. This allows you to update the firmware without resetting the host.

Three scenarios can cause this to corrupt your BIOS:

If you select this option, then power down the host and remove the server module from its slot before the BIOS update is complete.

If you select this option, then power down the host and power on the server module immediately before the BIOS update is complete.

If you start another SP firmware update before the BIOS update has been completed.

Workaround 1

Do not select the Delay BIOS Update option.

Workaround 2

If you use the Delay BIOS Update option, ensure that no one removes the server module from its slot, powers on the host, or attempts to update the SP firmware until after the host has been reset and the BIOS update is complete.

After the host is powered off, the BIOS update might take three to four minutes.

Command to Clear CMOS Doesn’t Work

The ILOM and ELOM documentation states that you sould clear CMOS if you can’t get output to the serial console after updating your ILOM firmware.

This command does not work.

It will be fixed in the next release.

Workaround

Use the procedure in the Sun Blade X6450 Server Module Service Manual.

Upgrading or Migrating From ELOM To ILOM 2.0 or ILOM 3.0

Your server module might be equipped with one of three service processors: ELOM, ILOM 2.0, or ILOM 3.0.

If you wish, you can upgrade (migrate) your ELOM service processor to ILOM 2.0 or ILOM 3.0.

To Migrate from ELOM to ILOM 2.0

Use the instructions in the ELOM-to-ILOM Migration User’s Guide.

Some of the file names in the ELOM-to-ILOM Migration User’s Guide are out of date. For example, the following files have been updated for SW2.0.3:

6450i20.bin has been replaced by 6450i203.bin

3B16.bat has been replaced by 3B19.bat

Caution - Filenames are sometimes updated more often than the documentation. Always use the files that came with the release you are installing, unless you receive specific instructions to do otherwise.

Caution - When you migrate from ELOM to ILOM 2.0, always migrate to ILOM 2.0.3. or later. Do not migrate to an earlier ILOM. We recommend that you migrate to the latest available version.

To Migrate from ELOM to ILOM 3.0

1. Migrate from ELOM to ILOM 2.0 as described in To Migrate from ELOM to ILOM 2.0.

2. Upgrade from ILOM 2.0 to ILOM 3.0 as described in the Sun Integrated Lights Out Manager Supplement for Sun Blade X6450 Server Module and in the ILOM 3.0 documentation collection.

The Existing BIOS Version Is Incorrect When Migrating from ILOM 2.0 to ILOM 3.0

During the ILOM 2.0 to ILOM 3.0 migration procedure, when you are updating the firmware, the existing BIOS version is listed as “unknown.”

This does not indicate a problem or a failure. You can ignore it.

Simultaneous Firmare Update (Flash) Sessions Could Cause Both To Fail

If you attempt to update (flash) the SP firmware from two different sessions at the same time, they will probably both fail and leave your SP in an unstable state.

Note - An SP firmware update takes about six minutes. Once it has started, you should not do anything else with the SP until it is finished.

Workaround

If your SP becomes unusable after updating the firmware, use the instructions in the corresponding documentation collection, and in the ILOM supplement documentation collection to recover.

Use the Video Connector When Migrating from ELOM to ILOM or from ILOM to ELOM

The Elom-to-Ilom Migration Guide states that you should connect a serial terminal to the dongle to do conversions. This is incorrect. Instead, connect a video monitor to the video connector on the dongle when doing the conversions.

Workaround

Connect a video monitor to the dongle cable to do the conversions.

`socflash` ILOM Recovery Utility Might Fail in Some Circumstances (6743159)

The ILOM supports the socflash recovery utility, which can be used to recover ILOM from DOS on newer server modules. However, in some circumstances, for example, when upgrading from ELOM to ILOM, socflash might fail with write errors.

Workaround

Use the afudos tool to flash the ILOM BIOS first. If the problem persists, retry the socflash.

See the Sun Integrated Lights Out Manager for Sun Blade X6450 Server Module for details.

Transition of ELOM to ILOM Does Not Work on Firefox 3.0.1

You cannot use Firefox 3.0.1 to transition from the ELOM to the ILOM.

Workaround

Use Firefox 2.x.x or IE 7.0.5730.11.

The Remote Console Session Times Out While a Storage Device is Mounted

After you have mounted a storage device through the web GUI remote console application, the web GUI session might time out, and the remote console connection to the mounted remote storage might be lost.

Workaround

Disable the session time out in the web GUI when using remote storage device using remote console application.

CMM Service Processor Issues

This section describes service processor issues that affect the Chassis Management Module (CMM).

Single-Sign On from the CMM to the Server Module ILOM Does Not Work (CR 6828014)

The single-sign on feature from the CMM to the server module ILOM does not work.

Workaround

Sign on directly to the server module’s ILOM.

CMM Reports Chassis Serial Number in The Wrong Field in a Sun Blade 6000 Chassis (CR 6837867)

On a Sun Blade 6000 chassis, when you enter the show /CH -d property command, the CMM displays the chassis serial number in the fru_serial_number field. The information in the product_serial_number field is irrelevant.

For example:

-> show /CH -d property
  /CH
    Properties:
        type = Chassis
        ipmi_name = /CH
        product_name = SUN BLADE 6000 MODULAR SYSTEM
        product_part_number = 541-1983-07
        product_serial_number = 0111APO-0814YT06B4 
        product_manufacturer = SUN MICROSYSTEMS
        fru_serial_number = 1005LCB-0802YM04JU
        fault_state = OK
        clear_fault_action = (none)
        power_state = On
-> version
CMM firmware 3.0.3.32
CMM firmware build number: 43452
CMM firmware date: Mon Mar 23 13:43:16 PDT 2009
CMM filesystem version: 0.1.22

You can also display the chassis serial number from a server module’s ILOM using the show /SYS/MIDPLANE command. For example:

-> show /SYS/MIDPLANE/
 
 /SYS/MIDPLANE
    Targets:
 
    Properties:
        type = Chassis
        ipmi_name = MIDPLANE
        product_name = SUN BLADE 6000 MODULAR SYSTEM
        product_part_number = 541-1983-07
        product_serial_number = 1005LCB-0802YM04JU
        product_manufacturer = SUN MICROSYSTEMS
 
    Commands:
        cd
        show

This display shows the chassis serial number in the product_serial_number field. Note that this number is identical to the fru_serial_number displayed by the CMM.

        product_serial_number = 1005LCB-0802YM04JU

CMM Information Missing

Earlier versions of the CMM fail to provide the following information:

Fan speed

PSU Information

NEM information

CMM FRU information

Workaround

Upgrade to CMM SW3.0. See the ILOM documentation collection for details.

CMM Shows X6450 Server Module with Hard Disk Drives

When you open the CMM, it displays pictures of the chassis and the components in the chassis. These pictures include a frontal view that includes pictures of the server modules.

The picture of the X6450 mistakenly shows the server module with four hard drives. This is incorrect.

In FIGURE 6-1, the CMM displays a chassis with an X6450 server module in BL3.

The chassis inventory shows an X6450 server module in BL3.

The picture of the front of the chassis shows (incorrectly) a server module with hard disk drives in BL3.

FIGURE 6-1 CMM With Incorrect Picture of X6450 Server Module

Incorrect Server Module Power Management Calculation Prevents Server Module From Powering On (6742133)

The CMM manages the power budget for the chassis. When an X6450 server module is inserted, cold booted, or the SP is reset, it reports its power requirements to the CMM.

Occasionally, the CMM incorrectly records that a X6450 server module requires 593W.

Normally, this will not cause any problems. However, in certain rare circumstances, this problem might be duplicated in many of the server modules in the chassis. If the total requested power exceeds the power allowance for the chassis, when a server module is inserted, cold booted, or the SP is reset, the host will fail to power on.

This problem is fixed in SW3.0.

Workaround 1

1. Power off the host.

2. Either reseat the server module, or reset the SP.

See the service processor documentation for details.

Workaround 2

Enter the following CMM command:

-> set /CMM/powermgmt/advanced/reserve_psus=0

See the service processor documentation for details.

Note - Because fully-configured X6450 server modules do not use more than 50% of the available power, the PSU can still be safely hotplugged.

ELOM Service Processor Issues

Mouse Redirection in Remote Console May Not Be Optimal

Mouse activity on the Remote Console may be unstable.

Workaround

For Solaris and Linux

1. In the X-Window user interface, open a terminal session.

2. Disable the hardware acceleration function with this command:

xset m 0

3. Press the mouse sync icon in the RKVM application.

For Windows

1. In the Control Panel, select Mouse Setting.

2. Select the Pointer Option tab.

3. Deselect Enhance Pointer Precision.

4. Press the mouse sync icon in the RKVM application.

CLI Path Changes With `start /SYS` Command

With ELOM, when the command start is issued in /SYS, the CLI path will change to /SP/AgentInfo. This has no impact.

Workaround

None needed.

Chassis Fan Failure Is Not Logged in SEL As a Warning

Chassis fan failures are not logged in BMC system event log (SEL) as a warning.

This does not impact the server module.

Workaround

Check the chassis status using the SP. Refer to the Sun Blade X6450 Server Module Embedded Lights Out Manager Administration Guide for more information.

Cannot Access Remote Console From ELOM Web GUI

The Remote Console Java application fails to launch through the ELOM web GUI.

Workaround

The Remote Console application requires JRE 1.6 or later.

Update the Java version on the host running the web browser and try again.

Server Module BMC IP Address Can Be Set From BIOS

To set the IP address from the BIOS:

1. Boot the Sun Blade 6450 Server Module and enter the BIOS set up menu.

2. Select the Server tab and press Enter.

3. Select Set AST2000 LAN Configuration and press Enter.

4. Select IP Address and press Enter.

5. Choose the desired IP Address Mode: DHCP or Static.

6. If Static then enter the IP address in the IP Address field.

7. Press the Escape key to go back, then select Subnet Mask.

8. Press F10 to save the settings, then reboot.

Note - The IP Address Mode does not change to the default (DHCP) when optimal defaults are loaded in the BIOS by pressing the F9 key. If the mode has been changed to Static, you can change it to DHCP manually from the Server tab of the BIOS set up menu.

Server Module Fails to Boot Because Insufficient Power Capacity Is Available

When you add a server module to a chassis, the CMM calculates the amount of power it requires. If the chassis cannot provide sufficient power:

The CMM prevents the server module from booting and places an entry in its error log.

The amber service required LED on the front panel of the server module blinks.

If your X6450 server module does not boot after initial installation:

Check to see if the amber service required LED is blinking.

Check the X6450 error log to see if the CMM is preventing the X6450 server module from booting due to insufficient power capacity.

Reconfigure the X6450 or the chassis to provide sufficient power.

Note - Previous releases of the X6450 server module required that you calculate the amount of power available, and the amount of power required by the X6450 server module. The CMM now does this automatically.

Calculating Power Consumption for Arbitrary Configurations

For any arbitrary configuration, you can use the power consumption per component information immediately below to calculate the power consumption per blade. With this, you can determine the number of blades that can be powered up simultaneously.

Base Blade: 80 Watts

CPU: 50 Watts for the L7345 CPU; 80 Watts for the E7220, E7320, and E7340 CPUs

DIMM: 13 Watts each

FEM: 15 Watts if FEM is populated

REM: 15 Watts if REM is populated

EM slot (PCIe Express Module) (2 per blade): 15 Watts each (static allocation, not based on presence of EM module)

Note - Power supply redundancy can be sacrificed to populate more blades in either the 6000 or 6048 chassis.

For mixed blade configurations, visit the Power Calculator web sites at:

http://www.sun.com/servers/blades/6000chassis/calc/index.jsp

http://www.sun.com/servers/blades/6048chassis/calc/index.jsp

ILOM Service Processor Issues

This section describes service processor issues that affect systems with an ILOM service processor.

ILOM 3.0 Only Supports Five User Sessions

ILOM 3.0 memory can only support five user sessions. If additional user sessions are created, it might terminate existing sessions. Also, under some conditions, it might crash the BIOS.

Unrecoverable Diskette Failure Message Appears in SEL Log After Upgrade to 3.0.3.33

An unrecoverable diskette failure message appears in the SEL log after upgrading the SP to SP3.0.3.33.

This message can be ignored. It will be fixed in a future release.

False Hotplug Chassis Events in SEL Log (6742169)

You might occasionally see false hot-insertion or hot-removal events in the web GUI or the CLI event log. For example:

Event ID    Class    Type    Severity    Date/Time    Description
5    Chassis    Action    major    Tue Sep 2 22:11:14 2008    Hot insertion of /SYS/PS0
4    Chassis    Action    major    Tue Sep 2 22:11:13 2008    Hot removal of /SYS/PEM0
3    Chassis    Action    major    Tue Sep 2 22:11:05 2008    Hot removal of /SYS/PS0
2    Chassis    Action    major    Tue Sep 2 22:11:05 2008    Hot insertion of /SYS/PEM0

You can disregard these events.

To be sure of hotplug events, use the IPMI SEL. It should always have the correct hotplug events. For example:

ipmitool -H MY.BLADE.IP.ADDR -U root -P changeme sel elist

shows component’s PRSNT sensor as Present or Absent.

SLES 9 Cannot Be Installed with RKVM In GUI Mode

On systems equipped with ILOM, SLES 9 cannot be installed with RKVM in GUI mode because SLES 9 can’t start the X server.

Workaround

Continue the installation in text mode.

Ignore Data-3 Portion of DIMM Error Message

When viewed using IPMItool version 1.8.9.4 or later (as provided with the service processor), DIMM error messages look like the following:

26 | Pre-Init Time-stamp   | Memory | Uncorrectable Error | Asserted | OEM Data-2 0xb5 OEM Data-3 0x0b

The Data-2 value identifies the faulty DIMM (channel B, slot 5 in this case). Ignore the Data-3 portion of the message.

Delay Before Green LED Responding to Power Button Push (6721024)

After you push the power button, there is a 5 to 6 second delay before the green LED responds.

OK To Remove LED is OFF During Flash Upgrade

On systems with an ILOM service processor, the OK to remove LED is OFF during a flash upgrade. This is unlike the behavior of systems with an ELOM service processor, where the OK to remove LED is ON during a flash upgrade.

Resetting SP Root Password Using J23 Jumper Does Not Work (6742739)

The jumper-based method of resetting the ILOM root password described in the service processor documentation does not work on the X6450 server module.

Workaround

Either:

Use BIOS Setup -> BMC Password Reset to reset the ILOM root password, or

Use the socflash ILOM recovery utility to restore the ILOM to the default configuration.

Graceful Shutdown of Host OS Does Not Work With Some Operating Systems (6723745)

The ILOM (GUI, CLI, and IPMI) performs a graceful OS shutdown by initiating an ACPI short button press.

Certain operating systems do not honor the ACPI short button press. For example, this might be the case when the console is logged in.

Workaround

Modify the operating system configuration, or login to the operating system to perform a graceful shutdown.

Green Power LED Works Differently with ILOM

On server modules equipped with an ILOM service processor, when the server module is plugged in:

The three status LEDs blink three times at 1Hz.

The green LED blinks at 1Hz during POST.

After post the green LED either:

Stays on if the server module is powered on.

Blinks 2.9 sec off/.1 sec on if the server module is on standby power.

Mouse Does Not Work During Remote Session (CR 6730145)

Older versions of Linux do not support the ILOM’s default absolute mouse mode.

With older versions of Linux on your server, if you configure a remote management session and the mouse doesn’t work, you must reset the ILOM mouse mode from absolute to relative.

Workaround

1. Click the Mouse Mode Settings tab.

2. Select Relative Mouse Mode.

3. Select Save.

The ILOM displays a message, then reboots itself. When the ILOM has rebooted, you can re-establish the remote session and the mouse will work.

Note - In order to switch control between the local mouse and the host mouse, press Alt +m.

General Service Processor Issues

ILOM Does Not Recognize Message From BIOS Warning of Unsupported DIMM (6764365)

Floppy Image Does Not Appear During Redirection With RHEL Host (6828797)

Workaround

Image Does Not Appear During Redirection of DVD from Solaris to RHEL (6876387)

Workaround

CLI Command stop/SYS Does Not Work After Upgrade to SW3.0 (687471)

Workaround

JavaRConsole Does Not Support Swedish or Finnish Keyboards (6781995 and 6824306)

Workaround

JavaRconsole Does Not Support Swiss-French Keyboards (6753081)

Workaround 1

Workaround 2

‘Upgrade Succeeded’ Message Does Not Appear In Event Log (6875008)

Exiting BIOS while Preserving BIOS Options Causes JRC To Lose Connection (6878636)

Can Not Set Locate LED To Blink Using ipmitool (6876420)

Default User Can’t Login to SP When check_physical_presence Is True (6875869)

SEL Log Incorrectly Reports “Correctable ECC Logging Limit Reached” (6855049)

Workaround

Delaying BIOS Upgrade During Firmware Update Can Corrupt BIOS (CR 6813514)

Workaround 1

Workaround 2

Command to Clear CMOS Doesn’t Work

Workaround

Upgrading or Migrating From ELOM To ILOM 2.0 or ILOM 3.0

The Existing BIOS Version Is Incorrect When Migrating from ILOM 2.0 to ILOM 3.0

Simultaneous Firmare Update (Flash) Sessions Could Cause Both To Fail

Workaround

Use the Video Connector When Migrating from ELOM to ILOM or from ILOM to ELOM

Workaround

socflash ILOM Recovery Utility Might Fail in Some Circumstances (6743159)

Workaround

Transition of ELOM to ILOM Does Not Work on Firefox 3.0.1

Workaround

The Remote Console Session Times Out While a Storage Device is Mounted

Workaround

CMM Service Processor Issues

Single-Sign On from the CMM to the Server Module ILOM Does Not Work (CR 6828014)

Workaround

CMM Reports Chassis Serial Number in The Wrong Field in a Sun Blade 6000 Chassis (CR 6837867)

CMM Information Missing

Workaround

CMM Shows X6450 Server Module with Hard Disk Drives

Incorrect Server Module Power Management Calculation Prevents Server Module From Powering On (6742133)

Workaround 1

Workaround 2

ELOM Service Processor Issues

Mouse Redirection in Remote Console May Not Be Optimal

Workaround

CLI Path Changes With start /SYS Command

Workaround

Chassis Fan Failure Is Not Logged in SEL As a Warning

Workaround

Cannot Access Remote Console From ELOM Web GUI

Workaround

Server Module BMC IP Address Can Be Set From BIOS

Server Module Fails to Boot Because Insufficient Power Capacity Is Available

Calculating Power Consumption for Arbitrary Configurations

ILOM Service Processor Issues

ILOM 3.0 Only Supports Five User Sessions

Unrecoverable Diskette Failure Message Appears in SEL Log After Upgrade to 3.0.3.33

False Hotplug Chassis Events in SEL Log (6742169)

SLES 9 Cannot Be Installed with RKVM In GUI Mode

Workaround

Ignore Data-3 Portion of DIMM Error Message

Delay Before Green LED Responding to Power Button Push (6721024)

OK To Remove LED is OFF During Flash Upgrade

Resetting SP Root Password Using J23 Jumper Does Not Work (6742739)

Graceful Shutdown of Host OS Does Not Work With Some Operating Systems (6723745)

Workaround

Green Power LED Works Differently with ILOM

Mouse Does Not Work During Remote Session (CR 6730145)

Workaround

CLI Command `stop/SYS` Does Not Work After Upgrade to SW3.0 (687471)

`socflash` ILOM Recovery Utility Might Fail in Some Circumstances (6743159)

CLI Path Changes With `start /SYS` Command