Launching SUM
If you downloaded SUM as a stand-alone application, the ISO, zip, or RPM does not include software, driver, or firmware components. You can download components from http://www.hpe.com. If you downloaded SUM as part of a SPP bundle release, the download includes component updates.
If you launch
SUM from a mounted ISO, such as iLO Virtual Media,
SUM creates a
%temp%/localsum
(Windows) or
/tmp/localsum
(Linux) directory. You need to delete the temporary
localsum
files manually because the
clean-cache
command does not clean these files.
SUM displays messages about copying files to the drive specified.
SUM does not need to copy the files if you run
SUM on a fileshare directory.
When you launch
SUM on a Windows node, the CHIF driver is installed automatically. To skip installing the CHIF driver, use the parameter
/skip_prereqs.
Gen10 servers require the CHIF driver. Gen9 and older servers do not require the CHIF driver to communicate with SUM, but the CHIF driver allows SUM to determine all component versions.
Windows 2012 and later: Add the system to the domain and use the Domain Admin group user.
SUM does not support multiple users logging into SUM at the same time. All users must have administrator privileges, or the equivalent, for all nodes you are updating.
Each time you launch SUM it determines the state of each node that it manages. This allows SUM to determine changes that might have happened between sessions.
-
GUI mode:
Navigate to the directory where you saved SUM. Type the command
smartupdate.bat
(Windows) orsmartupdate.sh
(Linux) to start the GUI. -
Text-based console mode (interactive CLI):
Navigate to the directory where you saved SUM. From the command line, type
smartupdate
and a console parameter. For a full list of parameters, typesmartupdate -h
(Linux) orsmartupdate /h
(Windows). -
CLI mode and Input file mode:
Navigate to the directory where you saved SUM. Type
smartupdate /s /h
Windows andsmartupdate -s -h
(Linux) for a full list of parameters. For full details on using SUM in CLI mode, see the Smart Update Manager CLI Guide.