SAA Service

User's Guide

Revision 2.0.1

SAA_SERVICE User's Guide Page 1

Table of contents:
Version History
1. Overview
1.1 Features​
1.2 Operation Requirements​
1.2.1 Requirements for OOB Usage​
[Link] Network​
[Link] Remote Management Server​
[Link] Managed Systems​
1.2.2 Requirements for In-Band Usage​
[Link] Additional Requirements​
1.2.3 Requirements for SAA Service GUI​
1.3 Typographical Convertions​
1.4 Introduction to Interfaces​
1.4.1 In-Band Interface​
1.4.2 Out-of-Band Interface​
1.4.3 Remote In-Band Interface​
1.4.4 Remote Redfish Host Interface​
2. Installation and Setup
2.1 Installing SAA_SERVICE on Linux and Windows​
3. Updating Firmware
3.1 Preparations for Update​
3.2 Pre-processing: Repository Information​
3.3 Pre-processing: Resource File Setting​
3.3.1 saasvc RC file​
3.3.2 rack config JSON file​
3.4 Pre-processing: UserManagement​
3.5 Pre-processing: Repository Synchronization​
3.6 Pre-processing: System List File Setting​
3.7 Command Parameters​
3.8 Verifying System or Repository Information​
3.8.1 Getting System Information​
3.8.2 Getting Bundle Information​
3.9 Updating Firmware through In-Band Method​

SAA_SERVICE User's Guide Page 2

 3.9.1 Updating Firmware Bundle​
3.9.2 Updating Individual Firmware​
[Link] Updating Single Firmware via Individual Firmware Update​
[Link] Updating Multiple Firmware via Individual Firmware Update​
3.10 Updating Firmware through Out-of-Band Method​
3.10.1 Updating Firmware Bundle​
3.10.2 Updating Individual Firmware​
3.11 Updating Firmware through Remote In-Band/RHI Method​
3.12 Updating Firmware on Multiple Systems​
4. Secure Erase
4.1 Command Parameters​
4.2 Listing Disk Information​
4.3 Erasing a Single Disk in a Single System​
4.4 Erasing a Single Disk in Multiple Systems​
4.5 Erasing Multiple Disks in a Single System​
4.6 Erasing Multiple Disks in Multiple Systems​
5. SAA Service GUI
5.1 Installation and Setup​
5.2 Creating a New Resource File​
5.3 Configuring an Existing Resource File​
5.4 Running the BundleSync Command with the SAA Service GUI​
5.4.1 Action Selection​
5.4.2 Option​
5.4.3 Preview​
5.4.4 Result​
5.5 Running the RemoteUpdate Command​
5.5.1 Interface Selection​
5.5.2 Login Information​
5.5.3 Option​
[Link] OOB, (Multi)OOB, No specific interface, and (Multi) No specific
interface​
[Link] Bundle Update of Remote-INB, Remote-RHI, (Multi)Remote-INB, and
(Multi)Remote-RHI​
[Link] Individual Update of Remote-INB, Remote-RHI, (Multi) Remote-INB,
and (Multi) Remote-RHI​

SAA_SERVICE User's Guide Page 3

 5.5.4 Firmware​
5.5.5 Preview​
5.5.6 Result​
5.6 Running the LocalUpdate Command to Initialize Update​
5.6.1 Action Selection​
5.6.2 Login Information​
5.6.3 Option​
5.6.4 Firmware​
5.6.5 Preview​
5.6.6 Result​
5.7 Running the LocalUpdate Command to Continue an Update​
5.7.1 Action Selection​
5.7.2 Result​
5.8 Running the SecureErase Command to List Disks​
5.8.1 Action Selection​
5.8.2 System Information​
5.8.3 Preview​
5.8.4 Result​
5.9 Running the SecureErase Command to Erase Disk​
5.9.1 Action Selection​
5.9.2 System Information​
5.9.3 Preview​
5.9.4 Result​
5.10 SAA Service Backend Access and User Management​
5.10.1 Login​
5.10.2 Change Password​
5.10.3 User Management​
5.10.4 Logout​
6. FAQ
6.1 Errors and Exceptions​
6.2 SAA Service GUI Exception​
Appendix A. SAA_SERVICE Exit Codes
Appendix B. Update Support Matrix
Appendix C. Rack-Level Compute Tray License Matrix
Contacting Supermicro

SAA_SERVICE User's Guide Page 4

The information in this USER’S GUIDE has been carefully reviewed and is believed to
be accurate. The vendor assumes no responsibility for any inaccuracies that may be
contained in this document, makes no commitment to update or to keep current the
information in this manual, or to notify any person organization of the updates. Please
Note: For the most up-to-date version of this manual, please see our web site at
[Link]

Super Micro Computer, Inc. (“Supermicro”) reserves the right to make changes to the
product described in this manual at any time and without notice. This product, including
software, if any, and documentation may not, in whole or in part, be copied,
photocopied, reproduced, translated or reduced to any medium or machine without
prior written consent.

DISCLAIMER OF WARRANTY ON SOFTWARE AND MATERIALS. You expressly

acknowledge and agree that use of the Software and Materials is at your sole risk.
FURTHERMORE, SUPER MICRO COMPUTER INC. DOES NOT WARRANT OR
MAKE ANY REPRESENTATIONS REGARDING THE USE OR THE RESULTS OF THE
USE OF THE SOFTWARE OR MATERIALS IN TERMS OF THEIR CORRECTNESS,
ACCURACY, RELIABILITY, OR OTHERWISE. NO ORAL OR WRITTEN
INFORMATION OR ADVICE GIVEN BY SUPER MICRO COMPUTER INC. OR SUPER
MICRO COMPUTER INC. AUTHORIZED REPRESENTATIVE SHALL CREATE A
WARRANTY OR IN ANY WAY INCREASE THE SCOPE OF THIS WARRANTY.
SHOULD THE SOFTWARE AND/OR MATERIALS PROVE DEFECTIVE, YOU (AND
NOT SUPER MICRO COMPUTER INC. OR A SUPER MICRO COMPUTER INC.
AUTHORIZED REPRESENTATIVE) ASSUME THE ENTIRE COST OF ALL
NECESSARY SERVICE, REPAIR, OR CORRECTION.

LIMITATION OF LIABILITY. UNDER NO CIRCUMSTANCES INCLUDING

NEGLIGENCE, SHALL SUPER MICRO COMPUTER INC. BE LIABLE FOR ANY
INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES THAT RESULT FROM
THE USE OR INABILITY TO USE THE SOFTWARE OR MATERIALS, EVEN IF
SUPER MICRO COMPUTER INC. OR A SUPER MICRO COMPUTER INC.
AUTHORIZED REPRESENTATIVE HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.

SAA_SERVICE User's Guide Page 5

Any disputes arising between manufacturer and customer shall be governed by the
laws of Santa Clara County in the State of California, USA. The State of California,
County of Santa Clara shall be the exclusive venue for the resolution of any such
disputes. Super Micro's total liability for all claims will not exceed the price paid for the
hardware product.

Manual Revision 2.0.1

Release Date: May 14, 2026

Unless you request and receive written permission from Super Micro Computer, Inc.,
you may not copy any part of this document.

Information in this document is subject to change without notice. Other products and
companies referred to herein are trademarks or registered trademarks of their
respective companies or mark holders.

Copyright © 2013-2026 by Super Micro Computer, Inc.

All rights reserved.
Printed in the United States of America

SAA_SERVICE User's Guide Page 6

Version History
Date Rev Description

December-27-
1.0.0 1. Created this document.
2024

1. Added RemoteUpdate individual firmware support.

2. Added DCPDB CPLD support in Update Support Matrix.
April-30-2025 1.1.0 3. Added GPU B200 support in Update Support Matrix.
4. Added AOM board CPLD support in Update Support Matrix.
5. Added GPU HGX support in Update Support Matrix.

June-16-2025 1.1.0 1. Enhance the introduction in Overview.

1. Added support for the RemoteUpdate command.

2. Added support for the LocalUpdate command.
3. Added support for the BundleSync command.
December-15- 4. Added support for the GetBundleInfo command.
2.0.0
2025 5. Add the proxy server setting.
6. Fix descriptions of command usage.
7. Fix figures.
8. Fix description for RC setting.

1. Added GB200/GB300 DCBBS support in Update Support

Matrix.
2. Added new option support for the RemoteUpdate command.
3. Added NVIDIA NVSwitch, Powershelf, CDU, BF3, LCMC,
May-14-2026 2.0.1
Backplane NVMe support in Update Support Matrix.
4. Added new command UserManagement.
5. Added description and usage about --firmware_cfg option.
6. Updated description about --rack_cfg option.

SAA_SERVICE User's Guide Page 7

1. Overview

Supermicro has developed an integrated solution to facilitate server management,

SAA_SERVICE. As an extension of SAA, SAA_SERVICE simplifies complex firmware
updates by using firmware bundles with built-in reliable update flows and dependency
management, easily synchronizes bundled images among different storages and is
able to securely erase multiple disks with one command.

You can run SAA_SERVICE on a single system or on multiple systems, either in-band
or out-of-band. The in-band channel allows communication through the local system
interfaces,while the OOB (out-of-band) channel allows communication through the IPMI
interface. Through the OOB channel, commands can be executed independently of the
OS on the managed system or even before the system OS is installed.

To update over in-band, in the beginning, you need to clone the repository to proxy
server or place the mirror file of repository on the managed system. You can use the
SAA_SERVICE LocalUpdate commands to update the bundled firmware package in a
local system. For details about the command usage, please refer to 3.8 Updating
Firmware through In-Band Method.

SAA_SERVICE User's Guide Page 8

To update out-of-band, since the bundled firmware images and their corresponding
update information are stored in the SAA Service backend, you need to use the saasvc
BundleSync commands to clone the repository from SAA Service backend to proxy
server, so as to update firmware in an intranet-only environment. For details about the
command usage, please refer to 3.2 Pre-processing: Repository Information.

The SAA_SERVICE can select one of repository sources to retrieve the bundled
firmware images and their corresponding update information. The repository sources
can be the SAA Service backend if the system has Internet access, the proxy server for
Intranet only environment or the local mirror file of repository. The saasvc can update
firmware to two types of managed system over out-of-band. One is a CMM system with
blade systems inside, the other is a common motherboard. For details about the
command usage, please refer to 3.9 Updating Firmware through Out-of-Band Method.

SAA_SERVICE User's Guide Page 9

To update over Remote In-Band, use the saasvc RemoteUpdate command to send
required files to the managed system and execute the LocalUpdate command on the
remotely managed system. The only difference with directly updating in-band is that
RemoteUpdate will handle the return code and automatically perform the required
actions to continue the update process if needed. For details about command usage,
please refer to 3.10 Updating Firmware through Remote In-Band/RHI Method.

SAA_SERVICE User's Guide Page 10

To make sure the data integrity of the repository, the saasvc will check whether the files
in repository are intact and unchanged. Once the files in repository are manually
modified, the saasvc will detect the inconsistence and stop running.

1.1 Features
Support for automatic bundle firmware update or individual firmware update
Command-line interface (CLI)
Independent from OS on managed systems (for OOB usage)
Operation through OOB and in-band channels

SAA_SERVICE User's Guide Page 11

 Simultaneous execution of commands on multiple systems through a system list file

1.2 Operation Requirements

1.2.1 Requirements for OOB Usage

[Link] Network

The table lists the network communication protocols and ports required for running
OOB commands.

Command Network Requirements

RMCP+ protocol through IPv4/IPv6 UDP with

All OOB commands port 623.

In addition to RMCP+ protocol through

IPv4/IPv6 UDP with port 623, HTTPS protocol
OOB command RemoteUpdate through IPv4/IPv6 with the port defined in
BMC/CMM configuration is required. The
default HTTPS port is defined as port 443.

[Link] Remote Management Server

System Requirements:

Environment Requirements

50 MB free disk space (Only for application)

Hardware 128 MB available RAM

Ethernet network interface card

SAA_SERVICE User's Guide Page 12

 Red Hat Enterprise Linux 5.11 (x86_64) or
later
CentOS 5.11 (x86_64) or later
Operating System Ubuntu 12.04 LTS (x86_64) or later
Debian 7 (x86_64) or later
SUSE Linux Enterprise Server 12 SP3 or later
Windows Server 2008 (x64) or later

The software you should have in advance:

Program Description

SAA_SERVICE package The main program for SAA_SERVICE

[Link] Managed Systems

You can remotely update firmware on selected Supermicro systems through

SAA_SERVICE. Both the BMC and BIOS firmware images must meet the following
requirements.

Firmware Image Requirements

X12 ATEN platform (SMT_X12): 1.00 or later

BMC Version H12 ATEN platform (SMT_H12): 1.00 or later
R12 OpenBMC platform: 2.9.1-v27 or later

CMM Version ATEN platform (SMT_MBIPMI): 2.45 or later

Version 1.0 or later for select X12 3rd

Generation Intel® Xeon® Scalable processors
with Intel® C620 Series Chipsets Product
BIOS Version Family X12/H12 or later systems

Version 1.0d or later for Ampere® Altra®/Altra®

Max processor family on R12 platforms

1.2.2 Requirements for In-Band Usage

For automatic firmware updates over in-band, the managed system must meet the
following requirements.

SAA_SERVICE User's Guide Page 13

 Environment Requirements

50 MB free disk space

Hardware
128 MB available RAM

BIOS Version 1.0 or later for X12/H12 select

systems
Firmware Image
BIOS Version 1.0d or later for Ampere®
Altra®/Altra® Max processor family on R12
platforms

Linux: Red Hat Enterprise Linux 5.11 (x86_64)

or later
Linux: CentOS 5.11 (x86_64) or later
Operating System Linux: Ubuntu 12.04 LTS (x86_64) or later
Linux: Debian 7 (x86_64) or later
Linux: SUSE Linux Enterprise Server 12 SP3
or later

Note:
Although SAA can be run on Red Hat Enterprise Linux Server 4 Update
3 or later, several operating systems might not be supported by the
hardware. For a list of supported operating systems, please check OS
Compatibility.

Requirements for execution privileges:

Privilege Description

To execute in-band functions, saasvc requires

saasvc Execution Privilege the root/Administrator privilege for the operating
system running on the managed system.

The software you should get in advance:

OS Program/Script Description

The main program for

Linux SAA_SERVICE package
SAA_SERVICE

SAA_SERVICE User's Guide Page 14

Please contact Supermicro for any necessary drivers.

[Link] Additional Requirements

When the saasvc LocalUpdate command is used to update BMC firmware, the
managed system must have both BMC firmware image and IPMI driver installed. The
BMC firmware image should meet the following requirements.

Firmware Image Requirement

X11 ATEN platform (SMT_X11): 1.00 or later

X12 ATEN platform (SMT_X12): 1.00 or later
BMC Version
H11 ATEN platform (SMT_H11): 1.28 or later
H12 ATEN platform (SMT_H12): 1.00 or later

The drivers you should get in advance:

OS Program/Script Description

Red Hat. Enterprise Linux

Server 4u3 or later Sends/Receives data to/from
Built-in IPMI driver
(x86_64)/Ubuntu 12.04 or BMC
later (x86_64)/

Program/Script Description

IPMI driver for accessing BMC through its

OpenIPMI.x86_64
KCS interface

1.2.3 Requirements for SAA Service GUI

To use SAA Service GUI, you must meet the following system requirements:

Environment Requirements

Runtime package [Link] version: 11

Operating System Linux: Red Hat Enterprise Linux Server 7

(x86_64) or later
Linux: CentOS 7 (x86_64) or later
Linux: Ubuntu 14.04 LTS (x86_64) or later
Linux: Debian 8 (x86_64) or later

SAA_SERVICE User's Guide Page 15

 Linux: SUSE Linux Enterprise Server 12 SP3
or later
Windows: Windows Server 2008 (x64) or later

1.3 Typographical Convertions

This user’s guide employs the following typographical conventions.

Convention Definition

Courier-New font
size 10
represents Command Line Interface (CLI) instructions in Linux terminal
mode.

Bold Keywords needing attention are in bold.

Italics Variables and section names are in italics.

<> encloses the parameters in the syntax description.

[shell]#
represents the input prompt in Linux terminal mode.

[SAA_SERVICE_HOME]# represents the SAA_SERVICE home directory prompt in Linux

terminal.

| A vertical bar separate the items in a list.

(|) separator for mutually exclusive items. You must choose one.

1.4 Introduction to Interfaces

1.4.1 In-Band Interface

If you want to launch SAA Service on a local system but not via network, you can
choose In-Band Interface.
And make sure the OS is normal.

SAA_SERVICE User's Guide Page 16

1.4.2 Out-of-Band Interface

If you want to launch SAA Service on a system, regardless of whether it has an

operating system, you can choose the Out-of-Band Interface. This interface will execute
all functions via BMC network.

1.4.3 Remote In-Band Interface

Remote In-Band Interface is like In-Band Interface, but you can launch SAA Service on
the local of a remote system. Ensure the remote system OS can run normally.

1.4.4 Remote Redfish Host Interface

The Remote Redfish Host Interface operates similarly to the remote In-Band Interface.
But while the Remote In-Band Interface executes functions via IPMI raw commands,
the Remote Redfish Host Interface executes functions via Redfish API.

SAA_SERVICE User's Guide Page 17

2. Installation and Setup

2.1 Installing SAA_SERVICE on Linux and Windows

To install SAA_SERVICE on Linux, follow these steps. Windows installation and usage
are similar.

1. Extract the SAA_SERVICE_x.x.x_Linux_x86_64_YYYYMMDD.[Link] archive file.

2. Go to the extracted SAA_SERVICE_x.x.x_Linux_x86_64 directory and name this
directory as “SAA_SERVICE_HOME.”
3. Run saasvc in the SAA_SERVICE_HOME directory

Linux Example:

[shell]# tar xzf SAA_SERVICE_x.x.x_Linux_x64_YYYYMMDD.[Link]

[shell]# cd SAA_SERVICE_x.x.x_Linux_x86_64

[SAA_SERVICE_HOME]# ./saasvc

SAA_SERVICE User's Guide Page 18

3. Updating Firmware

SAA_SERVICE includes one binary executable file: “saasvc”. In this document, only the
examples of running on Linux are provided. To display the usage information, use this
command:

[SAA_SERVICE_HOME]# ./saasvc

To display the usage information for each command, use this syntax:

[SAA_SERVICE_HOME]# ./saasvc -h -c <command name>

Example:

[SAA_SERVICE_HOME]# ./saasvc -h -c RemoteUpdate

3.1 Preparations for Update

Follow these steps:

1. Determine the system to be updated.

2. Refer to Appendix B. Update Support Matrix to check if the firmware is supported.

SAA_SERVICE User's Guide Page 19

3.2 Pre-processing: Repository Information
There are three types of repositories: Supermicro Gitea Server, SAA Service backend
proxy server, and mirror ZIP file. You can utilize Supermicro Gitea Server to download
repositories through an extranet. To prevent other machines from connecting to the
extranet, employ Supermicro Gitea Server to download repositories onto a designated
machine and effectively use it as a server. Subsequently, other machines can access

SAA_SERVICE User's Guide Page 20

this server via the intranet using the SAA Service backend proxy server method. To
update without connecting to any repository servers, use a mirror zip file as the
repository. To set up your repository, if you want to connect to Supermicro Gitea Server,
contact your sales representative to get login information. If you want to use a mirror file
directly, contact your sales representative to get the zip file or download it from
Supermicro Gitea Server.

Supermicro Gitea Server:

Advantages: To download any type of repository, you only need to change the rc file
settings.
Limitation: Extranet connection required.
Steps:
Change the configuration settings in the rc file ([Link]):

<RepositorySourceID>0</RepositorySourceID>

<URL>[Link]

<Username>(Repository username)</Username>

<Password>(Repository password)</Password>

<Service>(Repository service name)</Service>

SAA Service backend proxy server:

Advantages: It’s not required to connect to extranet, but only on the intranet. Setting
up one server can serve multiple nodes, and you can choose any type of repository.
Limitation: A server environment must be set up. Token is necessary for accessing
SAA Service backend proxy server. Please refer to 3.4 Pre-processing:
UserManagement
Steps:
Change the configuration settings in the rc file ([Link]):

<RepositorySourceID>1</RepositorySourceID>

<URL>[Link]

SAA_SERVICE User's Guide Page 21

 Note:
Please refer to the document called README-deployment in backend
proxy server package to deploy the backend proxy server.

Mirror File:
Advantages: Nodes are not required to connect to Extranet or Intranet.
Limitation: You need to set up the repositories one by one at a time
Steps:
1.) Get the repository zip file: You can download it from the Supermicro Gitea
Server or get it from Supermicro.
2.) Change the configuration settings in the rc file ([Link]):

<RepositorySourceID>0</RepositorySourceID>

(Set this value to 2)

3.) Change the configuration settings in the rc file ([Link]):

<Option ID="2" name="mirror">

<FilePath>(mirror zip file path)</FilePath>

</Option>

(Set this value to zip file path)

3.3 Pre-processing: Resource File Setting

3.3.1 saasvc RC file

The configurations of saasvc can be set in the rc file (“[Link]”), and you can also
use the GUI to configure the rc file.

Note that the default configuration will be only applied when nothing is assigned in a
command option and the [Link] file.

SAA_SERVICE User's Guide Page 22

To create a rc file, you can copy and rename the [Link] sample file in the
SAA_SERVICE release package to “[Link],” and save it in either the current
directory or your home directory.

There are three ways to set the rc file path:

The --rc_path Option: The path set with the --rc_path option is the main path. An
error message occurs if the path cannot be found.
File in the Current Directory: The rc file in the current directory is designated as
the file path.
The rc file in the Home Directory: The rc file in the home directory is designated
as the file path. An error message occurs if there is no rc file in the home directory.

For auto firmware updates, send your OEM request to Supermicro to obtain the settings
(“Username” “Password” and “Service”) first and refer to the table below to make your
configurations.

Setting Name Setting Value Sample Description

Sets the journal level for

saasvc. Options: 0:silent,
JournalLevel [1]1 1:fatal, 2:error, 3:warning,
4:information, 5:debug,
6:verbose.

Sets the journal path. Default is

JournalPath [1](empty) the path of the saasvc
executable.

Sets the checking timeout for

UDP connection in seconds.
UdpTimeout 1 ~ [1]240 Value should be between 1 and
240, inclusive. Default is 240.

Sets the thread count for

ThreadCount [1]50 multiple system OOB usage.
Default is 50.

Sets the retry count for multiple

MultiRetryCount [1]2 system OOB usage. Default is
2.

SAA_SERVICE User's Guide Page 23

 Enables or disables IPv6
Ipv6FileNameSwitch [1]0 filename switch. 0:disabled,
1:enabled.

Sets proxy for repository

[1][Link] connection. Format:
Proxy
3128 protocol://[username:password
@]ip[:port].

Sets the maximum upload

MaxUploadSpeed [1]1000 speed in Mbit/s for firmware
upload in multi-node mode.

[1]8080 Sets the managed system’s

BmcCfg/HttpsPort
HTTP port. Default is 443.

CommandCfg/UpdateCom 0:not preserved, Sets BIOS configuration to be

mon/BiosPreserveSetting [1]1:preserved preserved for BIOS update.

CommandCfg/UpdateCom 0:not preserved, Sets BMC configuration to be

mon/BmcPreserveSetting [1]1:preserved preserved for BMC update.

Sets the source ID for firmware

CommandCfg/UpdateCom [1]0 repository. 0:gitea, 1:proxy,
mon/RepositorySourceId
2:mirror.

Sets the requirements of all

CommandCfg/RemoteUpda 0:false, blades on the managed CMM
te/RequireAllBladeCredenti [1]1:true for RemoteUpdate command.
als
Default is 1.

Sets the wait time in seconds

CommandCfg/RemoteUpda [1]300 for RemoteUpdate after the
te/RebootWaitTime remote system is rebooted.
Default is 300 seconds.

CommandCfg/LocalUpdate/ [1]3 Sets the maximum rerun count

MaxRerunCount for local update.

Sets the wait time in seconds

CommandCfg/SecureErase [1]3 for erasing HDD. Default is
/PostTimeout
1800 seconds.

RepositoryCfg/Source/Opti [1][Link] Sets the Gitea repository URL

on[0]/URL [Link] for firmware update.

SAA_SERVICE User's Guide Page 24

 Sets the backend proxy server
RepositoryCfg/Source/Opti [1][Link] for firmware update. Format:
on[1]/URL 3128 protocol://[username:password
@]ip[:port].

RepositoryCfg/Source/Opti [1][Link] Sets the mirror file path for

on[2]/FilePath firmware update.

RecordTargetCfg/RecordFo [1](empty) Sets the record file path for

lderPath firmware update.

[1] Default configuration value.

[2] Username, password, and service settings can be obtained by sending your OEM
requests to Supermicro.
[3] Supermicro GITea needs Internet access. The backend proxy server can be used in
an Intranet only environment.

The [Link] file example in the package is provided below.

<?xml version="1.0" encoding="UTF-8"?>

<SAAServiceConfig xmlns="saasvc">
<Description>
<!-- This configuration file contains settings used for saasvc.-->
<!-- Instruction: -->
<!-- 1. Please copy this file to saasvc execution directory or user home
directory and rename to [Link] -->
<!-- 2. The saasvc execution directory will be read first and the user
home directory will be the second priority. -->
</Description>
<GlobalCfg>
<JournalLevel>1</JournalLevel>
<!-- If no value is provided, the default is 0 -->
<!-- Set saasvc journal level -->
<!-- Available Option: -->
<!-- 0: silent, 1: fatal, 2: error, 3: warning, 4: information, 5: debug, 6:
verbose -->
<JournalPath></JournalPath>
<!-- If no value is provided, the default is the path of the saasvc
executable -->
<!-- Set saasvc journal path -->
<UdpTimeout>30</UdpTimeout>
<!-- If no value is provided, the default is 240 -->
<!-- Set the checking timeout for udp connection in seconds -->
<!-- the value should be between 1 and 240, inclusive -->
<ThreadCount>4</ThreadCount>
<!-- If no value is provided, the default is 50 -->

SAA_SERVICE User's Guide Page 25

 <!-- Set thread count for multiple system OOB usage -->
<MultiRetryCount>2</MultiRetryCount>
<!-- If no value is provided, the default is 2 -->
<!-- Set retry count for multiple system OOB usage -->
<Ipv6FileNameSwitch>0</Ipv6FileNameSwitch>
<!-- If no value is provided, the default is 0 -->
<!-- Replace ':' with '-' when file name contains IPv6 address -->
<Proxy>[Link]
<!-- If no value is provided, the default is an empty string -->
<!-- Set proxy for connection to repository url (supermicro) -->
<!-- format: protocol://[username:password@]ip[:port] -->
<!-- Protocol support: https, socks4, socks4a, socks5 and socks5h -->
<!-- username and password should be url-encoded -->
<!-- ip can be ip address or hostname -->
<!-- '[]' means field between it is optional -->
<!-- proxy_setting = socks5://username:password@[Link]:1080 -->
<DestinationFolder>/supermicro/saasvc_RemoteFile/</DestinationFolder>
<!-- If no value is provided, the default is /supermicro/saasvc_RemoteFile/ -
->
<!-- Set the path under home directory of the remote machine to send files
for remote execution -->
<!-- Please make sure the path will not be cleared upon reboot -->
<MaxUploadSpeed>1000</MaxUploadSpeed>
<!-- If no value is provided, the defualt is 1000 Mbit/s -->
<!-- Set the Curl maximum upload speed for uploading firmware file in
multiple node mode. -->
</GlobalCfg>
<BmcCfg>
<HttpPort>8080</HttpPort>
<!-- If no value is provided, the default is 443 -->
<!-- Set managed system https port-->
</BmcCfg>
<CommandCfg>
<UpdateCommon>
<!-- 0=false, 1=true -->
<BiosPreserveSetting>1</BiosPreserveSetting>
<!-- If no value is provided, the default is 1 -->
<!-- Set BIOS configuration to be preserved for BIOS update -->
<!-- 0: not preserve, 1: preserve -->
<BmcPreserveSetting>1</BmcPreserveSetting>
<!-- If no value is provided, the default is 1 -->
<!-- Set BMC configuration to be preserved for BMC update -->
<!-- 0: not preserve, 1: preserve -->
<RepositorySourceId>2</RepositorySourceId>
<!-- If no value is provided, the default is 2 -->
<!-- Set source for firmware update -->
<!-- When the source is Supermicro Gitea Server, the username, password and
URL of the source must be set -->
<!-- 0: Supermicro Gitea Server, 1: Self-hosted Proxy Server, 2: Mirror -->
</UpdateCommon>
<RemoteUpdate>
<RequireAllBladeCredentials>0</RequireAllBladeCredentials>
<!-- If no value is provided, the default is 0 -->

SAA_SERVICE User's Guide Page 26

 <!-- Require credentials of all installed blades on the managed CMM for
RemoteUpdate command -->
<!-- Available Option: -->
<!-- 0: false, 1: true -->
<RebootWaitTime>60</RebootWaitTime>
<!-- If no value is provided, the default is 300 seconds -->
<!-- Set the wait time after reboot the remote machine -->
</RemoteUpdate>
<LocalUpdate>
<MaxRerunCount>3</MaxRerunCount>
<!-- The max rerun count is for task in rerun status -->
</LocalUpdate>
<SecureErase>
<PostTimeout>60</PostTimeout>
<!-- If no value is provided, the default is 1800 seconds -->
<!-- Set post complete polling timeout for erasing HDD -->
<!-- Please give the value according to the actual erase time -->
</SecureErase>
</CommandCfg>
<RepositoryCfg>
<Source>
<!-- Supermicro Gitea Server -->
<Option ID="0" name="gitea">
<URL>[Link]
<!-- The default is [Link] -->
<!-- Set repository url for firmware update -->
<Username></Username>
<!-- Set username for repository url -->
<Password></Password>
<!-- Set password for repository url -->
<Service></Service>
<!-- Set service name for firmware update -->
</Option>
<!-- Self-hosted Backend Proxy Server -->
<Option ID="1" name="backend proxy server">
<URL>[Link]
<!-- Set self-hosted backend proxy server url for firmware update -->
</Option>
<!-- Mirror file -->
<Option ID="2" name="mirror">
<FilePath>[Link]</FilePath>
<!-- Set mirror file path for firmware update -->
</Option>
</Source>
</RepositoryCfg>
<RecordTargetCfg>
<RecordFolderPath></RecordFolderPath>
<!-- Please fill with local storage path -->
</RecordTargetCfg>
</SAAServiceConfig>

SAA_SERVICE User's Guide Page 27

3.3.2 rack config JSON file

The rack configurations, including rack names, compute tray nodes, and chassis details
(e.g., power shelf, NVLink Switch IP/host, usernames, and passwords), are defined in
the [Link] file. These settings can be configured either by manually editing the
JSON file or via the GUI.

To create a rack configuration file, you can copy and rename the [Link] sample
file in the SAA_SERVICE release package to “[Link]”, and save it in either the
current directory or your home directory.

Chassis information is not necessary if you only update the compute trays.

{
"RACK":
[
{
"RackName":"RackA",
"ComputeTray":{
"Node":[
{
"IP":"[Link]",
"Username":"username",
"Password":"password"
},
{
"IP":"[Link]",
"Username":"username",
"Password":"password"
}
]
},
"Chassis":{
"Node":[
{
"IP":"[Link]",
"Username":"username",
"Password":"password"
},
{
"IP":"[Link]",
"Username":"username",
"Password":"password"
}
]
}
},

SAA_SERVICE User's Guide Page 28

 {
"RackName":"RackB",
"ComputeTray":{
"Node":[
{
"IP":"[Link]",
"Username":"username",
"Password":"password"
},
{
"IP":"[Link]",
"Username":"username",
"Password":"password"
}
]
},
"Chassis":{
"Node":[
{
"IP":"[Link]",
"Username":"username",
"Password":"password"
},
{
"IP":"[Link]",
"Username":"username",
"Password":"password"
}
]
}
}
]
}

3.4 Pre-processing: UserManagement

User Management

Description: Manage users and obtain tokens for calling backend APIs. Token is
required for using SAA Service backend proxy server as RepositorySource in the RC
file. After the SAA Service backend proxy server is set up, running UserManagement
command with action --bootstrap to initialize an admin account is required.
Usage: ./saasvc -c UserManagement --action <action>

SAA_SERVICE User's Guide Page 29

 (Required) --action: The action to execute the command. Supported actions are
bootstrap, login, logout, register, list_users, change_password and delete_user.
(Optional) --bu, --bp and --bp-stdin: Backend user information.
(Optional) --email: Backend user email for bootstrap and register action.
(Optional) --role: Role of the backend user account register action. Can be admin
or user
(Optional) --old_password: Old password of the backend user account for
change_password action.
(Optional) --new_password: New password of the backend user account for
change_password action.
(Optional) --target_username: Target backend user account for delete_user
action.

Usage:
1. ./saasvc -c UserManagement --action bootstrap --bu <backend_username> --email
<email> --bp <backend_password>
2. ./saasvc -c UserManagement --action login --bu <backend_username> --bp-stdin
3. ./saasvc -c UserManagement --action login --bu <backend_username> --bp
<backend_password>
4. ./saasvc -c UserManagement --action logout
5. ./saasvc -c UserManagement --action register --bu <backend_username> --email
<email> --role <role> --bp-stdin
6. ./saasvc -c UserManagement --action list_users
7. ./saasvc -c UserManagement --action change_password --old_password
<old_pwd> --new_password <new_pwd>
8. ./saasvc -c UserManagement --action delete_user --target_username
<backend_username>

3.5 Pre-processing: Repository Synchronization

Bundle Management

SAA_SERVICE User's Guide Page 30

Description: Manage bundle mirror file and bundles on the backend proxy server.
Usage: ./saasvc -c BundleSync --action <action> --mirror_file <file name>

(Required) --mirror_file: The name of the mirror file to save.

(Required) --action: The action to execute the command. The pull and pull_all
actions are designed for downloading bundles from the Supermicro Gitea Server
and save it as a mirror file; the push and force_push actions are designed for
uploading mirror file to the backend proxy server provided in the RC file.
(Optional) -i, -u and -p: System information of the bundle to download.
(Optional) --ip_list: The list of system information of the bundle to download as a
text file.
(Optional) --ppm: The Product PartModel Number of the bundle to download.
(Optional) --ppm_list: The list of Product PartModel Number of the bundle to
download as a text file.
(Optional) --bundle_id: The bundle id of the bundle to download.
(Optional) --tail: Download the latest provided numbers of bundles.
(Optional) --range: Download the bundles created in a range of date.

Usage:
1. ./saasvc -c BundleSync -i <BMC IP> -u <BMC username> -p <BMC user
password> --action pull_all --mirror_file <file name>
2. ./saasvc -c BundleSync --ip_list <system information list file> --action pull_all --
mirror_file <file name>
3. ./saasvc -c BundleSync --ppm <product PartModel Number> --action pull_all --
mirror_file <file name>
4. ./saasvc -c BundleSync --ppm_list <product PartModel Number list file> --action
pull_all --mirror_file <file name>
5. ./saasvc -c BundleSync -i <BMC IP> -u <BMC username> -p <BMC user
password> --action pull --mirror_file <file name> --tail <name of bundles>
6. ./saasvc -c BundleSync -i <BMC IP> -u <BMC username> -p <BMC user
password> --action pull --mirror_file <file name> --range <date,date>
7. ./saasvc -c BundleSync --ip_list <system information list file> --action pull --
mirror_file <file name>

SAA_SERVICE User's Guide Page 31

 --tail <name of bundles>
8. ./saasvc -c BundleSync --ip_list <system information list file> --action pull --
mirror_file <file name>
--range <date,date>
9. ./saasvc -c BundleSync --ppm <product PartModel Number> --action pull --
mirror_file <file name> --tail <name of bundles>
0. ./saasvc -c BundleSync --ppm <product PartModel Number> --action pull --
mirror_file <file name> --range <date,date>
11. ./saasvc -c BundleSync --ppm_list <product PartModel Number list file> --action pull
--mirror_file <file name>--tail <name of bundles>
2. ./saasvc -c BundleSync --ppm_list <product PartModel Number list file> --action pull
--mirror_file <file name> --range <date,date>
3. ./saasvc -c BundleSync --bundle_id <bundle id> --action pull --mirror_file <file
name>
4. ./saasvc -c BundleSync --action push --mirror_file <file name>
5. ./saasvc -c BundleSync --action force_push --mirror_file <file name>

3.6 Pre-processing: System List File Setting

If you want to create a system list file, you can create a txt file in the SAA_SERVICE
release package folder.
Here is the format and an example of writing a system list file ([Link]).

Format: BMC_IP BMC_Username BMC_Password

Example:
[SAA_SERVICE_HOME]# ./saasvc -l [Link] -c RemoteUpdate --reboot

[Link]:
[Link] ADMIN1 PASSWORD1
[Link] ADMIN2 PASSWORD2

3.7 Command Parameters

SAA_SERVICE User's Guide Page 32

There are many parameters in the command:

(Optional) --skip_curpkg_check: If the managed system’s current firmware

version doesn’t match any firmware bundle, you may need to manually recover the
system in case of an update failure due to the lack of origin firmware in the
repository source. Add this option to skip the check and acknowledge your
awareness of the risk.
(Optional) --skip_depend_check: Skip dependency requirement and directly
upgrade the individual firmware. The option must be used with the --firmware
option.
(Optional) --update_target: Specify the target bundle id for firmware upgrade. The
option must be used with the --firmware option.
(Optional) --reboot: If the firmware update requires a system reboot, you should
add this option to initiate the reboot.
(Optional) --dry-run: If you want to simulate firmware update, you can add this
parameter to simulate the update result.
(Optional) --rollback: Specifies the desired version of firmware bundle for rollback
using a bundle ID as a parameter.
(Optional) --forward: Confirms the update to a version that does not allow rollback.
(Optional) --poweron_check: Checks the power status and power on the
managed system if required. This option is required to update the (main or side)
switchboard CPLD. (For RemoteUpdate only)
(Optional) --poweroff: Forces the managed system to power off if the required.
(For LocalUpdate only).
(Optional) --rack_cfg: Specifies a JSON configuration file ([Link]) containing
rack details, including IP/Host addresses and credentials for compute trays and
chassis (e.g., Power Shelf, NVLink Switch). (RemoteUpdate only)
(Optional) --firmware: Specifies firmware to perform individual firmware update
(Optional) --firmware_cfg: Specifies a JSON configuration file ([Link])
containing update task to perform individual firmware update.

[Link]:
{
"TASK": [

SAA_SERVICE User's Guide Page 33

 {
"FirmwareType": "BMC",
"FirmwareIndex": "",
"ProductPartNumber": "",
"PcbRevision": ""
},
{
"FirmwareType": "CPLD_MB",
"FirmwareIndex": "1",
"ProductPartNumber": "",
"PcbRevision": ""
}
]
}

3.8 Verifying System or Repository Information

3.8.1 Getting System Information

Use the GetSystemIdentity command to get the system’s Product PartModel Number
and the BMC IP address. It is imperative that the metadata corresponding to the
Product PartModel Number must be present in the repository.

To get the system information of the local system, execute the following command:

[SAA_SERVICE_HOME]# ./saasvc -c GetSystemIdentity

SAA Service (for UEFI BIOS) 2.0.0 (2025/11/19) (x86_64)

Copyright(C) 2024 Super Micro Computer, Inc. All rights reserved.

Fetching configuration on the managed system..........Done

[System Information]
The list of information is provided below:
Product PartModel Number: <PPM>
BMC IP Address: <BMC IP>

To get system information from a remote machine using the Out-of-Band method,
execute the following command.
[SAA_SERVICE_HOME]# ./saasvc -c GetSystemIdentity -i <BMC IP> -u <BMC
username> -p <BMC user password>

SAA_SERVICE User's Guide Page 34

 To get system information of a remote machine using the Remote In-Band method,
execute the following command.
[SAA_SERVICE_HOME]# ./saasvc -c GetSystemIdentity --oi <OS IP> --ou <OS
username> --op <OS user password>

3.8.2 Getting Bundle Information

Use the GetBundleInfo command to get information from the configured repository
source in the rc file. Ensure that the bundle information matches the system
information.

To get the bundle information, execute the following command:

[SAA_SERVICE_HOME]# ./saasvc -c GetBundleInfo --all

SAA Service (for UEFI BIOS) 2.0.0 (2025/11/19) (x86_64)

Copyright(C) 2024-2025 Super Micro Computer, Inc. All rights reserved.
Checking firmware bundles source with [Link] file...Done

Scanning bundle source files...

Supported Product Part Model Number (PPM): X14DBM-SP
1. Bundle ID: X14DBM-SP_20250912_01
BMC: BMC_X14AST2600-ROT20-4501MS_20250906_01.03.02.00_STDsp.bin
BIOS: BIOS_X14DBMS-1D37_20250821_1.4_STDsp.bin
CPLD_MB(ID: 1): CPLD_X14DBM-SP-U28-30XXF248_20250516_F2.48.25_STDsp.bin
Done

GetBundleInfo also support the following optional command parameters

(Optional) --bundle_id: Provide a bundle id to retrieve information.

(Optional) --ppm: Provide a single Product PartModel Number to retrieve
information.
(Optional) --ppm_list: Provide multiple Product PartModel Number via a file to
retrieve information.
(Optional) --tail: Retrieves information of the latest provided numbers of bundles.
(Optional) --range: Retrieves information of the bundles in a range of date.
(Optional) --all: Displays the bundle information from the first bundle to the latest
one.

SAA_SERVICE User's Guide Page 35

 (Optional) --all_ppm: Displays all Product PartModel Number name.

3.9 Updating Firmware through In-Band Method

Use the saasvc LocalUpdate command to update bundled or individual firmware

through the in-band method. Updating firmware may require a system to reboot, so you
may need to run the LocalUpdate command several times.

SAA_SERVICE User's Guide Page 36

After executing the LocalUpdate command, two files are generated:

Metadata Folder
A folder named after the <Service> field under the <RepositoryCfg> table in the
[Link] file will be generated under the [SAA_SERVICE_HOME] directory.
Versions of bundled package metadata and firmware are available in JSON file
under the “<Service>/metadataFwVerInfo” folder.

Status JSON File

This file is stored locally(on the managed system) or remotely(on SAA_SERVER).
The file path at the local side is determined by the attribute <RecordFolderPath>
under [Link].

Bundle Update
Initializes Update

Description: Initializes the firmware update process.

Usage: ./saasvc -c LocalUpdate --init
*Optional: You can use the “--forward”, “--rollback <metadata version>”, or “--
skip_curpkg_check” option with this command. If the system needs to be updated by
the Redfish Host Interface (Redfish_HI), you can add the "-I Redfish_HI", followed by -u
and -p options, to this command. You can find the option description in 3.7 Command
Parameters.

Usage:
1. ./saasvc -c LocalUpdate --init --forward
2. ./saasvc -c LocalUpdate --init --rollback <metadata version>
3. ./saasvc -c LocalUpdate --init --skip_curpkg_check
4. ./saasvc -c LocalUpdate --init --rollback <bundle_id> --skip_curpkg_check
5. ./saasvc -c LocalUpdate --init -I Redfish_HI -u <BMC username> -p <BMC user
password> --forward
6. ./saasvc -c LocalUpdate --init -I Redfish_HI -u <BMC username> -p <BMC user
password> --rollback <metadata version>
7. ./saasvc -c LocalUpdate --init -I Redfish_HI -u <BMC username> -p <BMC user
password> --skip_curpkg_check

SAA_SERVICE User's Guide Page 37

8. ./saasvc -c LocalUpdate --init -I Redfish_HI -u <BMC username> -p <BMC user
password> --rollback <bundle_id> --skip_curpkg_check

Forces to Initialize Update

Description: Forces to initialize the firmware update process.

Usage: ./saasvc -c LocalUpdate --force_init
*Optional: You can add either the “--forward” or “--rollback <metadata version>” option,
and “--skip_curpkg_check” option to the command. If the system needs to be updated
by the Redfish Host Interface (Redfish_HI), you can add the "-I Redfish_HI", followed
by -u and -p options, to this command. You can find the option description in 3.7
Command Parameters.

Usage:
1. ./saasvc -c LocalUpdate --force_init --forward
2. ./saasvc -c LocalUpdate --force_init --rollback <version>
3. ./saasvc -c LocalUpdate --force_init --skip_curpkg_check
4. ./saasvc -c LocalUpdate --force_init --rollback <version> --skip_curpkg_check
5. ./saasvc -c LocalUpdate --force_init -I Redfish_HI -u <BMC username> -p <BMC
user password> --forward
6. ./saasvc -c LocalUpdate --force_init -I Redfish_HI -u <BMC username> -p <BMC
user password> --rollback <version>
7. ./saasvc -c LocalUpdate --force_init -I Redfish_HI -u <BMC username> -p <BMC
user password> --skip_curpkg_check
8. ./saasvc -c LocalUpdate --force_init -I Redfish_HI -u <BMC username> -p <BMC
user password> --rollback <version> --skip_curpkg_check

Dry-run Update

Description: Simulates firmware update process.

Usage: ./saasvc -c LocalUpdate --dry-run
*Optional: User can add either the “--forward” or “--rollback <metadata version>”
option, and “--skip_curpkg_check” option to the command. If the system needs to be
updated by the Redfish Host Interface (Redfish_HI), you can add the "-I Redfish_HI",

SAA_SERVICE User's Guide Page 38

followed by -u and -p options, to this command. You can find the option description in
3.7 Command Parameters.

Usage:
1. ./saasvc -c LocalUpdate --dry-run --forward
2. ./saasvc -c LocalUpdate --dry-run --rollback <version>
3. ./saasvc -c LocalUpdate --dry-run --skip_curpkg_check
4. ./saasvc -c LocalUpdate --dry-run --rollback <version> --skip_curpkg_check
5. ./saasvc -c LocalUpdate --dry-run -I Redfish_HI -u <BMC username> -p <BMC user
password> --forward
6. ./saasvc -c LocalUpdate --dry-run -I Redfish_HI -u <BMC username> -p <BMC user
password> --rollback <version>
7. ./saasvc -c LocalUpdate --dry-run -I Redfish_HI -u <BMC username> -p <BMC user
password> --skip_curpkg_check
8. ./saasvc -c LocalUpdate --dry-run -I Redfish_HI -u <BMC username> -p <BMC user
password> --rollback <version> --skip_curpkg_check

Continues Update

Description: Continues firmware update.

Usage: ./saasvc -c LocalUpdate --continue
*Optional: You can add the “--reboot” and "--poweroff" options if the update needs to
reboot the system or power off the system. If the system needs to be updated by the
Redfish Host Interface (Redfish_HI), you can add the "-I Redfish_HI", followed by -u
and -p options, to this command.

Individual Update
Initializes Update

Description: Initializes the firmware update process.

Usage: ./saasvc -c LocalUpdate --init --firmware 1 <firmware name(s)>
*Optional: You can add either the “--update_target <metadata version>” or “--rollback
<metadata version>” option, and “--skip_depend_check” option to the command. But “--
skip_depend_check” can’t be used with “--rollback <metadata version>”. If the system
needs to be updated by the Redfish Host Interface (Redfish_HI), you can add the "-I

SAA_SERVICE User's Guide Page 39

Redfish_HI", followed by -u and -p options, to this command. You can find the option
descriptions in 3.7 Command Parameters.

Usage:
1. ./saasvc -c LocalUpdate --init --firmware 1 <firmware name(s)> --
skip_depend_check

2. ./saasvc -c LocalUpdate --init --firmware 1 <firmware name(s)> --rollback <metadata

version>

3. ./saasvc -c LocalUpdate --init --firmware 1 <firmware name(s)> --update_target

<metadata version> --skip_depend_check
4. ./saasvc -c LocalUpdate --init --firmware_cfg [Link]
5. ./saasvc -c LocalUpdate --init -I Redfish_HI -u <BMC username> -p <BMC user
password> --firmware 1 <firmware name(s)> --skip_depend_check
6. ./saasvc -c LocalUpdate --init -I Redfish_HI -u <BMC username> -p <BMC user
password> --firmware 1 <firmware name(s)> --rollback <metadata version>
7. ./saasvc -c LocalUpdate --init -I Redfish_HI -u <BMC username> -p <BMC user
password> --firmware 1 <firmware name(s)> --update_target <metadata version> --
skip_depend_check
8. ./saasvc -c LocalUpdate --init -I Redfish_HI -u <BMC username> -p <BMC user
password> --firmware_cfg [Link]

Forces to Initialize Update

Description: Forces to initialize the firmware update process.

Usage: ./saasvc -c LocalUpdate --force_init --firmware 1 <firmware name(s)>
*Optional: You can add either the “--update_target <metadata version>” or “--rollback
<metadata version>” option, and “--skip_depend_check” option to the command. But
the “--skip_depend_check” option can’t be used with the “--rollback <metadata
version>” option. If the system needs to be updated by the Redfish Host Interface
(Redfish_HI), you can add the "-I Redfish_HI", followed by -u and -p options, to this
command. You can find the option descriptions in 3.7 Command Parameters.

Usage:

SAA_SERVICE User's Guide Page 40

1. ./saasvc -c LocalUpdate --force_init --firmware 1 <firmware name(s)> --
skip_depend_check

2. ./saasvc -c LocalUpdate --force_init --firmware 1 <firmware name(s)> --rollback

<metadata version>

3. ./saasvc -c LocalUpdate --force_init --firmware 1 <firmware name(s)> --

update_target <metadata version> --skip_depend_check
4. ./saasvc -c LocalUpdate --force_init _cfg [Link]
5. ./saasvc -c LocalUpdate --force_init -I Redfish_HI -u <BMC username> -p <BMC
user password> --firmware 1 <firmware name(s)> --skip_depend_check
6. ./saasvc -c LocalUpdate --force_init -I Redfish_HI -u <BMC username> -p <BMC
user password> --firmware 1 <firmware name(s)> --rollback <metadata version>
7. ./saasvc -c LocalUpdate --force_init -I Redfish_HI -u <BMC username> -p <BMC
user password> --firmware 1 <firmware name(s)> --update_target <metadata
version> --skip_depend_check
8. ./saasvc -c LocalUpdate --force_init -I Redfish_HI -u <BMC username> -p <BMC
user password> --firmware_cfg [Link]

Dry-run Update

Description: Simulate firmware update process.

Usage: ./saasvc -c LocalUpdate --dry-run --firmware 1 <firmware name(s)>
*Optional: User can add either the “--update_target <metadata version>” or “--rollback
<metadata version>” option, and “--skip_depend_check” option to the command. But “--
skip_depend_check” can’t be used with “--rollback <metadata version>.” If the system
needs to be updated by the Redfish Host Interface (Redfish_HI), you can add the "-I
Redfish_HI", followed by -u and -p options, to this command. You can find the option
description in 3.7 Command Parameters.

Usage:
1. ./saasvc -c LocalUpdate --dry-run --firmware 1 <firmware name(s)> --
skip_depend_check

2. ./saasvc -c LocalUpdate --dry-run --firmware 1 <firmware name(s)> --rollback

<metadata version>

SAA_SERVICE User's Guide Page 41

3. ./saasvc -c LocalUpdate --dry-run --firmware 1 <firmware name(s)> --update_target
<metadata version> --skip_depend_check
4. ./saasvc -c LocalUpdate --dry-run --firmware_cfg [Link]
5. ./saasvc -c LocalUpdate --dry-run -I Redfish_HI -u <BMC username> -p <BMC user
password> --firmware 1 <firmware name(s)> --skip_depend_check
6. ./saasvc -c LocalUpdate --dry-run -I Redfish_HI -u <BMC username> -p <BMC user
password> --firmware 1 <firmware name(s)> --rollback <metadata version>
7. ./saasvc -c LocalUpdate --dry-run -I Redfish_HI -u <BMC username> -p <BMC user
password> --firmware 1 <firmware name(s)> --update_target <metadata version> --
skip_depend_check
8. ./saasvc -c LocalUpdate --dry-run -I Redfish_HI -u <BMC username> -p <BMC user
password> --firmware_cfg [Link]

Continues Update

Description: Continues firmware update.

Usage: ./saasvc -c LocalUpdate --continue
*Optional: You can add the “--reboot” and "--poweroff" options if the update needs to
reboot the system or power off the system. If the system needs to be updated by the
Redfish Host Interface (Redfish_HI), you can add the "-I Redfish_HI", followed by -u
and -p options, to this command.

[1]: You can use the --firmware option followed by single or multiple firmware names to
update firmware individually. The parameter string of the --firmware option uses a
comma as the delimiter, i.e., ./saasvc -c LocalUpdate --init --firmware
“BMC;BIOS;CPLD” --update_target <metadata version>.

3.9.1 Updating Firmware Bundle

1. [SAA_SERVICE_HOME]# ./saasvc -c LocalUpdate --init

[root@localhost SAASVC_LOCAL]# ./saasvc -c LocalUpdate --init

SAA Service (for UEFI BIOS) 2.0.0 (2025/11/19) (x86_64)
Copyright(C) 2024-2025 Super Micro Computer, Inc. All rights reserved.

Extracting system information.......Done

SAA_SERVICE User's Guide Page 42

Checking bundle source connection...Done

Checking command options and conflicts...Done

Preparing resources and downloading bundle files..Done

Validating metadata and file sets...Done

Preparing modules and tools for update tasks...Done

Generating operation list and update tasks...........Done

Starting firmware update operations...

Checking record target availability on local storage...Done

Getting the latest operation status...Done

Preparing operation list...Done

System Information:
Product Part Number........X14DBM-SP

Operation list information:

Signature..................94914c32f2e25ace2547ec6e84771a87002add1e
Recovery support...........Yes
Create time (UTC)..........2025-11-19T02:38:26+0000

Current firmware information:

BMC version................[Link]
BIOS version...............1.4 (2025/08/21)
CPLD_MB (ID: 1) version....25

Target firmware information:

BMC version................[Link]
BIOS version...............1.4 (2025/08/21)
CPLD_MB (ID: 1) version....25

Metadata X14DBM-SP_20250912_01 (target) update tasks:

Type.......................Target BMC
Version....................[Link]
Status.....................pending

Type.......................Target BIOS
Version....................1.4 (2025/08/21)
Status.....................pending

Type.......................Target CPLD_MB
Index......................1
Version....................25
Status.....................pending

SAA_SERVICE User's Guide Page 43

 Synchronizing update record files...Done

***************************<<<<<CRITICAL WARNING>>>>>***************************

ExitCode = 254
Description = Manual steps are required
Program Error Code = 1030.2
Error message:
Please use --continue option to do the next process.

********************************************************************************

2. [SAA_SERVICE_HOME]# ./saasvc -c LocalUpdate --continue

[root@localhost SAASVC_LOCAL]# ./saasvc -c LocalUpdate --continue

SAA Service Local (for UEFI BIOS) 1.0.0 (2024/10/24) (x86_64)
Copyright(C) 2024 Super Micro Computer, Inc. All rights reserved.

Extracting system information.......Done

Checking bundle source connection...Done

Checking command options and conflicts...Done

Preparing resources and downloading bundle files..Done

Validating metadata and file sets...Done

Starting firmware update operations...

Checking record target availability on local storage...Done
Host side interface can be reached.
BMC side interface can be reached.
Redfish Host Interface has already been enabled.

Getting the latest operation status...Done

BMC will be updated from [Link] to [Link]

Managed system...........[Link]
BMC UFFN.............BMC_X14AST2600-ROT20-
4501MS_20250906_01.03.02.00_STDsp.bin
BMC type.............X14_RoT2.0_ATEN_AST2600_2_1
BMC version..........[Link]
BMC build date.......2025/09/06
Local BMC image file...../root/saasvc/SaasvcUpdate/X14DBM-SP/X14DBM-
SP_20250912_01/firmwarePkg/BMC_X14AST2600-ROT20-
4501MS_20250906_01.03.02.00_STDsp.bin
BMC UFFN.............BMC_X14AST2600-ROT20-
4501MS_20250906_01.03.02.00_STDsp.bin
BMC type.............X14_RoT2.0_ATEN_AST2600_2_1
BMC version..........[Link]

SAA_SERVICE User's Guide Page 44

 BMC build date.......2025/09/06
FW image.............Signed

Status: Start updating BMC for [Link]

************************************WARNING*************************************
Do not remove AC power from the server.
********************************************************************************

Uploading FW........................................Done
Updating FW...>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>Done

Status: BMC is updated for [Link]

Update Complete. Please wait for BMC reboot, about 3 mins.

..................................................
..................................................
..................................................
...........................Done

Waiting 30 seconds to perform the next task................................Done

BIOS will be updated from 1.4 (2025/08/21) to 1.4 (2025/08/21)

Managed system...........[Link]
Board ID.............1D37
BIOS build date......2025/08/21
BIOS version.........1.4
Local BIOS image file..../root/saasvc/SaasvcUpdate/X14DBM-SP/X14DBM-
SP_20250912_01/firmwarePkg/BIOS_X14DBMS-1D37_20250821_1.4_STDsp.bin
Board ID.............1D37
BIOS build date......2025/08/21
BIOS version.........1.4
FW image.............Signed
Signed Key.......RoT

Status: Start updating BIOS for [Link]

************************************WARNING*************************************
Do not remove AC power from the server.
********************************************************************************

Uploading BIOS.....................................................
......Done
Preparing for updating BIOS.....................................................
.........................Done
Updating BIOS...>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>Done

Status: BIOS is updated for [Link]

Note: You have to reboot or power up the system for the changes to take effect

***************************<<<<<CRITICAL WARNING>>>>>***************************

SAA_SERVICE User's Guide Page 45

 ExitCode = 92
Description = Manual reboot is required
Program Error Code = 1025.29
Error message:
Please reboot the machine then use --continue option to do the next
process.

********************************************************************************

3. (Reboot machine) [SAA_SERVICE_HOME]# reboot now(After reboot)

4. [SAA_SERVICE_HOME]# ./saasvc -c LocalUpdate --continue

[root@localhost SAASVC_LOCAL]# ./saasvc -c LocalUpdate --continue

SAA Service (for UEFI BIOS) 2.0.0 (2025/11/19) (x86_64)
Copyright(C) 2024-2025 Super Micro Computer, Inc. All rights reserved.

Extracting system information.......Done

Checking bundle source connection...Done

Checking command options and conflicts...Done

Preparing resources and downloading bundle files..Done

Validating metadata and file sets...Done

Starting firmware update operations...

Checking record target availability on local storage...Done
Done enabling Redfish Host Interface.

Getting the latest operation status...Done

CPLD_MB(ID: 1) will be updated from 25 to 25

Managed system.....................[Link]
Motherboard CPLD 1 version.....F2.48.25
Local CPLD image file............../root/saasvc/SaasvcUpdate/X14DBM-SP/X14DBM-
SP_20250912_01/firmwarePkg/CPLD_X14DBM-SP-U28-
30XXF248_20250516_F2.48.25_STDsp.bin
CPLD UFFN......................CPLD_X14DBM-SP-
30XXF248_20250516_F2.48.25_STDsp.bin
CPLD ID........................F248
CPLD version...................F2.48.25
FW image.......................Signed

Status: Start updating CPLD for [Link]

************************************WARNING*************************************

SAA_SERVICE User's Guide Page 46

 Do not remove AC power from the server.
********************************************************************************

Uploading FW...Done

Note: System will be powered off shortly to continue the update process.

Warning: Please wait for the system to power on again. Do not remove AC power
before system reboot.

System shutdown command applied.

Ready to reboot the system after 30 seconds...

System reboot command applied.

***************************<<<<<CRITICAL WARNING>>>>>***************************

ExitCode = 98
Description = Manual continuing process after reboot
Program Error Code = 1025.18
Error message:
The system is going to reboot. Please use --continue option to do the
next process after reboot.

********************************************************************************

5. (Reboot machine) [SAA_SERVICE_HOME]# reboot now(After reboot)

6. [SAA_SERVICE_HOME]# ./saasvc -c LocalUpdate --continue

[root@localhost SAASVC_LOCAL]# ./saasvc -c LocalUpdate --continue

SAA Service (for UEFI BIOS) 2.0.0 (2025/11/19) (x86_64)
Copyright(C) 2024-2025 Super Micro Computer, Inc. All rights reserved.
Extracting system information.......Done

Checking bundle source connection...Done

Checking command options and conflicts...Done

Preparing resources and downloading bundle files..Done

Validating metadata and file sets...Done

Starting firmware update operations...

Checking record target availability on local storage...Done
Done enabling Redfish Host Interface.

Getting the latest operation status...Done

All firmware has been updated successfully.

SAA_SERVICE User's Guide Page 47

 Finished firmware update operations

Checking whether the current firmware matches the target firmware...........

All current firmware matches the target firmware.

7. A message “All firmware has been updated successfully.” appears.

3.9.2 Updating Individual Firmware

[Link] Updating Single Firmware via Individual Firmware Update

1. [SAA_SERVICE_HOME]# ./saasvc -c LocalUpdate --init --firmware BMC

(You can change any firmware by “--firmware <here>”)

[root@localhost SAASVC_LOCAL]# ./saasvc -c LocalUpdate --init --firmware BMC

SAA Service (for UEFI BIOS) 2.0.0 (2025/11/19) (x86_64)
Copyright(C) 2024-2025 Super Micro Computer, Inc. All rights reserved.

Extracting system information.......Done

Checking bundle source connection...Done

Checking command options and conflicts...Done

Preparing resources and downloading bundle files..Done

Validating metadata and file sets...Done

Preparing modules and tools for update tasks...Done

Starting to check for Redfish host interface...

Host side interface can be reached.
BMC side interface can be reached.
Redfish Host Interface has already been enabled.
Done

Generating operation list and update tasks...........Done

Starting firmware update operations...

Checking record target availability on local storage...Done

Getting the latest operation status...Done

Preparing operation list...Done

System Information:
Product Part Number........X14DBM-SP

SAA_SERVICE User's Guide Page 48

 Operation list information:
Signature..................57587d389716971d541f1d8e10bab71247eb4aa7
Recovery support...........No
Create time (UTC)..........2025-11-19T03:01:02+0000

Current firmware information:

BMC version................[Link]

Target firmware information:

BMC version................[Link]

Metadata X14DBM-SP_20250912_01 (target) update tasks:

Type.......................Target BMC
Version....................[Link]
Status.....................pending

Synchronizing update record files...Done

***************************<<<<<CRITICAL WARNING>>>>>***************************

ExitCode = 254
Description = Manual steps are required
Program Error Code = 1030.2
Error message:
Please use --continue option to do the next process.

********************************************************************************

2. [SAA_SERVICE_HOME]# ./saasvc -c LocalUpdate --continue

[root@localhost SAASVC LOCAL]# ./saasvc -c LocalUpdate --continue

SAA Service (for UEFI BIOS) 2.0.0 (2025/11/19) (x86_64)
Copyright(C) 2024-2025 Super Micro Computer, Inc. All rights reserved.

Extracting system information.......Done

Checking bundle source connection...Done

Checking command options and conflicts...Done

Preparing resources and downloading bundle files..Done

Validating metadata and file sets...Done

Starting firmware update operations...

Checking record target availability on local storage...Done
Host side interface can be reached.
BMC side interface can be reached.
Redfish Host Interface has already been enabled.

Getting the latest operation status...Done

SAA_SERVICE User's Guide Page 49

 BMC will be updated from [Link] to [Link]

Managed system...........[Link]
BMC UFFN.............BMC_X14AST2600-ROT20-
4501MS_20250906_01.03.02.00_STDsp.bin
BMC type.............X14_RoT2.0_ATEN_AST2600_2_1
BMC version..........[Link]
BMC build date.......2025/09/06
Local BMC image file...../root/saasvc/SaasvcUpdate/X14DBM-SP/X14DBM-
SP_20250912_01/firmwarePkg/BMC_X14AST2600-ROT20-
4501MS_20250906_01.03.02.00_STDsp.bin
BMC UFFN.............BMC_X14AST2600-ROT20-
4501MS_20250906_01.03.02.00_STDsp.bin
BMC type.............X14_RoT2.0_ATEN_AST2600_2_1
BMC version..........[Link]
BMC build date.......2025/09/06
FW image.............Signed

Status: Start updating BMC for [Link]

************************************WARNING*************************************
Do not remove AC power from the server.
********************************************************************************

Uploading FW........................................Done
Updating FW...>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>Done

Status: BMC is updated for [Link]

Update Complete. Please wait for BMC reboot, about 3 mins.

..................................................
..................................................
..................................................
...........................Done

Waiting 30 seconds to perform the next task.................................Done

All firmware has been updated successfully.

3. A message “All firmware has been updated successfully” appears.

[Link] Updating Multiple Firmware via Individual Firmware Update

1. [SAA_SERVICE_HOME]# ./saasvc -c LocalUpdate --init --firmware "BMC;BIOS"

(You can change any firmware type in “--firmware <here>”)

[root@localhost SAASVC_LOCAL]# ./saasvc -c LocalUpdate --init --firmware

"BMC;BIOS"

SAA_SERVICE User's Guide Page 50

SAA Service (for UEFI BIOS) 2.0.0 (2025/11/19) (x86_64)
Copyright(C) 2024-2025 Super Micro Computer, Inc. All rights reserved.

Extracting system information.......Done

Checking bundle source connection...Done

Checking command options and conflicts...Done

Preparing resources and downloading bundle files..Done

Validating metadata and file sets...Done

Preparing modules and tools for update tasks...Done

Starting to check for Redfish host interface...

Host side interface can be reached.
BMC side interface can be reached.
Redfish Host Interface has already been enabled.
Done

Generating operation list and update tasks..........Done

Starting firmware update operations...

Checking record target availability on local storage...Done

Getting the latest operation status...Done

Updating record files of last session...Done

Preparing operation list...Done

System Information:
Product Part Number........X14DBM-SP

Operation list information:

Signature..................89c47c694feb00ace0ea02794fcbff144aed5723
Recovery support...........No
Create time (UTC)..........2025-11-19T03:02:59+0000

Current firmware information:

BMC version................[Link]
BIOS version...............1.4 (2025/08/21)

Target firmware information:

BMC version................[Link]
BIOS version...............1.4 (2025/08/21)

Metadata X14DBM-SP_20250912_01 (target) update tasks:

Type.......................Target BMC
Version....................[Link]
Status.....................pending

SAA_SERVICE User's Guide Page 51

 Type.......................Target BIOS
Version....................1.4 (2025/08/21)
Status.....................pending

Synchronizing update record files...Done

***************************<<<<<CRITICAL WARNING>>>>>***************************

ExitCode = 254
Description = Manual steps are required
Program Error Code = 1030.2
Error message:
Please use --continue option to do the next process.

********************************************************************************

2. [SAA_SERVICE_HOME]# ./saasvc -c LocalUpdate --continue

[root@localhost SAASVC_LOCAL]# ./saasvc -c LocalUpdate --continue

SAA Service (for UEFI BIOS) 2.0.0 (2025/11/19) (x86_64)
Copyright(C) 2024-2025 Super Micro Computer, Inc. All rights reserved.

Extracting system information.......Done

Checking bundle source connection...Done

Checking command options and conflicts...Done

Preparing resources and downloading bundle files..Done

Validating metadata and file sets...Done

Starting firmware update operations...

Checking record target availability on local storage...Done
Host side interface can be reached.
BMC side interface can be reached.
Redfish Host Interface has already been enabled.

Getting the latest operation status...Done

BMC will be updated from [Link] to [Link]

Managed system...........[Link]
BMC UFFN.............BMC_X14AST2600-ROT20-
4501MS_20250906_01.03.02.00_STDsp.bin
BMC type.............X14_RoT2.0_ATEN_AST2600_2_1
BMC version..........[Link]
BMC build date.......2025/09/06
Local BMC image file...../root/saasvc/SaasvcUpdate/X14DBM-SP/X14DBM-
SP_20250912_01/firmwarePkg/BMC_X14AST2600-ROT20-

SAA_SERVICE User's Guide Page 52

4501MS_20250906_01.03.02.00_STDsp.bin
BMC UFFN.............BMC_X14AST2600-ROT20-
4501MS_20250906_01.03.02.00_STDsp.bin
BMC type.............X14_RoT2.0_ATEN_AST2600_2_1
BMC version..........[Link]
BMC build date.......2025/09/06
FW image.............Signed

Status: Start updating BMC for [Link]

************************************WARNING*************************************
Do not remove AC power from the server.
********************************************************************************

Uploading FW........................................Done
Updating FW...>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>Done

Status: BMC is updated for [Link]

Update Complete. Please wait for BMC reboot, about 3 mins.

..................................................
..................................................
..................................................
...........................Done

Waiting 30 seconds to perform the next task................................Done

BIOS will be updated from 1.4 (2025/08/21) to 1.4 (2025/08/21)

Managed system...........[Link]
Board ID.............1D37
BIOS build date......2025/08/21
BIOS version.........1.4
Local BIOS image file..../root/saasvc/SaasvcUpdate/X14DBM-SP/X14DBM-
SP_20250912_01/firmwarePkg/BIOS_X14DBMS-1D37_20250821_1.4_STDsp.bin
Board ID.............1D37
BIOS build date......2025/08/21
BIOS version.........1.4
FW image.............Signed
Signed Key.......RoT

Status: Start updating BIOS for [Link]

************************************WARNING*************************************
Do not remove AC power from the server.
********************************************************************************

Uploading BIOS.....................................................
......Done

Preparing for updating BIOS.....................................................

...............................Done

SAA_SERVICE User's Guide Page 53

 Updating BIOS...>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>Done

Status: BIOS is updated for [Link]

Note: You have to reboot or power up the system for the changes to take effect

***************************<<<<<CRITICAL WARNING>>>>>***************************

ExitCode = 92
Description = Manual reboot is required
Program Error Code = 1025.29
Error message:
Please reboot the machine then use --continue option to do the next
process.

********************************************************************************

3. (Reboot machine) [SAA_SERVICE_HOME]# reboot now (after reboot)

4. [SAA_SERVICE_HOME]# ./saasvc -c LocalUpdate --continue

[root@localhost SAASVC_LOCAL]# ./saasvc -c LocalUpdate --continue

SAA Service (for UEFI BIOS) 2.0.0 (2025/11/19) (x86_64)
Copyright(C) 2024-2025 Super Micro Computer, Inc. All rights reserved.
Extracting system information.......Done

Checking bundle source connection...Done

Checking command options and conflicts...Done

Preparing resources and downloading bundle files..Done

Validating metadata and file sets...Done

Starting firmware update operations...

Checking record target availability on local storage...Done
Done enabling Redfish Host Interface.

Getting the latest operation status...Done

All firmware has been updated successfully.

Finished firmware update operations

Checking whether the current firmware matches the target firmware........

All current firmware matches the target firmware.

5. A message “All firmware has been updated successfully” appears.

SAA_SERVICE User's Guide Page 54

3.10 Updating Firmware through Out-of-Band Method

SAA_SERVICE User's Guide Page 55

SAA_SERVICE User's Guide Page 56
Use the saasvc RemoteUpdate command to update firmware with ISO images stored in
the repository through the out-of-band method.

Bundle Update

Description: Updates firmware through out-of-band method.

Usage: ./saasvc -c RemoteUpdate -i <BMC IP> -u <BMC username> -p <BMC user
password> --reboot
*Optional: You can add either “--rollback <metadata version>” or “--forward” option, “--
poweron_check”[1] option, “--skip_curpkg_check” and “--rack_cfg”[2][3] option to the
command. You can find the option description in 3.7 Command Parameters.

Usage:
1. ./saasvc -c RemoteUpdate -i <BMC IP> -u <BMC username> -p <BMC user
password> --reboot --rollback <metadata version>
2. ./saasvc -c RemoteUpdate -i <BMC IP> -u <BMC username> -p <BMC user
password> --reboot --forward
3. ./saasvc -c RemoteUpdate -i <BMC IP> -u <BMC username> -p <BMC user
password> --reboot --forward --skip_curpkg_check
4. ./saasvc -c RemoteUpdate -i <BMC IP> -u <BMC username> -p <BMC user
password> --reboot --poweron_check
5. ./saasvc -c RemoteUpdate -i <BMC IP> -u <BMC username> -p <BMC user
password> --reboot --rack_cfg [Link]

Individual Update

Description: Updates firmware individually through out-of-band method.

Usage: ./saasvc -c RemoteUpdate -i <BMC IP> -u <BMC username> -p <BMC user
password> --reboot --firmware <firmware name(s)>
*Optional: You can add either the “--update_target <metadata version>” or “--rollback
<metadata version>” option, “--skip_depend_check”, and “--rack_cfg”[2][3] option to the
command. But “--skip_depend_check” can’t be used with “--rollback <metadata
version>”. You can find the option descriptions in 3.7 Command Parameters.

Usage:

SAA_SERVICE User's Guide Page 57

1. ./saasvc -c RemoteUpdate -i <BMC IP> -u <BMC username> -p <BMC user
password> --reboot --firmware <firmware name(s)> --skip_depend_check
2. ./saasvc -c RemoteUpdate -i <BMC IP> -u <BMC username> -p <BMC user
password> --reboot --firmware <firmware name(s)> --rollback <metadata version>
3. ./saasvc -c RemoteUpdate -i <BMC IP> -u <BMC username> -p <BMC user
password> --reboot --firmware <firmware name(s)> --update_target <metadata
version> --skip_depend_check
4. ./saasvc -c RemoteUpdate -i <BMC IP> -u <BMC username> -p <BMC user
password> --reboot --firmware <firmware name(s)> --update_target <metadata
version> --rack_cfg [Link]
5. ./saasvc -c RemoteUpdate -i <BMC IP> -u <BMC username> -p <BMC user
password> --reboot --firmware_cfg [Link]

Dry-run Update

Description: Simulates firmware update process through out-of-band method.

Usage: ./saasvc -c RemoteUpdate -i <BMC IP> -u <BMC username> -p <BMC user
password> --dry-run
*Optional: You can add either “--rollback <metadata version>” or “--forward” option, “--
poweron_check” [1] option, “--skip_curpkg_check” option, and “--rack_cfg”[2][3] option to
the command. You can find the option description in 3.7 Command Parameters.

Usage:
1. ./saasvc -c RemoteUpdate -i <BMC IP> -u <BMC username> -p <BMC user
password> --dry-run --rollback <metadata version>
2. ./saasvc -c RemoteUpdate -i <BMC IP> -u <BMC username> -p <BMC user
password> --dry-run --forward
3. ./saasvc -c RemoteUpdate -i <BMC IP> -u <BMC username> -p <BMC user
password> --dry-run --forward --skip_curpkg_check
4. ./saasvc -c RemoteUpdate -i <BMC IP> -u <BMC username> -p <BMC user
password> --dry-run --poweron_check
5. ./saasvc -c RemoteUpdate -i <BMC IP> -u <BMC username> -p <BMC user
password> --dry-run --rack_cfg [Link]

SAA_SERVICE User's Guide Page 58

[1] To update the main and (right/left) side switchboard CPLD, the system must be in the
power-on state. Therefore, you must use the --poweron_check option to power on the
system.

[2] To update the chassis node(Power Shelf and NVLink Switch etc), the system must
have compute tray nodes. Therefore, you must use the --rack_cfg option to set the
related informatinon in the rack configuration file.

[3] If the managed system is a compute node, the --rack_cfg option is not required.

[4] If the managed system is a chassis, include the chassis information and at least one
compute node information in the rack configuration file.

3.10.1 Updating Firmware Bundle

1. [SAA_SERVICE_HOME]# ./saasvc -i <BMC IP> -u <BMC Username> -p <BMC

Password> -c RemoteUpdate --reboot

Note that the provided IP address below is only an example; when executing the
command, you should use the actual target IP address.

[SAA_SERVICE_HOME]$ sudo ./saasvc -i <BMC IP> -u <BMC Username> -p <BMC Password>

-c RemoteUpdate --reboot
SAA Service (for UEFI BIOS) 2.0.0 (2025/11/19) (x86_64)
Copyright(C) 2024-2025 Super Micro Computer, Inc. All rights reserved.

Extracting SKU machine name...................Done

Checking bundle source connection...Done

Checking command options and conflicts...Done

Preparing resources and downloading bundle files..Done

Validating metadata and file sets...Done

Generating operation list and update tasks.............Done

Starting firmware update operations...

System Information:
Product Part Number..................................X14DBM-SP

Operation list information:

SAA_SERVICE User's Guide Page 59

 Signature............................................N/A
Recovery support.....................................Yes
Create time (UTC)....................................N/A

Current firmware information:

BMC (pcb revision: 0123456789) version...............[Link]
BIOS (pcb revision: 0123456789) version..............1.4 (2025/08/21)
CPLD_MB (ID: 1, pcb revision: 0123456789) version....25

Target firmware information:

BMC (pcb revision: 0123456789) version...............[Link]
BIOS (pcb revision: 0123456789) version..............1.4 (2025/08/21)
CPLD_MB (ID: 1, pcb revision: 0123456789) version....25

Metadata X14DBM-SP_20250912_01 (target) update tasks:

Type.................................................Target BMC
pcb revision.........................................0123456789
Version..............................................[Link]
Status...............................................pending

Type.................................................Target BIOS
pcb revision.........................................0123456789
Version..............................................1.4 (2025/08/21)
Status...............................................pending

Type.................................................Target CPLD_MB
Index................................................1
pcb revision.........................................0123456789
Version..............................................25
Status...............................................pending

Target BMC: BMC_X14AST2600-ROT20-4501MS_20250906_01.03.02.00_STDsp.bin will be

updated
........
Managed system...........[Link]
BMC UFFN.............BMC_X14AST2600-ROT20-
4501MS_20250906_01.03.02.00_STDsp.bin
BMC type.............X14_RoT2.0_ATEN_AST2600_2_1
BMC version..........[Link]
BMC build date.......2025/09/06
Local BMC image file....../SaasvcUpdate/X14DBM-SP/X14DBM-
SP_20250912_01/firmwarePkg/BMC_X14AST2600-ROT20-
4501MS_20250906_01.03.02.00_STDsp.bin
BMC UFFN.............BMC_X14AST2600-ROT20-
4501MS_20250906_01.03.02.00_STDsp.bin
BMC type.............X14_RoT2.0_ATEN_AST2600_2_1
BMC version..........[Link]
BMC build date.......2025/09/06
FW image.............Signed

Status: Start updating BMC for [Link]

SAA_SERVICE User's Guide Page 60

************************************WARNING*************************************
Do not remove AC power from the server.
********************************************************************************

Uploading
FW..........................................................................Done
Updating FW.........
....>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>Done

Status: BMC is updated for [Link]

Update Complete. Please wait for BMC reboot, about 3 mins.

.................................................................................
...........
.......
.................................................................................
.............
......
.................................................................................
.............
......
.......................................................Done

Sleeping for 30 seconds for next update.........................................

....................Done
.....
Target BIOS: BIOS_X14DBMS-1D37_20250821_1.4_STDsp.bin will be updated
.........

Managed system...........[Link]
Board ID.............1D37
BIOS build date......2025/08/21
BIOS version.........1.4
Local BIOS image file...../SaasvcUpdate/X14DBM-SP/X14DBM-
SP_20250912_01/firmwarePkg/BIOS_X14DBMS-1D37_20250821_1.4_STDsp.bin
Board ID.............1D37
BIOS build date......2025/08/21
BIOS version.........1.4
FW image.............Signed
Signed Key.......RoT

Status: Start updating BIOS for [Link]

************************************WARNING*************************************
Do not remove AC power from the server.
********************************************************************************

Uploading BIOS.......................................................
...............................................
.......Done
Preparing for updating BIOS.................................................
.....................................................
................................................

SAA_SERVICE User's Guide Page 61

............Done
Updating BIOS>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>Done

Rebooting target system......................................................Done

Status: The managed system [Link] is waiting for POST complete

.........
Status: OEM

.......
...........
Status: MemoryInitializationStarted

........................................................................
..................
.................................................................................
.
..................
.....
Status: PCIResourceConfigStarted

.................................................
Status: OEM

............................
.......
Status: MemoryInitializationStarted

...........
.................................................................................
.
..................
...
Status: PCIResourceConfigStarted

.....................................
Status: OEM

.....................................
Status: MemoryInitializationStarted

.....
..................
.................................................................................
Status: PCIResourceConfigStarted

.
..................
............................
Status: The managed system [Link] is POST completed

SAA_SERVICE User's Guide Page 62

Status: BIOS is updated for [Link]

.............
Checking CPLD_MB(ID:1) available.....Done
..
Target CPLD_MB: CPLD_X14DBM-SP-U28-30XXF248_20250516_F2.48.25_STDsp.bin will be
updated
..

Managed system.....................[Link]
Motherboard CPLD 1 version.....F2.48.25
Local CPLD image file.............../SaasvcUpdate/X14DBM-SP/X14DBM-
SP_20250912_01/firmwarePkg/CPLD_X14DBM-SP-U28-
30XXF248_20250516_F2.48.25_STDsp.bin
CPLD UFFN......................CPLD_X14DBM-SP-
30XXF248_20250516_F2.48.25_STDsp.bin
CPLD ID........................F248
CPLD version...................F2.48.25
FW image.......................Signed
.............
Status: Start updating CPLD for [Link]

************************************WARNING*************************************
Do not remove AC power from the server.
********************************************************************************

Uploading FW.....Done

Preparing for updating CPLD.....

..........................................Done

Updating FW......>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>Done
Update Complete, Please wait for BMC reboot, about 1.5 mins
......................................................
.............................................
........................................................
............................................
...................................Done

Rebooting target system.......................

..................................................Done

Status: The managed system [Link] is waiting for POST complete

Status: OEM

....................................
Status: MemoryInitializationStarted

..............
.....................................

SAA_SERVICE User's Guide Page 63

 Status: MemoryInitializationStarted

............
....................................................
................................................
............
Status: PCIResourceConfigStarted

........................................
.....
Status: The managed system [Link] is POST completed

.
Status: CPLD is updated for [Link]

Checking CPLD_MB(ID:1) available....Done

.Finished firmware update operations

All current firmware is already up-to-date.

3.10.2 Updating Individual Firmware

1. [SAA_SERVICE_HOME]# ./saasvc -i <BMC IP> -u <BMC Username> -p <BMC

Password> -c RemoteUpdate --firmware BIOS --reboot

Note that the provided IP address below is only an example; when executing the
command, you should use the actual target IP address

[SAA_SERVICE_HOME]$ sudo ./saasvc -i [Link] -u username -p password -c

RemoteUpdate --firmware BIOS --reboot
SAA Service (for UEFI BIOS) 2.0.0 (2025/11/19) (x86_64)
Copyright(C) 2024-2025 Super Micro Computer, Inc. All rights reserved.
Extracting SKU machine name....................Done

Checking bundle source connection...Done

Checking command options and conflicts...Done

Preparing resources and downloading bundle files..Done

Validating metadata and file sets...Done

Generating operation list and update tasks.............Done

Starting firmware update operations...

System Information:
Product Part Number..................................X14DBM-SP

SAA_SERVICE User's Guide Page 64

Operation list information:
Signature............................................N/A
Recovery support.....................................No
Create time (UTC)....................................N/A

Current firmware information:

BIOS (pcb revision: 0123456789) version..............1.4 (2025/08/21)

Target firmware information:

BIOS (pcb revision: 0123456789) version..............1.4 (2025/08/21)

Metadata X14DBM-SP_20250912_01 (target) update tasks:

Type.................................................Target BIOS
pcb revision.........................................0123456789
Version..............................................1.4 (2025/08/21)
Status...............................................pending

Target BIOS: BIOS_X14DBMS-1D37_20250821_1.4_STDsp.bin will be updated

............

Managed system...........[Link]
Board ID.............1D37
BIOS build date......2025/08/21
BIOS version.........1.4
Local BIOS image file...../SaasvcUpdate/X14DBM-SP/X14DBM-
SP_20250912_01/firmwarePkg/BIOS_X14DBMS-1D37_20250821_1.4_STDsp.bin
Board ID.............1D37
BIOS build date......2025/08/21
BIOS version.........1.4
FW image.............Signed
Signed Key.......RoT

Status: Start updating BIOS for [Link]

************************************WARNING*************************************
Do not remove AC power from the server.
********************************************************************************

Uploading
BIOS.............................................................................
.
.........................
...........Done
Preparing for updating
BIOS...................................................................
...................................
...........................................................Done
Updating BIOS>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>Done

Rebooting target system...............

......................................Done

SAA_SERVICE User's Guide Page 65

Status: The managed system [Link] is waiting for POST complete

Status: OEM

.................................
Status: MemoryInitializationStarted

.............................
.....................................
................................................................
....................................
.............................
Status: PCIResourceConfigStarted

...................................
..............
Status: OEM

......................
............
Status: MemoryInitializationStarted

....................................................
....................................
............................
Status: PCIResourceConfigStarted

....................................

Status: OEM

....................................

Status: MemoryInitializationStarted

................................................................
....................................
.........
Status: PCIResourceConfigStarted

...........................................
Status: The managed system [Link] is POST completed

.
Status: BIOS is updated for [Link]

.....
.......Finished firmware update operations

All current firmware is already up-to-date.

SAA_SERVICE User's Guide Page 66

3.11 Updating Firmware through Remote In-Band/RHI
Method

Use the saasvc RemoteUpdate command on a single-managed system with its OS

login information (--oi, --ou, and --op options) to update bundled or individual firmware

SAA_SERVICE User's Guide Page 67

through remote in-band method via SSH. With this command, firmware updates can be
executed automatically.

For systems supporting RHI (Redfish Host Interface), in addition to the OS login
information, you need to add the BMC username (-u) and password (-p) options to the
command.

If you update firmware on a single system through remote In-band/RHI method,

executing saasvc with the “-I < Remote_INB or Remote_RHI >” option is not necessary.
However, if you want to update firmware on multiple systems using the remote In-
band/RHI method, executing saasvc with the “-I < Remote_INB or Remote_RHI >”
option is necessary.

If you update firmware on a single system through remote In-band/RHI method using
SAA Service backend proxy server as RepositorySource, executing saasvc with the "-
bu <username> --bp-stdin or --bp-stdin" is necessary.

Firmware Bundle Update

Description: Updates firmware through remote In-band / RHI method.

Usage: ./saasvc -c RemoteUpdate -I <Remote_INB / Remote_RHI> --oi <OS IP> --ou
<OS username> --op <OS user password> -u <BMC username> -p <BMC user
password> (only for Remote_RHI) --reboot
*Optional: You can add either the “--forward” or “--rollback <metadata version>” option,
and “--skip_curpkg_check” option to the command. You can find the option description
in 3.7 Command Parameters.

Usage:
1. ./saasvc -c RemoteUpdate -I <Remote_INB / Remote_RHI> --oi <OS IP> --ou
<OS username> --op <OS user password> -u <BMC username> -p <BMC user
password> (only for Remote_RHI) --reboot --rollback <metadata version>
2. ./saasvc -c RemoteUpdate -I <Remote_INB / Remote_RHI> --oi <OS IP> --ou
<OS username> --op <OS user password> -u <BMC username> -p <BMC user
password> (only for Remote_RHI) --reboot --forward
3. ./saasvc -c RemoteUpdate -I <Remote_INB / Remote_RHI> --oi <OS IP> --ou
<OS username> --op <OS user password> -u <BMC username> -p <BMC user

SAA_SERVICE User's Guide Page 68

 password> (only for Remote_RHI) --reboot --forward --skip_curpkg_check
4. ./saasvc -c RemoteUpdate -I <Remote_INB / Remote_RHI> --oi <OS IP> --ou
<OS username> --op <OS user password> -u <BMC username> -p <BMC user
password> (only for Remote_RHI) --reboot -bu <username> --bp-stdin
5. iv. ./saasvc -c RemoteUpdate -I <Remote_INB / Remote_RHI> --oi <OS IP> --ou
<OS username> --op <OS user password> -u <BMC username> -p <BMC
user password> (only for Remote_RHI) --reboot -bu <username> --bp
<backend_password>

Firmware Bundle Dry-run Update

Description: Simulates firmware bundle update process through remote In-band / RHI
method.
Usage: ./saasvc -c RemoteUpdate -I <Remote_INB / Remote_RHI> --oi <OS IP> --ou
<OS username> --op <OS user password> -u <BMC username> -p <BMC user
password> (only for Remote_RHI) --dry-run
*Optional: You can add either the “--forward” or “--rollback <metadata version>” option,
and “--skip_curpkg_check” option to the command. You can find the option description
in 3.7 Command Parameters.

Usage:
1. ./saasvc -c RemoteUpdate -I <Remote_INB / Remote_RHI> --oi <OS IP> --ou
<OS username> --op <OS user password> -u <BMC username> -p <BMC user
password> (only for Remote_RHI) --dry-run --rollback <metadata version>
2. ./saasvc -c RemoteUpdate -I <Remote_INB / Remote_RHI> --oi <OS IP> --ou
<OS username> --op <OS user password> -u <BMC username> -p <BMC user
password> (only for Remote_RHI) --dry-run --forward
3. ./saasvc -c RemoteUpdate -I <Remote_INB / Remote_RHI> --oi <OS IP> --ou
<OS username> --op <OS user password> -u <BMC username> -p <BMC user
password> (only for Remote_RHI) --dry-run --forward --skip_curpkg_check

Individual Firmware Update

Description: Updates individual firmware through remote In-band / RHI method.

Usage: ./saasvc -c RemoteUpdate -I <Remote_INB / Remote_RHI> --oi <OS IP> --ou
<OS username> --op <OS user password> -u <BMC username> -p <BMC user

SAA_SERVICE User's Guide Page 69

password> (only for Remote_RHI) --firmware <firmware name(s)> --reboot
*Optional: You can add the “--rollback <metadata version>” option to the command.
You can find the option description in 3.7 Command Parameters.

Individual Firmware Dry-run Update

Description: Simulates the individual firmware update process through the remote In-
band / RHI method.
Usage: ./saasvc -c RemoteUpdate -I <Remote_INB / Remote_RHI> --oi <OS IP> --ou
<OS username> --op <OS user password> -u <BMC username> -p <BMC user
password> (only for Remote_RHI) --dry-run
*Optional: You can add the “--rollback <metadata version>” option to the command.
You can find the option description in 3.7 Command Parameters.

1. [SAA_SERVICE_HOME]# ./saasvc --oi <OS IP> --ou <OS Username> --op <OS
Password> -u <BMC username> -p <BMC user password> -c RemoteUpdate --
reboot

[SAA_SERVICE_HOME]$ sudo ./saasvc --oi [Link] --ou <OS Username> --op <OS
Password> -u <BMC username> -p <BMC user password> -c
RemoteUpdate --reboot

SAA Service (for UEFI BIOS) 2.0.0 (2025/11/20) (x86_64)

Copyright(C) 2024-2025 Super Micro Computer, Inc. All rights reserved.

Checking command options and conflicts...Done

Starting firmware update operations...

Verifying if the managed system supports update via Remote_INB/Remote_RHI method.

Sending required files to [Link].....................Done

==========[Begins of Initialization Output]==========

.SAA Service (for UEFI BIOS) 2.0.0 (2025/11/20) (x86_64)

Copyright(C) 2024-2025 Super Micro Computer, Inc. All rights reserved.
Journal created:
/root/journal/supermicro/saasvc/journal_253969.txt
/root/journal/supermicro/saasvc/saasvc_journal_253969_2025-11-19_13-39-
[Link]

Extracting system information...........Done

Checking bundle source connection...Done

SAA_SERVICE User's Guide Page 70

Checking command options and conflicts....Done

Preparing resources and downloading bundle files..Done

Validating metadata and file sets....Done

Preparing modules and tools for update tasks.....Done

Starting to check for Redfish host interface...

..Host side interface can be reached.
BMC side interface can be reached.
Redfish Host Interface has already been enabled.
Done

Generating operation list and update tasks......................Done

Starting firmware update operations...

Checking record target availability on local storage....Done

Getting the latest operation status...Done

Updating record files of last session...Done

Preparing operation list....Done

System Information:
Product Part Number........X14DBM-SP

Operation list information:

Signature..................f2f1146dd2027593682fba0699b5e526e7fe05b1
Recovery support...........Yes
Create time (UTC)..........2025-11-19T05:39:35+0000

Current firmware information:

BMC version................[Link]
BIOS version...............1.4 (2025/08/21)
CPLD_MB (ID: 1) version....25

Target firmware information:

BMC version................[Link]
BIOS version...............1.4 (2025/08/21)
CPLD_MB (ID: 1) version....25

Metadata X14DBM-SP_20250912_01 (target) update tasks:

Type.......................Target BMC
Version....................[Link]
Status.....................pending

Type.......................Target BIOS
Version....................1.4 (2025/08/21)
Status.....................pending

SAA_SERVICE User's Guide Page 71

 Type.......................Target CPLD_MB
Index......................1
Version....................25
Status.....................pending

Synchronizing update record files...Done

***************************<<<<<CRITICAL WARNING>>>>>***************************

ExitCode = 254
Description = Manual steps are required
Program Error Code = 1030.2
Error message:
Please use --continue option to do the next process.

********************************************************************************

============[Ends of Initialization Output]==========

Execute via Remote_INB/Remote_RHI method.

Waiting 30 seconds before continue to update on

[Link]....................................
..........................Done

===========[Begins of Update Output]===========

.....................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
.............................
============[End of Update Output]============

Waiting 30 seconds before continue to update on

[Link].............................................
................Done

===========[Begins of Update Output]===========

SAA_SERVICE User's Guide Page 72

SAA Service (for UEFI BIOS) 2.0.0 (2025/11/20) (x86_64)
Copyright(C) 2024-2025 Super Micro Computer, Inc. All rights reserved.
Journal created:
/root/journal/supermicro/saasvc/journal_261261.txt
/root/journal/supermicro/saasvc/saasvc_journal_261261_2025-11-19_13-40-
[Link]

Extracting system information.......Done

Checking bundle source connection...Done

Checking command options and conflicts...Done

Preparing resources and downloading bundle files..Done

Validating metadata and file sets...Done

Starting firmware update operations...

Checking record target availability on local storage...Done
Host side interface can be reached.
BMC side interface can be reached.
Redfish Host Interface has already been enabled.

Getting the latest operation status...Done

BMC will be updated from [Link] to [Link]

Managed system...........[Link]
BMC UFFN.............BMC_X14AST2600-ROT20-
4501MS_20250906_01.03.02.00_STDsp.bin
BMC type.............X14_RoT2.0_ATEN_AST2600_2_1
BMC version..........[Link]
BMC build date.......2025/09/06
Local BMC image file...../root/supermicro/saasvc_RemoteFile/SaasvcUpdate/X14DBM-
SP/X14DBM-SP_20250912_01/firmwarePkg/BMC_X14AST2600-ROT20-
4501MS_20250906_01.03.02.00_STDsp.bin
BMC UFFN.............BMC_X14AST2600-ROT20-
4501MS_20250906_01.03.02.00_STDsp.bin
BMC type.............X14_RoT2.0_ATEN_AST2600_2_1
BMC version..........[Link]
BMC build date.......2025/09/06
FW image.............Signed

Status: Start updating BMC for [Link]

************************************WARNING*************************************
Do not remove AC power from the server.
********************************************************************************

Uploading FW........................................Done
Updating FW...>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>Done

Status: BMC is updated for [Link]

SAA_SERVICE User's Guide Page 73

Update Complete. Please wait for BMC reboot, about 3 mins.
..................................................
..................................................
..................................................
...........................Done

Waiting 30 seconds to perform the next task................................Done

BIOS will be updated from 1.4 (2025/08/21) to 1.4 (2025/08/21)

Managed system...........[Link]
Board ID.............1D37
BIOS build date......2025/08/21
BIOS version.........1.4
Local BIOS image file..../root/supermicro/saasvc_RemoteFile/SaasvcUpdate/X14DBM-
SP/X14DBM-SP_20250912_01/firmwarePkg/BIOS_X14DBMS-1D37_20250821_1.4_STDsp.bin
Board ID.............1D37
BIOS build date......2025/08/21
BIOS version.........1.4
FW image.............Signed
Signed Key.......RoT

Status: Start updating BIOS for [Link]

************************************WARNING*************************************
Do not remove AC power from the server.
********************************************************************************

Uploading BIOS.....................................................
.....Done
Preparing for updating BIOS.....................................................
............................Done
Updating BIOS...>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>Done

Status: BIOS is updated for [Link]

Note: You have to reboot or power up the system for the changes to take effect

***************************<<<<<CRITICAL WARNING>>>>>***************************

ExitCode = 92
Description = Manual reboot is required
Program Error Code = 1025.29
Error message:
Please reboot the machine then use --continue option to do the next
process.

********************************************************************************

.................
============[End of Update Output]============

SAA_SERVICE User's Guide Page 74

SAA Service (for UEFI BIOS) 2.0.0 (2025/11/20) (x86_64)
Copyright(C) 2024-2025 Super Micro Computer, Inc. All rights reserved.
Journal created:
/root/journal/supermicro/saasvc/journal_352110.txt
/root/journal/supermicro/saasvc/saasvc_journal_352110_2025-11-19_13-51-
[Link]

Extracting system information.......Done

Checking bundle source connection...Done

Checking command options and conflicts...Done

Preparing resources and downloading bundle files..Done

Validating metadata and file sets...Done

Starting firmware update operations...

Checking record target availability on local storage...Done
Host side interface can be reached.
BMC side interface can be reached.
Redfish Host Interface has already been enabled.

Getting the latest operation status...Done

CPLD_MB(ID: 1) will be updated from 25 to 25

********************************<<<<<ERROR>>>>>*********************************

ExitCode = 5
Description = Missing option
Program Error Code = 505.6
Error message:
--reboot/--poweroff option is required because CPLD can only be updated
in power-off status on this system.

********************************************************************************

***************************<<<<<CRITICAL WARNING>>>>>***************************

ExitCode = 97
Description = Confirmation of automatic rebooting system
Program Error Code = 1025.21
Error message:
In the following process, the update tool will reboot the system. If the
system allows the tool to reboot, please use --continue and --reboot options
to do the next process.

********************************************************************************

SAA_SERVICE User's Guide Page 75

Waiting 180 seconds to confirm [Link] is
rebooting.....................................................
.................................................
....................................................
................................................
....................................................
................................................
....................................................
..Done

Checking if [Link] completes the reboot process within 60

seconds..........................................................................
...........................
.................................................Done
Waiting 30 seconds before continue to update on [Link].............
................................................Done

===========[Begins of Update Output]===========

SAA Service (for UEFI BIOS) 2.0.0 (2025/11/19) (x86_64)

Copyright(C) 2024-2025 Super Micro Computer, Inc. All rights reserved.
Journal created:
/root/journal/supermicro/saasvc/journal_149515.txt
/root/journal/supermicro/saasvc/saasvc_journal_149515_2025-11-19_16-22-
[Link]

Extracting system information.......Done

Checking bundle source connection...Done

Checking command options and conflicts...Done

Preparing resources and downloading bundle files..Done

Validating metadata and file sets...Done

Starting firmware update operations...

Checking record target availability on local storage...Done
Host side interface can be reached.
BMC side interface can be reached.
Redfish Host Interface has already been enabled.

Getting the latest operation status...Done

CPLD_MB(ID: 1) will be updated from 25 to 25

Managed system.....................[Link]
Motherboard CPLD 1 version.....F2.48.25
Local CPLD image
file............../root/supermicro/saasvc_RemoteFile/SaasvcUpdate/X14DBM-
SP/X14DBM-SP_20250912_01/firmwarePkg/CPLD_X14DBM-SP-U28-
30XXF248_20250516_F2.48.25_STDsp.bin

SAA_SERVICE User's Guide Page 76

 CPLD UFFN......................CPLD_X14DBM-SP-
30XXF248_20250516_F2.48.25_STDsp.bin
CPLD ID........................F248
CPLD version...................F2.48.25
FW image.......................Signed

Status: Start updating CPLD for [Link]

************************************WARNING*************************************
Do not remove AC power from the server.
********************************************************************************

Uploading FW...Done

Note: System will be powered off shortly to continue the update process.

Warning: Please wait for the system to power on again. Do not remove AC power
before system reboot.

System shutdown command applied.

Ready to reboot the system after 30 seconds...

System reboot command applied.

***************************<<<<<CRITICAL WARNING>>>>>***************************

ExitCode = 98
Description = Manual continuing process after reboot
Program Error Code = 1025.18
Error message:
The system is going to reboot. Please use --continue option to do the
next process after reboot.

********************************************************************************

...............
============[End of Update Output]============

Waiting 180 seconds to confirm [Link] is

rebooting.........................
.............................................................................
........................
............................................................................
........................
............................................................................
........................
..............................Done

Checking if [Link] completes the reboot process within 100 seconds....Done

SAA_SERVICE User's Guide Page 77

 Waiting 30 seconds before continue to update on
[Link]..............................................................Done

===========[Begins of Update Output]===========

SAA Service (for UEFI BIOS) 2.0.0 (2025/11/19) (x86_64)

Copyright(C) 2024-2025 Super Micro Computer, Inc. All rights reserved.
Journal created:
/root/journal/supermicro/saasvc/journal_7803.txt
/root/journal/supermicro/saasvc/saasvc_journal_7803_2025-11-19_16-[Link]

Extracting system information.......Done

Checking bundle source connection...Done

Checking command options and conflicts...Done

Preparing resources and downloading bundle files..Done

Validating metadata and file sets...Done

Starting firmware update operations...

Checking record target availability on local storage...Done
Done enabling Redfish Host Interface.

Getting the latest operation status...Done

All firmware has been updated successfully.

Finished firmware update operations

Starting firmware update verification...

Checking whether the current firmware matches the target firmware.

All current firmware matches the target firmware.

Firmware update verification completed
....
.........
============[End of Update Output]============

Finished firmware update operations

3.12 Updating Firmware on Multiple Systems

For managing multiple systems, use the “-l” option to simultaneously execute
commands on multiple systems enumerated in a system list file.

To set up system list file, follow these steps.

SAA_SERVICE User's Guide Page 78

 Update Firmware on Multiple Systems

Description: Updates firmware on multiple systems.

Usage:

1. ./saasvc -c RemoteUpdate -I <OOB / Remote_INB / Remote_RHI> -l <system list

file> --reboot
2. ./saasvc -c RemoteUpdate -l <system list file> --reboot (No-specific-interface)
*Optional: You can add either the “--rollback <metadata version>” or “--forward”
option or “--skip_curpkg_check” option, and “--rack_cfg” option to the command.
You can find the option description in 3.7 Command Parameters.

Dry-run Firmware Update on Multiple Systems

Description: Simulates a firmware update on multiple systems.

Usage:

1. ./saasvc -c RemoteUpdate -I <OOB / Remote_INB / Remote_RHI> -l <system list

file> --dry-run
2. ./saasvc -c RemoteUpdate -l <system list file> --reboot (No-specific-interface)
*Optional: You can add either the “--rollback <metadata version>” or “--forward”
option or “--skip_curpkg_check” option, and “--rack_cfg” option to the command.
You can find the option description in 3.7 Command Parameters.

Updates CMM with Blade

Description: Updates firmware on both CMM and Blade.

Usage:

1. ./saasvc -c RemoteUpdate -I <OOB> -l <system list file> --blade_list <blade list file>
--reboot
2. ./saasvc -c RemoteUpdate -l <system list file> --blade_list <blade list file> --reboot
(No-specific-interface) *Optional: You can add the the “--forward” or “--
skip_curpkg_check” option to the command. You can find the option description in
3.7 Command Parameters.

Updating CMM with Blade Dry-run

SAA_SERVICE User's Guide Page 79

Description: Simulates the firmware update on both CMM and Blade.
Usage:

1. ./saasvc -c RemoteUpdate -I <OOB> -l <system list file> --blade_list <blade list file>
--dry-run
2. ./saasvc -c RemoteUpdate -l <system list file> --blade_list <blade list file> --dry-run
(No-specific-interface) *Optional: You can add the “--forward” or “--
skip_curpkg_check” option to the command. You can find the option description in
3.7 Command Parameters.

Note:
IPs or hostnames of the managed systems in the system list file cannot
be repeated.

Different interfaces have various formats for their system lists. The following will
introduce the differences between these interfaces. You can use the “-I” option to switch
between them.

The available interface options are OOB (out-of-band), Remote In-Band (Remote_INB),
and Remote RHI (Remote_RHI). While setting a specific interface, the system list file
must follow the format of the specified interface. The managed systems should be
enumerated row by row in the system list file. The format example is provided below.

If no interface is specified, you need to provide all information in the system list. The
RemoteUpdate command will verify the interfaces and update with the available one.
Currently, OOB has the highest priority followed by Remote In-Band and Remote RHI.

Interface System List Format

OOB BMC_IP/CMM_IP
BMC_Username/CMM_Username
BMC_Password/CMM_Password

OOB with --rack_cfg option @RackName

Remote In-Band OS_IP

OS_Username

SAA_SERVICE User's Guide Page 80

 OS_Password

Remote RHI OS_IP

OS_Username
OS_Password
BMC_Username
BMC_Password

No-Specific-Interface BMC_IP
BMC_Username
BMC_Password
OS_IP
OS_Username
OS_Password

The “--blade_list” option can only be supported by updating a CMM with -l <system list
file> option. The blade systems to be updated with CMM should be enumerated row-by-
row in the blade list file. See the blade list example below.

Format: Blade_BMC_IP Blade_BMC_Username Blade_BMC_Password

Example:

[SAA_SERVICE_HOME]# ./saasvc -I OOB -l [Link] -c RemoteUpdate --reboot

[Link] (For OOB):

[Link] ADMIN1 PASSWORD1
[Link] ADMIN2 PASSWORD2

[SAA_SERVICE_HOME]# ./saasvc -I OOB -l [Link] -c RemoteUpdate --reboot --

rack_cfg [Link]

[Link] (For OOB):

@RackNameA
@RackNameB

Note: When using OOB interface with the --rack_cfg option, rack names in the
system list file must be prefixed with the @ symbol (e.g., @RackNameA). Each rack
name in the system list file (e.g., @RackNameA ) will be matched against the RackName

SAA_SERVICE User's Guide Page 81

field in the [Link] file. Only the nodes associated to the matched racks will be
updated.

[SAA_SERVICE_HOME]# ./saasvc -I Remote_INB -l [Link] -c RemoteUpdate --

reboot

[Link] (For Remote In-Band):

[Link] root1 111111
[Link] root2 222222

[SAA_SERVICE_HOME]# ./saasvc -I Remote_RHI -l [Link] -c RemoteUpdate --

reboot

[Link] (For Remote RHI):

[Link] root1 111111 ADMIN1 PASSWORD1
[Link] root2 222222 ADMIN2 PASSWORD2

[SAA_SERVICE_HOME]# ./saasvc -l [Link] -c RemoteUpdate --reboot

[Link] (For No-Specific-Interface):

[Link] ADMIN1 PASSWORD1 [Link] root1 111111
[Link] ADMIN2 PASSWORD2 [Link] root2 222222

[SAA_SERVICE_HOME]# ./saasvc -I OOB -l [Link] -c RemoteUpdate --blade_list

[Link] --reboot

[Link]:
[Link] ADMIN1 PASSWORD1
[Link] ADMIN2 PASSWORD2

[Link]:
[Link] ADMIN1 PASSWORD1
[Link] ADMIN2 PASSWORD2

[SAA_SERVICE_HOME]# ./saasvc -l [Link] -c RemoteUpdate --blade_list

[Link] --reboot

SAA_SERVICE User's Guide Page 82

[Link]:
[Link] ADMIN1 PASSWORD1
[Link] ADMIN2 PASSWORD2

[Link]:
[Link] ADMIN1 PASSWORD1 [Link] root1 111111
[Link] ADMIN2 PASSWORD2 [Link] root2 222222

Notes:
Repeated managed system IPs or names in the blade list file are not
allowed.
To update a CMM with a blade list, all blades in the list must be
successfully updated first.
For details on the “RemoteUpdate” command, see the note in 3.10
Updating Firmware through Out-of-Band Method.

SAA_SERVICE User's Guide Page 83

4. Secure Erase

SecureErase is a command that allows you to erase disks and ensure data cannot be
recovered.

4.1 Command Parameters

(Required) --list: Lists all disks and RAID of the managed system.
(Required) --erase_file: Erases disks and RAID listed in the specified file.
(Required) --erase_id: Erases a single disk with the specified ID enumerated by --
list.
(Optional) --file: Saves the disks or RAID information listed by --list to a file.
(Optional) --current_password: Checks the current BIOS Administrator password.
(Optional) --overwrite: Overwrites the output file specified by --file.
(Optional) --reboot: Forces the managed system to reboot or power up after
operation.
(Optional) --cur_pw_file: The specified file path to read the current password.
(Optional) --psid: Enters the PSID for erasing disk if it's supported.
(Optional) --disk_pwd: Enters the disk's password for erasing the disk (if
supported).

4.2 Listing Disk Information

To use SecureErase function on a system, you may need to identify its disks. You can
use this command to display a disk list or output it as a file.

Lists Disk Information

Description: Lists all disks including the RAID of the managed system.
Usage:

SAA_SERVICE User's Guide Page 84

1. ./ saasvc -l <system list file> -c SecureErase --list
2. ./ saasvc -i <BMC IP> -u <BMC username> -p <BMC user password> -c
SecureErase --list *Optional: You can add either the “--current_password <BIOS
password>” or “--cur_pw_file <BIOS password file>” option to the command. You
can find the option description in 4.1 Command Parameters.

Saves Disk Information

Description: Saves the disks information listed by --list to a file.

Usage:

1. ./ saasvc -l <system list file> -c SecureErase --list --file <JSON output file>
2. ./ saasvc -i <BMC IP> -u <BMC username> -p <BMC user password> -c
SecureErase --list --file <JSON output file> *Optional: You can add the “--
overwrite” option and either “--current_password <BIOS password>” or “--
cur_pw_file <BIOS password file>” option to the command. You can find the option
description in 4.1 Command Parameters.

Example:
[SAA_SERVICE_HOME]# ./saasvc -i <BMC IP> -u <BMC Username> -p <BMC
Password> -c SecureErase --list --file [Link]

SAA Service (for UEFI BIOS) 1.0.0 2024/10/24 (x86 64)

Copyright(C) 2024 Super Micro Computer, Inc. All rights reserved.

Querying disk information....................................

.........................................................
..............................................Done

----------------------------------Disk List--------------------------------
ID |Disk Name |Serial Number |NeedPassword
|Support SecureErase
1 |INTEL SSDSC2KG240G8 |PHYG009403NH240AGN |No |Yes
------------------------------RAID List--------------------------
ID | Vendor | Serial Number | RAID Controller |
Support SecureErase
2 | ATA | W472PFFF | AVAGO 3108 MegaRAID(Broadcom) | Yes
3 | ATA | W472TJXH | AVAGO 3108 MegaRAID(Broadcom) | Yes
4 | ATA | W472PFGE | AVAGO 3108 MegaRAID(Broadcom) | Yes
5 | ATA | W472PFEW | AVAGO 3108 MegaRAID(Broadcom) | Yes
6 | ATA | 9XF4AFVB | AVAGO 3108 MegaRAID(Broadcom) | Yes
7 | ATA | 9XF4AE8Q | AVAGO 3108 MegaRAID(Broadcom) | Yes

SAA_SERVICE User's Guide Page 85

 8 | ATA | 9XF4AF08 | AVAGO 3108 MegaRAID(Broadcom) | Yes
9 | ATA | 9XF4AFN4 | AVAGO 3108 MegaRAID(Broadcom) | Yes

Notes:
You can also use the “--overwrite” option to overwrite disk
information in the same file.
If the system requires a BIOS password, use the “--
current_password <BIOS password>” or “--cur_pw_file <BIOS
password file>” options.
The “--list” option can’t be used with the “--erase_id” or “--erase_file”
options.

4.3 Erasing a Single Disk in a Single System

Erases a Single Disk by ID in a Single System

Description: Erases a single disk identified by its ID in accordance with the

enumeration provided by the --list option, starting from 1.
Usage: ./saasvc -I <BMC IP> -u <BMC username> -p <BMC user password> -c
SecureErase --erase_id <id>
*Optional: You can add the either the --current_password <BIOS password>” or --
cur_pw_file <BIOS password file>” option to enter BIOS password while erasing non-
RAID disks if required. Additionally, you can add the either the --disk_pwd <disk
password>” or --PSID <disk PSID>” option to erase non-RAID disks protected by a disk
password. And the --reboot” option is only used when a non-RAID disk is listed in the
erasing file.
Usage:

1. ./saasvc -i <BMC IP> -u <BMC username> -p <BMC user password> -c

SecureErase --erase_id <id> --current_password <BIOS password>
2. ./saasvc -i <BMC IP> -u <BMC username> -p <BMC user password> -c
SecureErase --erase_id <id> --cur_pw_file <BIOS password file> --reboot
3. ./saasvc -i <BMC IP> -u <BMC username> -p <BMC user password> -c
SecureErase --erase_id <id> --disk_pwd <disk password>

SAA_SERVICE User's Guide Page 86

4. ./saasvc -i <BMC IP> -u <BMC username> -p <BMC user password> -c
SecureErase --erase_id <id> --PSID <disk PSID> --reboot

Notes:
If the system requires a BIOS password, use the --current_password
<BIOS password>” or --cur_pw_file <BIOS password file>” option.
The --erase_id” option can’t be used with the --list” or --erase_file”
options.
To erase a non-RAID disk, add the --reboot” parameter.
Due to the uncertainty of the secure erase execution time, if you set
a Post timeout specified in [Link] that is shorter than the
execution time, you will need to manually check the result of the
secure erase. Otherwise, if the Post timeout setting is longer than the
execution time, the secure erase result will be displayed
automatically.
The disk password will remain on the disk if secure erase fails. In the
event of erasing the disk without the disk password, try the default
password “111111111.”

Example:
[SAA_SERVICE_HOME]# ./saasvc -i <BMC IP> -u <BMC Username> -p <BMC
Password> -c SecureErase --erase_id <id> --reboot

[SAA_SERVICE_HOME]$ ./saasvc -i [Link] -u <BMC Username> -p <BMC Password>

-c SecureErase --
erase_id 1 --reboot
SAA Service (for UEFI BIOS) 1.0.0 (2024/10/24) (x86_64)
Copyright(C) 2024 Super Micro Computer, Inc. All rights reserved.

Querying disk information...........................................

................................................
................................................
..............Done

SecureErase target disk with ID [1]:

---------------------------------Disk List---------------------------------
ID | Disk Name | Serial Number | NeedPassword |
Support SecureErase
1 | SAMSUNG MZ7LH240HAHQ-00005 | S45RNC0T126247 | No | Yes

Note: The unsupported disk will be skipped.

SAA_SERVICE User's Guide Page 87

 Start disk Security Erase without
password............................................
.................................................
.................................................
.................................................
.................................................
.................................................
................Done

Getting erasing disk result...Done

Note: Only display the disk has the erasing result.

---------------------------------Disk Result---------------------------------
ID | Disk Name | Serial Number | Erase result
1 | SAMSUNG MZ7LH240HAHQ-00005 | S45RNCOT126247 | Success

---------------------------------RAID Result---------------------------------
No erase job to RAID.

4.4 Erasing a Single Disk in Multiple Systems

Erases a Single Disk by ID in Multiple Systems

Description: Erases a single disk with the specified ID enumerated by the --list option
which starts from 1.
Usage: ./saasvc -l <system list file> -c SecureErase --erase_id <id>
*Optional: You can add either the “--current_password <BIOS password>” or “--
cur_pw_file <BIOS password file>” option to enter BIOS password while erasing non-
RAID disks if required. You can also add either the “--disk_pwd <disk password>” or “--
PSID <disk PSID>” option to erase non-RAID disks if they are protected by a disk
password. And the “--reboot” option is only used when no non-RAID disks are listed in
the erasing file.
Usage:

1. ./saasvc -l <system list file> -c SecureErase --erase_id <id> --current_password

<BIOS password>
2. ./saasvc -l <system list file> -c SecureErase --erase_id <id> --cur_pw_file <BIOS
password file> --reboot

SAA_SERVICE User's Guide Page 88

3. ./saasvc -l <system list file> -c SecureErase --erase_id <id> --disk_pwd <disk
password>
4. ./saasvc -l <system list file> -c SecureErase --erase_id <id> --PSID <disk PSID> --
reboot

Example:
1. [SAA_SERVICE_HOME]# ./saasvc -l <system list file> -c SecureErase --erase_id
<id> --reboot

[SAA_SERVICE_HOME]$ ./saasvc -l [Link] -c SecureErase --erase_id 1 --

reboot
SAA Service (for UEFI BIOS) 1.0.0 (2024/10/24) (x86_64)
Copyright(C) 2024 Super Micro Computer, Inc. All rights reserved.
Press ENTER to see the current execution status:
Start to do SecureErase for systems listed in [Link]
Multi system log file created:
[Link].log_2823-06-07_17-40-55_355559
----------------------------Final Results----------------------------
Executed Command:
./saasvc -l [Link] -c SecureErase --erase_id 1 --reboot
Summary:
2 EXECUTIONS ( WAITING: 0 RUNNING: 0 SUCCESS: 2 FAILED: 0 INCOMPLETE: 0
RETRY:
0 IGNORED: 0 CANCEL: 0 )
Status List:
System Name | Elapsed | Status | Exit Code
[Link] | 00:03:54 | SUCCESS | 0
[Link] | 00:06:20 | SUCCESS | 0
Summary:
2 EXECUTIONS ( WAITING: 0 RUNNING: 0 SUCCESS: 2 FAILED: 0 INCOMPLETE: 0
RETRY: 0
IGNORED: 0 CANCEL:0)
Please check output message:
[Link].log_2024-10-0717-40-55_355559

Notes:
If the system requires a BIOS password, use the “--
current_password <BIOS password>” or “--cur_pw_file <BIOS
password file>” option.
The “-- erase_id” option can’t be used with the “-- list” or “--
erase_file” options.
To erase a non-RAID disk, add the “--reboot” parameter.
Due to the uncertainty of the secure erase execution time, if you set
a Post timeout specified in [Link] that is shorter than the

SAA_SERVICE User's Guide Page 89

 execution time, you will need to manually check the result of the
secure erase. Otherwise, if the Post timeout setting is longer than the
execution time, the secure erase result will be displayed
automatically.
The disk password will remain on the disk if secure erase fails. In the
event of erasing the disk without the disk password, try the default
password “111111111.”

4.5 Erasing Multiple Disks in a Single System

To erase multiple disks in a system, you should create a disk list to record all the target
disks, including their configurations if required. Use the “listing disk” command to create
a disk list. For details, see 4.2 Listing Disk Information.

Erasing Disks by File in a Single System

Description: Erases disks including RAID listed in the specified file.

Usage: ./saasvc -i <BMC IP> -u <BMC username> -p <BMC user password> -c
SecureErase --erase_file <file name>
*Optional: You can add either the “--current_password <BIOS password>” or “--
cur_pw_file <BIOS password file>” option to enter BIOS password while erasing non-
RAID disks if required. And the “--reboot” option is only used when a non-RAID disk
listed in the erasing file.
Usage:

1. ./saasvc -i <BMC IP> -u <BMC username> -p <BMC user password> -c

SecureErase --erase_file <file name> --current_password <BIOS password>
2. ./saasvc -i <BMC IP> -u <BMC username> -p <BMC user password> -c
SecureErase --erase_file <file name> --cur_pw_file <BIOS password file> --reboot

Example:
1. [SAA_SERVICE_HOME]# ./saasvc -i <BMC IP> -u <BMC Username> -p <BMC
Password> -c SecureErase --erase_file <file name> --reboot

[SAA_SERVICE_HOME]$ ./saasvc -i [Link] -u <BMC Username> -p <BMC

Password> -c SecureErase -

SAA_SERVICE User's Guide Page 90

-erase_file [Link] --reboot
SAA Service (for UEFI BIOS) 1.0.0 (2024/10/24) (x86_64)
Copyright(C) 2024 Super Micro Computer, Inc. All rights reserved.

Querying disk information.............Done

SecureErase target disk list:

--------------------------------------Disk List----------------------------------
----
ID | Disk Name | Serial Number | Need Password | Support
SecureErase
1 | SAMSUNG MZ7LH240HAHQ-00005 | S45RNCOT126247 | No | Yes
2 | SAMSUNG MZ7LH240HAHQ-00005 | S45RNCOT126252 | No | Yes

Note: The unsupported disks will be skipped.

Start disk Security Erase without

password............................................
................................................................
................................................................
................................................................
................................................................
................................................................
.........Done

Getting erasing disk result...Done

Note: Only display the disk has the erasing result.

--------------------------------------Disk Result--------------------------------
------
ID | Disk Name | Serial Number | Erase result
1 | SAMSUNG MZ7LH240HAHQ-00005 | S45RNCOT126247 | Success
2 | SAMSUNG MZ7LH240HAHQ-00005 | S45RNCOT126252 | Success

---------------------------------RAID Result---------------------------------
No erase job to RAID.

Notes:
If the system requires a BIOS password, use the “--
current_password <BIOS password>” or “--cur_pw_file <BIOS
password file>” option.
The “--erase_file” option can’t be used with the “--list” or “--erase_id”
options.
To erase a non-RAID disk, add the “--reboot” parameter.
Due to the uncertainty of the secure erase execution time, if you set
a Post timeout specified in [Link] that is shorter than the
execution time, you will need to manually check the result of the

SAA_SERVICE User's Guide Page 91

 secure erase. Otherwise, if the Post timeout setting is longer than the
execution time, the secure erase result will be displayed
automatically.
The disk password will remain on the disk if secure erase fails. In the
event of erasing the disk without the disk password, try the default
password “111111111.”
Provide the HDD password or PSID in the disk list if needed.

4.6 Erasing Multiple Disks in Multiple Systems

To erase multiple disks in multiply systems, you should create a disk list to record all the
target disks, including their configurations if required. Use the “listing disk” command to
manually combine the disk lists. For details, see 4.2 Listing Disk Information. Here is an
example of the combined disk list.

{
"RAID": {
"system_list": [
{
"Controller": [
{
"DeviceId": 0,
"DeviceName": "AVAGO 3108 MegaRAID",
"VendorName": "Broadcom",
"disk_list": [
{
"DiskId": 4,
"EnclosureId": 0,
"SN": "XXXXXXXXXXX",
"VendorName": "WDC"
}
]
}
],
"bmc_ip": "[Link]"
},
{
"Controller": [
{
"DeviceId": 1,
"DeviceName": "AVAGO 3108 MegaRAID",
"VendorName": "Broadcom",
"disk_list": [
{

SAA_SERVICE User's Guide Page 92

 "DiskId": 0,
"EnclosureId": 0,
"SN": "XXXXXXXXXXX",
"VendorName": "TOSHIBA"
}
]
}
],
"bmc_ip": "[Link]"
}
]
}
}

Erases Disks by File in Multiple Systems

Description: Erases disks, including those in RAID, as listed in the specified file
Usage: ./saasvc -l <system list file> -c SecureErase --erase_file <file name>
*Optional: You can add either the “--current_password <BIOS password>” or “--
cur_pw_file <BIOS password file>” option to enter BIOS password while erasing non-
RAID disks if required. And the “--reboot” option is only used when a non-RAID disk is
listed in the erasing file.
Usage:

1. ./saasvc -l <system list file> -c SecureErase --erase_file <file name> --

current_password <BIOS password>
2. ./saasvc -l <system list file> -c SecureErase --erase_file <file name> --cur_pw_file
<BIOS password file> --reboot

Example:
1. [SAA_SERVICE_HOME]# ./saasvc -l <system list file> -c SecureErase --erase_file
[Link] --reboot

[SAA_SERVICE_HOME]$sudo ./saasvc-c SecureErase -l systemlist_hdd.txt --erase_file

[Link] --reboot
SAA Service (for UEFI BIOS) 1.0.0 (2024/10/24) (x86_64)
Copyright(C) 2024 Super Micro Computer, Inc. All rights reserved.

Press ENTER to see the current execution status:

Start to do SecureErase for systems listed in systemlist_hdd.txt
Multi system log file created:
machinelist_hdd.log_2023-06-06_14-15-12_100294

SAA_SERVICE User's Guide Page 93

----------------------------Final Results----------------------------
Executed Command:
./saasvc -c SecureErase -l systemlist_hdd.txt --erase_file [Link] --
reboot
summary:
2 EXECUTIONS ( WAITING: 0 RUNNING:0 SUCCESS: 2 FAILED:0 INCOMPLETE:0 RETRY:0
IGNORED:0 CANCEL:0 )
Status List:
System Name | Elapsed | Status | Exit Code
[Link] | 00:05:38 | SUCCESS | 0
[Link] | 00:05:06 | SUCCESS | 0
summary:
2 EXECUTIONS ( WAITING: 0 RUNNING:0 SUCCESS: 2 FAILED:0 INCOMPLETE:0 RETRY:0
IGNORED:0 CANCEL:0 )

Notes:
If the system requires a BIOS password, use the “--
current_password <BIOS password>” or “--cur_pw_file <BIOS
password file>” option.
The “--erase_file” option can’t be used with the “--list” or “--erase_id”
option.
To erase a non-RAID disk, add the “--reboot” parameter.
Due to the uncertainty of the secure erase execution time, if you set
a post timeout specified in [Link] that is shorter than the
execution time, you will need to manually check the result of the
secure erase. Otherwise, if the Post timeout setting is longer than the
execution time, the secure erase result will be displayed
automatically.
If the secure erase is unsuccessful, the disk password will still be
there. If the disk originally didn’t have a disk password, use the
default password “111111111.”
Provide the HDD password or PSID in the disk list if needed.

SAA_SERVICE User's Guide Page 94

5. SAA Service GUI

The GUI (graphical user interface) version of SAA Service makes it easy for you to
navigate and use the service.

5.1 Installation and Setup

1. For Linux users, find and extract
SAA_SERVICE_x.x.x_Linux_x86_64_YYYYMMDD.[Link]
For Windows users, find and extract
SAA_SERVICE_x.x.x_Win_x86_64_YYYYMMDD.zip
2. Extract the SAA_SERVICE_x.x.x_Linux_x86_64_YYYYMMDD.[Link] archive file.
3. Go to the extracted SAA_SERVICE_x.x.x_Linux_x86_64 directory and name this
directory as “SAA_SERVICE_HOME”.
4. Run the saasvc-gui file in the SAA_SERVICE_HOME directory with root privileges.

Example (on Linux):

[shell]# tar xzf SAA_SERVICE_x.x.x_Linux_x64_YYYYMMDD.[Link]

[shell]# cd SAA_SERVICE_x.x.x_Linux_x86_64

[SAA_SERVICE_HOME]# sudo -E ./saasvc-gui

5.2 Creating a New Resource File

To create a resource file, follow these steps:

1. Click RC Setting on the left pane, click the “File Selection” tab, select New under
Step1: Select the file source.

saasvcrc: configures resource files for the BundleSync, RemoteUpdate,

LocalUpdate and SecureErase commands.

SAA_SERVICE User's Guide Page 95

3. On the Configuration tab, click each category (BmcCfg, CommandCfg, GlobalCfg,
and RecordTargetCfg) to make the necessary configurations. For details on the
categories, see 3.3 Pre-processing: Resource File Setting.

SAA_SERVICE User's Guide Page 96

4. Click Save to save the resource file configurations in .xml format.

5.3 Configuring an Existing Resource File

To configure an existing resource file, follow these steps:

1. Click RC Setting on the left pane, click the File Selection tab, select Open under
“Step1: Select the file source.”
2. Enter the desired file name in the “RC file” field or click the Browse button to select
the desired resource file. Click Next.

SAA_SERVICE User's Guide Page 97

3. On the Configuration tab, click each category (BmcCfg, CommandCfg, GlobalCfg,
and RecordTargetCfg) to make any necessary changes. For details on the
categories, see 3.3 Pre-processing: Resource File Setting.
4. Click Save to save the resource file configurations in .xml format.

5.4 Running the BundleSync Command with the SAA

Service GUI
To run the BundleSync command, click BundleSync on the left pane. For details on the
BundleSync command, see 3.5 Pre-processing: Repository Synchronization.

SAA_SERVICE User's Guide Page 98

5.4.1 Action Selection

1. On the “Action Selection” tab, use the “Chose an action” drop-down list to select the
desired action (push, pull, pull_all, and force_push). For details, see 3.5 Pre-
processing: Repository Synchronization.
2. Enter the desired file name in the “RC file” field or click the Browse button to select
the desired resource file. Click Next.

5.4.2 Option

The items shown on the “Option” tab vary based on the action you select on the “Action
Selection” tab.

SAA_SERVICE User's Guide Page 99

The options are mirror file, overwrite, and methods for the pull_all action. For details,
see 3.5 Pre-processing: Repository Synchronization.

After finishing the configuration, click Next.

5.4.3 Preview

SAA_SERVICE User's Guide Page 100

On the “Preview” tab, you can preview the execution.
If you confirm the execution, click Next and then click Yes in the message box.

5.4.4 Result

On the “Result” tab, you can view the execution result. The Done button becomes
visible after the execution is finished. Review the result and click Done to complete the
process.

5.5 Running the RemoteUpdate Command

To run the RemoteUpdate command, click RemoteUpdate on the left pane. For details
on the RemoteUpdate command, see 3.9 Updating Firmware through Out-of-Band
Method, 3.10 Updating Firmware through Remote In-Band/RHI Method, and 3.11
Updating Firmware on Multiple Systems.

5.5.1 Interface Selection

1. On the “Interface Selection” tab, select the type of system you want to update under
“Step 1: select the type of update target.”
2. Use the “Step 2: Select the update interface” drop-down list to select the desired
update interface: OOB, Remote-INB, Remote-RHI, No specific interface, (Multi)
OOB, (Multi) Remote-INB, (Multi) Remote-RHI, or (Multi) No specific interface.
3. Enter the desired file name in the “RC file” field or click the Browse button to select
the desired resource file. Click Next.

SAA_SERVICE User's Guide Page 101

5.5.2 Login Information

1. The items shown on the “Login Information” tab vary based on the action you
select on the “Interface Selection” tab. To update one system, enter the BMC or
OS login information for the desired system in the corresponding field.

SAA_SERVICE User's Guide Page 102

2. To update multiple systems, enter the desired file names in the system list field, or
click the Browse button to select the desired systems, and then click Next.

SAA_SERVICE User's Guide Page 103

3. After finishing the configuration, click Next.

5.5.3 Option

The items shown on the “Option” tab vary based on the action you select on the
“Interface Selection” tab.
For details on Option, see 3.7 Command Parameters.

[Link] OOB, (Multi)OOB, No specific interface, and (Multi) No specific interface

For OOB, (Multi) OOB, No specific interface, and (Multi) No specific interface, follow
these steps:

1. You can configure the following options: Reboot (--reboot), Skip current package
check (--skip_curpkg_check), Acknowledge to power on system (--poweron_check),
Forward (--forward), and Rollback (--rollback).

SAA_SERVICE User's Guide Page 104

2. Note that upon clicking the "Rollback" checkbox, a dropdown list for selecting the
metadata version will appear. Choose the desired version.
3. You can configure the rack configuration file for rack-level chassis update (OOB,
(Multi) OOB only).
4. After finishing the configuration, click Next.

[Link] Bundle Update of Remote-INB, Remote-RHI, (Multi)Remote-INB, and

(Multi)Remote-RHI

For bundle update of Remote-INB, Remote-RHI, (Multi)Remote-INB, and

(Multi)Remote-RHI, follow these steps:

1. Select “Bundle” under “Step 1: Select the type of the firmware update.”
2. You can configure the following options: Reboot(--reboot), Skip current package
check (--skip_curpkg_check), Skip dependency check (--skip_depend_check),

SAA_SERVICE User's Guide Page 105

 Forward (--forward), and Rollback (--rollback).
3. Note that upon clicking the "Rollback" checkbox, a dropdown list for selecting the
metadata version will appear. Choose the desired version.

4. After finishing the configuration, click Next.

[Link] Individual Update of Remote-INB, Remote-RHI, (Multi) Remote-INB, and (Multi)

Remote-RHI

For individual update of Remote-INB, Remote-RHI, (Multi) Remote-INB, and (Multi)

Remote-RHI, follow these steps:

1. Select the Individual under “Step 1: Select the type of the firmware update.”
2. You can configure the following options: Reboot(--reboot), Skip current package
check (--skip_curpkg_check), Skip dependency check (--skip_depend_check),
Update target (--update_target), and Rollback (--rollback).

SAA_SERVICE User's Guide Page 106

3. Note that upon clicking the "Rollback" or "Update target" checkbox, a dropdown list
for selecting the metadata version will appear. Choose the desired version.

4. After finishing the configuration, click Next.

5.5.4 Firmware

The “Firmware” tab is accessible only when you select Individual on the “Option” tab.
Click the checkbox(es) in front of the firmware you want to update.

SAA_SERVICE User's Guide Page 107

After finished configuring, click Next.

5.5.5 Preview

On the “Preview” tab, you can view the execution preview.

If you confirm the execution, click Next and then click Yes in the message box.

5.5.6 Result

On the “Result” tab, you can view the execution result. The Done button becomes
visible after the execution is finished. Review the result and click Done to complete the
process.

5.6 Running the LocalUpdate Command to Initialize

Update

SAA_SERVICE User's Guide Page 108

To run the LocalUpdate command, click LocalUpdate on the left pane. For details on
the LocalUpdate command, see 3.8 Updating Firmware through In-Band Method. This
section is about to initialize a new update session.

5.6.1 Action Selection

1. On the “Action Selection” tab, select Start a new update session under “Choose
an update action.”
2. Enter the desired file name in the “RC file” field or click the Browse button to select
the desired resource file.
3. Click Next and then click Yes in the message box.

5.6.2 Login Information

1. The items shown on the “Login Information” tab vary based on the action you
select on the “Choose an update action”. To update one system over “Redfish

SAA_SERVICE User's Guide Page 109

 Host Interface”, enter the BMC login information for the desired system in the
corresponding field.

3. After finishing the configuration, click Next.

5.6.3 Option

For details on options, see 3.7 Command Parameters.

To set up bundle update options, follow these steps:

1. Select Bundle under “Step 1: Select the type of the firmware update.”
2. Under “Step 2: Set options for the firmware update”, you can configure the following
options: Reboot(--reboot), Skip current package check (--skip_curpkg_check),
Forward (--forward), and Rollback (--rollback). Note that upon clicking the
"Rollback" checkbox, a dropdown list for selecting the firmware bundle will appear.
Choose the desired version.

SAA_SERVICE User's Guide Page 110

3. After finishing the configuration, click Next.

To set up individual update options, follow these steps:

1. Select Individual under “Step 1: Select the type of the firmware update.”
2. Under “Step 2: Set options for the firmware update”, you can configure the following
options: Reboot(--reboot), Skip dependency check (--skip_depend_check), Update
target (--update_target), and Rollback (--rollback). Note that upon clicking the
"Rollback" or "Update target" checkbox, a dropdown list for selecting the metadata
version will appear. Choose the desired version.
3. After finishing the configuration, click Next.

SAA_SERVICE User's Guide Page 111

5.6.4 Firmware

The “Firmware” tab is accessible only when you select Individual on the “Option” tab.
Click the checkbox(es) in front of the firmware you want to update. After finishing the
configuration, click Next.

SAA_SERVICE User's Guide Page 112

5.6.5 Preview

On the “Preview” tab, you can view the execution preview.

After confirming the execution, click Next and then click Yes in the message box.

5.6.6 Result

On the “Result” tab, you can view the execution result. The Done button becomes
visible after the execution is finished. Review the result and click Done to complete the
process.

5.7 Running the LocalUpdate Command to Continue an

Update

SAA_SERVICE User's Guide Page 113

To run the LocalUpdate command, click LocalUpdate on the left pane. For details on
the LocalUpdate command, see 3.9 Updating Firmware through In-Band Method. This
command is used to continue an unfinished update session.

5.7.1 Action Selection

1. On the “Action Selection” tab, select Continue the unfinished update session
under “Choose an update action.”
2. Enter the desired file name in the “RC file” field or click the Browse button to select
the desired resource file. Click Next and then click Yes in the message box.

5.7.2 Result

On the “Result” tab, you can view the execution result. The Done button becomes
visible after the execution is finished. Review the result and click Done to complete the
process.

SAA_SERVICE User's Guide Page 114

5.8 Running the SecureErase Command to List Disks
To run the Secure command, click SecureErase on the left pane. For details on the
SecureErase command, see 4 Secure Erase. This command is used to generate a disk
list.

5.8.1 Action Selection

1. On the “Action Selection” tab, select to list the disks on a single system or multiple
systems under “Step 1: Select the type of secure erase target.”
2. Select Generate disk list under “Step 2: Select the secure erase action.”
3. Enter the desired file name in the “RC file” field or click the Browse button to select
the desired resource file. Click Next.

5.8.2 System Information

SAA_SERVICE User's Guide Page 115

1. On the “System Information” tab, enter the BMC information in the corresponding
field for a single system, or enter the desired file name in the system list field, or
click the Browse button to select the desired system list file for multiple systems.
2. Enter the desired file name in the “Disk list file” field or click the Browse button to
select the desired disk list file.
3. Click the Overwrite disk list file checkbox if you want to overwrite an existing disk
list file.

4. Click the “Has BIOS password” checkbox if the system is password-protected,

enter the desired file name in the “BIOS password file” field, or click the Browse
button to select the desired BIOS password file.

SAA_SERVICE User's Guide Page 116

5. After finishing configuration, click Next.

5.8.3 Preview

On the “Preview” tab, you can view the execution preview.

After confirming the execution, click Next and then Yes in the message box.

5.8.4 Result

On the “Result” tab, you can view the execution result. The Done button becomes
visible after the execution is finished. Review the result and click Done to complete the
process.

5.9 Running the SecureErase Command to Erase Disk

To run the Secure command, click SecureErase on the left pane. For details on the
SecureErase command, see 4 Secure Erase. This command is used to run
SecureErase on disks listed in the disk list.

5.9.1 Action Selection

1. On the “Action Selection” tab, select to secure erase disks on a single system or on
multiple systems under “Step 1: Select the type of secure erase target.”
2. Select SecureErase by disk list under “Step 2: Select the secure erase action.”
3. Enter the desired file name in the RC file field or click the Browse button to select
the desired resource file. Click Next.

SAA_SERVICE User's Guide Page 117

5.9.2 System Information

1. On the “System Information” tab, enter the BMC information in the corresponding
field for a single system, or enter the desired file name in the system list field, or
click the Browse button to select the desired system list file for multiple systems.
2. Enter the desired file name in the disk list file field or click the Browse button to
select the desired disk list file.
3. Click the “Overwrite disk list file” checkbox if you want to overwrite an existing disk
list file.

SAA_SERVICE User's Guide Page 118

4. Click the “Has BIOS password” checkbox if the system is password-protected,
enter the desired file name in the BIOS password file field, or click the Browse
button to select the desired BIOS password file.

5. After finishing the configuration, click Next.

5.9.3 Preview

On the “Preview” tab, you can view the execution preview.

SAA_SERVICE User's Guide Page 119

If you confirm the execution, click Next and then click Yes in the message box.

5.9.4 Result

On the “Result” tab, you can view the execution result. The Done button becomes
visible after the execution is finished. Review the result and click Done to complete the
process.

5.10 SAA Service Backend Access and User Management

To login the SAA Service backend or manage the users (view, add, and delete users),
click BackendAccess on the left pane. For details on the corresponding command-line
interface function, see 3.4 Pre-processing:UserManagement. Administrator privileges
are required for user management operations.

5.10.1 Login

1. On the “Login” tab, enter the following information:

Enter the desired file name in the “RC file” field or click the Browse button to
select the desired resource file.
Enter your Username.
Enter your Password.
2. Click the Login button.

SAA_SERVICE User's Guide Page 120

After successful login:

The status Logged in as: [username] will be displayed.

The Change Password button will be enabled.
If you have administrator privileges, the User Management tab will appear
automatically.

Notes:
You must select a valid RC file before logging in.
Regular users can log in successfully but cannot access the User Management tab.

5.10.2 Change Password

1. After logging in, click the Change Password button.

2. In the pop-up window, enter the following:
Enter your Old Password.

SAA_SERVICE User's Guide Page 121

 Enter your New Password.
Enter your Confirm New Password.
3. Click the Change Password button.

Notes:
The new password must be at least 10 characters long and contain at least one
uppercase letter, one lowercase letter, and one special character.
After the password is changed successfully, you will be automatically logged out
and required to log in again.

5.10.3 User Management

Note: This tab is only visible to users with Administrator privileges.

SAA_SERVICE User's Guide Page 122

1. On the “User Management” tab, the current list of backend users is displayed in the
table.

Available Actions:

Add User
Click the Add User button to create a new user account.

In the Add User dialog:

i. Enter Username, Password, Confirm Password, and Email

ii. Select the Role (Admin or User).
iii. Click the Add button.

Notes:
The new password must be at least 10 characters long and contain at least one
uppercase letter, one lowercase letter, and one special character.

SAA_SERVICE User's Guide Page 123

 Refresh
Click the Refresh button to reload the latest user list from the server.

Delete User
In the Action column, click the delete icon (Trash basket) for the user you want to
remove.
Confirm the deletion in the confirmation dialog box.

Warning: This action cannot be undone.

5.10.4 Logout

1. Go back to the Login tab.

2. Click the Logout button.

SAA_SERVICE User's Guide Page 124

3. Click Yes in the confirmation message box.

After logging out:

All input fields will be cleared and re-enabled.

The User Management tab will be removed if it was visible.
You must log in again to perform any backend operations.

SAA_SERVICE User's Guide Page 125

6. FAQ

6.1 Errors and Exceptions

Question: What does the “--skip_curpkg_check” option mean?

********************************<<<<<ERROR>>>>>*********************************

ExitCode = 93
Description = Manual steps are optional
Program Error Code = 532.28
Error message:
Firmwares on the managed system cannot match with metadata in the
SAA_SERVER (IP: [Link], Port: 80) so the auto-recovery will not be
executed if the update fails.
Instruction:
Please make sure firmware version on the managed system can exactly
match with one of the metadata or execute RemoteUpdate command with
--skip_curpkg_check option.
All metadata supported firmwares package information can be found in
.json file under metadataFwVerInfo folder.

*******************************************************************************

Answer: That means the current firmware version does not fully match any metadata in
the SAA Service repository. If you want to skip the version check, use this option.

Question: What does the “Verifying Mirror repository integrity failed” message mean?

********************************<<<<<ERROR>>>>>*********************************

ExitCode = 65
Description = Invalid internal file
Program Error Code = 511.112
Error message:
Verifying Mirror repository integrity failed.

********************************************************************************

SAA_SERVICE User's Guide Page 126

Answer: The repository zip file has been modified. To fix this problem, reproduce a new
repository zip file.

6.2 SAA Service GUI Exception

Question: Why does the error persist despite entering a username?

Answer: The system prevents users from entering incorrect information. Enter the
correct username and add a “_script” string at the end. In the figure above, "user" is
incorrect because it doesn’t contain the "_script" string. The correct username should
be "user_script".

SAA_SERVICE User's Guide Page 127

Appendix A. SAA_SERVICE Exit Codes

Exit Code Number Description

0 Successful

Others Failed

GROUP1 (1~30) Command line parsing check failed

1 GetOpt unexpected option code

2 Unknown option

3 Missing argument

5 Missing option

6 Unknown command

7 Option conflict

8 Can not open file

9 File already exists

11 Invalid command line data

12 Function access denied

GROUP2 (31~59) Resource management error

31 File management error

32 Thread management error

33 TCP connection error

34 UDP connection error

35 Program interrupted and terminated

38 Function is not supported

SAA_SERVICE User's Guide Page 128

40 Http connection error

41 Repository management error

GROUP3 (60~79) File parsing errors

61 Utility internal error

62 Invalid input file

64 Invalid download file

65 Invalid internal file

GROUP4 (80~90) IPMI operation errors

80 Node Product key is not activated

81 Internal communication error

GROUP5 (9199,190199) Action Required

91 Manual updating forward confirmation

92 Manual reboot is required

93 Manual skipping system firmware bundle check

94 Manual forcing initializing update confirmation

95 Update and recovery failed

96 Update failed but recovery succeeded

97 Confirmation of automatic rebooting system

98 Manual continuing process after reboot

99 Manual solving unsatisfied update dependency

190 Confirmation of automatic power-off system

GROUP6 (200~) Special Group

200 System call failed

SAA_SERVICE User's Guide Page 129

253 Known limitation

254 Manual steps are required

SAA_SERVICE User's Guide Page 130

Appendix B. Update Support Matrix

Executable

saasvc

Firmware
Remote In-
OOB Remote RHI In-Band
Band

BMC Yes Yes Yes Yes

BIOS Yes Yes Yes Yes

MB CPLD Yes [1]No Yes Yes

Backplane [1]No [1]No [1]No

Yes
CPLD

Switchboard [1]No
Yes Yes Yes
CPLD

Fanboard [1]No
CPLD Yes Yes Yes

DCPDB CPLD Yes [1]No Yes Yes

AOM board [2]No [2]No [2]No

Yes
CPLD

CMM Yes [1]No [1]No [1]No

BBP Yes [1]No [1]No [1]No

NIC (Intel) [2]No Yes [2]No Yes

NIC AOC Yes [2]No Yes Yes

BF3 (as Yes [1]No Yes Yes

NIC_AOC)

SAA_SERVICE User's Guide Page 131

GPU_A100 [1]No
Yes Yes Yes
(CEC)

GPU_A100 Yes Yes [1]No Yes

(FPGA)

GPU_A100 [1]No [1]No

Yes Yes
(NVSwitch)

GPU_A100 [1]No Yes [1]No Yes

(Retimer)

GPU_A100 [1]No [1]No

Yes Yes
(VBIOS)

GPU_HGX_HM [1]No
Yes Yes Yes
C

GPU_HGX_FP Yes [1]No Yes Yes

GA

GPU_HGX_FP [1]No
Yes Yes Yes
GA_ERoT

GPU_HGX_ER Yes [1]No Yes Yes

oT

GPU_HGX_NV [1]No
Yes Yes Yes
_SWITCH

GPU_HGX_PCI [1]No
Yes Yes Yes
E_SWITCH

GPU_HGX_PCI Yes [1]No Yes Yes

E_RETIMER

GPU_HGX_NV
LINKMANAGE Yes [1]No Yes Yes
MENTNIC

GPU_HGX_CP [1]No [1]No [1]No

Yes
LD

GPU_HGX_CP Yes [1]No [1]No [1]No

U

GPU_HGX_CP [1]No [1]No [1]No

Yes
U_ERoT

SAA_SERVICE User's Guide Page 132

GPU_HGX_GP [1]No [1]No [1]No
Yes
U

GPU_HGX_INF [1]No [1]No [1]No

Yes
ORM

MB SSD [1]No Yes [1]No Yes

(Micron 7450)

RAID Controller
(Broadcom Yes [1]No Yes Yes
3808)

RAID Controller
(Broadcom Yes [1]No Yes Yes
3816)

RAID Controller
(Broadcom Yes [1]No Yes Yes
3908)

RAID Controller
(Broadcom Yes [1]No Yes Yes
3916)

RAID Controller
(Marvell Yes [1]No Yes Yes
SE92308)

PCIe Switch
(Broadcom Gen Yes Yes [1]No Yes
5 synthetic
mode)

PCIe Switch
(Broadcom Gen [1]No Yes [1]No Yes
5 base mode)

PCIe Switch
(Broadcom Gen [1]No Yes [1]No Yes
4 base mode)

PCIe Switch
(Microchip Gen [1]No Yes [1]No Yes
4)

BPN SSD [2]No

Yes Yes Yes
(Micron 7450)

SAA_SERVICE User's Guide Page 133

BPN SSD
(Samsung Yes [2]No Yes Yes
PM9A3)

BPN SSD
(Samsung Yes [2]No Yes Yes
PM1653)

BPN SSD [2]No

Yes Yes Yes
(Kioxia CD8P)

Coolant
Distribution Unit Yes [2]No [2]No [2]No
In-Rack

Coolant
Distribution Unit Yes [2]No [2]No [2]No
RDHx

Coolant
Distribution Unit Yes [2]No [2]No [2]No
SideCar

Coolant
Distribution Unit Yes [2]No [2]No [2]No
In-Row

LCMC Yes [2]No Yes Yes

NVIDIA [2]No [2]No [2]No

Yes
NVSwitch BMC

NVIDIA
NVSwitch Yes [2]No [2]No [2]No
FPGA

NVIDIA
NVSwitch Yes [2]No [2]No [2]No
ERoT

NVIDIA
NVSwitch Yes [2]No [2]No [2]No
CPLD

NVIDIA [2]No [2]No [2]No

Yes
NVSwitch BIOS

NVIDIA
NVSwitch Yes [2]No [2]No [2]No
NVOS

SAA_SERVICE User's Guide Page 134

 Powershelf Yes [2]No [2]No [2]No
PSU

Powershelf [2]No [2]No [2]No

Yes
PMC

[1] The firmware update with this interface is not supported due to limitation.
[2] The firmware update with this interface is not supported for now.

SAA_SERVICE User's Guide Page 135

Appendix C. Rack-Level Compute Tray License
Matrix

O indicates the license applies for that feature flag; X indicates it does not.

Platform-level license checking

SFT-OBF-NODE: If the system is NV-based OBMC, the license is required.

SFT-DCMS-SINGLE: If it does not require SFT-OBF-NODE, this license will be
required.

Rack-level license checking

Based on the platform-level license checking, if the system is installed in a rack and
users need to perform rack-level operations, the following additional licenses will be
required:

SFT-ODLCR-NODE: If the rack has NV-based OBMC and is a liquid-cooling rack,

the license is required.
SFT-SDLCR-NODE: If the rack does not have NV-based OBMC and is a liquid-
cooling rack, the license is required.
SFT-SDDC-SINGLE: If the rack is an air-cooling rack, the license is required.

For NV-based OBMC

License SFT-DCMS-
SINGLE SFT-
OBF- SFT-
SDLCR- SFT-
ODLCR- SFT-SDDC-
SINGLE
NODE NODE NODE

Liquid-
Cooling X O X O X
Rack

Air-Cooling
X O X X O
Rack

For Supermicro-defined BMC (OpenBmc or others)

SAA_SERVICE User's Guide Page 136

License SFT-DCMS-
SINGLE SFT-
OBF-
NODE SFT-
SDLCR-
NODE SFT-
ODLCR-
NODE SFT-SDDC-
SINGLE

Liquid-
Cooling O X O X X
Rack

Air-Cooling
O X X X O
Rack

SAA_SERVICE User's Guide Page 137

Contacting Supermicro
Headquarters:

Address: Super Micro Computer, Inc.

980 Rock Ave.
San Jose, CA 95131 U.S.A.
Tel: +1 (408) 503-8000
Fax: +1 (408) 503-8008
Email: Sales-USA@[Link] (Sales Inquiries)
Government_Sales-USA@[Link] (Gov. Sales Inquiries)
support@[Link] (Technical Support)
RMA@[Link] (RMA Support)
Website: [Link]
Europe
Address: Super Micro Computer B.V.
Het Sterrenbeeld 28, 5215 ML
's-Hertogenbosch, The Netherlands
Tel: +31 (0) 73-6400390
Fax: +31 (0) 73-6416525
Email: Sales_Europe@[Link] (Sales Inquiries)
Support_Europe@[Link] (Technical Support)
RMA_Europe@[Link] (RMA Support)
Website: [Link]
Asia-Pacific
Address: Super Micro Computer, Inc.
3F, No. 150, Jian 1st Rd.
Zhonghe Dist., New Taipei City 235
Taiwan (R.O.C.)
Tel: +886-(2) 8226-3990
Fax: +886-(2) 8226-3992

SAA_SERVICE User's Guide Page 138

Email: Sales-Asia@[Link] (Sales Inquiries)
Support@[Link] (Technical Support)
RMA@[Link] (RMA Support)
Website: [Link]

SAA_SERVICE User's Guide Page 139