Bug ID 23634048
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.
Affected hardware and software:
Oracle ILOM 3.1 and 3.2.4
Platform software releases 1.0 and later.
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
BugID: 15584702 (formerly CR 6875309)
Issue:
When using the Oracle ILOM Remote Console (with the mouse mode set to Absolute) on a server with a Sun Storage 6 Gb SAS PCIe RAID HBA Internal option card installed, if you boot the system and press Ctrl+H to enter the LSI MegaRAID BIOS Utility, the mouse pointer only moves vertically and horizontally on the left and top sides of the utility.
Affected hardware and software:
Sun Storage 6 Gb SAS PCIe RAID HBA, Internal option card (SGX-SAS6-R-INT-Z and SG-SAS6-R-INT-Z)
Platform software releases 1.0 and later.
Workaround:
In the Oracle ILOM Remote Console, change the mouse mode setting from Absolute (the default) to Relative mode. For instructions for setting Oracle ILOM Remote Console to Relative mode, see the Oracle ILOM 3.2 Documentation Library at https://www.oracle.com/goto/ilom/docs.
BugID: 15736328 (formerly CR 7080526)
Issue:
Unified Extensible Firmware Interface (UEFI) boot priority list settings might be lost when transitioning between UEFI BIOS and Legacy BIOS. This issue might occur if you need to run system diagnostics using the Pc-Check utility, which only runs in the Legacy BIOS. UEFI configuration settings should be saved prior to switching between UEFI BIOS and Legacy BIOS.
Affected software:
Platform software releases 1.0 and later.
Workaround:
Use the Oracle ILOM BIOS Configuration Backup and Restore feature to save configuration settings prior to transitioning between the BIOS modes. Then restore the BIOS configuration settings after transitioning back to UEFI mode. For more information and procedures for saving UEFI configuration settings, refer to the Oracle ILOM Administrator's Guide for Configuration and Maintenance in the Oracle Integrated Lights Out Manager (ILOM) 3.2 Documentation Library at https://www.oracle.com/goto/ilom/docs.
BugID: 15735895 (formerly CR 7079855)
Issue:
On rare occasions, when a USB keyboard and/or mouse is directly connected to the server, the keyboard and/or mouse might not be recognized by BIOS. This problem is indicated by a failure of BIOS to respond to key presses during the time the BIOS splash screen is displayed.
Affected software:
Platform software releases 1.0 and later.
Workaround:
Reboot the host. If the problem persists after two or three reboots, contact your authorized Oracle service provider for assistance.
BugID: 15818528
Issue:
During operating system installations in Unified Extensible Firmware Interface (UEFI) mode, operating system installers creates the UEFI Boot variables to be used in BIOS menus to select the operating system to boot. To avoid potential loss of a boot variable created by the operating system installer, you should not use any operating system tools or utilities to manage (create, modify, or delete) these boot variables. Loss of a boot variable precludes users from being able to boot the operating system.
Affected software:
All supported UEFI capable operating systems
Platform software releases 1.0 and later.
Workaround:
If a UEFI Boot variable is lost, reinstall the operating system so as to create a new UEFI Boot variable.
BugID: 15790853 (formerly CR 7167796)
Issue:
Any time an Oracle ILOM Unified Extensible Firmware Interface (UEFI) BIOS configuration is loaded, the configuration file might contain inactive parameters, that is, parameters that are no longer valid for the current version of the BIOS, or typographical errors. This can result in the failure of one or more parameters to load. When this occurs, the Oracle ILOM /System/BIOS/Config/restore_status parameter, which provides the user with the status of the last attempted configuration load, reports that the load was partially successful. The value of /System/BIOS/Config/restore_status parameter does not change until a subsequent load of an Oracle ILOM UEFI BIOS configuration occurs.
Affected software:
Oracle ILOM 3.1 and 3.2.4
Platform software releases 1.0 and later.
Workaround:
Using a text editor, create an XML file with the following contents:
<BIOS>
</BIOS>
Save the file to any XML file name.
For purposes of this example, the file name used is bios_no_op_config.xml
To load the configuration, enter the following command:
% load -source <URI_location>/bios_no_op_config.xml /System/BIOS/Config
If host power is on, enter the following Oracle Integrated Lights Out Manager (ILOM) command to reset the host:
> reset /System
BugID: 15785186 (formerly CR 7160984)
Issue:
At the UEFI Driver control HII menu for the Emulex host bus adapter (HBA), with Set Boot From San set to enabled, if you run the Add Boot Device function, you see the Please Wait message for approximately 3 to 5 seconds, and then the system hangs. You must reset the server to clear the server hang condition.
However, if you run the Scan Fibre Devices function first, and then you run the Add Boot Device function, the Add Boot Device function works correctly. The hang condition only occurs if the Add Boot Device function is run first.
Affected hardware and software:
Sun StorageTek 8 Gb FC PCIe HBA Dual Port Emulex, with EFIBoot version 4.12a15 firmware (SG-PCIE2FC-EM8-Z and SG-XPCIE2FC-EM8-N)
Platform software releases 1.0 and later.
Workaround:
To recover from this hang condition, enter the following command to reset the server:
-> reset /System
BugID: 15803551, 15803553 (formerly CRs 7183782, 7183789)
Issue:
In single-processor systems, Ethernet ports NET 2 and NET 3, and PCIe slot 1 are nonfunctional. However, the following Oracle Integrated Lights Out Manager (ILOM) web interface screens incorrectly show these ports as available for use:
The Oracle ILOM System Information → Summary screen and the System Information → Networking screen show the number of supported Ethernet NICs (Network Interface Controllers) as 4, when actually only two Ethernet NICs (NET 0 and NET 1) are supported and available for use.
The Oracle ILOM System Information → PCI Devices screen shows the Maximum Add-on Devices as 4, when actually only three PCIe slots (slots 2, 3, and 4) are supported and available for use. This screen also shows the number of On-board Devices (NICs) as 4, when actually only NET 0 and NET 1 are supported and available for use.
Affected hardware and software:
Single-processor systems
Oracle ILOM 3.1 and 3.2.4
Platform software releases 1.0 and later.
Workaround:
None.
BugID: 15803564 (formerly CR 7183799)
Issue:
For the Oracle Integrated Lights Out Manager (ILOM) command-line interface (CLI), the show /System/memory command incorrectly returns max DIMMs = 16, when the maximum number of DIMMs supported in a single-processor system is 8.
Additionally, if a DIMM is mistakenly installed in a socket associated with processor 1 (P1), the following Oracle ILOM CLI commands identify the misconfiguration by showing the DIMM associated with P1, even though P1 is not actually present in the system. Note, however, that the DIMM is not usable by the system.
> show /System/Memory/DIMMs
> show /System/Memory/DIMMs/DIMM_n, where n can be any number from 8 through 15
> show /SP/powermgmt/powerconf/memory
> show /SP/powermgmt/powerconf/memory/MB_P1_D0
For the Oracle ILOM web interface, the System Information → Summary screen and the System Information → Memory screen incorrectly show the maximum number of DIMMs supported as 16, when the maximum number of DIMMs supported on a single-processor system is 8.
Affected hardware and software:
Single-processor systems
Oracle ILOM 3.1 and 3.2.4
Platform software releases 1.0 and later.
Workaround:
None.
BugID: 15802805 (formerly CR 7182919)
Issue:
If the server is configured with a Sun Storage 6 Gb SAS PCIe Internal host bus adapter (HBA) installed in PCIe slot 4 and a Sun Storage 6 Gb SAS PCIe External HBA installed in one of the external PCIe slots (slots 1, 2, or 3), the storage drives are not detected during the BIOS boot. As a result, Pc-Check does not detect and test the internal storage drives and you are not able to designate an internal storage drive as the boot drive.
Affected hardware and software:
Sun Storage 6 Gb SAS PCIe Internal HBA (SG-SAS6-INT-Z and SGX-SAS6-INT-Z)
Sun Storage 6 Gb SAS PCIe External HBA (SG-SAS6-EXT-Z and SGX-SAS6-EXT-Z)
Platform software releases 1.0 and later.
Workaround:
To reconfigure the internal and external HBA cards so that the internal storage drives are detected at boot time, perform the following steps:
Reboot the server.
As the BIOS boots, the LSI Corporation MPT SAS2 BIOS screen appears.
When the "Type Control+C to enter SAS Configuration Utility" message appears, type: Ctrl+C.
The LSI Corp Config Utility screen appears.
Notice that the internal PCIe card (SG-SAS6-INT-Z) does not show up in the Boot Order (it is not assigned a number).
Press the right arrow key to select the Boot Order column.
Press the Insert key (Alter Boot List).
The number 1 is inserted next to the internal PCIe card (SG-SAS6-INT-Z).
To change the boot order, press the - (minus) key (Alter Boot Order).
The number for the boot order for the internal PCIe card is changed to 0 (zero) and the boot order for the external PCIe card (SG-SAS6-EXT-Z) is change to 1 (one).
Use the arrow keys to select the Boot Order column for the external PCIe card and press the Del key (Alter Boot List) to remove that card from of the boot order.
To exit the LSI Corp Config Utility, press the Esc key.
An Exit Confirmation window appears.
In the Exit Confirmation window, scroll down to "Save Changes and Reboot" and press the Enter key.
When the BIOS screen appears, press the F2 to enter the BIOS Setup Utility.
The BIOS Main Menu screen appears.
In the BIOS Main Menu screen, select the Boot option in the menu bar.
The Boot Menu screen appears.
Verify that the server's internal storage drives are now displayed in the Boot menu screen.
You can now select an internal storage drive to be at the top of the boot list.
BugID: 16014346
Issue:
For configurations in which the auto-negotiation process takes more than five seconds, the boot script might fail with the following message:
ethX: failed. No link present. Check cable?
Affected software:
Red Hat Enterprise Linux 5.9, 5.10, 6.4, and 6.5
Platform software releases 1.0 and later.
Workaround:
If this error message appears, even though the presence of a link can be confirmed using the ethtool ethX command, try this setting: LINKDELAY=5 in /etc/sysconfig/network-scripts/ifcfg-ethX
The server might reboot after removing the Physical Function (PF) device driver when the Virtual Function (VF) device driver is active in guest.
Alternatively, you can use NetworkManager to configure the interfaces, which avoids the set timeout. For configuration instructions for using NetworkManager, refer to the documentation provided with your operating system distribution.
BugID: 15944904
Issue:
After you install an operating system using a Preboot eXecution Environment (PXE) or a Linux ISO image, the host might fail to assign an IP address to the network interface port (NET 0-3) the first time you log in to the operating system.
Affected software:
Platform software releases 1.0 and later.
Workaround:
Add the line LINKDELAY=10 in the ifcfg-ethX file located in the /etc/sysconfig/network-scripts/ directory.
BugID: 18240994
Issue:
When you use the BIOS Setup Utility menu to access UEFI Driver Control → Oracle Sun Storage 16Gb Fibre Channel LP → Add Boot Device, the system hangs.
Affected hardware and software:
Sun Storage 10 Gb FCoE Short Range Optics, Emulex (7101687 and 7101688)
Sun Storage 16 Gb FC Short Wave Optics, Emulex (7101685 and 7101686)
Platform software releases 1.0 and later.
Workaround:
When you use the BIOS Setup Utility menu, enter this command first: UEFI Driver Control → Oracle Sun Storage 16Gb Fibre Channel LP → Scan for Fibre Devices.
BugID: 16346073
Issue:
If you try to reboot the service processor (SP) while the host is rebooting, the server's BIOS might hang.
Affected software:
Platform software releases 1.0 and later.
Workaround:
Do not reboot the server's SP and host simultaneously.