Reference Guide

NOTE: Depending on the network trac, the HTTP packet transfer may fail if you perform update
operation from a remote RACADM through a local share. In such cases, retry the operation. If the issue
persists, use remote RACADM with the CIFS or NFS share.
Synopsis
racadm update -f <updatefile> [--reboot]
racadm update -f <updatefile> -l <Remote CIFS Share> -u <username for CIFS
share> -p <password for CIFS share> [--reboot]
racadm update -f <updatefile> -l <Remote NFS Share> [--reboot]
racadm update –f <catalog file> -t <Repository type> -l <Remote CIFS/NFS Share> -
u <username for CIFS share> -p <password for CIFS share> [-a <FALSE|TRUE>] [--
verifycatalog]
racadm update –f <catalog file> -t <Repository type> -l <Remote CIFS/NFS Share> -
u <username for CIFS share> -p <password for CIFS share>
racadm update –f <catalog file> -t <Repository type> –e <FTP server with the
path to the catalog file> [-a <FALSE|TRUE>] [--verifycatalog]
racadm update viewreport
Input
• -f — Update lename for Windows DUP, .d7, .pm, .pm only.
For update from repository .xml les are allowed.
If a le name is not specied for repository update, then the Catalog.xml is taken as default.
• -u — Species user name of the remote share that stores the update le. Specify user name in a domain as
domain/username.
• -p — Species password of the remote share that stores the update le.
• -l — Species network share location that stores the update le. For more information about NFS or CIFS
share, see the Usage examples section.
• -a — This option indicates whether or not the server must be restarted after the update from repository
operation completes. It takes TRUE and FALSE as options. These options are case-insensitive.
• -t — Type of repository being used for update. The valid options are FTP, CIFS, NFS, TFTP, and HTTP. These
options are case-insensitive. If the repository update functionality is invoked, then this option must be run.
• -e — Species the server path for the FTP.
• --verifycatalog — Tests the list of DUPs that are applied and generates a report.
• —reboot — Performs a graceful system reboot after the rmware update.
• -ph — Species the IP address of the proxy server.
• -pp — Species the password for proxy credentials.
• -pu — Species the user name for proxy credentials.
• -po — Species the port for proxy server.
• -pt — Species the proxy type. Valid values are HTTP and HTTPS. These values are case-insensitive.
NOTE:
• If the repository has to be through a proxy, then the proxy server address, proxy username and the
proxy password must be specied.
• The Lifecycle Controller must be enabled for repository update.
Output Firmware update job for <filename> is initiated.
This rmware update job may take several minutes to complete depending on the component or rmware being
updated. To view the progress of the job, run the racadm jobqueue view command.
For repository update command, the output is:
Update from repository operation has been initiated. Check the progress of the
operation using "racadm jobqueue view -i JID_809364633532" command.
RACADM Subcommand Details 101