0% found this document useful (0 votes)
20 views

Releasehh

jhb
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
20 views

Releasehh

jhb
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 5

================================================================================

Intel(R) Server Board S2600CW Family


for Intel(R) Deployment Assistant, Intel(R) One Boot Flash Update Utility,
Windows* Preboot Execution Environment
================================================================================
Intel(R) Server Boards and Systems
Intel Corporation
2111 N.E. 25th Avenue, Hillsboro, OR 97124 USA
================================================================================
DATE : September, 20 2015
TO : Intel(R) Server Board S2600CW Family
SUBJECT : Release Notes for System Firmware Update Package
================================================================================
ABOUT THIS RELEASE
================================================================================
BIOS : 01.01.0009
ME : 03.00.07.168
BMC : 01.28.8586
FRUSDR : 1.10
================================================================================
Support Platforms and Dependency
================================================================================
Processors supported:
Intel(R) Xeon processor E5-2600 v3 series

Microcode update versions:


Intel(R) Xeon(R) processor E5-2600 v3 series C0/C1 stepping: 0x0000002E CPUID =
0x306f2

Production boards:
Product Fab Version
S2600CW Fab2 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:
- 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 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:
<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:
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 R01.01.0009
================================================================================
EPSD100027182 ME status show "Not Ready" in SETUP(MFG mode).
EPSD100027258 HII - Day information hard coded to always 'Thu' irrespective
of date we save in Schedule CC page
EPSD100245060 System intermittently reboots due to watchdog timer failure.
EPSD100245810 The description for "boot mode" under advanced controller
property gets truncated
EPSD100246351 Set Boot Mode=UEFI via ITK,"Launch EFI Shell" will disappear.
EPSD100246372 No video signal when enable ESRT2 UEFI BIOS and Emulex 16002B.
EPSD100246418 Sysinfo_v13.1.6:some BIOS options should not displayed
"Possible Values" in sysinfo_log.txt.
EPSD100246978 Cannot enter BIOS setup after enabling serial console redirection
for serial port B
EPSD100027610 [E5-16xx] Wrong "Memory Array Handle" mapping cause SMBIOS Type
16/17/19/20 has wrong structure.
EPSD100027259 [S2600WT]Not calling INT15h handler of iMR when MR OPROM loads
EPSD100027735 "Intel Embedded Server RAID Technology 2" OpROM not show in BIOS
EPSD100027816 [E5-16xx] Trigger MBE at channel A1 will get wrong sel log.
EPSD100247226 BSOD under Windows 2012 R2 when hot plugging NVMe SSD drives
EPSD100247285 [24HDD]The hot plug function of HSBP cannot work normal.
EPSD100245307 Pressing multiple F6 from SOL skips through boot manager.
EPSD100247506 BMC DHCP HOST NAME can not be changed if DMN is DYNAMIC and BMC
EPSD100028176: HW RAID HII: Arrow listing is not displayed correctly when lines
EPSD100247654: Help to integrate the LAN OPROM20 oprom.
EPSD100244429: System sporadically hangs at post code 0x89
EPSD100028560: [24HDD] The value of OEMID at ACPI table is not expected value.
EPSD100028741 No Error Message display when boot into unsigned OS with secure
boot enable
EPSD100248330 ME status error with ME force update jumper
EPSD100028678 SUT will get IERR event when enable secure boot via ITK or Syscfg.
EPSD100028810 Windows2012R2 reboot cycle failed.
EPSD100248466 [S2600WT] System locks up during OS DC cycling test
EPSD100028878 [S2600WT] Dmesg record. Corrupted low memory after finish
SLES 12 installation
EPSD100028803 [S2600WT] VTK-125R2 can't execute.
EPSD100248439 Conflict message in Linux when serial port A is set as 0x2f8 and
IRQ3
EPSD100028852 After change "Active Processor Cores" , then press F10 to save
Setup
menu, it will pop up a fail screen as picture.
EPSD100248533 Memory speed changes when POR setting is disabled and with a
specific
CPU - 3 DIMMS per channel

================================================================================
KNOWN ISSUES in ME 03.00.07.168 release
================================================================================
If host main power delayed relatively to the standby power for 720-770ms ME stop
responding.
Unable to set Alert Threshold Limit to 0 degrees (minimum from capabilities) for
Inlet Temperature Trigger Type Policy.
[MESDC] ME FW Status in S3 State is failed.
During Host Warm Reset flow, unexpected Intel� SPS 3.0 E5 Firmware exception may be
promoted to Platform Global Reset.
When auto configuration is performed and efficiency readings are provided from BMC,
ME keeps requesting PSUs for readings.
Alert Immediate Messages (Host Comm Error) on SandStorm.
NMPTU Get NM Capabilities updated to invalid values.

Permanent Node Busy completion code received when trying to ColdReset ME after
setting new value of SlopeComp and Offset coefficients.
After increasing scanning period of DC Power sensor, min correction time for
policies in secondary power domain (DC power) will not be updated.
SpsInfox86 crashes when executed with 64-bit addressing enabled.
Node Manager cannot maintain power limit after PSU power loss in Redundant PSU
Configuration.
When "PIA Platform PSU Efficiency" sensor is disabled in xml Node Manager uses
incorrect power reading for power limiting.
The sensor 0x18 SEL for HW protection policy correction time exceeded.
Get NM Parameter cmd (FAh) responds with incorrect readings when the sensor
scanning is disabled.
Potential race condition in NM component handling SMART/CLST functionality.

===============================================================================
BMC Changes in 01.28.8586
===============================================================================
-EPSD100248398: Spelling error in SEL log.
-EPSD100248427: After SUT power off, there is "Front panel temp sensor has failed
and may
not be providing a valid reading - assert" logged for BMC FW health sensor
-EPSD100248399: Change Bad Passwordk Threshold parameter string in EWS to be same
with spec.
-EPSD100248480: Chassis intrusion is always enabled on MTM2 exit.

================================================================================
FRUSDR Changes in release 1.10
================================================================================

Issue Fixed:
- None.
Features added:
- Update FRUSDR utility to version 11 build 20.

=============================================================================
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) 2014 Intel Corporation.

A portion of this firmware is open source code, which falls under the
GPL 2.0 license.

[END OF RELEASE NOTES]

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy