| Sun Blade X6250 Server Module Product Notes |    
|
| C H A P T E R 4 |
|
Service Processor Issues |
This chapter describes the service processor issues.
It is divided into the following sections:
This section describes service processor issues that affect systems regardless of the type of service processor.
The ILOM does not recognize messages from the BIOS warning that unsupported DIMMs are installed.
The contents of the floppy drive do not appear during redirection with a RHEL host.
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.
If you redirect a physical DVD or image file from Oracle Solaris to RHEL, when you select the CDROM icon, it appears empty.
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:
The DVD contents appear under /mnt.
After upgrading to SW3.0, the CLI command stop/SYS does not work.
Use the GUI or the stop -f /SYS command.
Remote JavaRconsole sessions do not support Swedish or Finnish keyboards.
Remote JavaRconsole sessions do not support Swiss-French keyboards.
After upgrading (flashing) the SP image to 3.0.6.13, the message that the upgrade succeeded does not appear in the event log.
During a Java Remote Console session, if you configure the BIOS, then select Save Changes and Exit, the JRC session might be disconnected.
Using ipmitool ... chassis identify 0 should cause the locate LED to blink, but it does not.
The default user can’t login to the SP when check_physical_presence is true.
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.
Upgrade to ILOM 3.0. 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.
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:
Do not select the Delay BIOS Update option.
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.
The ILOM and ELOM documentation states that you should clear CMOS if you can’t get output to the serial console after updating your ILOM firmware.
Use the procedure in the Sun Blade X6250 Server Module Service Manual.
In order to use the full functionality of ILOM 3.0, the server modules and the chassis must both be updated to ILOM 3.0. However, ILOM 3.0 is not required for the server modules to operate in a chassis with CMM 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.
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:
6250i20.bin has been replaced by 6250i203.bin
3B11.bat has been replaced by 3B14.bat
|
Caution - When you migrate from ELOM to ILOM 2.0, always migrate to ILOM 2.0.4 or later. Do not migrate to an earlier ILOM. |
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. If a message about unknown information is displayed, you can ignore it.
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. |
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.
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.
Connect a video monitor to the dongle cable to do the conversions.
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.
Upgrade the software to SW3.0.
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 X6250 Server Module for details.
Before upgrading from ELOM to ILOM, download software release 2.0.2 or newer.
In the ELOM-to-ILOM Migration Guide, it states that you must reseat your server module after making the transition. With software release 2.0.2 or newer, this is not necessary.
You can obtain downloads of the latest software releases at:
You cannot use Firefox 3.0.1 to transition from the ELOM to the ILOM.
Use Firefox 2.x.x or IE 7.0.5730.11.
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.
Disable the session time out in the web GUI when using remote storage device using remote console application.
This section describes service processor issues that affect the Chassis Management Module (CMM).
After a host reboot, the fans run at full speed momentarily. This is caused by a false overtemperature event.
Earlier versions of the CMM fail to provide the following information:
Upgrade to CMM SW3.0. See the ILOM documentation collection for details.
The CMM manages the power budget for the chassis. When an X6250 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 X6250 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.
2. Either reseat the server module, or reset the SP.
See the service processor documentation for details.
Enter the following CMM command:
-> set /CMM/powermgmt/advanced/reserve_psus=0
See the service processor documentation for details.
| Note - Because fully-configured X6250 server modules do not use more than 50% of the available power, the PSU can still be safely hotplugged. |
The Sun Blade 6000 CMM cannot identify the server module correctly, and lists it incorrectly as an “unknown blade.” When queried for the part number, it displays an incorrect number (501-7376) instead of the correct number (540-7254).
There is no workaround for this problem. Please contact your Sun service representative.
This section describes service processor issues that affect systems with an ELOM service processor.
Changing the ELOM root password can cause the ELOM to become inaccessible.
This issue has been fixed with ELOM version 4.0.54 of Software release 1.3.3.
To change the ELOM root password:
1. Login to the ELOM web GUI or CLI.
3. Logout of the ELOM web GUI or CLI.
4. Login again, using the new password.
See the Sun Blade X6250 Server Module Embedded Lights Out Manager Administration Guide for details.
The ELOM does not support setting time zones. Instead, it synchronizes with the time setting in the BIOS.
Use the BIOS to set the time zone.
Chassis fan failures are not logged in BMC (service processor) system event log (SEL) as a warning.
This does not impact the server module.
Check the chassis status using the ELOM. Refer to the Sun Blade X6250 Server Module Embedded Lights Out Manager Administration Guide for more information.
The Remote Console Java application fails to launch through the ELOM web GUI interface.
The Remote Console application requires JRE 1.5.0 or later.
Update the Java version on the host running the web browser and try again.
Disable the session time out in the web GUI when using remote storage device using remote console application.
This section describes service processor issues that affect systems with an ILOM service processor.
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.
You might occasionally see false hot-insertion or hot-removal events in the web GUI or the CLI event log. For example:
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.WOLF.IP.ADDR -U root -P changeme sel elist
shows component’s PRSNT sensor as Present or Absent.
This is fixed in release 2.0.2.
On systems equipped with ILOM, SLES 9 cannot be installed with RKVM in GUI mode because SLES 9 can’t start the X server.
Continue the installation in text mode.
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.
After you push the power button, there is a 5 to 6 second delay before the green LED responds.
The ILOM provides a UUID to uniquely and globally identify the server. However in the X6250 server module, the UUID is incorrectly formatted, and is not guaranteed to be unique.
Use another number (such as the server’s port 0 MAC address) to uniquely identify the server.
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.
The jumper-based method of resetting the ILOM root password described in the service processor documentation does not work on the X6250 server module.
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.
Modify the operating system configuration, or login to the operating system to perform a graceful shutdown.
On server modules equipped with an ILOM service processor, when the server module is plugged in:
Older versions of Linux do not support the ILOM's default absolute mouse mode.
If you have an older version of Linux on your server module, if you configure a remote management session and the mouse doesn't work, you must reset the ILOM mouse mode from absolute to relative.
1. Click the Remote Control tab.
2. Click the Mouse Mode Settings tab.
3. Select Relative Mouse Mode.
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. |
| Sun Blade X6250 Server Module Product Notes | 820-1186-33 |
|
Copyright © 2007, 2011, Oracle and/or its affiliates. All rights reserved.
To Migrate from ELOM to ILOM 2.0