This chapter contains release notes information and issues for Sun Fire X4170 M2 Servers.
This chapter contains the following sections:
1.1 General Information
Table 1–1 identifies the software/firmware versions for X4170 M2 servers, which are included in the Exalogic machine (EL X2-2).
Table 1-1 X4170 M2 Software/Firmware Versions Supported
Software/Firmware | Version |
Server Firmware Release | 1.2.1 |
Operating System | Oracle Linux 5.5 |
BIOS | 08.04.02.03 (1.2.1a) |
ILOM | 3.0.9.27.a/r58740/SW1.2.1 |
1.2 Latest Product Information
For latest information about Sun Fire X4170 M2 Servers, including the product notes, see the following link:
http://docs.sun.com/app/docs/prod/sf.x4170m2#hic
1.3 Versions of Intel Microcode and Reference Code Used in BIOS Firmware
Table 1–2 lists the versions of the Intel Microcode and Reference Code used in the BIOS firmware image for Release 1.2.1.
Table 1-2 Intel Microcode and Reference Code Used in BIOS Firmware
Intel Software | Version Used in 1.2.1 |
Intel CPU Microcode | SRV_C_89 |
Intel RC | 2.90 |
Intel CPU Reference Code | 1.08 |
Intel QuickPath Interconnect (QPI) Reference Code | 1.85 |
Intel Memory Reference Code (MRC) | 2.20 |
1.4 Known Issues
It consists of the following topics:
1.4.1 Hardware Known Issues
Table 1-3 Hardware Known 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. |
| Workaround: Use ILOM to determine fan module status or turn host power back on. |
1.4.2 BIOS Known Issues
Table 1-4 BIOS Known 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. |
| 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. |
| Workaround: Do one of the following:
|
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: |
| 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. |
| Workaround: Reboot the system with PC Check disabled before trying to install or boot an operating system. |
1.4.3 ILOM Known Issues
Table 1-5 ILOM Known 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 (SB) network port sharing, in-chip connectivity between the service processor (SP) and the host OS is not supported by the on-board host Gigabit Ethernet controller. |
| 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. |
| Workaround:
Or
|
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: 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. |
| Workaround: Log out of the serial console and try to run |
6936585 | 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. |
| Workaround: The HDD PRSNT sensor status can be forced to update by refreshing the ILOM web interface components page or by showing -> Subsequently, the following CLI command will return the correct status of the sensor: -> |
