Updating BIOS Firmware on Intel® Server Board S2600WF Family - kcox-ByteSpeed/Test_Intel_Documentation GitHub Wiki

Instructions for Updating BIOS Firmware on Intel® Server Board S2600WF Family

This tutorial provides step-by-step instructions to update the BIOS and firmware of the Intel® Server Board S2600WF Family using the UEFI System Update Package (SUP). The procedure described here applies to version R02.01.0017 and will generally work for later versions. Read documentation on [Intel's site][intel] to ensure you meet the prerequisites and follow the instructions carefully to avoid any issues during the update process.

Here is a video featuring the steps outlined below. Note: The video may not match actual version numbers and is meant to be a general outline. More specific details can be found below. Click the image to watch the video on YouTube:

Note: This update procedure will work for any Intel Server boards (version numbers will vary).


Prerequisites

  1. Hardware Requirements:

    • Intel® Server Board S2600WF Family
    • A USB flash drive (formatted to FAT32)
  2. Current System Software Stack:

    • System BIOS: R02.01.0016
    • ME Firmware: 04.01.04.804
    • BMC Firmware: 2.88.71773d70
    • FRUSDR: 2.04

Ensure that your current system software stack matches these versions before proceeding. Failure to meet these requirements may result in an unsuccessful update. Refer to Intel's site for recommended software versions for updates beyond R02.01.0017.

  1. Software Downloads:

Verify the integrity of the downloaded file using the SHA256 checksum provided on the site.

Important Notes:

  • Ensure you have the correct SSL certificate (2048-bit or longer) starting from BMC v2.88.
  • Review any warnings related to BMC firmware updates, especially those that may affect Active Directory, security settings, and SSL certificates.

Warnings

  • Do Not Interrupt: Interrupting the update process can render your system inoperable
  • Do Not Downgrade: Avoid downgrading the system software as it may also cause system failure

Step-by-Step Instructions

  1. Prepare the Update Package:
    • Unzip the contents of the downloaded update package.
    • Copy all files to the root directory of a USB flash drive formatted with the FAT32 file system.
    • Insert the USB flash drive into any available USB port on the back of the server

Download BIOS and Firmware Update Package

  1. Boot into UEFI Shell
    • Reboot the server and rapidly pressing F6 during POST to access the Boot Menu
    • Select UEFI Internal Shell

Alternatively, enter the Boot Menu through the BIOS by rapidly pressing F2 during POST. Then select Boot Manager.

  1. Execute the Update

    • The update process will typically start automatically by executing the Startup.nsh script located on your USB drive
    • If the Startup.nsh script does not start automatically: [Source][efi-shell]
      • Use the command map -b to list all of the drives connected to the system
      • Review the output list and locate the drive that matches the size and model of your USB disk
      • For servers running Windows, type fs0: at the prompt. For VMWare/ESXi servers, select the removable media device (e.g., blk1:)
      • Run ls to display the files in the mounted drive. You should see the contents of the USB drive, including the Startup.nsh script
      • Run the command Startup.nsh to manually start the update process
    • The update process will begin automatically.
    • Partway through, you will be prompted to select an option (1-5). Choose 3, then press N for the following questions
    • Do not interrupt or power off the system once the update process begins. The screen will remain off, and the ID LED will turn solid blue during the update
    • The system will reboot automatically after the update is complete, which may take approximately 20 minutes
    • Remove the USB after the update is complete
  2. Reset BIOS settings

    • Boot into the BIOS by rapidly pressing F2 during the boot sequence
    • Navigate to Main and press enter
      • Ensure Quiet Boot is set to Disabled
      • Press esc
    • Navigate to Advanced > Processor Configuration
      • Ensure Intel Virtualization Technology (Intel VT) is enabled
    • Check any other custom BIOS settings

    If running VMWare disable Memory Mapped I/O above 4GB under Advanced > PCI Configuration

    • Press F10 to save changes and exit after verifying the update (see step 5 below)

Following these instructions will help ensure a successful BIOS and firmware update on the Intel® Server Board S2066WF Family. Always refer to the included release notes for detailed information on any known issues and additional guidance.

  1. Post-Update Verification

    Version numbers for all components can be found on the [download page][intel] under Detailed Description

    • After the update and reboot, press F2 during POST to access the BIOS Setup Utility

    • Verify the BIOS revision matches the updated version at the top of the BIOS home screen

    • Navigate to SERVER MANAGEMENT > SYSTEM INFORMATION to verify the BMC, ME, SDR, and CPLD firmware revisions

    • Press F10 to save changes and exit

      Alternatively:

      • View version numbers through the Integrated BMC Web Console if you set up remote management through the BMC
      • Or boot into the EFI shell and run sysfwupdt.efi -i to verify the active firmware versions

Troubleshooting and Additional Resources

  • Security and Compatibility Issues: Refer to the PDFs on Intel's site (e.g., TA-1143) for more information on ipmitool and BMC security settings.
  • Firmware Downgrades: Downgrading BMC below version 1.43.660a4315 is not supported due to security changes.
  • Operating System Compatibility: Refer to the respective installation guides (e.g., RHEL73_InstallationGuide_Rev1.00.pdf) for operating systems that might encounter boot issues due - to the BMC PCIe bridge being disabled.

Sources

Revision History

Revision Date Comments Author
1.0 08/13/2024 Initial release Keegan Cox
1.1 08/19/2024 Added media Keegan Cox
1.2 08/26/2024 Reviewed Keegan Cox
⚠️ **GitHub.com Fallback** ⚠️