================================================================================ Intel(R) Server Board S2600JF, Intel(R) Server System H2000JF Product Family Firmware Update Package for Intel(R) Deployment Assistant, Intel(R) One Boot Flash Update Utility, The embedded EFI Shell, Windows* Preboot Execution Environment ================================================================================ Intel Enterprise Platform & Services Division - Marketing Intel Corporation 2111 N.E. 25th Avenue, Hillsboro, OR 97124 USA ================================================================================ DATE : Spet 2, 2013 TO : Intel(R) Server Board S2600JF Family Intel(R) Server System H2000JF Family customers SUBJECT : Release Notes for System Firmware Update Package ================================================================================ ABOUT THIS RELEASE ================================================================================ BIOS : 02.01.0002 ME : 02.01.07.231 BMC : 01.19.5018 FRUSDR : 1.12 ================================================================================ Support Platforms and Dependency ================================================================================ Processors supported: Intel(R) Xeon processor E5-4600/2600/2400 series Intel(R) Xeon processor E5-4600/2600/2400 v2 series Microcode update versions: Intel(R) Xeon processor E5-4600/2600/2400 series C0 stepping: 0x00000513 CPUID = 0x206D5 Intel(R) Xeon processor E5-4600/2600/2400 series C1 stepping: 0x00000619 CPUID = 0x206D6 Intel(R) Xeon processor E5-4600/2600/2400 series C2 stepping: 0x00000710 CPUID = 0x206D7 Intel(R) Xeon processor E5-4600/2600/2400 v2 series C0/C1 stepping: 0x00000416 CPUID = 0x306e4 Production boards: Product Fab Version S2600JF family Fab3 or above The following update process must be followed to ensure a trouble free update. 1. BMC firmware 2. BIOS 3. Manageability Engine (ME) firmware 4. FRUSDR ================================================================================ System Firmware Update Package Usage instructions ================================================================================ This package can be updated using one of the following methods: - The embedded UEFI shell - Intel(R) Deployment Assistant - Windows* or Linux* operating system using Intel(R) One-boot Flash Update (OFU) V11.0 Build 14 or later) - Windows* Preboot Execution Environment (WinPE) To update from the embedded EFI Shell Update system firmware from Intel server EFI shell by the following steps: - Download Intel server system firmware update package from http://downloadcenter.intel.com/ - Unzip package and copy all files to root folder in USB flash drive - Insert USB flash drive to server USB port - Reboot server, system will start BIOS/BMC/FRUSDR update automatically If the unzipped package is not under the root folder of USB flash drive: - Reboot server to EFI shell manually - Run command "map -r" in EFI shell to find the mount point of the USB flash drive - The USB flash drive may mount to fs0: or fs1: or other. - Run command "fs0:" or other to change folder to USB flash drive, - Change folder to the folder storing the firmware package - Run command "startup.nsh" to start firmware update process Please refer to "EFI_Instructions.pdf" in this firmware package for a quick guide to use the EFI commands To Update from Intel(R) Deployment Assistant (IDA) The Intel(R) Deployment Assistant software is easy to use and is present on the "Intel(R) Server Deployment & Management" DVD shipped with the system. User can download the latest version IDA CD ISO image from http://downloadcenter.intel.com/ To use the IDA CD to update the system firmware: - Boot server with IDA CD - Select "Get System Updates" - Choose one of the three options . From http://www.intel.com/support/ Automatically downloads the latest Firmware Update Package from Intel Requires Internet connection Enter your local IP address and proxy configuration Click "Next" to start the download and update process . From my network Download the latest Firmware Update Package from http://downloadcenter.intel.com/ and copy it to a Windows* shared folder Enter your local IP address, the Windows* file server name, and a Windows user name and password Select the firmware package in pop-up window Click "Next" to start the update process . From USB flash drive or Hard Disk Download the latest Firmware Update Package from http://downloadcenter.intel.com/ and copy it to a USB flash drive, then insert the USB flash drive into the server USB port Click "Browse" Select the firmware package in pop-up window Click "Next" to start the update process Note: The Firmware Update Package is in the ZIP file format. Do not unzip before copying to a Windows* shared folder or USB flash drive. To update from Windows* and Linux* or operating systems using the Intel(R) One Boot Flash Update Utility (OFU) Intel(R) One boot Flash Update utility can be downloaded from http://downloadcenter.intel.com/ and it is part of the "BIOS, Firmware Update & Configuration Utilities" for Windows* and Linux*. Please refer to Intel OFU user guide about the details of installation and usage of 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: :\flashupdt -u \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: 1. The Intel(R) 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 upper case to lower case and vice versa. 2. To make Intel(R) OFU utility run properly under x86 or x64 OS, you have to read OFU release notes on known issues for OFU installation. 3. 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. 4. Windows PE 2.0 - built from Windows Vista SP1 32bit or EM64T 5. Windows PE 2.1 - built from Windows Vista SP1 or Windows Server 2008, EM64T 6. Windows PE 3.1 - built from Windows Server 2008R2, EM64T 7. 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 Note: IPI0001 is the device ID for Microsoft IPMI driver. ================================================================================ BIOS changes in release 02.01.0002 ================================================================================ - Fixed: There is no System event log when SBE or MBE is triggered from some specific memory slot. - Fixed: SysCfg utility ver. 12.8 has compatibility issues with BIOS R02.01.0001. - Fixed: Administrator/user password will be cleared by clearing CMOS on BIOS R02.01.0001. Others: - Change "UEFI network stack" and "IPv4 PXE support" default value to "Disabled". ================================================================================ ME Changes in release 02.01.07.112 ================================================================================ - Fixed: Improper ME FW Health Event is sent when ME is reset to factory defaults with IPMI command Force ME Recovery - Fixed: Throttling statistics in domain 0 and 1 are equal to 0, when power policy is active in domain 0 - Fixed: Power limit oscillations were observed after adding 7 NM power limiting policies - Fixed: NM Capabilities event is not sent after disabling then re-enabling scanning on its sensor - Fixed: ME Power State Change notification is not sent after Set ME Power State command (M3 -> MOff) ================================================================================ BMC Changes in release 01.19.5018 ================================================================================ - Fixed: The Intel(R) Xeon(R) Phi(TM) Coprocessor adapters Status Sensor shows "Unknown" when only 1 adapter is in the system - Fixed: System Events for DIMM thermal margin sensors are not decoded properly in the Embedded Web Server and Embedded Web Server log files. - Fixed: Embedded Web console not displaying sensor values for sensors from another controller - Fixed: Chassis identify not working as expected. - Fixed: The IHC (Intel(R) Hybrid Cloud) interface exposes a self-signed certificate containing a developer name and email address. - Fixed: Integrated BMC Web Console Keyboard Macro Cltrl+Alt+F1 not working as expected. - Fixed: BMC does not ignore momentary PWM interruptions after SMBALERT is asserted (SmaRT event). - Fixed: Embedded Web Console Power Statistic page time value not getting updated. - Fixed: IBMC used in Web Console Server Health > Event Log Page. - Fixed: Embedded Web Console SEL decoding BMC FW Update Minor version incorrectly. - Fixed: IO module Temperature sensor reading is always 0 on S2600JF. - Fixed: Get User Access Command - Number of enabled users not correct. - Fixed: Get/Set Processor Error Configuration and Status command not working as expected. - Fixed: BMC update failing after 4 consecutive firmware updates. BMC will no longer stay in recovery mode (uboot) after four consecutive firmware updates. - Fixed: JViewer always shows "Error reading video data" popup and a black screen when mouse mode is set to relative and JViewer tries to hide the cursor. - Fixed: Multicast traffic was being passed through to the BMC causing slow downs and resets. This change enables multicast filtering, but still allows IPv6 multicasts for Neighbor Advertisement, Router Advertisement, and DHCPv6 relay and server multicast. - Fixed: The UBoot code detects a bad CRC of the Ram Image when attempting to boot after getting a cold reset. - Fixed: The recommendations in the Web Console Mouse Mode tab are out of date. - Fixed: S1600JP 5V STBY sensor intermittently reporting low voltage error during AC cycle testing. - Fixed: Disable POST codes LED output after system has completed POST - Fixed: Correct the 750w PSU FW version. - Fixed: S2600JP: Update SDR to version 1.04. - Fixed: S2600CO: Update SDR to version 1.10. - Fixed: W2600CR/S2600IP: Update SDR to version 1.10. - Fixed: S2600JF: Update SDR to version 1.11. - Fixed: Update EPSD Platforms Based on Intel(R) Xeon(R) Processor E5-4600/2600/2400/1600/1400 Product Families HSBP to 1p3 . - Fixed: Update for 1600W DC PSU FW. - Fixed: Updated version number information for S2400BB and S2600GL/S2600GL platforms. - Fixed: Changed Fan Speed sensing and control when SMB Alert assertion is detected (SmaRT event) - Fixed: Seeing false watchdog events after a BMC update or reset. - Fixed: BMC watchdog resets seen during network flooding. - Fixed: Some logged POST Errors codes causing Embedded Web Server SEL viewer to stop displaying. - Added: DCMI 1.5 spec compliance on EPSD Platforms Based on Intel(R) Xeon(R) Processor E5-4600/2600/2400/1600/1400 Product Families - Added: Enable Intel(R) Xeon(R) Phi(TM) Coprocessor adapters for W2600CR/S2600IP. - Added: Added remote KVM watchdog. If there is an error on the remote KVM then wait one minute and then open a new KVM session. ================================================================================ FRUSDR Changes in release 1.12 ================================================================================ - Upgrade FRUSDR utility to Version11 Build20 ============================================================================= LEGAL INFORMATION ============================================================================= Information in this document is provided in connection with Intel products. No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by this document. Except as provided in Intel's Terms and Conditions of Sale for such products, Intel assumes no liability whatsoever, and Intel disclaims any express or implied warranty, relating to sale and/or use of Intel products including liability or warranties relating to fitness for a particular purpose, merchantability, or infringement of any patent, copyright or other intellectual property right. Intel Corporation may have patents or pending patent applications, trademarks, copyrights, or other intellectual property rights that relate to the presented subject matter. The furnishing of documents and other materials and information does not provide any license, express or implied, by estoppel or otherwise, to any such patents, trademarks, copyrights, or other intellectual property rights. Intel products are not intended for use in medical, life saving, or life sustaining applications. Intel may make changes to specifications and product descriptions at any time, without notice. Intel is a registered trademark of Intel Corporation. *Other names and brands are the property of their respective owners. Copyright (c) 2013 Intel Corporation. A portion of this firmware is open source code, which falls under the GPL 2.0 license. [END OF RELEASE NOTES]