Upgrade/Downgrade commands

install

The install command copies the specified eos image onto the switch (if the source is external), configures the boot-config file to point to the specified eos image, copies the image to the standby supervisor (on dual-supervisor switches), and optionally reloads the switch to run the new eos.

Command Mode

Privileged EXEC

Command Syntax

install source source_path [destination destination_path] [now] [reload]

Parameters

  • source_path file path and name of eos image. If no file path is specified, the switch will look for the image on the flash drive of the primary supervisor.
  • destination destination_path destination file path and name of the eos image. If no destination or name is specified, the eos image will be stored on the flash drive with its original file name.
  • now command is executed immediately without further prompts.
  • reload supervisor is reloaded after the image and updated boot-config file are installed. On dual-supervisor switches, reloads both supervisors, after which control is returned to the primary supervisor.
Example
  • This command updates the boot-config file to point to the eos.swi file on the primary supervisors flash drive, copies the image and boot-config file to the secondary supervisor, and reboots both.
    switch(config)#install source eos.swi reload
    Preparing new boot-config... done.
    Copying new software image to standby supervisor... done.
    Copying new boot-config to standby supervisor... done.
    Committing changes on standby supervisor... done.
    Reloading standby supervisor... done.
    Committing changes on this supervisor... done.
    Reloading this supervisor...

reload fast-boot

The reload fast-boot command starts the Accelerated Software Upgrade (ASU) process using the eos image specified by the boot-config file (configured by the boot system command).

ASU significantly decreases downtime and packet loss during a software upgrade, but the data plane is still restarted after the control plane has loaded, resulting in approximately 30 seconds of downtime. If available, Arista recommends using Smart System Upgrade (SSU) instead.

ASU shortens downtime and minimizes packet loss during eos upgrades in three ways:

  • performing time-intensive tasks (including copying the eos image) before rebooting the control plane
  • forwarding packets in hardware (based on the last known good state) while the control-plane is offline
  • optimizing the boot process by performing only tasks essential for software upgrade

Command Mode

Privileged EXEC

Command Syntax

reload fast-boot

Guidelines

  • ASU is supported only for upgrades (not downgrades).
  • ASU is not supported if the eos upgrade requires an FPGA upgrade.
  • Enough free space must be available on the flash drive to store two copies of the target eos image.
Example
  • This command starts the Accelerated Software Upgrade process.
    switch#reload fast-boot
    Proceed with reload? [confirm]

    When the reload fast-boot command is entered, the switch sends a message prompting the user to save the configuration if it contains unsaved modifications, then asks the user to confirm the reload request.

reload hitless

The reload hitless command starts the Smart System Upgrade (SSU) process using the eos image specified by the boot-config file (configured by the boot system command).

Command Mode

Privileged EXEC

Command Syntax

reload hitless

Guidelines

  • SSU is supported only for upgrades (not downgrades).
  • SSU is not supported if the eos upgrade requires an FPGA upgrade.
  • Enough free space must be available on the flash drive to store two copies of the target eos image. It is also recommended that an additional 240MB be available to store diagnostic information.
Example
  • This command starts the SSU process.
    switch#reload hitless
    Proceed with reload? [confirm]
  • If there are issues with the current switch configuration that will prevent SSU from being performed, the switch lists the changes that must be made before SSU can begin.
    switch#reload hitless
    switch#'reload hitless' cannot proceed due to the following:
    Spanning-tree portfast is not enabled for one or more ports
    Spanning-tree BPDU guard is not enabled for one or more ports
    switch#
  • When the reload hitless command is entered, the switch sends a message prompting the user to save the configuration if it contains unsaved modifications, then asks the user to confirm the reload request.
    switch#reload hitless
    System configuration has been modified. Save? [yes/no/cancel/diff]:y
    Copy completed successfully.
    Proceed with reload? [confirm]y