SoftHub

Versions:

- BIOS: R01.02.0001
- ME: R04.00.03.075
- BMC: 00.20.9366
- FRUSDR: 0.15

BIOS Changes:

- Update BIOS version to 01.02.0001 for gold build.

ME Changes:

- ME partition corruption results in ME hang.
- unexpected SMART-CLST event during DC cycle with PMBus 1.1 PSUs
- ME FW is accessing PSUs when autocon?guration is switched to BMC
- Get NM Statistics command reports 100% for maximum memory throttling.
- ME FW is sending NM Health Event - Power Sensor Reading Failure alert for domain 3.

BMC Changes:

- Disable Stunel for IHC
- Latest log status of System SOL is abnormal on EWS.
- Can receive alert mail from all NICs even no cable connected.

FRUSDR Changes:

- The PS1 Curr Out % status shows "Unknow" in sensor readings of EWS(1U,350W).

System Firmware Update Package Usage instructions

This package can be updated using one of the following methods:
- Windows or Linux operating system using Intel One-boot Flash Update (OFU) V12.0 Build 4 or later)
- Windows Preboot Execution Environment (WinPE)

To update from Windows and Linux or operating systems using the Intel One Boot Flash Update Utility (OFU)

Use OFU to update system firmware by the following steps:

- Install OFU on Windows or Linux system
- Download the latest firmware update package from http://downloadcenter.intel.com/
- Unzip package to a folder
- Run the following command in Windows command line/Linux terminal window: <OFU install folder name>:\flashupdt -u <package folder name>\flashupdt.cfg

To update from Windows Preboot Execution Environment (WinPE)

The System Firmware Update Package can be inserted to Windows PE customized image for creating a bootable Windows PE CD. User is able to update system firmware from customized WinPE CD by the following steps:
- Boot server with customized WinPE CD
- Run script "WinPE21_x64_Update.bat" or "WinPE20_x86_Update.bat" (name may be varied depends on your own customization)

Note:

- The Intel OFU utility is case sensitive. Therefore, when you transfer the Firmware Update Package using USB flash drive from a Microsoft Windows system to a Linux environment, you must first extract under the Linux environment. Otherwise, you will need to mount the USB flash drive manually with 'vfat' option under Linux to avoid conversion from uppercase to lowercase and vice versa.
- To make Intel OFU utility run properly under x86 or x64 OS, you have to read OFU release notes on known issues for OFU installation.
- In this SFUP package, Intel only provide batch file "WinPE_x86_Update.bat" for WinPE2.0 32 bit solution "WinPE_x64_Update.bat" for WinPE2.1/3.0 64 bit solution as an example. Please refer to white paper "White Paper-Intel Server Utilities Procedure for WinPE.pdf" for details on building your own customized WinPE CD.
- Windows PE 2.0 - built from Windows Vista SP1 32bit or EM64T
- Windows PE 2.1 - built from Windows Vista SP1 or Windows Server 2008, EM64T
- Windows PE 3.1 - built from Windows Server 2008R2, EM64T
- Microsoft IPMI driver is loaded by default from WinPE CD, if you want to use Intel IPMI driver instead of MS IPMI driver for firmware update, you can un-install Microsoft IPMI driver by: Devicesetup.exe ¨Cv remove IPI0001 and know that IPI0001 is the device ID for Microsoft IPMI driver.

About Firmware Updates:

Applying a newer firmware version than the one already installed on your unit can bring various enhancements, include workarounds for diverse problems encountered by the device, and improve or add newly developed features.

On the other hand, downgrading the firmware version can recover the device’s functionality in the event of a software update either turning up faulty or causing the unit’s overall performance to drop. However, bear in mind that applying an older firmware isn’t recommended and might not always be possible.

When it comes to the update steps, due to the large variety of devices and numerous ways for installing a new firmware, it is recommended that you carefully read and understand the upgrade steps, and consider applying a different firmware only when you have familiarized yourself with the update method.

As the installation process is most of the times quite risky, this step should be taken by users that have the ability to successfully complete the update; regular users may initiate it at their own risk. Moreover, it’s best that this task be performed in a steady power environment such as the one ens