Launching SUM
If you downloaded SUM as a standalone application, the ISO, zip, or RPM does not include software, driver, or firmware components. You can download components from https://www.hpe.com. If you downloaded SUM as part of an SPP bundle release, the download includes component updates.
When you launch SUM for the first time on the system the $home/sum folder is created. This folder contains critical SUM user files. If you delete the contents of this folder or the folder itself, you must also delete all SUM configurations by running the clean-cache.sh script shipped with the SUM package. You can then launch SUM again.
When you launch
SUM from a mounted ISO, such as iLO Virtual Media,
SUM creates a local copy of the SUM binaries.%LOCALAPPDATA%\localsum
(Windows) or
/var/tmp/localsum
(Linux) directory. 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. If you run
SUM on a fileshare directory,
SUM does not need to copy the files if you run.
When you launch
SUM on a Windows node, the CHIF driver is installed automatically. To skip installing the CHIF driver, use the
/skip_prereqs
parameter.
Gen10 servers require the CHIF driver. Gen9 and older servers do not require the CHIF driver, 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 in to 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. SUM determines changes that might have happened between sessions.