firmware download

Downloads the firmware on the device, reboots the system, and commits the firmware.

Syntax

firmware download { default-config | ftp | scp | sftp | tftp | usb | interactive | migrate } [ manual ] [ nocommit ] [ noreboot ] [ noactivate ] [ coldboot ] host { hostname | host_ip_address } user username password password directory directory [ file file_name ] [ use-vrf vrf-name] ]

Command Default

By default, firmware download downloads the firmware to the system, reboots the system, and commits the firmware automatically. The user can specify noactivate to download the firmware to the system without activating it (the node is not rebooted). You can run the firmware activate command later to activate the firmware.

BMC firmware image is bundled with the SLX-OS firmware image. When the SLX-OS firmware image is updated, the update process checks the version of the BMC installed on the device. If the installed BMC version is found to be older than the bundled BMC version, the upgrade process automatically installs the bundled BMC version replacing the installed BMC version.

Parameters

default-config: Sets the configuration back to default.
ftp | scp | sftp | usb: Valid protocols are ftp (File Transfer Protocol), scp (Secure Copy), sftp (SSH File Transfer Protocol), tftp (Trivial File Transfer Protocol), or usb (Universal Serial Bus). The values are not case-sensitive.
interactive: Runs firmware download in interactive mode. You are prompted for input.
migrate: Runs full-install to install a new compatible NOS. The installed SLX-OS will be over written and will be erased.
manual: Currently, this keyword has no effect.
nocommit: Disables auto-commit mode. When auto-commit mode is disabled, firmware is downloaded only to the primary partition. You must execute the firmware commit command manually to propagate the new image to the secondary partition.
noreboot: Disables auto-reboot mode. When auto-reboot mode is disabled, you must reboot the device manually.
noactivate: Downloads the firmware to the system without activating it, so the device is not automatically rebooted. You can run the firmware activate command later to activate the firmware.

coldboot

Downloads the firmware to the system and reboots the device.

host

Specifies the host by DNS name or IP address.

hostname: Specifies an IPv4 DNS host name.
host_ip_address: Specifies the host IP address. IPv4 and IPv6 addresses are supported.

directory directory

Specifies a fully qualified path to the directory where the firmware is located.

file file_name

Specifies the firmware .plist file. This parameter is optional; if unspecified, the default file, release.plist, is used.

user username

Specifies the user login name for the host.

password password

Specifies the account password.

use-vrf vrf-id

Use this option to specify the name of the VRF where the host is located. If this option is not set, mgmt-vrf is used by default.

Modes

Privileged EXEC mode

Usage Guidelines

Unless you specify noactivate, the upgrade or downgrade involves system reboots that disrupt traffic.

If the firmware download command is interrupted because of an unexpected reboot, such as a result of a software error or power failure, the command automatically recovers the corrupted secondary partition. Wait for the recovery to complete before beginning another firmware download.

Examples

Example of firmware download with the coldboot option:

device# firmware download ftp directory /buildsjc/sre/SQA/slxos/17r.1.00/17r.1.00 host 10.31.2.27 user releaseuser password releaseuser coldboot  

Performing system sanity check... 

This command will cause a cold/disruptive reboot and will require that existing telnet, secure telnet or SSH sessions be restarted. 


Do you want to continue? [y/n]y

Example of firmware download with the default-config option:

device# firmware download default-config ftp directory /buildsjc/sre/SQA/slxos/17r.1.00/17r.1.00 host 10.31.2.27 user releaseuser password releaseuser

Performing system sanity check... 



This command will cause a cold/disruptive reboot and will require that existing telnet, secure telnet or SSH sessions be restarted. 



Do you want to continue? [y/n]y