Skip to main content
Version: v25.1.5

Server BIOS and BMC Setup

Required BIOS and BMC settings for all servers in the AIsware cluster. Complete these before installing the operating system.

BMC configuration

Common to all servers — run through the BMC web interface.

Configuration › Account Services — create the following users:

User namePasswordNetwork privilegeAccount types
operatorunique per machineOperatorRedfish/IPMI
metricsobservability passwordUserRedfish/IPMI; SNMP (Auth: HMAC-MD5, Auth Key: observability password, Encryption: None)

Configuration › Notifications › SNMP:

SettingValue
Enable SNMPOn
SNMPv3On
AuthHMAC_MD5
EncryptionNone

Configuration › Network › Port:

SettingValue
SNMP PortOn

Configuration › BMC Settings:

SettingValue
Host InterfaceOff
note

Host Interface can only be set from the OS or EFI shell — setting it from the BIOS throws an error. Setting it to Off restricts OS-level IPMI access so that unprivileged OS users cannot add or change accounts or upgrade firmware (equivalent to KCS Control: Operator).

Machines that contain GPUs or network cards should set their fan mode accordingly to help cool these cards. Go to BMC setting — Configuration › Fan Mode:

SettingValue
Fan ModeHeavyIO Speed

BMC Fan Mode set to HeavyIO Speed

Secure Boot key enrollment

Optional

Only required when Secure Boot is required and when it is not in factory-default state, for example, after a firmware reset or key clear. Note that if the server is re-provisioned, some steps need to be done again.

  1. In BIOS, navigate to Security › Secure Boot, set CSM Support to Disabled, then open Key Management and perform the following sequence:
    • Factory Key Provision: Enabled → Install factory defaults: Yes → Reset without saving: No
    • Factory Key Provision: Disabled — select Disabled again to toggle it off after the factory restore
    • Reset To Setup Mode: Yes → Reset without saving: No
    • Esc, then Save Changes and Reset
  2. From an Arch Linux machine, install and copy sbctl to the target host:
    sudo pacman -S sbctl
    scp /usr/bin/sbctl root@<host>:/usr/local/bin/
  3. On the target host, confirm Setup Mode is active:
    sbctl status
    # Installed: ✓ sbctl is installed
    # Setup Mode: ✗ Enabled
    # Secure Boot: ✗ Disabled
    # Vendor Keys: none
  4. Enroll keys and reboot:
    sbctl create-keys # skip if keys already exist at /usr/share/secureboot
    sbctl enroll-keys -m
    reboot
  5. In BIOS: Security › Secure Boot › Enter Deployed Mode, set Secure Boot to Enabled, then Save and Reset.
  6. Verify enrollment:
    sbctl status
    # Installed: ✓ sbctl is installed
    # Setup Mode: ✓ Disabled
    # Secure Boot: ✓ Enabled
    # Vendor Keys: microsoft
    mokutil --pk | grep Issuer # must not show "DO NOT TRUST - AMI Test PK"
note

After enabling Secure Boot, the nVidia GRID host driver must be reinstalled (rebuilt). The build generates a Machine-Owned Key (MOK) that must be enrolled on the next reboot via the "Perform MOK management" menu. To re-enroll an existing MOK without rebuilding the driver:

mokutil --import /var/lib/shim-signed/mok/MOK.der
# On reboot: Enroll MOK → Continue → Yes → <MOK password> → Reboot
# Verify:
mokutil --list-enrolled | grep Issuer

BIOS settings

SuperMicro 5019

BIOS pathSettingValue
Advanced › Boot FeatureWait For "F1" If ErrorDisabled
Advanced › NB ConfigurationIOMMUEnabled
Advanced › PCIe/PCI/PnP ConfigurationSR-IOV SupportEnabled
Advanced › PCIe/PCI/PnP ConfigurationPCIe ROM typesEFI (all)
Advanced › PCIe/PCI/PnP ConfigurationNetwork StackEnabled
Advanced › PCIe/PCI/PnP Configuration › Network Stack ConfigurationIPv4 PXE SupportEnabled
Advanced › PCIe/PCI/PnP Configuration › Network Stack ConfigurationIPv6 PXE SupportDisabled
Advanced › PCIe/PCI/PnP Configuration › Network Stack ConfigurationHTTP Support (all options)Disabled
Security › Secure BootCSM SupportDisabled
BootBoot mode selectUEFI
tip

Save and reset after the PCIe/PCI/PnP changes before continuing to the Secure Boot and Boot settings — some firmware versions require a reboot for the Network Stack sub-menu to appear.

Boot priority: #1 UEFI Hard Disk, #2 UEFI Network, #3 UEFI Built-in EFI Shell, #4–#9 Disabled. Under UEFI Network Drive BBS Priorities, disable all entries except the first.

SuperMicro 1115 and 4125

BIOS pathSettingValue
Advanced › Boot FeatureWait For "F1" If ErrorDisabled
Advanced › NB ConfigurationIOMMUEnabled
Advanced › NB ConfigurationPower Profile SelectionEfficiency Mode
Advanced › PCIe/PCI/PnP ConfigurationAbove 4G DecodingEnabled
Advanced › PCIe/PCI/PnP ConfigurationRe-Size BAR SupportEnabled (required if GPUs are installed)
Advanced › PCIe/PCI/PnP ConfigurationSR-IOV SupportEnabled
Advanced › Network ConfigurationIPv6 PXE SupportDisabled
Advanced › Network Configuration › 1st NIC › IPv4 Network ConfigurationConfiguredEnabled
Advanced › Network Configuration › 1st NIC › IPv4 Network ConfigurationEnable DHCPEnabled
Security › Secure BootCSM SupportDisabled

Boot priority and UEFI Network Drive BBS Priorities: same as 5019 above.

SuperMicro AS-1115CS, ASG-2115S, and AS-8126GS-NB3RT

GPU hypervisor servers.

BIOS pathSettingValue
Advanced › Boot FeatureWait For "F1" If ErrorDisabled
Advanced › CPU ConfigurationWorkload ProfileVirtualization (Hypervisors) (AS-1115CS and AS-8126GS-NB3RT only)
Advanced › NB ConfigurationIOMMUEnabled
Advanced › NB ConfigurationDMAr SupportEnabled
Advanced › NB ConfigurationPower Profile SelectionAuto (High-performance mode)
Advanced › PCIe/PCI/PnP ConfigurationAbove 4G DecodingEnabled
Advanced › PCIe/PCI/PnP ConfigurationRe-Size BAR SupportEnabled (required if GPUs installed)
Advanced › PCIe/PCI/PnP ConfigurationSR-IOV SupportEnabled
Advanced › Network ConfigurationIPv6 PXE SupportDisabled

AS-8126GS-NB3RT machines have BlueField-3 NICs. For each NIC port, under Advanced › Nvidia Network Adapter:

PathSettingValue
NIC ConfigurationLegacy Boot ProtocolNone
Device Level ConfigurationVirtualization ModeNone
Device Level ConfigurationPXE Boot FiltersEnabled
BlueField Internal CPU ConfigurationInternal CPU Offload EngineDisabled (1st port only)
(top level)Network Link TypeEthernet
note

Virtualization Mode: None enables SR-IOV with 8 virtual functions per port. Internal CPU Offload Engine must be Disabled on the 1st port only.

For GPU servers — create the OS boot RAID array before first boot via Advanced › BROADCOM SAS 3808N Configuration Utility › Configure › Create Virtual Drive:

  • RAID Level: RAID1
  • Media Type: SSD, Interface Type: NVMe
  • Select drives C0:01:00 and C1:01:01 → Apply Changes
  • Save Configuration: Confirm Enabled → Yes → OK

Boot priority and UEFI Network Drive BBS Priorities: same as 5019 above.

MS-01 (Intel AMT)

The MS-01 uses Intel Active Management Technology (AMT) for out-of-band management instead of a dedicated BMC.

BIOS update

If the installed BIOS version is below v1.27, update it first:

  1. Format a USB stick with a single EFI FAT32 partition.
  2. Place the UEFI shell binary on the partition.
  3. Download and unpack the MS-01 BIOS v1.27 package onto the same partition.
  4. In BIOS setup, disable Security › Secure Boot.
  5. Reboot into the EFI shell (force it from the BIOS boot menu if it does not boot automatically).
  6. Run AfuEfiFlash.nsh.

AMT setup

  1. Enter the BIOS setup screen and open MEBx (Intel Management Engine BIOS Extension).
  2. Set the AMT password — default credentials are admin/admin. Store the new password securely.
  3. Open AMT Network Setup and assign a static IP. Record the address in the static IP inventory for BMC devices.

BIOS settings

BIOS pathSettingValue
Advanced › Onboard DevicesAperture Size128 MB
Advanced › Onboard DevicesHD AudioDisabled
Advanced › Onboard DevicesDeep S5Disabled
Advanced › Onboard DevicesSR-IOVEnabled
Advanced › Onboard DevicesAbove 4G DecodingEnabled
Advanced › Onboard DevicesRe-Size BAR SupportEnabled
Advanced › Onboard DevicesDMA Control GuaranteeEnabled
Advanced › Onboard DevicesSA GVDisabled
Advanced › ACPI SettingsRestore On AC Power LossAlways On
Advanced › ACPI SettingsWake Up On LANEnabled
Advanced › HM Monitor & Smart FanCPU Fan Smart ModeFull Mode
Advanced › HM Monitor & Smart FanM.2 Fan 1 Smart ModeFull Mode
Advanced › HM Monitor & Smart FanM.2 Fan 2 Smart ModeFull Mode
Advanced › Network Stack ConfigurationNetwork StackDisabled
Advanced › Network Stack ConfigurationIPv4 PXE SupportDisabled
Advanced › Network Stack ConfigurationIPv6 PXE SupportDisabled
SecuritySecure BootDisabled (BIOS update and OS install); Enabled (post-install)

AMT activation

After completing the BIOS settings:

  1. In the AMT BIOS menu, set Network Access State to Network Active.
  2. In the AMT BIOS menu, open the User Consent menu and set:
    • User Opt-in: None
    • Opt-in Configurable from Remote IT: Enabled

Connecting via AMT

Use MeshCommander (bundled in the meshcmd tool) to connect to an AMT device:

wget "https://alt.meshcentral.com/meshagents?meshcmd=6" -O meshcmd
chmod +x meshcmd
./meshcmd MeshCommander

Open http://localhost:3000, then:

  1. Add Computer
  2. Fill in:
    • Friendly Name: name matching the inventory
    • Hostname: <inventory-name>.<environment-tld> — the DHCP/DNS entry configured in the routers
    • Auth / Security: Digest / TLS
  3. OK, then Connect