Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

iDRAC 8/7 v2.70.70.70 RACADM CLI Guide

PDF

update

Table 1. Details of updateThe following table provides the details of update subcommand:
Description
Allows you to update the firmware of devices on the server. The supported firmware image file types are:
  • .exe — Windows-based Dell Update Package (DUP)
  • .d7
  • .pm

The supported catalog files are:

  • .xml
  • xml.gzip

NOTE: : Updating the platforms from the repository is not supported for IPv6.

NOTE: : Depending on the network traffic, 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.

NOTE: : This command supports both IPV4 and IPV6 formats. IPV6 is applicable only for CIFS, HTTP and HTTPS remote shares.

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 filename for Windows DUP, .d7, .pm, .pm only.

    For update from repository .xml files are allowed.

    If a file name is not specified for repository update, then the Catalog.xml is taken as default.

  • -u—Specifies username of the remote share that stores the update file. Specify username in a domain as domain/username.
  • -p—Specifies password of the remote share that stores the update file.
  • -l—Specifies network share location (CIFS/NFS/HTTP/HTTPS) that stores the update file. For more information about these shares, see the Usage examples section.
  • -a—This option indicates whether 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, HTTP, and HTTPS. These options are case-insensitive. If the repository update functionality is invoked, then this option must be run.
  • -e—Specifies the server path for the FTP, TFTP, HTTP, and HTTPS.
  • --verifycatalog—Tests the list of DUPs that are applied and generates a report.
  • —reboot—Performs a graceful system reboot after the firmware update.
  • -ph—Specifies the IP address of the proxy server.
  • -pp—Specifies the password for proxy credentials.
  • -pu—Specifies the username for proxy credentials.
  • -po—Specifies the port for proxy server.
  • -pt—Specifies the proxy type. Valid values are HTTP and SOCKS4. These values are case-insensitive.

    NOTE: :

    • If the repository must be through a proxy, then the proxy server address, proxy username and the proxy password must be specified.
    • The Lifecycle Controller must be enabled for repository update.

Output Firmware update job for <filename> is initiated.

This firmware update job may take several minutes to complete depending on the component or firmware 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.

For devices that perform update process without rebooting the host, the update status changes from Downloading to Completed. For devices that require host reboot to perform update process, the update status changes from Downloading to Scheduled. When the status is displayed as Scheduled, reboot the host to start the update process.

The following devices require host reboot to perform the update process:
  • Backplanes
  • BIOS
  • Complex programmable logic device (CPLD)
  • Hard disk drives
    • Solid state drives (SSD)
  • Network interface cards (NIC) or Fibre Channel (FC) cards
  • PCIe SSD devices
  • Power supply unit (PSU)
  • Storage controllers
Example
  • Upload the update file from a remote CIFS share.
    racadm update -f <updatefile> -u admin -p mypass -l //1.2.3.4/share
  • Upload the update file from a remote CIFS share and under a user domain "dom"
      racadm update -f <updatefile> -u dom/admin -p mypass -l //1.2.3.4/share
  • Upload the update file from a remote NFS share:
    racadm update -f <updatefile> -l 1.2.3.4:/share
  • Configure a RAC from an XML configuration file located on a remote HTTP share:
    racadm set -f myfile.xml -t xml -u httpuser -p httppwd -l http://test.com/myshare
  • Configure a RAC from an XML configuration file located on a remote HTTPS share.
    racadm set -f myfile.xml -t xml -u httpsuser -p httpspwd -l https://test.com/myshare
  • Upload the update file from the local file system using local racadm
    racadm update -f <updatefile>
  • Upload the update file from the local file system using local racadm and to perform a graceful system reboot after update
    racadm update -f <updatefile> --reboot
  • Upload the update file from a remote CIFS share and to perform a graceful system reboot after update
     racadm update -f <updatefile> -u admin -p mypass -l //1.2.3.4/share --reboot
  • Upload the update file from a remote NFS share and to perform a graceful system reboot after update:
     racadm update -f <updatefile> -l 1.2.3.4:/share --reboot
  • Upload the update file from the local file system using local racadm and perform a graceful system reboot after the firmware update:
    racadm update -f <updatefile> --reboot
  • Perform update from a CIFS repository and reboot the server to apply the updates.

    racadm update -f Catalog.xml -l //192.168.11.10/Repo -u admin -p mypass -a TRUE -t CIFS
  • Generate a comparison report using about the available updates in the repository.
    racadm update -f Catalog.xml -l 192.168.11.10:/Repo -t NFS -a FALSE --verifycatalog
  • Perform update from an FTP repository and reboot the server to apply the updates.
    racadm update -f Catalog.xml -e 192.168.11.10/Repo/MyCatalog -a TRUE -t FTP 
  • Perform update from an FTP repository with authentication and reboot the server to apply the updates.
    racadm update -f Catalog.xml -e 192.168.11.10/Repo/MyCatalog -u user -p mypass -a TRUE -t FTP
  • Perform update from an HTTP repository and reboot the server to apply the updates.
    racadm update -f Catalog.xml -e 192.168.11.10/Repo/MyCatalog -a TRUE -t HTTP
  • Perform update from a TFTP repository and reboot the server to apply the updates.
    racadm update -f Catalog.xml -e 192.168.11.10/Repo/MyCatalog -a TRUE -t TFTP
  • Perform update from an FTP repository through a proxy server.
    racadm update -f Catalog.xml -e 192.168.11.10/Repo/MyCatalog -a TRUE -ph 145.140.12.56 -pu prxyuser -pp prxypass -po 80 -pt http -t FTP
  • Perform update from ftp.dell.com
    racadm update -f Catalog.xml.gz -e ftp.dell.com/Catalog -a TRUE -t FTP
  • View the comparison report generated when --verifycatalog is used.
    racadm update viewreport
  • View the comparison report generated.
    racadm update viewreport
    ComponentType     = Firmware
    ElementName       = PERC H730P Mini
    FQDD              = RAID.Integrated.1-1
    Current Version   = 25.2.1.0025
    Available Version = 25.2.1.0029

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\