================================================================================ Intel(R) Server System P4000IP/R2000IP Family Intel(R) Workstation System P4000CR 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 : June 30, 2012 TO : Intel(R) Server system P4000IP/R2000IP Family Intel(R) Workstation System P4000CR Family customers SUBJECT : Release Notes for System Firmware Update Package ================================================================================ ABOUT THIS RELEASE ================================================================================ BIOS : 01.03.0002 ME : 02.01.05.107 BMC : 1.10.3560 FRUSDR : 1.08 ================================================================================ Support Platforms and Dependency ================================================================================ Intel(R) Server Processors supported: Intel(R) Xeon(R) Processor E5-2600 series Microcode update versions: Intel(R) Xeon processor E5-2600/2400 series C0 stepping: 0x80000513 CPUID = 0x206D5 Intel(R) Xeon processor E5-2600/2400 series C1 stepping: 0x80000615 CPUID = 0x206D6 Intel(R) Xeon processor E5-2600/2400 series C2 stepping: 0x8000070A CPUID = 0x206D7 The following update process must be followed to ensure a trouble free update. 1. BMC firmware to 1.00 or later 2. BIOS 01.01.1002 or later 3. Manageability Engine (ME) firmware 02.01.05.69 or later 4. Latest FRU/SDR package specific to the baseboard. ================================================================================ 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 9 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://www.intel.com/support/ - Unzip package and copy all files to root folder in USB disk on key - Insert USB disk on key to server USB port - Reboot server, system will start BIOS/BMC/FRUSDR update automatically If case for some reason or you didn't put unzipped package under root folder of USB key, you can do it by: - Reboot server to EFI shell manually - Run command "map -r" in EFI shell to mount USB disk on key - Run command "fs0:" to change folder to USB disk on key, USB key may also mount to fs1:. The number of "fs" is dependent on the result of command "map -r" - 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://www.intel.com/support/ 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 It 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://www.intel.com/support/ 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 Disk on Key or Hard Disk Download the latest Firmware Update Package from http://www.intel.com/support/ and copy it to a USB key, then insert the key 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 disk. 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://www.intel.com/support/ 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://www.intel.com/support/ - 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 key 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 key 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 releaenotes 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 01.03.0002 ================================================================================ - Fixed: NIC Information can not be saved in the Sysinfo log file and it cannot be retrieved or set using the syscfg utility. - Fixed: If Remotely redirecting an ISO image from a client and the target system is restarted, the target system will automatically boot to the redirected ISO image and start an OS installation. ================================================================================ ME Changes in release 02.01.05.107 ================================================================================ - Fixed: FW may hang in initialization state after the update of entire ME region is interrupted by AC loss. - None of the available ME resets (AC cycle or Global Reset or Power Button Override) can get ME out of the error condition, only reflashing ME image. - Fixed: FW may become unresponsive after switching from Recovery to Operational (e.g. during Direct Update). - Global Reset or Power Button Override can’t get ME out of the error condition. ================================================================================ BMC Changes in release 1.10.3560 ================================================================================ - Fixed: Updated FRUSDR files. - S2400BB to version 0.09 - S2600CP to version 1.06 - S2600CO to version 1.07 - W2600CR to version 1.07 - S2400EP to version 1.00 - S2600IP to version 1.07 - S2600JF to version 1.07 - S2400LP to version 1.06 - S2600CP to version 1.07 - S2600CO to version 1.08 - W2600CR/S2600IP to version 1.08 - S2400GP to version 1.05 - S1600JP to version 0.05 - S2600JF to version 1.08 - S4600LH to version 0.12 - S2600WP to version 1.05 - S2600GZ/S2600GL to version 1.03 - Fixed: Adjust RGMII Tx clock delay to -250ps for S1400SP according to SI requirement - Fixed: Command OEM Get Reading. will now return units-based value converted by using .y=Mx+B - Fixed: Fixes to LCD Code defects identified in code review were incorporated - Fixed: Some strings on LCD were formerly displayed improperly on LCD - Fixed: Increased total SDR record length to 0x48h from 0x40h to accommodate the S4600LH SDR requirements - Fixed: S1600JP: Corrects the baseboard temperature sensor mapping so that it works - Fixed: After forcing a CATERR on S4600LH, the debug information from Embedded Web Server lacks some information - Fixed: LAN channel cannot get DHCP IPv4 address after disabling VLAN on it - Fixed: NMI sensor event isn't logged after issuing "chassis control" command to trigger NMI - Fixed: SUT hang at POSTCODE: 0x63 while BMC LAN connected to a switch loop environment - BMC would freeze under heavy network traffic loads (e.g. broadcast storm) - Fixed: S4600LH: Fan speed reading not correct - Added other chassis support in S4600LH and corrected RPM calc - Also updated S1400FP/S1400SP SDR to reflect change. - Fixed: Network Interface hold time was out of spec for S2600GZ/S2600GL and S2400BB - Fixed: Issuing incorrect "Set CR Configuration" command returns wrong error code - Fixed: LCP error messages are not scrolling automatically without pressing LEFT and RIGHT keys - Fixed: LCP default banner text when server with normal health is displaying some junk characters at the end - Fixed: Number of characters displaying in LCP display is only 16 but it should be 18 characters - Fixed: LCP displays "No BIOS POST C" when enter into LPC under VIEW menu - Fixed: Unable to view the entire IP or Gateway or Subnet addresses using LCP display, last digit is missing during display. - Fixed: Firmware information contents in LCP displaying does not match the actual version - Fixed: Banner text is not reflecting correct information after selecting SM, LPC, or POW as a banner - Fixed: LCP default screen after power on is not the correct banner text - Fixed: S2400SC shows no socket present in CPU information page of Embedded Web Server - SMBIOS rev 2.7.1 added additional socket types. This change adds those types to the SMBIOS translation tables. - Fixed: Updated S4600LH SDR to resolve issues where fans specified in FCT SDRs couldn't be controlled with fan domains. - Fixed: BMC 1.08 S4600LH SDR was missing Sensor 0x2C (Riser 2 Left Forward Temperature) - Fixed: Exit Air Temp reading mismatch when using IPMI command under Linux - The sensor initialization code was checking both assertion and deassertion enables and settable/readable thresholds before actually setting the thresholds. This was causing the Exit Air Temp sensor to fail to set thresholds (all thresholds became 0) - Fixed: Host name is not included in Email Alert subject line - Subject line could potentially be set before host name was set. This change sets the subject line again after the host name is changed - Fixed: BMC FW must satisfy open source advertising clause for OpenSSL - Added "About" button to top bar to satisfy item 6 in the OpenSSL license. - Added: Changed SDR of S2600CP, S2600CO, W2600CR/S2600IP, and S2400GP to add Dynamic Power Unit Redundancy Sensors - Added: Add S1600JP and S2600WP PCIeSlotMap Table - Added: Adds option (0xfe) for SlotIPMB command to ignore mux completely ================================================================================ FRUSDR Changes in release 1.08 ================================================================================ - Change power unit redundancy sensor to manual rearm. - Change the tag for SDR type 11 related to PSU. ============================================================================= 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) 2012 Intel Corporation. A portion of this firmware is open source code, which falls under the GPL 2.0 license. [END OF RELEASE NOTES]