================================================================================
Intel(R) Server Board S2600ST 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    :	November 1, 2017
TO      :	Intel(R) Server Board S2600ST Family
SUBJECT : 	Release Notes for System Firmware Update Package 
================================================================================
                              ABOUT THIS RELEASE
================================================================================
BIOS   : 00.01.0009
ME     : 04.00.04.288
BMC    : 1.29
FRUSDR : 1.24
================================================================================
                           Support Platforms and Dependency
================================================================================
Processors supported: 
Intel(R) Xeon(R) Scalable processors

Microcode versions:
        CPUID           Version       Status
        0x50653        0x01000138     (Xeon Scalable B1)
        0x50654        0x02000026     (Xeon Scalable H0)

The following update process must be followed to ensure a trouble free update.
1.	BMC firmware
2.	BIOS
3.	Manageability Engine (ME) firmware
4. 	FD
5.	FRUSDR

================================================================================
                             IMPORTANT NOTE!!!                   
================================================================================
 - This Update package must be installed using 
   Intel(R) One-boot Flash Update (OFU) V14.1 Build 14 or later
   

1. Package C-State only works well with Xeon Scalable Family H0 parts, for other Xeon Scalable Family stepping, C6 non-retention is hardcode from BIOS side.
2. BIOS R00.01.0001 does not support online downgrade to any Dxxx or Xxxx BIOS.
3. BIOS R00.01.0001 removed Xeon Scalable Family A1 microcode(m1350651_8000002B) and Xeon Scalable Family B0 microcode(m9750652_80000035).
4. Removed 'UpdateNvram' support for iflash32 tool for security reason of SRA bios.
5. Security revision upgrade to v0002 on BIOS R00.01.0002 will prevent BIOS downgrade via normal mode to R00.01.0001, user can use BIOS recovery mode for BIOS downgrade. Although Intel doesn't recommend downgrading firmware
6. One new production key is integrated onto R0004 BIOS, which will correct an OEM string. 
7. This release include security revision upgrade to version 0004. This will prevent BIOS downgrade via normal mode to previous version with lower security revision, user can use BIOS recovery mode process for BIOS downgrade.
8. System will prevent downgrading ME from 04.00.04.288 to 04.00.04.235 or older version, if system BIOS version is R0009. This is an expected behavior. 

IMPORTANT: BIOS 00.01.2001 is an earlier version than 00.01.0004 if you have 
this version please update to 00.01.0004 first

================================================================================
                  System Firmware Update Package Usage instructions                   
================================================================================
This package can be updated using one of the following methods:
 - Windows* or Linux* operating system using Intel(R) One-boot Flash Update (OFU)
   V14.1 Build 14 or later)
 - Windows* Preboot Execution Environment (WinPE)

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(R) 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 "WinPE_x64_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 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_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 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 2008 R2, 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 00.01.0009
================================================================================
Rename BIOS ID from X0084 to R0009.
HSD-ES: 2103619332, , [S2600WF] NIC configuration page not show OCP controller and MAC info or show wrong when install Cascade DA2 on S2600WFT SKU or Cascade DA4 on S2600WFQ SKU.
HSD-ES: 2103619390, , [S2600BP] Set "NIC1 Port1/2" to Disabled cannot be saved under legacy mode with S2600BP NIC X550.
HSD-ES: 1504599235, , [PC Stitching] Sync Microcode 0x30 for Xeon Scalable Family H0 from RP.
HSD-ES: 2103619297, , [S2600BP] ME status shows "Not ready" and ME revision shows "Unknown" after SPS FW downgrade from 04.00.04.285 to 04.00.03.235.
HSD-ES: 1504615636, , [PC Stitching] Sync Microcode 0x32 for Xeon Scalable Family H0 from RP.
Update BIOS security version to 0004.
HSD-ES: 2103619238, , [S2600WF] PXE function still work whether press F12 or selected from boot manager when disable NIC control.
Check in SPS FW 04.00.04.288 on critical security issue 
HSD-ES: 220788736, ,S2600WF system goes into continuous restart loop after SUP update process on H48104-701 board with SUP x0060 installed and two embedded NIC ports disabled
HSD-ES: 1504597970, ,Fix issue- Array OCPDID Index Out of Bounds.
HSD-ES: 1504579741, , CCB 2030:  Enable/disable individual embedded only NIC ports
HSD-ES: 1504582533/1504582491,  CCB 2022: Support storage and networking SMBIOS extensions for RSD2.2 on S2600WF
HSD-ES: 1504589353, , [PC Stitching] Sync Microcode 0x2e for Xeon Scalable Family H0 from RP 
HSD-ES: 1504581907/1504580980/1504573931/1504563070, , CCB 1896: Provide SMBIOS table type 197 for RSD 2.2 Spec.
HSD-ES: 2103618468, , [S2600BP] Current Active Processor Cores do not show the corresponding number when Active Processor Cores changed with Quad core QMRN CPU
HSD-ES: 2103618733, , [S2600WF] SMBIOS Type 16 of maximum capacity value of 0x90000000, is not represented in the Extended Maximum Capacity field.
HSD-ES: 1504580965, , RsaReadyToBoot should run before AssertPostGpio in ReadToBootEvent
HSD-ES: 220680356, , X722 NVM v3.49 BIOS integration
HSD-ES: 2103618637, , [S2600BP] SKU SFP+/1G: UUT show "Nmi activated - system halted" during POST when PCIE riser 2 x8 slot 2 installed a NIC/RAID card
HSD-ES: 1504580069, , [PC Stitching] Sync Xeon Scalable Family B1 Production Patch 0x13b from RP 
HSD-ES: 1504580058, , [PC Stitching] Sync Microcode 0x2c for Xeon Scalable Family H0 from RP
HSD-ES: 1504580414, , XPT Prefetch BIOS knob remove from PCSD BIOS. (XPT on Xeon Scalable Family Server is no longer POR)
HSD-ES: 1504579991, , S2600WF IFT config dat support class 3
HSD-ES: 2006669546, , RAID module RMS3HC080 and Software RAID RSTe can't work together on a S2600WF system
HSD-ES: 2103618307, , System Boot Timeout function not working if enable Power On Password
HSD-ES: 2103614644, , [S2600WF] "HDD Rebuild in progress" events were occurred during DC cycling
HSD-ES: 1504559251, , [PC-Stitching]Update ME SPS version to MR 235
HSD-ES: 2103618046, , After injecting MBIST error at rank sparing mode, memory size shows wrong.
HSD-ES: 1504567201, , RP production code sync up
HSD-ES: 2103618268, , [S2600WF] When Add-in M6000 in riser 1 slot1, SUT cannot boot normally on S2600WPQ
HSD-ES: 1504567160, , [S2600WF]Hard code the variable value of  Processor MSR Lock Control
HSD-ES: 2103617172, , [S2600BP]UEFI Mode,Boot order value doesn't follow ITKs' with FDD device.
HSD-ES: 2103618243, , [S2600SP] An new item "Diagnostic Messages" which should be invisible in BIOS setup.
HSD-ES: 2103618185, , [S2600WF] The memory info will show 'Empty/NO DIMM' in SMBIOS Type 17 if populate 1R DIMM on CPU1 Channel A and B and build Rank Sparing mode.
HSD-ES: 1504551789, , [PC Stitching] Sync Xeon Scalable Family B1 Production Patch 0x13a from RP 
HSD-ES: 1504551442, , [PC Stitching] Sync Microcode 0x29 for Xeon Scalable Family H0 from RP
HSD-ES: 1504549582, , Integration BIOS ACM to 1.3.3
HSD-ES: 1504543699, , [PC Stitching] Sync Xeon Scalable Family B1 Production Patch 0x139 from RP
HSD-ES: 2103617864, ,[S2600WF] BIOS will not keep boot order after remove boot device.
HSD-ES: 220203024, , [S2600WF Retimer] VMD menus do not match system state  (for example 3 slot riser + 4P/8P switch + VROC key + VMD enabled does not enable VROC OpROM in some cases)
HSD-ES: 1504525281, , The uncore frequency cannot fix at the max frequency when UFS is disabled on S2600WF
HSD-ES: 1504539977, , #CCB 1974:  Remove BIOS WA which requested in SW CCB1958# and move to HW solution for S2600BP Full QAT
                      Enable all QAT EP in BIOS,  Enable PCIE x4 link from CPU to PCH.
HSD-ES: 1504536397, , Syscfg_V14.1.16: The boot order is different between press F9 and key command “syscfg /bldfs “ ” " to load default on Legacy mode.
HSD-ES: 1504396363, , BIOS should include production key when secure boot enabled.
HSD-ES: 1504411203, , CCB#1751[Purley BIOS]Need to port Customer work from S2600V3/V4 BIOS to Xeon Scalable Family BIOS for Customer on S2600SP

===============================================================================
							BMC  1.29
===============================================================================
    1504594253 - Fail to power control by IPMI command after front BIOS setup option Front Panel Lock is enabled
    2006642484 - udev initilization timeout during RHEL 7.3 installation after firmware upgrade
    2103617779 - [S2600ST]Failed to retrieve config/info data via KCS from BMC during AC/DC/Warmboot cycle test only under Linux OS
    1504560658 - vm0.log created after VMViewer1.23 executed
    1504574159 - [S2600ST]Something abnormal happened when VMviewer should be gracefully shutdown and disconnect from SUT
    2103618332 - [S2600WF] The status LED remain solid green after plug out the fan
    2103618333 - [S2600BT] The status LED remain solid green after plug out the fan
    2103618714 - [S2600WF] Auto-config error can't be triggered after disconnect the HSBP I2C cable.
    2103618717 - [S2600BT] Auto-config error can't be triggered after disconnect the HSBP I2C cable.
    1504553952 - [S2600BT]  In EWS IPv4 Network configuration show IPv6 address after setting IPv6 DNS address with syscfg
    1504561477 - [S2600BP] System didn't shutdown when pump power is unplugged
    1504565644 - Failed to login EWS with IPV6 address: fe80::11, but we can login it with other IPV6 address liking 2014::11 or 2016::11
    1504589411 - Q4'17 #CCB 1945 Force Node Manager Policy to ¡°Force aggressive mode¡± via EWS
    2103617773 - [S2600WF] Status LED will solid amber after insert PSU1 to trigger auto configuration(1300W)
    2103618167 - [S2600WF] ME update description in EWS event log is differ from SELViewer.
    2103618170 - [S2600BT] ME update description in EWS event log is differ from SELViewer.
    2103618270 - [S2600BT] The EWS sel log description is not match with Selview.
    2103618494 - [S2600WF] The description of PS1/2 status are incorrect in EWS SEL after remove PS1/2 power cable.
    2103618496 - [S2600BT] The description of PS1/2 status are incorrect in EWS SEL after remove PS1/2 power cable.
	220269450 - Refresh button in Virtual Storage does not refresh the existing connections of other users.
    1504560668 - VMViewer 1.23 will have error comparing glibc version on SLES11.4
    1504566375 - when updated the FRUSDR,  EWS-->Event log page always show LOADING...
    2103616311 - [S2600ST] After set NM Configuration in Embedded Web Server (EWS), NM policy cannot limit the current power reading.
    2103618378 - [S2600WF] The SEL of EWS cannot display events after update FRUSDR
    2103618459 - [S2600ST] The SEL log of "Event Log" page shows incorrect in Embedded Web Server (EWS) after SDR updated successfully with BMC 1.25.
    2103618379 - [S2600BT] The SEL of EWS cannot display events after update FRUSDR
	1209233977 - [S2600ST] The "PS1 Status" sensor sometime(70%) not rearm(refresh) from AC LOST status.
    1504552360 - Q3'17 #CCB 1965:  [Purley BMC]Support Redfish protocol and minimal set of schemas
    2103616629 - [S2600BP] System appear config missatch (USB device appear yellow mark) randomly during AC/DC/Reboot cycle test under Windows OS.
    2103618161 - [S2600WF]The response of "Run parse" and "Get parse status" Command are incorrect.
    2103618168 - [S2600ST] The description of some events showed English words in Event Log page at Simplified Chinese based Embedded Web Server (EWS).
    2103618291 - The S2600BP BMC 1.24.9dda0979: the update script in the "fwUpdateBMC.nsh" file does not define the BMC file name
    220269450 - Refresh button in Virtual Storage does not refresh the existing connections of other users.
    1504560668 - VMViewer 1.23 will have error comparing glibc version on SLES11.4
    1504521715 - [S2600BT]Run ¡°syscfg /r xx.ini /f¡± pop "Error: Invalid Query" after user change LAN setting on BIOS setup and boot to OS.
    2103618162 - [S2600BT]The response of "Run parse" and "Get parse status" Command are incorrect.
	220280665 - [VMViewer] Mounting device with VMViewer after KVM launch will not be seen in KVM Virtual media device section
    1209245248 - ¡°PS1 update failed - Failed to transfer image, retrying¡± error when PSU1 is inserted and PSU2 is already present and FW just updated.
    1504560008 - [S2600BP] No FAN Control Profile (lower bank) support during FSC record test on liquid cooling SKU
    2103617024 - [S2600ST] CPU missing event can not be triggered when remove CPU 1 from SUT.
    2103617593 - [S2600BP]The SEL timestamp start with 01/01/2016, not pri-init timestamp after Clear CMOS
    2103618176 - [WFP]Unable to open KVM under IPv6 Env.
    2103618291 - The S2600BP BMC 1.24.9dda0979: the update script in the "fwUpdateBMC.nsh" file does not define the BMC file name
	
=============================================================================
				FRUSDR 1.29
=============================================================================

 2103618303 - [STP] Installed single PSU info the SUT and flash LED will be green blinking after AC cycle.

================================================================================
			SYSTEM HARDWARE & SOFTWARE REQUIREMENTS/REVISIONS
================================================================================
- S2600STB, S2600STQ baseboards only.

  System BIOS  - 00.01.0004 or later
  ME Firmware  - 04.00.03.219.0 or later
  BMC Firmware - 1.04 or later
  FRUSDR       - 1.02 or later

- Front Panel, Hot-swap backplane, and Baseboard FRU data must be available
  for chassis auto-detection to succeed.

===============================================================================
                        KNOWN ISSUES/WORKAROUNDS/REQUIREMENTS
===============================================================================
WARNING: This release has the BMC PCIe bridge disabled. This will cause the 
    majority of operating systems to fail at boot as they stall during video 
    driver initialization
    
    Steps to recover a failing operating system:
    
	Linux variants (one of the below):
        A. Ensure the "modprobe.blacklist=ast" parameter is set in your boot loader (grub)
        B. Ensure you are using a kernel version v4.10 or newer
    For Red Hat* Enterprise Linux* v7.3, please refer to the included "RHEL73_InstallationGuide_Rev1.00.pdf"
	For SUSE* Linux* Enterprise Server v12 SP1 or SP2, please refer to the included "SLES12_InstallationGuide_Rev1.00.pdf"
	
    Windows variants:
        Boot to safe mode, and load aspeed video driver v1.03 or greater and reboot
	For Windows* Server 2016, please refer to the included "WinSrv16_InstallationGuide_Rev1.00.pdf" 

=============================================================================
				IMPORTANT NOTE
=============================================================================
After completing the FW upgrade to this release, the following messages may be displayed in the BMC event log:
	--Manufacturing error. Wrong manufacturing configuration detected by ME Firmware. The Flash device must be replaced (if error is persistent). - OEM - Asserted
	--Restore factory presets using 'Force ME Recovery' IPMI command or by doing AC power cycle with Recovery jumper asserted. If this does not clear the issue, reflash the SPI flash. If the issue persists, provide the content of Event Data 3 to Intel support team for interpretation. - OEM - Asserted
This is an known event when updating the Management Engine the first time and can be safely ignored. No further action is required from the customer.
	
=============================================================================
                            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) 2017 Intel Corporation.

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