Go to main content

Sun Fire X4470 Server Product Notes

Exit Print View

Updated: September 2018
 
 

Oracle ILOM Known Issues

Starting with system software release 2.0.0, your system is equipped with Oracle ILOM 4.0.2.25 or newer.

  • For information about Oracle ILOM on systems with Oracle ILOM 4.0.2.25 or newer, refer to the Oracle ILOM 4.0 Documentation Library.

  • For information about Oracle ILOM on systems with Oracle ILOM 3.2.N.N, refer to the Oracle ILOM 3.2 Documentation Library.

  • For information about Oracle ILOM on systems with Oracle ILOM 3.1.2.50.b or earlier, refer to the Oracle ILOM 3.0 Documentation Library.

Oracle ILOM libraries are located at https://www.oracle.com/goto/ilom/docs.

Table 8  Oracle ILOM Known Open Issues
Bug ID
Description
23634048
Oracle ILOM SNMP v3 Traps Are Not Delivered After SNMP Engine ID Change
If you change the engine ID, create an SNMP v3 user, and configure an alert using that user without waiting approximately 10 seconds between each action, the internal user configuration might be incorrect and traps are missed.
Workaround:
Do not create multiple configuration changes without verifying the effect of each configuration change. To prevent misconfigured users and missed traps, insert sleep statements in the script. For example:
# change engineID
set /SP/services/snmp engineid=NEWENGINEID
# sleep 10 seconds to give snmp enough time to make the change
sleep 10
# verify engineID
show /SP/services/snmp engineid
# verify SNMPv3 users have been deleted
show /SP/services/snmp/users

# create snmpv3 user
create /SP/services/snmp/users newuser authenticationpassword=...
# sleep 10 seconds to give snmp enough time to make the change
sleep 10
# verify user
show /SP/services/snmp/users newuser
# do a snmpget with that user to verify it

# configure alert
set /SP/alertmgmt/rules/1 type=snmptrap ...
# sleep 10 seconds to give snmp enough time to make the change
sleep 10
# verify alert
show /SP/alertmgmt/rules/1
set /SP/alertmgmt/rules/1 testrule=true
23564626
Third-Party Web Scan and Test Tools Cause Sluggish Oracle ILOM Performance
Issue:
Under certain conditions, third-party web scanning and test tools can cause Oracle ILOM to run extremely slowly.
Affected Software:
System software release 1.7.0 and 1.7.1.
Workaround:
Install system software release 1.7.2 or newer.
21836276
Attempting to Use a CD/DVD Drive as the System Boot Device Might Fail
Issue:
If you want to set the system boot device to be a CD/DVD drive, and you do so by issuing the set boot_device=cdrom command, you might encounter an error message or a boot failure when performing a system boot from the Oracle ILOM remote console. This issue occurs because, in the Sun Fire X4470 server, the default CD/DVD drive is the one physically installed in the Sun Fire X4770 system. Thus, if you load the image from the remote console, Oracle ILOM creates a new virtual CD drive in the boot list, which is different from the default CD/DVD that is physically located in the system. As a result, an error message is displayed, or the system boot fails.
Affected Software:
  • Release 1.3, or later

Workaround:
To initiate a system boot from the Oracle ILOM remote console, use the set /SP/bootlist bootdev=<device_number> command instead. The system will boot successfully from the specified device in the command.
15726612
When Flashing a New Oracle ILOM Image, Additional Steps Are Required Due to Service Processor DRAM Expanded to 256 MB
Issue:
With Software Release 1.3, or later, service processor (SP) DRAM has been expanded from 128 MB to 256 MB. This change in SP DRAM size requires that you perform additional steps when upgrading or downgrading the Oracle ILOM image on the Sun Fire X4470 Server. Note that if you do not perform the steps listed in the workaround, Oracle ILOM will work abnormally and you will encounter unexpected errors.
Affected Software:
  • Release 1.3, or later

Workaround:
  1. Power off the host.

  2. Flash the new Oracle ILOM image.

  3. Power off the server after the Oracle ILOM image upgrade or downgrade is complete.

  4. Wait for at least 10 seconds (delay for some device/capacitors discharge).

  5. Power on the server.

15620790
SPrestore Command Is Partially Successful and Reports an Error in the Log
Issue:
If the serial console is in use, properties related to the serial console cannot be restored and you will receive messages similar to the following:
Config restore: Unable to restore property '/SP/serial/host/commitpending'
Config restore: Unable to restore property '/SP/serial/external'
Because such properties could not be restored, this is a partial failure and, therefore, results in the above message about the partial failure. This is not a defect.
Affected Software:
  • Release 1.0 and later

Workaround:
Log out of the serial console and try to run the restore command again.
15624057
BIOS Does Not Get Updated When You Use IPMIflash to Upgrade the Oracle ILOM Service Processor Image
Issue:
BIOS might not get updated when you use IPMIflash to upgrade the Oracle ILOM service processor (SP) image with the Delay BIOS option enabled. When you power the server off and on quickly, the BIOS image should be updated, but it is not.
Affected Operating System and Software:
  • Oracle Linux 5.4, and later

  • Release 1.0 and later

Workarounds:
Use one of the following workarounds:
  • If you power off the server using the Power button, wait at least 10 seconds before powering the server back on.

or
  • Instead of powering the server off and on using the Power button, run a power-cycle command. This will guarantee that BIOS is updated.

For example, use one of the following commands:
Using IPMI: ipmitool power cycle
Using the Oracle ILOM web interface: Remote Control → Remote Power Control → Power Cycle
15624521
Unable to Launch Oracle ILOM Remote Console Using JRE 1.6.0 U14, U15, and U16
Issue::
If you try to launch the Oracle ILOM Remote Console via the web using some builds of Java Runtime Environment (JRE), the system returns the error Unable to Launch the Application.
Affected Operating Systems and Software:
  • All operating systems using JRE 1.6.0, U14, U15, and U16

  • Release 1.0 and later

Workaround:
Upgrade to JRE 1.6.0 U17 or later.
15656571
Erroneous Error Message Is Returned When Serial Port Owner Is Changed
Issue:
If you use the Configuration → Serial Port tab in the Oracle ILOM web interface to change the serial port owner, changes to the port owner take effect, but the system returns the error Cannot change serial settings - the serial console in use.
Affected Software:
  • Release 1.0 and later

Workaround:
Ignore the error message.
15685821
Serial Port Ownership Cannot Be Changed On Serial Console
Issue:
If you are logged in to Oracle ILOM from the serial console, and you set the serial port owner to host, you cannot set the serial port owner back to SP.
Affected Software:
  • Release 1.0 and later

Workaround:
To avoid this problem, ensure that you are not logged in to the serial console, and then change console port ownership using an SSH session.
If the problem occurs, you can recover by rebooting the system.