General Information
Topics
|
|
Description
|
Link
|
Firmware supported
|
|
Versions of Intel Microcode and Reference Code used in the BIOS firmware
|
|
Download site for firmware updates
|
|
Supported operating systems
|
|
Support information
|
|
Tools and Drivers DVD
|
|
New features Supported in release 1.2.2
|
|
Download site for latest product documentation
|
|
FMOD hardware option not supported
|
|
Firmware Supported
TABLE 1 identifies the Oracle ILOM and BIOS firmware versions that are supported.
TABLE 1 Server Firmware Versions Supported
Release Version
|
Oracle ILOM SP Firmware Version
|
BIOS Firmware Version
|
1.3
|
3.0.14.11
|
08.06.01.08
|
1.2.3
|
3.0.9.27.c (r60665)
|
08.04.03.01
|
1.2.2
|
3.0.9.27.b (r60221)
|
08.04.03.01
|
1.2
|
3.0.9.27 (r58107)
|
08.04.01.10
|
1.1
|
3.0.9.22
|
08.03.01.03
|
1.0
|
3.0.9.15
|
08.01.04.05
|
Versions of Intel Microcode and Reference Code Used in the BIOS Firmware
TABLE 2 lists the versions of the Intel Microcode and Reference Code used in the BIOS firmware image for Releases 1.0, 1.1, 1.2, 1.2.2, 1.2.3, and 1.3.
TABLE 2 Intel Microcode and Reference Code Used in BIOS Firmware
Intel Software
|
Versions Used in 1.0 and 1.1
|
Versions Used In 1.2
|
Versions Used In 1.2.2 and 1.2.3
|
Versions Used In 1.3
|
Intel CPU Microcode
|
SRV_C_87
|
SRV_C_89
|
SRV_C_89
|
SRV_C_89
|
Intel RC
|
p2.70
|
2.90
|
2.90
|
2.93
|
Intel CPU Reference Code
|
1.06
|
1.08
|
1.08
|
1.08
|
Intel QuickPath Interconnect (QPI) Reference Code
|
1.85
|
1.85
|
1.85
|
1.85
|
Intel Memory Reference Code (MRC)
|
2.11
|
2.20
|
2.20
|
2.20
|
Firmware Updates
The latest Oracle ILOM and BIOS firmware is shipped installed on the server. If you need to reinstall this firmware or obtain updates to this firmware, you can obtain the firmware for the server at:
From the product page:
1. Expand the Downloads box located on the lower right side, then click Downloads and Firmware.
2. At the product Downloads and Firmware site, click the appropriate software release for your server.
3. Follow the remaining online instructions to download the server software and firmware.
Supported Operating Systems
The Sun Fire X4170 M2 and X4270 M2 Servers support the following operating system editions:
- Oracle Linux 5.5 (64-bit)
- Oracle Unbreakable Enterprise Kernel for Linux
- Oracle VM 2.2.1
- Oracle Solaris 10 10/09 and Oracle Solaris 10 9/10
- Windows Server 2008 SP2 (64-bit)
- Windows Server 2008 R2
- Red Hat Enterprise Linux (RHEL) 5.5 and 6.0 (64-bit)
- SUSE Linux Enterprise Server (SLES) 10 SP3 (64-bit)
- SUSE Linux Enterprise Server (SLES) 11 (64-bit) and SLES 11 SP1 (64-bit)
- VMware ESX and ESXi 4.0 Update 2 and 4.1
For installation instructions for the operating systems listed above, refer to the Sun Fire X4170 M2 and X4270 M2 Servers Installation Guide for Linux, Virtual Machine Software, and Oracle Solaris Operating Systems Installation Guide.
Note - The Oracle Solaris 10 Operating System and Oracle VM software are both available as preinstalled options on a server disk drive. For configuration instructions for these preinstalled options, refer to the Sun Fire X4170 M2 and X4270 M2 Servers Installation Guide. |
Support and Patches for Sun Fire X4170 M2 and X4270 M2 Servers
Support information and patches for the servers are available at: http://support.oracle.com
Tools and Drivers DVD for Sun Fire X4170 M2 and X4270 M2 Servers
A Tools and Drivers DVD for the servers is shipped with your order. This DVD includes device drivers, RAID management software, and other software utilities for use with your server. If you need a copy of this DVD, or require updates to the software it contains, you can download the latest Tools and Drivers DVD image for the server at:
From the product page:
1. Expand the Downloads box located on the lower right side, then click Downloads and Firmware.
2. At the product Downloads and Firmware site, click the appropriate software release for your server.
3. Follow the remaining online instructions to download the server software and firmware.
New Features Supported in Software Release 1.2.2
As of software release 1.2.2, the Oracle Unbreakable Enterprise Kernel for Linux is supported.
Oracle Unbreakable Enterprise Kernel for Linux
The Oracle Unbreakable Enterprise Kernel for Linux is a recommended kernel that can be installed on top of Oracle Linux 5 Update 5 or Red Hat Enterprise Linux 5 Update 5. This new kernel is based on the 2.6.32 Linux Kernel and includes optimizations developed by Oracle to ensure stability and optimal performance. All patches added to the 2.6.32 mainline kernel are open source.
Oracle Unbreakable Enterprise Kernel for Linux has demonstrated its stability, reliability, and performance improvements in demanding environments. It is the kernel used in Oracle’s Exadata and Exalogic systems. Furthermore, the Oracle Unbreakable Enterprise Kernel for Linux is now used in all benchmarks on Linux that Oracle participates in, as well as in Oracle’s Validated Configurations program.
Because the Oracle Unbreakable Enterprise Kernel for Linux installs directly on top of Oracle Linux 5 or Red Hat Enterprise Linux 5, there is no need to upgrade to a new major release of the Linux operating system to gain the benefits and features of this new kernel. And after you have installed this new kernel, you still have the option of easily switching back to the Red Hat Enterprise Linux kernel, and then, switching back and forth between the two kernels.
Oracle highly recommends deploying the Oracle Unbreakable Enterprise Kernel for Linux in your Linux environment, especially if you are running Oracle software. Oracle Unbreakable Enterprise Kernel for Linux is optional, however, and Oracle Linux continues to include a Red Hat compatible kernel, which is compiled directly from Red Hat Enterprise Linux (RHEL) source code, for customers who require strict RHEL compatibility. Oracle also recommends this new kernel for customers running third-party software and third-party hardware.
For more information about benefits and features of the Oracle Unbreakable Enterprise Kernel for Linux, go to:
http://www.oracle.com/us/technologies/linux/ubreakable-enterprise-kernel-linux-173350.html
For installation instructions for Oracle Unbreakable Enterprise Kernel for Linux, see the Sun Fire X4170 M2 and X4270 M2 Servers Installation Guide for Linux, Virtual Machine Software, and Oracle Solaris Operating Systems Installation Guide.
Documentation for Sun Fire X4170 M2 and X4270 M2 Servers
For Product documentation, as well as updated Product Notes for the Sun Fire X4170 M2 and X4270 M2 Servers, go to the following site and navigate to the server documentation page:
http://www.oracle.com/documentation
FMOD Hardware Option Not Supported
The original installation and service documentation for the Sun Fire X4170 M2 and X4270 M2 Servers stated that the optional flash modules (FMODs) and the associated energy storage module (ESM) were supported; however, these hardware options are not supported. The installation and service documentation for the Sun Fire X4170 M2 and X4270 M2 Servers has been revised to reflect this change.
Removing support for FMODs does not affect the capabilities of the server, because the server’s storage drives can also perform the data backup function that the FMODs provided.
Note - Translated versions of the Sun Fire X4170 M2 and X4270 M2 Servers documents include information about the optional flash modules (FMODs) and the energy storage module (ESM), however, those components are not supported. Please disregard this information in the translated documents and refer to the latest English-language versions of the documents. |
Known Issues Fixed
Oracle ILOM Known Issues Fixed
TABLE 3 Oracle ILOM Known Issues Fixed
CR
|
Description
|
6806444
|
Oracle ILOM Remote Console Might Hang on Windows Client When Redirecting a CD-ROM Image or Floppy Image
|
Issue:
When using a Windows client to redirect a CD-ROM image or floppy image from the Oracle ILOM Remote Console, the Oracle ILOM Remote Console might not respond.
|
Affected Operating Systems and Software:
- Windows operating system installed on client system
- Oracle ILOM 3.0 or later
- Oracle ILOM Remote Console
- Java Development Kit (JDK) 1.6.0_07
- Releases 1.0, 1.1, 1.2, 1.2.2, and 1.2.3
|
Fixed In:
Software release 1.3.
|
6936585
|
Oracle ILOM CLI Shows an Incorrect HDD PRSNT Value After a Storage Drive Has Been Hot Removed or Hot Inserted
|
Issue:
HDD PRSNT sensor status update is inconsistent after hot removal or hot insertion of a storage drive. Sometimes the sensor status updates immediately and other times it does not.
|
Affected Hardware and Software:
- Sun Fire X4170 M2 Server
- Releases 1.0, 1.1, 1.2, 1.2.2, and 1.2.3
|
Fixed In:
Software release 1.3.
|
Oracle Solaris Known Issues Fixed
TABLE 4 Oracle Solaris Known Issues Fixed
CR
|
Description
|
6919562
|
Correctable Memory Errors Are Interpreted Incorrectly When Using the fmdump -V Commands
|
Issue:
Correctable memory errors appear in the log file after executing the fmdump -V commands as an undiagnosed fault, defect.sunos.eft.undiag.fme. In the Solaris OS message log, there is a corresponding message, the ID is SUNOS-8000-FU.
To identify the DIMM location in the FMA log, follow the list below.
Processor 0:
- D0: chip 0, controller 0, channel 0, DIMM 2
- D1: chip 0, controller 0, channel 0, DIMM 1
- D2: chip 0, controller 0, channel 0, DIMM 0
- D3: chip 0, controller 0, channel 1, DIMM 2
- D4: chip 0, controller 0, channel 1, DIMM 1
- D5: chip 0, controller 0, channel 1, DIMM 0
- D6: chip 0, controller 0, channel 2, DIMM 2
- D7: chip 0, controller 0, channel 2, DIMM 1
- D8: chip 0, controller 0, channel 2, DIMM 0
Processor 1:
- D0: chip 1, controller 0, channel 0, DIMM 2
- D1: chip 1, controller 0, channel 0, DIMM 1
- D2: chip 1, controller 0, channel 0, DIMM 0
- D3: chip 1, controller 0, channel 1, DIMM 2
- D4: chip 1, controller 0, channel 1, DIMM 1
- D5: chip 1, controller 0, channel 1, DIMM 0
- D6: chip 1, controller 0, channel 2, DIMM 2
- D7: chip 1, controller 0, channel 2, DIMM 1
- D8: chip 1, controller 0, channel 2, DIMM 0
|
Affected Operating System and Software:
- Oracle Solaris 10 10/09
- Releases 1.0, 1.1, 1.2, 1.2.2, and 1.2.3
|
Fixed In:
Software release 1.3.
|
Documentation Errata Fixed
TABLE 5 Documentation Errata Fixed
CR
|
Description
|
None
|
Oracle Hardware Installation Assistant Replaces Name for Sun Installation Assistant
|
Issue:
In the documentation for the Sun Fire X4170 M2 and X4270 M2 Servers, Oracle Hardware Installation Assistant is referred to as Sun Installation Assistant (SIA).
|
Locations of Faulty DIMMs Using Oracle ILOM Versus BIOS Is Incorrectly Documented in the Service Manuals
|
Affected Service Manuals:
- Sun Fire X4170 M2 Server Service Manual
- Sun Fire X4270 M2 Server Service Manual
|
Correction:
The corrected information is:
Pn/D0 - CPUn/CHANNEL0/DIMM2
Pn/D1 - CPUn/CHANNEL0/DIMM1
Pn/D2 - CPUn/CHANNEL0/DIMM0
Pn/D3 - CPUn/CHANNEL0/DIMM2
Pn/D4 - CPUn/CHANNEL0/DIMM1
Pn/D5 - CPUn/CHANNEL0/DIMM0
Pn/D6 - CPUn/CHANNEL0/DIMM2
Pn/D7 - CPUn/CHANNEL0/DIMM1
Pn/D8 - CPUn/CHANNEL0/DIMM0
Where Pn is processor 0 or 1 and CPUn is CPU 0 or 1.
Note - Processor and CPU are different ways of referring the CPU chips on the motherboard. A server can have up to two CPU chips installed.
|
Fixed In:
The service manuals were updated for software release 1.2.3 to fix this issue.
|
6991053
|
Detailed Procedure for Viewing or Assigning the Oracle ILOM SP IP Address Using the BIOS Setup Utility Needs to be Added to the Service Manuals
|
|
Affected Service Manuals:
- Sun Fire X4170 M2 Server Service Manual
- Sun Fire X4270 M2 Server Service Manual
|
Procedure:
View or Assign the Oracle ILOM SP IP Address Using the BIOS Setup Utility
Use this procedure when you are ready to apply main power to the server.
To access the BIOS Setup Utility and view the Oracle ILOM SP IP address, complete the following steps:
1. Power on the server (or restart the server if it is running).
See section “Apply Main Power to the Server.”
2. When the BIOS splash screen or text prompt appears during the power-on self-test (POST) operation, press F2 to access the BIOS Setup Utility.
3. Using the left and right arrow keys on the keyboard, navigate to the Advanced tab.
The Advanced screen appears.
4. Using the up and down arrow keys, select the IPMI Configuration option and press Enter to go to the subscreen.
The IPMI Configuration subscreen appears.
5. Using the up and down arrow keys, select the Set LAN Configuration option and press Enter.
The LAN Configuration subscreen appears and shows the current Oracle ILOM SP IP address.
6. Do one of the following:
o If the DHCP server has assigned the IP address, record the IP address as you will need it to log in to Oracle ILOM using SSH or a web browser.
Note - If the IP address is in the form of 192.168.xxx.xxx, the DHCP server might not have assigned an address and the SP might use a static address.
o To assign an IP address, select Set LAN Configuration, then use the arrow keys to select settings. Specify the appropriate settings, then proceed to Step 7.
7. Select Commit and press Enter.
8. Allow about five seconds for the Commit to complete, then select Refresh and press Enter.
9. Select Refresh a second time and press Enter to confirm that the IP address information has been set.
10. Press F10 to save any changes you made and to exit the BIOS Setup Utility.
|
Fixed In:
The service manuals were updated for software release 1.2.3 to fix this issue.
|
Known Open Issues
Topics
|
|
Description
|
Link
|
Hardware known issues, descriptions, and workarounds
|
|
BIOS known issues, descriptions, and workarounds
|
|
Oracle ILOM known issues, descriptions, and workarounds
|
|
Oracle Solaris known issues, descriptions, and workarounds
|
|
Virtual Machine Software known issues, descriptions, and workarounds
|
|
Oracle, Red Hat, and SUSE Linux known issues, descriptions, and workarounds
|
|
Windows known issues, descriptions, and workarounds
|
|
Oracle Hardware Installation Assistant known issues, descriptions, and workarounds
|
|
Hardware Known Issues
TABLE 6 Hardware Known Open Issues
CR
|
Description
|
6926877
|
Fan OK/Fault Status LED Is Not Lit When Host Power Is Off
|
Issue:
With server host power is off, a fan OK/Fault status LED might not be lit. Each fan module has one bicolored status LED that is located on the fan module. The status LED should illuminate green (OK) or amber (Fault) even when the server is in Standby power mode.
|
Affected Hardware and Software:
- Sun Fire X4170 M2 Server
- Releases 1.0, 1.1, 1.2, 1.2.2, 1.2.3, and 1.3
|
Workaround:
Use Oracle ILOM to determine fan module status or turn host power back on.
|
7006904
|
Error Displayed in System Information When a Sun Storage 6 Gb SAS PCIe Internal HBA Is Installed in The Server
|
Issue:
When using RHEL 6 or SLES 11 SP1 on a server with a Sun Storage 6 Gb SAS PCIe Internal HBA installed, the following error message is displayed in the system information:
pcieport 0000:00:03.0: AER: Multiple Corrected error received: id=0018
pcieport 0000:00:03.0: AER: Corrected error received: id=0018
pcieport 0000:00:03.0: PCIE Bus Error: severity=Corrected, type=Physical Layer, id=0018(Receiver ID)
pcieport 0000:00:03.0: device [8086:340a] error status/mask=00000001/00002000
pcieport 0000:00:03.0: [ 0] Receiver Error (First)
|
Affected Hardware, Operating System, and Software:
- Sun Fire X4170 M2 and X4270 M2 Servers with Sun Storage 6 Gb SAS PCIe HBA, Internal option card (SGX-SAS6-INT-Z and SG-SAS6-INT-Z)
- Red Hat Enterprise Linux (RHEL) 6.0
- SUSE Linux Enterprise Server (SLES) 11 SP1
- Releases 1.3
|
Workaround:
None. This message can be safely ignored.
|
BIOS Known Issues
TABLE 7 BIOS Known Open Issues
CR
|
Description
|
6716289
|
Amount of Memory Reported by BIOS and System Is Less Than Actual Memory Installed
|
Issue:
In the BIOS splash screen and in the main BIOS Setup menu, the system reports 8MB less memory than installed.
|
Affected Software:
- Releases 1.0, 1.1, 1.2, 1.2.2, 1.2.3, and 1.3
|
Workaround:
There is no workaround. Check for the availability of a patch for this defect.
|
6898588
|
Using <CTRL-N> With the SGX-SAS6-INT-Z Option Card Installed Might Bypass Network Boot and SGX-SAS6-INT-Z Option ROM Load
|
Issue:
If the PCI-Express SAS LSI Controller (SGX-SAS6-INT-Z) option card is installed in the system, and <CTRL-N> is used on the serial console to initiate a network boot, the network boot might not be initiated, and the Option ROM for the SGX-SAS6-INT-Z option card might not be loaded.
|
Affected Hardware and Software:
- SGX-SAS6-INT-Z option card
- Releases 1.0, 1.1, 1.2, 1.2.2, 1.2.3, and 1.3
|
Workaround:
Do one of the following:
- Use the Oracle ILOM Remote Console and press F12 to initiate a network boot.
- If using the serial console, use <CTRL-E> to get to the BIOS boot device priority menu, and then move the desired PXE adapter (network boot device) to the top of the boot device priority list. The PXE adapter will then be used as the boot device.
- Press <CTRL-N> during, or after, the time SGX-SAS6-INT-Z Option ROM code is running. The Option ROM code is running when the following banner is displayed:
LSI Corporation MPT SAS2 BIOS. Copyright 2000-2010 LSI Corporation.
|
6901163
|
“EHCI BIOS handoff failed” Message Appears
|
Issue:
The "EHCI BIOS handoff failed" message appears in VMware ESX 4.0 Update 1. The failure message appears in the dmesg output.
|
Affected Operating System and Software:
- VMware ESX 4.0 Update 1
- Releases 1.0, 1.1, 1.2, 1.2.2, 1.2.3, and 1.3
|
Workaround:
This message can be safely ignored. It does not cause any functional problems.
|
6975299
|
PXE Boot Might Fail After Running PC Check
|
Issue:
If you attempt to boot the server using PXE boot immediately after running PC Check, the boot might fail with a message similar to the following:
Intel(R) Boot Agent GE v1.3.31
Copyright (C) 1997-2009, Intel Corporation
PXE-EC8: !PXE structure was not found in UNDI driver code segment.
PXE-M0F: Exiting Intel Boot Agent.
|
Affected Software:
- Releases 1.0, 1.1, 1.2, 1.2.2, 1.2.3, and 1.3
|
Workaround:
To avoid this issue, reboot the system after running PC Check.
|
6931438
|
After running PC Check, an Operating System Install or Boot Might Hang at the GRUB Menu
|
Issue:
After running PC Check, if a user attempts to install or boot an operating system, the install or boot might hang at the GRUB menu.
|
Affected Software:
- Releases 1.0, 1.1, 1.2, 1.2.2, 1.2.3, and 1.3
|
Workaround:
Reboot the system with PC Check disabled before trying to install or boot an operating system.
|
Oracle ILOM Known Issues
Note - Oracle Integrated Lights Out Manager (ILOM) was formerly called Sun Integrated Lights Out Manager. |
TABLE 8 Oracle ILOM Known Open Issues
CR
|
Description
|
6779289
|
In-chip Connectivity Between the SP and the Host OS Is Not Supported When Using Sideband Network Port Sharing
|
Issue:
When configured for sideband network port sharing, in-chip connectivity between the service processor and the host OS is not supported by the on-board host Gigabit Ethernet controller.
|
Affected Software:
- Releases 1.0, 1.1, 1.2, 1.2.2, 1.2.3, and 1.3
|
Workaround:
Use a different port or route to transmit traffic between the source and destination targets instead of using L2 bridging/switching.
|
6795975
|
When multiple ILOM Remote Console Sessions Are Open, the KVMS Interface Might Not Work
|
Issue:
When multiple ILOM Remote Console sessions are opened to the same service processor, the additional session's keyboard interface might not work. The first session's keyboard interface is not affected.
|
Affected Software:
- Releases 1.0, 1.1, 1.2, 1.2.2, 1.2.3, and 1.3
|
Workaround:
- Double-click in the ILOM Remote Console dialog to activate the mouse, then move the mouse.
Or
- In the ILOM Remote Console menu bar, select Devices --> Mouse, then move the mouse.
|
6923903
|
SP Restore 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 such as 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:
- Releases 1.0, 1.1, 1.2, 1.2.2, 1.2.3, and 1.3
|
Workaround:
Log out of the serial console and try to run restore again.
|
6928047
|
BIOS Is Not Updated When You Use IPMIflash to Upgrade the ILOM SP Image
|
Issue:
BIOS does not get updated when you use IPMIflash to upgrade the ILOM service processor (SP) image with the Delay BIOS option on. When you power the server off and on, the BIOS image should be updated, but it is not.
|
Affected Operating System and Software:
- Oracle Linux 5.4
- Releases 1.0, 1.1, 1.2, 1.2.2, 1.2.3, and 1.3
|
Workaround:
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 the ILOM web interface: Remote Control->Remote Power Control->Power Cycle
- Using IPMI: ipmitool power cycle
|
6928567
|
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.
- Releases 1.0, 1.1, 1.2, 1.2.2, 1.2.3, and 1.3
|
Workaround:
Upgrade to JRE 1.6.0 U17 or later.
|
6875309
|
MegaRAID Mouse Pointer Does Not Work on Oracle ILOM Remote Console
|
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 the user boots the system and presses 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)
- Releases 1.0, 1.1, 1.2, 1.2.2, 1.2.3, and 1.3
|
Workaround:
In the Oracle ILOM Remote Console, change the mouse mode setting from Absolute (the default) to Relative mode. The mouse mode setting is located on the Remote Console/KVMS tab in the server’s Oracle ILOM web interface.
For instructions for setting Oracle ILOM Remote Console to Relative mode, see “Configure Oracle ILOM Remote Control Video Redirection Settings” in the Oracle Integrated Lights Out Manager (ILOM) 3.0 Web Interface Procedures Guide. This guide is included in the Oracle ILOM 3.0 Documentation Collection. To access the Oracle ILOM 3.0 Documentation Collection, go to the Oracle documentation site and navigate to the server documentation page:
http://www.oracle.com/documentation
|
7009287
|
Attempts to Set The flow control Setting on The External Serial Port Fail
|
Issue:
If you attempt to use Oracle ILOM to configure the flow control setting on the external serial port on the server, the new setting does not take effect.
|
Affected Software:
- Oracle ILOM 3.0.14.11
- Release 1.3
|
Workaround:
None. This is a planned new feature for software release 1.3, but it is not yet available. Do not try to use it.
|
Oracle Solaris Known Issues
TABLE 9 Oracle Solaris Known Open Issues
CR
|
Description
|
7009052
|
DDR3 DIMMs Displayed As Unknown Type in Solaris 10
|
Issue:
If you use the prtdiag command in Solaris 10, the DDR3 DIMM will be displayed as unknown type.
|
Affected Operating System and Software:
- Oracle Solaris 10 10/09
- Oracle Solaris 10 9/10
- Releases 1.0, 1.1, 1.2, 1.2.2, 1.2.3 and 1.3
|
Workaround:
A workaround is not yet available. This is a purely a display issue and it has no functional impact. The problem will be solved in a future Solaris release.
|
Virtual Machine Software Known Issues
TABLE 10 Virtual Machine Software Known Open Issues
CR
|
Description
|
6869812
|
Local Storage Drive Is Not Seen After Installing VMware ESXi 4.0 Update 1
|
Issue:
If the Sun Fire X4170 M2 or X4270 M2 Server has a local storage drive attached to the PCI-Express SAS LSI Controller (SG-SAS6-INT-Z), the local storage drive is not seen by the system after installing VMware ESXi 4.0 Update 1.
|
Affected Operating System and Software:
- VMware ESXi 4.0 Update 1
- Releases 1.0, 1.1, 1.2, 1.2.2, 1.2.3, and 1.3
|
Workaround:
After completing the ESXi installation, follow these steps to add the local storage drive to the storage inventory.
- Add the ESXi host to the datacenter of your choice using the Virtual Infrastructure Client.
- Select the ESXi host added in step one, then click the Configuration tab.
- In the hardware box (in the upper left of the display), select Storage.
- In the upper right part of the display, click the Add Storage... link.
- Ensure that the Disk/LUN Storage Type is selected, then click Next.
- Highlight the vmhba entry that corresponds to the local storage drive, then click Next.
- Select the Use free space entry, then click Next.
- Create a Datastore Name (for example, local_storage), then click Next.
- Adjust the Maximum file size, if needed, then click Next.
- Verify the proposed disk layout, then click Finish.
The local Virtual Machine File System (VMFS) datastore should now be available for use.
|
6927196
|
Oracle VM Manager 2.2 Installation Fails on Some 6-Core CPU Configurations
|
Issue:
When installing Oracle VM Manager 2.2 on a Sun Fire X4170 M2 or X4270 M2 Server with 6-core CPUs, the install might fail and exit with the message "Database is not available."
|
Affected Hardware, Operating System, and Software:
- Sun Fire X4170 M2 and X4270 M2 Servers
- Oracle VM Manager 2.2
- Releases 1.0, 1.1, 1.2, 1.2.2, 1.2.3, and 1.3
|
Workaround:
To resolve this issue, obtain the patch and installation instructions at http://oss.oracle.com/oraclevm/manager/patch
|
Oracle, Red Hat, and SUSE Linux Known Issues
TABLE 11 Oracle, Red Hat, and SUSE Linux Known Open Issues
CR
|
Description
|
6808230
6894153
|
Storage Drive LEDs Are Incorrectly Illuminated When Using ICH10 On-board HBA With SATA Drives
|
Issue:
On a server without a RAID PCIe card (with on-board ICH10 SATA controller), disk drive Fault and OK-to-Remove LEDs are incorrectly illuminated on hard disk drive slots.
|
Affected Operating System and Software:
- SUSE Linux Enterprise Server (SLES) 11
- Release 1.0
|
Workaround:
This issue is fixed in SLES 11 SP1, which is supported in Software Releases 1.1, 1.2, and 1.2.2.
If you want to use SLES 11, this issue has been addressed with an SLE(S/D) 11 kernel update available from Novell. Refer to the Novell Documentation Administration Guide for information on obtaining updates using Yast Online Updater or use Novell patch finder at http://download.novell.com/patch/finder/
|
6875599
|
PCI-e AER Driver Might Produce Excessive Error Messages
|
Issue:
The PCI-e AER driver in SLES 11 might produce excessive log messages that contain incomplete information about hardware errors.
|
Affected Operating System and Software:
- SUSE Linux Enterprise Server (SLES) 11
- Release 1.0
|
Workaround:
This issue is fixed in SLES 11 SP1, which is supported in Software Releases 1.1, 1.2, and 1.2.2.
If you want to use SLES 11, this issue has been addressed with an SLE(S/D) 11 kernel update available from Novell. Refer to the Novell Documentation Administration Guide for information on obtaining updates using Yast Online Updater or use Novell patch finder at http://download.novell.com/patch/finder/
|
6904919
|
m1x4_core Driver for InfiniBand Fails to Load or Defaults to Single Pin Interrupt
|
Issue:
InfiniBand IO devices using the mlx4_core driver and MSI-X interrupts on systems with 16 or more CPUs might cause the driver to not load or to only load using IO-APIC interrupts.
|
Affected Operating System and Software:
- SUSE Linux Enterprise Server (SLES) 11
- Release 1.0
|
Workaround:
This issue is fixed in SLES 11 SP1, which is supported in Software Releases 1.1, 1.2, and 1.2.2.
If you want to use SLES 11, this issue has been addressed with an SLE(S/D) 11 kernel and OFED package update available from Novell. Refer to the Novell Documentation Administration Guide for information on obtaining updates using Yast Online Updater or use Novell patch finder at http://download.novell.com/patch/finder/
|
6907462
|
Error Messages Are Logged About Loading EHCA Driver
|
Issue:
If the OFED package group is installed, the system generates benign error messages about loading the InfiniBand EHCA driver. The errors are logged because the supported InfiniBand IO device does not use the EHCA driver.
|
Affected Operating System and Software:
- SUSE Linux Enterprise Server (SLES) 11 and SLES 11 SP1
- Releases 1.0, 1.1, 1.2, 1.2.2, 1.2.3, and 1.3
|
Workaround:
Supported InfiniBand devices use the mlx4_core device driver. Ignore the error messages about the EHCA driver or disable attempts to automatically load the EHCA driver by editing the configuration file /etc/infiniband/openib.conf to change EHCA_LOAD=yes to EHCA_LOAD=no.
|
6907463
|
Errors in Subnet Manager Start Script for SLES 11
|
Issue:
SLES 11 is unable to execute the subnet manager start script opensmd.
|
Affected Operating System and Software:
- SUSE Linux Enterprise Server (SLES) 11
- Release 1.0
|
Workaround:
This issue is fixed in SLES 11 SP1, which is supported in Software Releases 1.1, 1.2, and 1.2.2.
If you want to use SLES 11, this issue has been addressed with an SLE(S/D) 11 kernel and OFED package update available from Novell. Refer to the Novell Documentation Administration Guide for information on obtaining updates using Yast Online Updater or use Novell patch finder at http://download.novell.com/patch/finder/
|
6915768
|
During a Reboot of the System, a Kernel Panic Might Occur
|
Issue:
During a warm reboot of the system, you might see an intermittent kernel panic __cpufreq_governor.
|
Affected Operating Systems and Software:
- Oracle Linux 5.4
- Red Hat Enterprise Linux (RHEL) 5.4
- Releases 1.0, 1.1, 1.2, 1.2.2, 1.2.3, and 1.3
|
Workaround:
A patch has been issued to fix this issue. You can download the patch at:
https://bugzilla.redhat.com/attachment.cgi?id=336296&action=diff
|
6940552
|
CPU Power-state Cannot Be Capped on Host Reboots If Hard Cap Is Enabled
|
Issue:
Oracle ILOM Power Management limits might not be honored upon boot in Oracle Linux 5.5 or in Red Hat Enterprise Linux (RHEL) 5.5.
|
Affected Operating Systems and Software:
- Oracle Linux 5.5
- Red Hat Linux (RHEL) 5.5
- Releases 1.0, 1.1, 1.2, 1.2.2, 1.2.3, and 1.3
|
Workaround:
Using Oracle ILOM, disable then re-enable Power Limiting using the following steps:
- Select the Power Management tab.
- Select the Limit tab
- Next to the Power Limiting option, uncheck Enabled.
- Click Save.
- Next to the Power Limiting option, check Enabled.
- Click Save.
|
Windows Known Issues
TABLE 12 Windows Known Open Issues
CR
|
Description
|
6879304
|
Windows Server 2008 R2 Generates System Event Log Warning Messages When Power Is Being Limited by Oracle ILOM Power Management
|
Issue:
When power is being limited by the Oracle ILOM Power Management feature, the Windows Server 2008 R2 operating system will generate warning messages in the System Event Log informing the user that the processor(s) are being restricted. Example Event: The Speed of Processor xx in group x is being limited by system firmware. The processor has been in this reduced performance state for xxxx seconds since last report.
|
Affected Hardware, Operating Systems, and Software:
- All Sun servers with Power Management support
- Windows Server 2008 R2
- Releases 1.0, 1.1, 1.2, 1.2.2, 1.2.3, and 1.3
|
Workaround:
No workaround is needed. These warning messages are expected events and, therefore, do not indicate a problem.
|
Oracle Hardware Installation Assistant Known Issues
Note - Oracle Hardware Installation Assistant previously was called Sun Installation Assistant (SIA). |
TABLE 13 Oracle Hardware Installation Assistant Known Open Issues
CR
|
Description
|
6835303
|
Oracle Hardware Installation Assistant Installation Does Not Work Correctly When Installing an ISO Image of the Red Hat Operating System Using NFS
|
Issue:
If you elect to install the Red Hat operating system from an ISO image that is exported using a network file system (NFS) server, profiles for the Red Hat installation will not be propagated to the installation. This will result in the following behavior:
- Anaconda will prompt the user for the installation type (desktop, client, server, or minimal).
- Individual packages will not be pre-selected based on the installation type, and the user will have to select these manually.
|
Affected Operating Systems and Software:
- Red Hat Enterprise Linux (RHEL) 5.4 and 5.5
- Releases 1.0, 1.1, 1.2, 1.2.2, 1.2.3, and 1.3
|
Workaround:
When using Oracle Hardware Installation Assistant to install the Red Hat operating system, do not use an ISO image exported using NFS.
|