================================================================================
Intel(R) Server Board S2600WF, Intel(R) Server System R1000WF Product Family and
Intel(R) Server System R2000WF Product Family Firmware Update Package
for Intel(R) One Boot Flash Update Utility and Windows* Preboot Execution Environment 
================================================================================
Intel(R) Server Boards and Systems
Intel Corporation
2111 N.E. 25th Avenue, Hillsboro, OR 97124 USA
================================================================================
DATE    : 	Nov 21, 2018
TO      : 	Intel(R) Server Board S2600WF Product Family 
			Intel(R) Server System R1000WF Product Family 
			Intel(R) Server System R2000WF Product Family               
SUBJECT : Release Notes for System Firmware Update Package 
================================================================================
                              ABOUT THIS RELEASE
================================================================================
BIOS   : 00.01.0015
ME     : 04.00.04.340
BMC    : 1.74.ee39402a
FRUSDR : 1.74
================================================================================
                           Support Platforms and Dependency
================================================================================
Processors supported: 
Intel(R) Xeon(R) Scalable processors

Microcode versions:
        CPUID           Version       Status
        0x50653        0x01000144     (Xeon Scalable B1)
        0x50654        0x0200004D     (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 19 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. 
9. Security revision upgrade to 0005 since BIOS R010, it will prevent BIOS downgrade via normal mode to previous version that with lower security revision, user can use BIOS recovery mode for BIOS downgrade.
10. Downgrading below 1.43.660a4315 is not supported due to a security revision change.
11. Security revision upgrade to 0006 on BIOS R0014, it will prevent BIOS downgrade via normal mode to previous version that with lower security revision, user can use BIOS recovery mode for BIOS downgrade.
================================================================================
                  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 19 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 R00.01.0015(This release)
================================================================================
Rename BIOS ID from X0168 to R0015
HSD-ES:1504683593, Clone from HSD - Security VT - PCH UEFI FW shall delay PCI Bus Master Enable (PCICMD.BME) until end of POST to prevent DMA attacks on UEFI FW in RAM.
HSD-ES:1506731732, [S2600BP] SEL error during AC cycling: IPMI Watchdog reports the watchdog initiated a hard reset.
HSD-ES:2103623411, There is no SEL log generate when flash BIOS and ME version which same as SUT version.
HSD-ES:1506125764, Q3'18 #CCB2446 BIOS:  Purley Post -SRA feature: OOB Update and Config.
HSD-ES:1504788000, [PC Production] Sync Skylake Production code to PC Production.(5387193:Need Updated BIOS for External Use to Resolve P2P Issue)
HSD-ES:1506754163, FW-UEFI-Vuln-2018-031 - Dynamic loops accessing one element beyond boundary due to <= operator.
FIV_00008379[PC Stitching]Update ESRTIISataEFi version to 05140000.
5387405:PSIRT-FW-UEFI-Vuln-2018-040 SvSmmHandler SMI call-out. 
HSD-ES:1506132901, [S2600BP]MTT CPU1/MTT CPU2 sensors show no reading when run AC cycles and can't recovery within 300s[Only path for this issue,not a final solution].
HSD-ES:1506132509, [S2600BP]SUT hang post screen when run DC cycles.
HSD-ES:1506119814, [S2600BP]HSTI is absent on Windows Server 2016.
HSD-ES:2103623155, SUT will hang up on 0x9D after installed NIC card-X550 and enable RSD.
HSD-ES:2103623142, Update BIOS X0155 SEL LOG BIOS ID is wrong,it show 20.01.0155.
HSD-ES:2007015469, DIMM LED(chX) turns off after another correctable error is injected to a DIMM in different Channel(chY)-V01.
HSD-ES:2204466754, RSD 2.2-SMBIOS Type 199 had zeros value for port 3 and 4 for PCIe Cable ERROR Data.
HSD-ES:2205038517, Random Machine Check failure QPI Phy init abort during reboot reported on S2600ST.	
HSD-ES:2007360181, After CE injection,fault DIMM LED remains asserted despite follow up reset shows healthy memory subsystem-V02.			
HSD-ES:1506438632, Q3'18 CCB2437 [Purley BIOS]SOL function terminal type need to support more terminal types the same as console redirection types
HSD-ES:1506131214, Q3'18 #CCB2343[Purley] Add BIOS options in ITK to change USB 2.0 ports equalization parameters
HSD-ES:1506435385, Add Factory BIOS flag and .Factory string to SMBIOS Type 0
HSD-ES:1506129880, Q3'18 #CCB2443 [Purley BIOS]UPI latency performance parameters which impact bandwidth and latency to be exposed in setup/ITK/syscfg
HSD-ES:2202762181, [S2600BP] Warning SEL during AC Cycling: BMC FW Health reports SSB Temp has failed and may not be providing a valid reading
OSS_0008351/OSS_0008352:Integration BIOS ACM to 1.3.7 and SINIT to 1.3.4
HSD-ES:2103622995, [S2600ST]VMD enable in BIOS is mismatch with motherboard NVME SSD
HSD-ES:1506129887, Q3'18 #CCB2415 [Purley BIOS]Extend option value range for Memory Correctable  Error Threshold
HSD-ES:1506395072, ME update failed for X0148 online update to 0D.01.0008

===============================================================================
		BMC v1.74.ee39402a - (This release)
===============================================================================
    1506764699 - OEM Get reading command isn't workable
    2205369358 - [S2600BP] Exit Air Temp SEL events seen during OS Install and AC Cycling
    1209275701 - PCIe register access from host can be remapped to any base address into BMC address space.
    2202523214 - SPS FW Command Filtering
    2205369288 - [S2600BP] OpenIPMI driver fails to detect BMC on startup
    1506759784 - [redfish]UpdateMe Error with biospack 0D010125
    2205425827 - Baseboard FRU information missing with Redfish Schema
    1506749803 - [iKVM over HTML5]Up and Down key can control HTML5 iKVM session menu and BIOS setup menu in the same time
    2103623408 - [S2600WF] The threshold info will disappear after change sensor owner.
    2205369358 - [S2600BP] Exit Air Temp SEL events seen during OS Install and AC Cycling
    1506755754 - [OOB BIOS Configuration]the actual value is different with the value you click to change after do change value steps
    1506745023 - [iKVM over HTML5]Virtual media will be terminated when refresh the session of Virtual Media over HTML5 by press "F5"
    2205467333 - [S2600WF]Control BMC Services command sometimes cannot disable BMC Services
    2103623431 - [S2600WF] The button of Launch KVM over HTML5 not gray out when use operator user.
    2103623444 - [S2600WF] PSU redundancy lost event not showing after remove power supply cable
    2103623437 - [S2600BT] PSU redundancy lost event Not showed after remove power supply cable
    1506731715 - [OOB BIOS Configuration]Some variable show in EWS BIOS configuration but can’t map it in BIOS setup menu.
    2204837267 - Redfish ComputerSystem node has invalid field
    1506745202 - [iKVM over HTML5]When changed the language from English to Chinese, there always some English characters in the session
    1209275701 - PCIe register access from host can be remapped to any base address into BMC address space.
    2202523214 - SPS FW Command Filtering
    2205369288 - [S2600BP][Q2] OpenIPMI driver fails to detect BMC on startup
    2205425827 - Baseboard FRU information missing with Redfish Schema
    2103623352 - S2600BP: Use BMC_1.71 or 1.72 and S2600BPS mainboard, after updating the FruSdr_1.37, some sensors in EWS shows "unavailable" or incorrect reading
    1506132921 - [S2600BP LCR]NVME 1 Therm Mgn sensor  show no reading when run AC/DC cycles and can't recovery within 300s
    1506745145 - [iKVM over HTML5]It will show "SecurityResult Failed(Retry after 30 sec or iKVM reset)" if we launch the 5th ikvm session
    2007464975 - [S2600ST] IPMI command to get fan speed not working on CPU fans
    2205369288 - [S2600BP][Q2] OpenIPMI driver fails to detect BMC on startup
    2103623344 - [S2600BT] EWS help page show 404 about Virtual Media over HTML5
    2205425827 - Baseboard FRU information missing with Redfish Schema
    1506731715 - [OOB BIOS Configuration]Some variable show in EWS BIOS configuration but can’t map it in BIOS setup menu.
    1506659800 - [HTML5 KVM] No error or warning message displayed when 5th HTML5 KVM is opened, but the session is blank.
    1506109146 - CCB1964(PSME 2.2 support in BMC 1.57) doesn't align with PSME restful API specification
    1506129772 - Q3'18 #CCB2447 [Purley BMC]HTML5 support
    1506659800 - [HTML5 KVM] No error or warning message displayed when 5th HTML5 KVM is opened, but the session is blank.
    1506706272 - [S2600BT]Access still be denied after unmounted USB disk from rKVM
    1506733454 - [S2600WF]Seneor report PWR Unit Redundancy lost with FCT SDR
    1506733968 - [redfish]URL spelling error ,bios settings
    1506745202 - [iKVM over HTML5]When changed the language from English to Chinese, there always some English characters in the session
    1606376899 - [HTML5 KVM] 'Options' and 'User List' menu are always greyed out in the HTML5 KVM
    1606376909 - [HTML5 KVM] 'Defined Macros' option disabled in Keyboard Macro menu, hence the user added keyboard macros in EWS->Configuration page also not getting reflected.
    1606376917 - [HTML5 Virtual Media] Java Virtual media supports 4 devices whereas HTML5 Virtual media supports only 3
    1606652628 - FRUSDR update via EWS fails with BMC 1.71
    2103623223 - [S2600BT] No "start" and "completed" in FW update event description
    2103623248 - The warning messages of "restore system defaults" doesn't match test case.
    2103623309 - [S2600BT] SDR parse failed after press "Parse" button in EWS SDR configuration page.
    2103623322 - On-Line Update the firmware (such as BMC or ME), the event log does not show the "update process" clearly
    2103623344 - [S2600BT] EWS help page show 404 about Virtual Media over HTML5
    2205425824 - Unable to enable SSH using Redfish Schema
    2204837759 - Redfish DMTF schema does not have a Bios/Settings XML field
    1504742896 - Q3'18 #CCB2202[BMC]Need log to track user/IP logins to BMC
    2202470727 - [S2600WF] PSOC on rear HSBP becoming corrupted
    2103623271 - Use Windows Client PC, mount a USB Flash then un-mount it later, the USB Flash could not be accessed on the Client PC

================================================================================
				FRUSDR 1.74
================================================================================    

- HSD 1506731770 - SDR record failure

================================================================================
			SYSTEM HARDWARE & SOFTWARE REQUIREMENTS/REVISIONS
================================================================================
- S2600WFT, S2600WF0, S2600WFQ baseboards only.

  System BIOS  - 00.01.0014 or later
  ME Firmware  - 04.00.04.340 or later
  BMC Firmware - 1.60.56383bef
  FRUSDR       - 1.60 or later

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


===============================================================================
                        KNOWN ISSUES/WORKAROUNDS/REQUIREMENTS
===============================================================================
HSD-ES 2103620418: After downgrade FD and ME, SUT will halt with beep code 1-5-1-2 when reboot. 
       Please use the following WA when online downgrading SW stacks from R010 SUP to previous SUP version: 
       Online downgrade process: flash BIOS -> flash FD -> reset SUT -> flash ME -> flash BMC -> flash FRUSDR -> AC cycle SUT -> SUT can boot up normally.

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

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