| Sun Blade 6000 Modular System Product Notes |    
|
| Sun Blade 6000 Modular System Product Notes |
|
| C H A P T E R 3 |
Oracle ILOM Notes and Issues |
This chapter describes the Oracle Integrated Lights Out Manager (ILOM) service processor updates and issues.
This chapter includes the following sections:
Make sure that you download the software release that is supported with your chassis model. For information on determining which chassis model that you have, refer to the Sun Blade 6000 Modular System Service Manual.
This section describes information specific to the software releases available for Sun Blade 6000 modular system.
The following software releases are available:
The following sections describe the updates for each of the 4.x software releases:
CMM software 4.2.5 (Oracle ILOM 3.1.1.10.e) provides bug fixes for several minor issues for the A90-D and 7105379 chassis. Refer to the Read Me file included with the download for information about firmware component compatibility with this release.
CMM software 4.2.4 (Oracle ILOM 3.1.1.10.d) provides a fix for bug 18285751 (Java 7u51 requirements for RIAs). Refer to the Read Me file included with the download for information about firmware component compatibility with this release.
CMM software 4.2.3 (Oracle ILOM 3.1.1.10.c) provides bug fixes for several minor issues for the A90-D and 7105379 chassis. Refer to the Read Me file included with the download for more information about which issues are fixed.
CMM software 4.2.2 (Oracle ILOM 3.1.1.10.b) provides bug fixes for several minor issues for the A90-D and 7105379 chassis. Refer to the Read Me file included with the download for more information about which issues are fixed.
CMM software 4.2.1 (Oracle ILOM 3.1.1.10.a) provides bug fixes for several minor issues for the A90-D chassis. Refer to the Read Me file included with the download for more information about which issues are fixed.
Chassis monitoring module (CMM) software 4.2 (Oracle ILOM 3.1.1.10) includes several changes to the Web interface and CLI.
For detailed information about Oracle ILOM 3.1.x, refer to the Oracle ILOM 3.1 documentation library at:
http://www.oracle.com/pls/topic/lookup?ctx=ilom31
Server modules that have Oracle ILOM 3.0 installed, are supported in a chassis that has been upgraded to Oracle ILOM 3.1.x.
| Note - If you are using a 3.0.x server module or a 3.0.x CMM, use the 3.0 Oracle ILOM documentation. If you are using a 3.1.x server module or 3.1.x CMM, use the 3.1 Oracle ILOM documentation. |
Chassis monitoring module (CMM) software 4.1 (Oracle ILOM 3.0.16) includes the following new features:
CMM software 4.0 (Oracle ILOM 3.0.12) provides support for the Sun Blade 6000 modular system A90-D chassis. SW 4.0 is not supported on the A90-B chassis.
The A90-D chassis requires a minimum of SW 4.0, so do not update the CMM with any previous versions.
The following additional features are supported in this release for the Sun Blade 6000 modular system A90-D chassis:
| Note - IPV6 is not supported for the A90-B chassis. |
Refer to the Oracle Integrated Lights Out Manager CMM Administration Guide for more information about configuring the IPV6 network protocol.
The following sections describe the updates for each of the 3.x software releases:
CMM software 3.3.9 (Oracle ILOM 3.0.12.11.h) provides a fix for Bug 19880886 (Bash Shellshock Command Injection Vulnerability) for the A90-A/B chassis. Refer to the Read Me file included with the download for information about firmware component compatibility with this release.
CMM software 3.3.8 (Oracle ILOM 3.0.12.11.g) provides a fix for bug 18287369 (Java 7u51 requirements for RIAs) for the A90-A/B chassis. Refer to the Read Me file included with the download for information about firmware component compatibility with this release.
CMM software 3.3.7 (Oracle ILOM 3.0.12.11.f) provides bug fixes for several minor issues for the A90-A/B chassis. Refer to the Read Me file included with the download for more information about which issues are fixed.
CMM software 3.3.6 (Oracle ILOM 3.0.12.11.e) provides bug fixes for several minor issues for the A90-A/B chassis. Refer to the Read Me file included with the download for more information about which issues are fixed.
CMM software 3.3.5 (Oracle ILOM 3.0.12.11.d) provides bug fixes for several minor issues for the A90-A/B chassis. Refer to the Read Me file included with the download for more information about which issues are fixed.
CMM software 3.3.2 (Oracle ILOM 3.0.12.11.a) is now available. This software releases fixes several chassis issues. Refer to the Read Me file included with the download for more information about which issues are fixed.
CMM software 3.3 (Oracle ILOM 3.0.12) provides support for the SPARC T3-1B server module. This software release also provides several bug fixes. See Issues Fixed in SW 3.3 for more information.
CMM software release 3.2.2 (Oracle ILOM 3.0.10.15b) is required for SGX-SAS6-REM-Z support on the Sun Blade X6270 M2 server module.
Additional firmware updates are also required for SAS-2 NEMs and storage modules. Refer to the component documentation for more information.
The following CMM Software 3.2.1 notes are included in this section:
Starting with CMM software release 3.2.1 (Oracle ILOM 3.0.10.15a), you can now upgrade your Sun Blade 6000 modular system chassis storage assignments to enable SAS-2 capable server modules, storage modules and NEMs.
You must have the following hardware and firmware installed in the chassis to enable SAS-2 storage assignments between a server module and storage module.
Refer to server module, storage module, and NEM documentation for availability and additional requirements for these SAS-2 components.
Sun Blade Zone Manager is an Oracle ILOM-based application that allows you to assign storage devices from a Sun Blade 6000 storage module to SAS-2 capable server modules. Sun Blade Zone Manager is available in Oracle ILOM 3.0.10.15a (SW 3.2.1) and later. See the Oracle Integrated Lights Out Manager (ILOM) CMM Administration Guide for Sun Blade 6000 and Sun Blade 6048 Modular Systems.
The best practice is to use the latest released firmware for all Sun Blade 6000 modular system components. The current release, and most recent previous release, are tested and available at from My Oracle Support.
You can access specific software releases from:
http://www.oracle.com/technetwork/systems/patches/firmware/release-history-jsp-138416.html
Oracle 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. Oracle recommends that all components use the latest available firmware or the prior version.
To use the full functionality of Oracle ILOM 3.x, the server modules must also be updated to Oracle ILOM 3.x. However, Oracle ILOM 3.x is not required for the server modules to operate in a Oracle ILOM 3.x CMM chassis. Refer to your server module documentation for available Oracle ILOM versions. This document also contains information about known issues with Oracle ILOM version compatibility.
For instructions on updating the firmware, refer to the Oracle ILOM documentation for the Oracle ILOM version that is running on your system.
The Oracle Integrated Lights Out Manager 3.x Supplement for Sun Blade 6000 Modular System has specific Oracle ILOM 3.x information for the Sun Blade 6000 modular system.
Additional Oracle ILOM documentation is available in the Oracle ILOM documentation libraries:
The following issues apply to the Sun Blade 6000 modular system Oracle ILOM:
The issues in this section are specific to the Oracle ILOM 3.0.12.11d on the Sun Blade 6000 modular system.
The service processor resets itself when the server module firmware is updated from the CMM CLI /CH/BLx/SP/cli_level. This problem is caused by the CMM hardware limitation.
Update the server module firmware from blade CLI, rather than the CMM CLI.
The issues in this section are specific to the Oracle ILOM 3.0.2.32 on the Sun Blade 6000 modular system.
When updating the CMM Oracle ILOM firmware from 2.0.3.10 to 3.0.3.32, the share sensor ID is changed, so a server module running Oracle ILOM 2.x cannot read the share sensor correctly.
When the CMM is updated to Oracle ILOM 3.0, reset all server module SPs that are running Oracle ILOM 2.x.
The issues in this section are specific to the Oracle ILOM 2.0.3.2 on the Sun Blade 6000 modular system.
The following commands have new functionality for Oracle 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 Oracle ILOM 2.0.3.1 version of stop /CH.
The issues in this section are specific to the Oracle ILOM 2.0.3.1 on the Sun Blade 6000 modular system.
Software 1.1 for the Sun Blade 6000 modular system contains a build of Oracle ILOM 2.0.3.1 with a serious bug. Upgrading to this Oracle ILOM version causes some FRU data to be lost. Because of this, software 1.1 has been withdrawn and replaced by software 1.1a.
If you have not yet upgraded to the Oracle ILOM provided with software 1.1, this issue does not affect you. Simply discard any copies of software 1.1 and obtain software 1.1a which contains Oracle ILOM firmware with the fix.
If you have upgraded to the Oracle ILOM provided with software 1.1, you must install the Oracle ILOM firmware provided with software 1.1a. Doing so will both remove the bug and recover some of the FRU data that was previously not viewable. The remaining FRU data must be re-entered manually.
You can identify your Oracle ILOM firmware using the Oracle ILOM CLI or web interface:
In the information you obtain, find the Firmware Version (just “Firmware” in the CLI) and Firmware Build Number. Depending on the values you obtain, you should take one of the following actions:
The Oracle ILOM bug causes the following FRU data to be lost:
You can recover the Product Part Number and Product Serial Number by installing the Oracle ILOM firmware provided with Software 1.1a. If you downgraded the Oracle ILOM after observing the problem, Product Part Number and Product Serial Number must be re-entered manually.
The Chassis Serial Number will not be recovered with the Software 1.1a update and must be re-entered in any case.
| Note - Contact Oracle service for information on how to create a Sun service account. |
Follow these steps to re-enter the lost FRU data:
1. Use SSH to log in to the “sunservice” Oracle ILOM account. From the Oracle Solaris OS or Linux command line:
where ipaddress is the service processor IP address.
2. Enter one of the following commands.
servicetool --fru_chassis_serial_number
servicetool --fru_product_part_number --fru_product_serial_number --fru_chassis_serial_number
3. Enter the FRU ID numbers when prompted.
The issues in this section are not specific to one Oracle ILOM version.
The Remote Console for Sun Blade X4-2B server module SW1.2 fails when you launch it as follows:
1. Log in to CMM ILOM from the browser.
2. Choose your X4-2B server module from "Manage Menu" at the top left corner.
3. Press "Launch Remote Console".
This affects all CMM firmware SW3.3.9/SW4.2.5 and earlier.
To access the Sun Blade X4-2B Server Module (SW 1.2), bypass the CMM and do the following:
1. Access the server module service processor (SP) directly using the SP IP address.
2. Start a Remote Console session.
In order to ensure safe and reliable network operation, and continuation of PCIe/SAS IO expander services for Sun Blade servers installed in Sun Blade 6000 chassis, the CMM ILOM has implemented the behavior described in this section.
For some network express module (NEM) types, the CMM ILOM can reset the NEM service processor (SP) only if NEM is in one of the following states:
If the NEM is in any other state, the CMM will report a failure in resetting the NEM. See the following example:
Are you sure you want to reset /CH/NEM0/SP (y/n)? y
Performing hard reset on /CH/NEM0/SP
Performing hard reset on /CH/NEM0/SP failed
reset: Cannot perform the requested operation yet; please try again later.
This applies to the following NEM types:
To reset the NEM SP, login to NEM service processor and perform the reset from the individual NEM SP.
Are you sure you want to reset /SP (y/n)? y
Refer to the NEM documentation for more information.
The FRU ID information for the A251 power supply unit is too long for IMPItool to read. The FRU ID reading for this component might be incorrect or missing. This issue only affects the A251 power supply in the A90-D model chassis.
When the CMM is at software version 3.x and the Sun Blade X6220 server module is at 2.x, the sensor readings for the blade are not readable through the CMM.
| Note - The Sun Blade X6220 server module is not capable of measuring its own power, so the VPS parameter is not readable, regardless of the blade’s Oracle ILOM version. |
Update the Sun Blade X6220 server module to SW 3.x (Oracle ILOM 3.x or later).
The Oracle ILOM SP may in rare circumstances stop responding on serial management port. You can avoid this issue by choosing one of the following workarounds to reset and restart the SP:
The /CH/BLx/SP/cli/ user command accepts invalid values.
Insert a valid user name in user property field.
When an LDAP or radius user tries to authenticate, authentication is not allowed:
To authenticate LDAP and radius user, and connect as the desired user, use the root login then set the CLI user property to allow remote connection.
The CMM might not allow you to change or detect the blade IP address. To change the IP address, connect to the blade service processor, then use the blade’s service processor Oracle ILOM interfaces to update and display the IP address.
There are several methods available to access the blade Oracle ILOM, use one of the following workarounds:
The issues fixed in a specific software release are listed in this section. The issues are listed under the software (SW) release that provides a fix for the issue. Some of the issues were found in a particular software update.
This issue only applies to the A90-D chassis. This issue was introduced in SW 4.0 and fixed in Oracle ILOM 4.1.
The Locate LED on the CMM might not illuminate when either the Locate button is pressed or the LED is turned on through the Oracle ILOM Web or CLI interface.
The chassis Locate LED or NEM Locate LED can also be used to identify the CMM location.
You can use the Locate button to illuminate the LEDs:
Refer to the Sun Blade 6000 Server Module Service Manual or NEM documentation for information on locating the Locate buttons and LEDs.
You can also use the Oracle ILOM CLI or Web interface to illuminate the NEM LEDs:
-> set /CH/NEMx/LOCATE value=Fast_Blink
-> set /CH/NEMx/LOCATE value=Off
Refer to the Oracle Integrated Lights Out Manager (Oracle ILOM) 3.0 Web Interface Procedure Guide for information on turning about the LEDs using the Web interface.
This issue applies to both the A90-B and the A90-D chassis.This issue was introduced in SW 4.0 and fixed in Oracle ILOM 4.1.
In the Sun Blade 6000 chassis with Sun Blade Storage Module M2, if you cycle chassis power from the CMM using the stop /CH and start /CH commands, one or more of the following components might be diagnosed with a fault, even though the component is not faulty:
You will notice faults as follows in the CLI:
1. Cycle chassis power from the CMM CLI with the following commands:
|
Caution - This will reset all power to the blades and impact the OS running on the blades. This is a service interruption. |
2. Clear the faults on the Sun Blade 6000 Virtualized Multi-Fabric 10GE NEM M2 and Sun Blade Storage Module M2.
In the following examples, the NEM is in Slot 0 and the blade storage module is in slot 9:
-> set /CH/NEM0 clear_fault_action=true
-> set /CH/BL9 clear_fault_action=true
3. Type the following command:
4. If the components are still faulty after repeating Steps 1-3 three times, continue to Step 5.
5. Cycle AC power to the PSUs by doing one of the following:
6. Clear the faults on the Sun Blade 6000 Virtualized Multi-Fabric 10GE NEM M2 and Sun Blade Storage Module M2.
In the following example, the NEM is in slot 0 and the storage module is in slot 9:
-> set /CH/NEM0 clear_fault_action=true
-> set /CH/BL9 clear_fault_action=true
7. Type the following command:
If no faults are shown for the Sun Blade 6000 Virtualized Multi-Fabric 10GE NEM M2 or Sun Blade Storage Module M2, then the workaround was successful.
8. If components are still faulty, contact your authorized service provider.
This issue was introduced in SW 4.0 and fixed in Oracle ILOM 4.1.
The following chassis faults do not have Knowledge Articles available.
When you drill down to /CMM/faultmgmt/ to review these faults, the
sunw-msg-id field will contain ---. For example:
If Oracle ILOM displays the fault.chassis.power.undervoltage fault, this indicates that the specified PSU might be in need of repair or replacement.
If Oracle ILOM displays the fault.chassis.sas.comm.fail fault, this indicates a SAS communication error fault between the CMM and storage blades or NEMs. Determine whether there are any problems associated with the blade or NEM with which the CMM is failing to communicate.
If either of these two faults persist, or you require assistance replacing one of the failed components, contact your authorized service provider.
This issue applies only to the A90-D chassis. This issue was introduced in SW 4.0 and fixed in Oracle ILOM 4.1.
When all the blades in the Sun Blade 6000 M2 chassis are powered off, the fan modules will be set to an rpm value which is interpreted as a fault. In these cases, the fans will typically reduce the speed of one fan in the module to zero, while maintaining a constant setting for the second fan in the module.
It is safe to ignore cases when a fan is marked faulty and the power has been removed from all blades in the chassis. The fault should clear itself automatically when power is restored to the blades. If the fault persists, the fans may require service.
From the Oracle ILOM CLI, the fault can be seen from the fault management section as shown in the following example:
One of the two fans within the fan module will typically show a value of zero as with /CH/FM1/F1/TACH in the example below.
Although the fans are functioning normally, the Oracle ILOM fault handler will report a fault due to the rpm value being below the minimal expected range.
This issue applies to both the A90-B and A90-D chassis. This issue was introduced in SW 4.0 and fixed in Oracle ILOM 4.1.
Updating the Sun Blade 6000 Ethernet Switched NEM 24p 10GE firmware from the CMM sometimes fails when the tftp protocol is used as with the following example:
-> set load_uri=tftp://10.182.92.28/sp/Sun_Blade_6000_Ethernet_Switched_NEM_24p_10GE.pkg set: Component firmware update failed. |
Use an alternate protocol such as ftp, http, or sftp.
The following example uses ftp:
-> set load_uri=ftp://root:abc123@10.182.92.28//tftpboot/sp/Sun_Blade_6000_Ethernet_Switched_NEM_24p_10GE.pkg Load successful. |
This issue was introduced in SW 4.0 and fixed in Oracle ILOM 4.1.
Output from the ipmitool sdr elist command shows V_3V3 readings of
0 Volts for a PSU that is not installed. For example, if PS1 is removed from the chassis and the ipmitool sdr elist command is invoked, the following might appear:
Since PS1 is not present, the correct display forPS1/V_3V3 is:
The V_3V3 reading can be ignored and is not indicative of any Oracle ILOM errors or faults.
This issue was introduced in SW 4.0 and fixed in Oracle ILOM 4.1.
When the -h flag for help is specified with the Oracle ILOM shell load command, it displays load: Command Failed at the end of the usage options. For example:
The load: Command Failed message can be safely ignored when the load command is invoked with the -h option, as load in this scenario does not attempt to install an image and the Command Failed message is erroneous.
If this message is seen without the -h option, it indicates a failure to load and install an image. The user options displayed by the -h flag are otherwise correct.
The following issue is fixed in software release 3.3.
| Note - Additional issues that were fixed in SW 3.3 are listed in a ReadMe that is included with the software download. |
If the CMM is replaced or moved to a different chassis, the first time Oracle ILOM boots an incorrect host name or product serial number might appear.
After Oracle ILOM boots, reset the CMM with one of the following:
a. Log in to the Oracle ILOM Web interface as an Administrator or Operator.
b. Navigate to the CMM Maintenance tab.
c. Click the Reset Components sub-tab and select /CH/CMM.
The CMM reboots with the correct product information.
When a Sun Blade 6000 chassis or 6048 shelf is powered on, the fan speed quickly ramps up from minimum speed to maximum speed, then ramps down to minimum speed. This does not allow enough time for the fans to cool the blades, so the fan speed ramps back up again, which causes a fan speed oscillation effect.
The CMM steps up the fans one step every 40 seconds (so there’s a slower ramp-up time), and decreases fan speeds one step every two minutes to allow appropriate temperature adjustment of all blades.
The following algorithm is also applied to the fan actions. Starting from number 1 in the list, the first condition that is true determines the fan speeds:
1. If at least one blade is at a critical temperature level, then blast fans.
2. If at least one blade is at a hot temperature level, then fan speeds increase.
3. If at least one blade is at a cool temperature level, then fan speeds are lowered
4. If at least one blade is at normal level, then fans are held at current speed.
5. If none of the preceding conditions are true, the blades are powered off, so the fans are turned off.
This issue was introduced in Oracle ILOM 3.0.6.11 and fixed in Oracle ILOM 3.0.10.
When a NEM is hot plugged into a powered on chassis, the NEM should not power on until the ATTN button is pushed. With Oracle ILOM 3.0.6.11, the Sun Blade 6000 Virtualized Multi-Fabric 10GbE NEM powers on when inserted in the chassis and before the ATTN button is pressed.
This issue was fixed in Oracle ILOM 3.0.10.
When the blade is already powered on, you should not be able to set its permitted_power to a value lower than what is currently already allocated to it. The error message that appears on both the CLI and web interface when you attempt to allocate a lower power value should be more descriptive of the reason why the power level is not permitted.
This issue was introduced in Oracle ILOM 3.0.6.11 and fixed in Oracle ILOM 3.0.10.
When trying to reset the Sun Blade 6000 Virtualized Multi-Fabric 10GbE NEM SP from the CMM, the reset does not work.
This issue was fixed in Oracle ILOM 3.0.10.
When trying to start a target that has already been started, the following message should appear:
This message does not appear when start /CH or start /CH/NEMx is attempted when the target has already been started.
This issue was fixed in Oracle ILOM 3.0.10.
Booting the chassis by unplugging and plugging in the AC power causes the fans to run at an abnormal speed.
Execute the following commands to return the fan speed to normal:
This issue was fixed in Oracle ILOM 3.0.10.
When the OK-to-Remove LED is pressed on the Sun Blade 6000 Virtualized Multi-Fabric 10GbE NEM, the NEMx/OK2RM value in the CMM is still set to OFF.
This issue was fixed in Oracle ILOM 3.0.10.
The CMM requires that the NEM light the OK status LED in order to be viewed as powered up and operational. The LED should signal the status of the switch itself and only light the LED when it is operational and blink when the switch is not operational or in some transitional state.
This issue was found in Oracle ILOM 3.0.3.32 and fixed in Oracle ILOM 3.0.6.11.
After upgrading the Sun Blade 6000 modular system CMM to Oracle ILOM version 3.0.3.32, the CMM Power/OK LED does not turn on.
This issue was fixed in Oracle ILOM 3.0.6.11.
With Sun Blade X6275 (and possibly Sun Blade X6270) blades, the chassis fan speed can run as low as 1800 RPM, even when the blades are powered on.
With CMM Oracle ILOM 3.0.3.11.c (SW 3.1.3), the CMM sets the fans to a minimum speed of approximately 2000 RPM.
This issue was fixed in Oracle ILOM 3.0.6.11b.
When using the show /CH/NEM[0|1] command from the CMM Oracle ILOM, the name for the Sun Blade 6000 Ethernet Switched NEM 24P 10GE NEM is not displayed in the fru_name field.
This issue was fixed in Oracle ILOM 3.0.6.11b.
After typing the set /CH/NEM0/LOCATE value=fast_blink command from the CMM, the LOCATE LED for the NEM does not blink as fast as expected.
This issue was fixed in Oracle ILOM 3.0.6.11.
Sometimes, the chassis amber LED lights when a power supply is plugged into the PS0 slot.
When trying to reset the Sun Blade 6000 Virtualized Multi-Fabric 10 GbE Network Express Module from the Sun Blade 6000 modular system CMM, the NEM is left in a powered off state, however, the NEM STATE value is running.
This issue was fixed in Oracle ILOM 3.0.6.11.
When the chassis contains blades that do not run Oracle ILOM, displaying blade information through the CMM web interface can be slow.
This issue was fixed in Oracle ILOM 3.0.6.11.
Power supply fan speeds should be adjusted to run slower when the chassis power is off or less than half the blade slots are populated
Refer to the Oracle Integrated Lights Out Manager (Oracle ILOM) CMM Administration Guide for information on lowering the PSU fan speed.
This issue was fixed in Oracle ILOM 3.0.6.11.
The CMM assembly product number should be displayed in Product Number field for the CMM FRU device description.
This issue was found in Oracle ILOM 2.0.3.10 and fixed in Oracle ILOM 3.0.3.32.
The CMM OK LED which is located on the CMM front panel lights up for approximately one minute before turning off whenever the CMM is inserted into chassis or chassis AC is completely power cycled.
This issue was fixed in Oracle ILOM 3.0.3.32.
The Oracle ILOM CMM service processor does not report current detailed power supply or fan status information.When a PSU fan is removed, the CLI and IPMItool does not report this change. To determine fan or power supply status information, you should check the following objects:
This issue was fixed in Oracle ILOM 3.0.3.32.
/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.
This issue was fixed in Oracle ILOM 3.0.3.32.
When running Oracle 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.
This issue was found in Oracle ILOM 2.0.3.10 and fixed in Oracle ILOM 3.0.3.32.
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.
This issue was fixed in Oracle ILOM 3.0.3.32.
If you change the CMM IP address in the SP web interface, you cannot log in to the web interface using the new IP address. You can only log in to the CLI interface.
If you change the CMM IP address in the web interface, you must log in to the CLI interface to reconfigure the IP address, then log in to the web interface with the new IP address.
To change the IP address in the Oracle ILOM CLI:
1. Log in to the Oracle ILOM CLI.
2. Type the following commands to set the SP working directory:
3. Type the show command to view the IP address assigned.
4. Type the following commands to change the existing settings.
set pendingipaddress=ipaddress
Where ipddress is the new IP address.
For more information about configuring the IP address in the web interface, refer to the Oracle Integrated Lights Out Manager User’s Guide for the version of Oracle ILOM that you are running.
This issue was found in Oracle ILOM 2.0.3.10 and fixed in Oracle ILOM 3.0.3.32.
If you are running Oracle ILOM version 2.0.3.10, you will not be able to set the CMM netmask through the CMM Oracle ILOM.
To set the netmask, you can manually edit the /conf/interfaces file using the sunservice account or 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).
This issue was fixed in Oracle ILOM 3.0.3.32.
The stop /CH/NEMx, start /CH/NEMx and reset /CH/NEMx commands for the Sun Blade 6000 Virtualized Multi-Fabric 10 GbE NEM (Virtualized NEM) have been disabled in the CMM.
|
|
Caution - Disruption of host operation: Do not attempt to reset the Virtualized NEM SP, as it can cause a reset of the entire NEM, which disrupts host operation for all blades using the NEM. |
This issue was fixed in Oracle ILOM 2.0.3.10.
The front panel power LED does not power on immediately.
Oracle ILOM service processor bootup sequence takes approximately one minute. You should wait for this boot process to complete, then reexamine the LEDs.
This issue was fixed in Oracle ILOM 2.0.3.3.
It should be possible to specify, per alert rule, what the destination port of the trap should be. Currently it is hard coded.
This issue was fixed in Oracle 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 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.
When running a test on a Sun Blade 6000 Disk Module or Sun Blade 6000 Multi-Fabric Network Express Module, a message similar to the following is displayed in the SEL:
8e00 | 06/11/2008 | 14:19:49 | Module/Board nem1.state | Transition to Degraded 8f00 | 06/11/2008 | 14:20:01 | Module/Board nem1.state | Transition to Running
These messages can be safely ignored.
This issue was fixed in Oracle ILOM 2.0.3.2.
When a power supply unit (PSU) is removed from the chassis, the PSU status might report different values in the /CH/PSN ILOM CM CLI objects.
If a power supply is removed, and you receive a report of different PSU status values, you can safely ignore information displayed in the /CH/PSN ILOM CM CLI objects.
This issue was found in Oracle ILOM 1.1.6 and fixed in Oracle ILOM 2.0.3.2.
CMM Oracle ILOM service processor provides monitoring and management of chassis power supplies. In certain circumstances, the power supply kill signal is being asserted, which causes DC output of the power supply to stop.
Update your firmware to Oracle ILOM version 2.0.3.2 in software release 1.2 to fix this issue.
This issue was fixed in Oracle ILOM 2.0.3.1.
The Oracle ILOM service processor does not report threshold information that is not used or controlled by the service processor. Therefore, fan and power supply threshold values cannot be read by the CMM and blades.
This issue was fixed in Oracle ILOM 2.0.3.1.
When a fan is removed or installed, an assert and deassert event is logged for each event in the IPMI SEL log. The example below shows the assert and deassert event messages displayed when the fan is removed or installed:
These messages can be safely ignored.
This issue was fixed in Oracle ILOM 2.0.3.1.
NET MGT 1 Port which is the Ethernet port of the CMM will be disabled by default. NET MGT 1 Port will be delivered disable because of the inability to guarantee the setup of your network, if your network is not configured properly using this port can cause network degradation.
Future software upgrades will allow for either port to be connected, and possibly both ports to be enabled if the certain features of the network can be guaranteed.
This issue was fixed in Oracle ILOM 2.0.3.1.
The chassis reports as powered on when it is powered off.
Reset the CMM, then retry the operation again.
This issue was fixed in Oracle ILOM 2.0.3.1.
The Oracle ILOM CMM service processor only allows a single remote Oracle ILOM CLI session to be started via the /CH/BLN/SP/cli object at a time. If an existing CLI session is active and a second CLI session is initiated, an error message might display.
To avoid this issue, you should use ssh from a remote system to initiate additional sessions to a remote Oracle ILOM, or use the following command to terminate the current session.
This issue was fixed in Oracle ILOM 1.1.6.
The network might be slow when both CMM gigabit Ethernet ports are connected to the same network switch.
This issue was fixed in Oracle ILOM 1.1.6.
When the power chords to PS0 is removed, the CMM I_12V sensor on S1 side reads 2.5 Amps. On the S0 side it correctly reads 0 Amps.
You can safely ignore these readings.
This issue was fixed in Oracle ILOM 1.6.6.
The BMC might intermittently stop responding, and the CPLD version displays 0.0. If this issue should arise, you should perform the following steps:
| Sun Blade 6000 Modular System Product Notes | E23069-14 |
|
Copyright © 2014, Oracle and/or its affiliates. All rights reserved.