Intel S2600WFQ Server Board OFU Firmware 00.01.0009

Versions:

- BIOS : 00.01.0009
- ME : 04.00.04.288
- BMC : 1.29
- FRUSDR : 1.29

BIOS 00.01.0009:

- Rename BIOS ID from X0084 to R0009.
- [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.
- [S2600BP] Set "NIC1 Port1/2" to Disabled cannot be saved under legacy mode with S2600BP NIC X550.
- [PC Stitching] Sync Microcode 0x30 for Xeon Scalable Family H0 from RP.
- [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.
- [PC Stitching] Sync Microcode 0x32 for Xeon Scalable Family H0 from RP.
- Update BIOS security version to 0004.
- [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
- 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
- Fix issue- Array OCPDID Index Out of Bounds.
- CCB 2030: Enable/disable individual embedded only NIC ports
- CCB 2022: Support storage and networking SMBIOS extensions for RSD2.2 on S2600WF
- [PC Stitching] Sync Microcode 0x2e for Xeon Scalable Family H0 from RP
- CCB 1896: Provide SMBIOS table type 197 for RSD 2.2 Spec.
- [S2600BP] Current Active Processor Cores do not show the corresponding number when Active Processor Cores changed with Quad core QMRN CPU
- [S2600WF] SMBIOS Type 16 of maximum capacity value of 0x90000000, is not represented in the Extended Maximum Capacity field.
- RsaReadyToBoot should run before AssertPostGpio in ReadToBootEvent
- X722 NVM v3.49 BIOS integration
- [S2600BP] SKU SFP+/1G: UUT show "Nmi activated - system halted" during POST when PCIE riser 2 x8 slot 2 installed a NIC/RAID card
- [PC Stitching] Sync Xeon Scalable Family B1 Production Patch 0x13b from RP
- [PC Stitching] Sync Microcode 0x2c for Xeon Scalable Family H0 from RP
- XPT Prefetch BIOS knob remove from PCSD BIOS. (XPT on Xeon Scalable Family Server is no longer POR)
- S2600WF IFT config dat support class 3
- RAID module RMS3HC080 and Software RAID RSTe can't work together on a S2600WF system
- System Boot Timeout function not working if enable Power On Password
- [S2600WF] "HDD Rebuild in progress" events were occurred during DC cycling
- [PC-Stitching]Update ME SPS version to MR 235
- After injecting MBIST error at rank sparing mode, memory size shows wrong.
- RP production code sync up
- [S2600WF] When Add-in M6000 in riser 1 slot1, SUT cannot boot normally on S2600WPQ
- [S2600WF]Hard code the variable value of Processor MSR Lock Control
- [S2600BP]UEFI Mode,Boot order value doesn't follow ITKs' with FDD device.
- [S2600SP] An new item "Diagnostic Messages" which should be invisible in BIOS setup.
- [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.
- [PC Stitching] Sync Xeon Scalable Family B1 Production Patch 0x13a from RP
- [PC Stitching] Sync Microcode 0x29 for Xeon Scalable Family H0 from RP
- Integration BIOS ACM to 1.3.3
- [PC Stitching] Sync Xeon Scalable Family B1 Production Patch 0x139 from RP
- [S2600WF] BIOS will not keep boot order after remove boot device.
- [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)
- The uncore frequency cannot fix at the max frequency when UFS is disabled on S2600WF
- 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.
- Syscfg_V14.1.16: The boot order is different between press F9 and key command “syscfg /bldfs “ ” " to load default on Legacy mode.
- BIOS should include production key when secure boot enabled.
- [Purley BIOS]Need to port Customer work from S2600V3/V4 BIOS to Xeon Scalable Family BIOS for Customer on S2600SP

BMC 1.29:

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

FRUSDR 1.29:

- Updates Storage FP Temp to 78C to match previous generation.

GENERAL INSTALLATION PROCEDURE

1. Unzip the contents of the update package and copy all files to the root directory of a removable media (USB flash drive)
2. Insert the USB flash drive to any available USB port on the system to be updated
3. Power on the server and load the uEFI shell
4. Begin the update process running the Startup.nsh
5. Reboot the system after the update process has successfully completed

Web GUI update

1. Unzip the package onto your system
2. Log into the BMC web GUI
3. Navigate to Configuration, then Firmware Update
4. Click browse, and direct the browser to the location of the .bin file
5. Click upload. Progress and status will be shown as the update progresses

UEFI update

1. Unzip package and load onto a flash drive
2. Boot to UEFI shell, and navigate to the folder where this package lives
3. Run fwUpdateBMC.nsh and follow the prompts

Verifying Updates:

01. After the final update has completed successfully, reboot the system
02. During POST, hit the <F2> Key when prompted to access the BIOS Setup Utility
03. From the BIOS Setup Utility main menu, hit the <F9> key to load BIOS defaults
04. Hit the <F10> key to Save Changes and Exit the BIOS defaults
04. At the main menu verify the BIOS revision is correct
05. Move cursor to the SERVER MANAGEMENT menu and hit Enter
06. Move cursor to the SYSTEM INFORMATION Option and hit Enter
07. Verify the BMC Firmware revision is correct
08. Verify the SDR revision is correct
09. Verify the ME Firmware revision is correct
10. Configure desired BIOS Option settings
11. Hit the F10 Key to Save Changes and Exit  

About Firmware Updates:

Applying a newer firmware version than the one already installed on your unit can bring various enhancements, include workarounds for diverse problems encountered by the device, and improve or add newly developed features.

On the other hand, downgrading the firmware version can recover the device's functionality in the event of a software update either turning up faulty or causing the unit's overall performance to drop. However, bear in mind that applying an older firmware isn't recommended and might not always be possible.

When it comes to the update steps, due to the large variety of devices and numerous ways for installing a new firmware, it is recommended that you carefully read and understand the upgrade steps, and consider applying a different firmware only when you have familiarized yourself with the update method.

As the installation process is most of the times quite risky, this step should be taken by users that have the ability to successfully complete the update; regular users may initiate it at their own risk. Moreover, it's best that this task be performed in a steady power environment such as the one ensured by a UPS unit.

Therefore, if you consider applying this release, hit the download button, take into account all the aforementioned aspects, and update the device's firmware. Also make sure you constantly check with our website to ensure that you don't miss a single new release.