uEFI System Update Package (SUP) Installation and Operation Instructions Intel highly recommends reading this document in its entirety before performing the system update. Verifying that your system meets the documented requirments will ensure a successful update and provide the most reliable system functionalityafter the update has completed. Released - April 05, 2022 ******************************************************************************** This update package includes the following production level system firmware updates: System BIOS - R02010015 ME Firmware - 04.01.04.601.0 BMC Firmware - 2.88.6999d21a FRUSDR - 1.48 Intel® Optane™ DC Persistent Memory Firmware (PMEM) - 01.02.00.5446 --- Firmware Update Tools --- iFlash32_V14_1_Build15 FWPIAUPD_v14_1_Build19 FRUSDR_V14_1_Build18 --- Supported Products --- Intel(R) Server Board S2600BP Family ************************************************************************************* IMPORTANT NOTES ************************************************************************************* WARNING: Starting from BMC v2.86, BMC does not allow upload .key files and only accepts .pem file for SSL certificate. If uploaded SSL Certificate or Key files fail to format checking, BMC will remove the invalid format file before starting BMC EWS and re-generate a self-signed certificate to ensure the BMC EWS can boot up successfully. Please consult TA-1176 for more details WARNING: Starting from BMC v2.88, Purley platfomrs only support SSL certificate which is equal to or longer than 2048 bit. WARNING: A security issue was fixed in Purley platforms. BMC credential is required to access files in internal virtual media from BMC v2.88. Issue:[Internal Virtual Media] Files in internal virtual media are accessible without BMC credential WARNING: Starting from BMC v2.88, EWS Active Directory should allow domain name and user name longer than 16 characters. The AD Setting will be cleared after downgrade to v2.86 or lower BMC versions if the Domain Name is equal to or longer than 32 characters. *** Please Check your IPMI through LAN commands *** Starting from BMC 2.22.59c3b83a, when KCS Policy Control Mode is configured as "Deny ALL" on BMC EWS, BMC and FRUSDR cannot be upgraded/downgraded as expected behavior. Updates can still be performed via Redfish or BMC EWS Extra parameter for ipmitool through LAN is required since BMC firmware 1.90 as the Cipher Suite 3 is disabled by default since BMC firmware 1.90 and only keep Cipher Suite 17 opened by default. Due to this the extra parameter "-C 17" is required for ipmitool to work via LAN. The Cipher Suite 17 was first introduced in ipmitool 1.8.18 on Oct 8th 2016, you have to update ipmitool to this version or newer one, earlier versions of ipmitool don’t have Cipher 17 support ipmitool is not working well when running in high load network. We recommend to add extra timeout by using “-N 5”. Default is 1 second for RMCP+, which is not enough. –N 5 will set 5 second as timeout. So the command will look like: ipmitool –I lanplus –H ip –U user –P password –C 17 –N 5 command Please refer to the included "TA-1143_Extra_parameters_needed_for_ipmitool.pdf" for more information. Downgrading BMC below 1.43.660a4315 is not supported due to a security revision change. 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" *** Advisory Note *** Do not modify any of the script files. The scripts as written will provide the most reliable update experience To run these updates, you must boot the system to the embedded uEFI shell If for any reason the System BIOS, BMC Firmware, or FRUSDR data need to be re-installed after the initial update has been performed, the package does include standalone script files that can be run individually. These files are: UpdBIOS.nsh, UpdMe.nsh, UpdFD.nsh, fwUpdateBMC.nsh, and UpdS2600BP.nsh We recommend to use these files after the system has been updated initially using the Startup.nsh file When booting the system for the first time after a firmware update is complete, it may automatically reboot several times, this is an expected behavior ************************************************************************************* SYSTEM HARDWARE and FIRMWARE REQUIREMENTS ************************************************************************************* To update the system firmware stack to the versions included in this update package, the currently loaded system firmware stack on the system must meet the following: System BIOS - R02010014 or later ME Firmware - 04.01.04.505 or later BMC Firmware - 2.86.2da97d3f or later FRUSDR - 1.47 or later If the system doesn't currently meet the above system firmware requirements, you must download a previously-posted System Update Package (SUP) and update the system to the preceding described firmware revisions before updating the system to the firmware stack included in this package. ******************************************************************************** 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. Access to the USB flash drive insterted and begin the update process running the Startup.nsh 5. Systen will reboot automatically after the update process has successfully completed 6. If PMEM installed, run Startup.nsh a second time after the first reboot to upgrade PMEM Firmware and power cycle the system to allow PMEM load the new FW. ******************************************************************************** Whenever the system BIOS is updated, two BIOS images are installed, a primary image and a backup image. The backup image is loaded during the 1st system reboot after the primary BIOS image is updated. During the 1st system reboot, the screen will be black for approximately 2 minutes while the backup BIOS image is being loaded. DO NOT power off or reboot the system during this time. A message will appear on the screen when the backup BIOS image update has completed. Verifying Updates: 01. After the final update has completed successfully, reboot the system 02. During POST, hit the Key when prompted to access the BIOS Setup Utility 03. From the BIOS Setup Utility main menu, hit the key to load BIOS defaults 04. Hit the 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 The System Software Update is Complete. *** Warning: *** !! Do NOT interrupt or reboot or remove power from your system during the update process !! !! Doing so may render your system inoperable !! !! Do NOT attempt to downgrade the system software once loaded on the system !! If after performing an FW downgrade using the recovery jumper the system doesn't boot, perform a reset of the BIOS settings by moving the BIOS default jumper position momentarily to the clear BIOS settings. Details regarding the jumper ID and location can be obtained from the Board TPS. Please refer to the respective "Release Notes" files for complete list of known issues, workarounds and detailed requirements: - BIOS: ReleaseNotes_BIOS####.txt - BMC: ReleaseNotes_BMC####.txt - FRUSDR: ReleaseNotes_FRUSDR####.txt