CLI Guide

Table 114. Details of update subcommand (continued)
Synopsis
For single file or DUP update:
racadm update -f <updatefile>
racadm update -f <updatefile> -l <location> -u <username for CIFS share> -
p <password for CIFS share>
racadm update -f <updatefile> -l <location>
For Repository updates
racadm update -f <catalog file> -t <Repository type> -l <location> \ -u
<username for CIFS share> -p <password for CIFS share> \ [-a <restart>]
[--verifycatalog]
racadm update -f <catalog file> -t <Repository type> \ -e <FTP server
with the path to the catalog file> [-a <restart>] \[--verifycatalog]
racadm update -f <catalog file> -t <Repository type> \ -e <FTP server
with the path to the catalog file> [-a <restart>] \ -ph <proxy ip> -pu
<proxy user> -pp <proxy pass> -po <proxy port> \
-pt <proxy type>
racadm update viewreport
Input
For single file or DUP update:
● -f: <updatefile>—Update filename (Windows DUP, .d9,.pm, .sc) only.
● -u: < username for CIFS share>—Specifies username of the remote share that stores the
update file. Specify username in a domain as domain/username.
● -p: <password for CIFS share—Specifies password of the remote share that stores the
update file.
● -l: <location>—Specifies network share location that stores the update file. For more information
on NFS or CIFS share, see section on Usage examples
● —reboot—Performs a graceful system reboot after the firmware update.
For Repository update:
● -f: <updatefile>—Update filename .
For update from repository .xml files are allowed. If a file name is not specified for repository update,
Catalog.xml is taken as default.
If a file name is not specified for repository update, then the Catalog.xml is taken as default.
● -u: < username for CIFS share>—Username of the remote share that stores the update file.
Specify username in a domain as domain/username.
● -p: <password for CIFS share — Specifies password of the remote share that stores the
update file.
● -l: <location>—Specifies network share location (CIFS/NFS/HTTP/HTTPS/FTP), that stores
the update file. For more information on network share, see section on Usage examples
● -a: <restart> — This option indicates if the server should be restarted after the update from
repository operation completes. Must be one of the below:
○ TRUE : restart after update completes
○ FALSE : do not restart after update completes
NOTE: These options are case insensitive.
● -t:Repository type>—Specifies the type of repository being used for the update.
158
RACADM Subcommand Details