Standard Upgrades and Downgrades

Standard software upgrades and downgrades on Arista switches are accomplished by installing a different eos image and reloading the switch. On switches with redundant supervisors, the eos image must be installed on both supervisors. Using the procedure described below will minimize packet loss during a standard upgrade or downgrade.

These sections describe standard switch upgrade and downgrade procedures

Upgrading or Downgrading the eos on a Single-Supervisor switch

Modifying the active eos image is a five-step process:

  1. Prepare switch for upgrade ( Prepare the switch).
  2. Transfer image file to the switch ( Transfer the Image File). (Not required if desired file is on the switch).
  3. Modify boot-config file to point to the desired image file ( Modify boot-config for Single-Supervisor switch).
  4. Reload switch (Reload).
  5. Verify that switch is running the new image ( Verify).

Prepare the switch

Before upgrading the eos image, ensure that backup copies of the currently running eos version and the running-config file are available in case of corruption during the upgrade process. To copy the running-config file, use the copy running-config command. In this example, running-config is copied to a file in the flash drive on the switch.

switch#copy running-config flash:/cfg_06162014
Copy completed successfully.
switch#

Determine the size of the new eos image. Then verify that there is enough space available on the flash drive for two copies of this image (use the dir command to check the bytes free figure).

switch#dir flash:
Directory of flash:/
-rwx 293168526Nov 422:17 eos4.11.0.swi
-rwx36Nov 810:24 boot-config
-rwx 37339Jun 16 14:18 cfg_06162014

<-------OUTPUT OMITTED FROM EXAMPLE-------->
606638080 bytes total (602841088 bytes free)

Ensure that the switch has a management interface configured with an IP addresses and default gateway. Refer the sections, Assigning a Virtual IP Address to Access the Active Ethernet Management Port and Configuring a Default Route to the Gateway (see Assigning a Virtual IP Address to Access the Active Ethernet Management Port and Configuring a Default Route to the Gateway), and confirm that it can be reached through the network by using the show interfaces status command and pinging the default gateway.

switch#show interfaces status
PortName Status Vlan Duplex SpeedType
Et3/1notconnect 1 autoauto 1000BASE-T

<-------OUTPUT OMITTED FROM EXAMPLE-------->
Ma1/1connected routed unconf unconfUnknown 

switch#ping 1.1.1.10
PING 172.22.26.1 (172.22.26.1) 72(100) bytes of data.
80 bytes from 1.1.1.10: icmp_seq=1 ttl=64 time=0.180 ms
80 bytes from 1.1.1.10: icmp_seq=2 ttl=64 time=0.076 ms
80 bytes from 1.1.1.10: icmp_seq=3 ttl=64 time=0.084 ms
80 bytes from 1.1.1.10: icmp_seq=4 ttl=64 time=0.073 ms
80 bytes from 1.1.1.10: icmp_seq=5 ttl=64 time=0.071 ms

Transfer the Image File

The target image must be copied to the file system on the switch, typically onto the flash drive. After verifying that there is space for the image, use the CLI copy command to copy the image to the flash drive, then confirm that the new image file has been correctly transferred.

These command examples transfer an image file to the flash drive from various locations.

USB Memory

Command 

copy usb1:/sourcefile flash:/destfile

Example 

Sch#copy usb1:/eos-4.13.2.swi flash:/eos-4.13.2.swi

FTP Server

Command 

copy ftp:/ftp-source/sourcefile flash:/destfile

Example 

sch#copy ftp:/user:password@10.0.0.3/eos-4.13.2.swi flash:/eos-4.13.2.swi

SCP

Command 

copy scp://scp-source/sourcefile flash:/destfile

Example 

sch#copy scp://user:password@10.1.1.8/user/eos-4.13.2.swi flash:/eos-4.13.2.swi

HTTP

Command 

copy http://http-source/sourcefile flash:/destfile

Example 

sch#copy http://10.0.0.10/eos-4.13.2.swi flash:/eos-4.13.2.swi

Once the file has been transferred, verify that it is present in the directory, then confirm the MD5 checksum using the verify command. The MD5 checksum is available from the eos download page of the Arista website.

switch#dir flash:
Directory of flash:/
-rwx 293168526 Nov 4 22:17 eos4.11.0.swi
-rwx36 Nov 8 10:24 boot-config
-rwx 37339 Jun 1614:18 cfg_06162014
-rwx 394559902 May 3002:57 eos-4.12.2.swi

606638080 bytes total (208281186 bytes free)
switch#53#verify /md5 flash:eos-4.13.2.swi 
verify /md5 (flash:eos-4.13.2.swi) =c277a965d0ed48534de6647b12a86991

Modify boot-config for Single-Supervisor switch

After transferring and confirming the desired image file, use the boot system command to update the boot-config file to point to the new eos image.

This command changes the boot-config file to point to the image file located in flash memory at eos-4.12.2.swi.

switch#configure terminal
switch(config)#boot system flash:/eos-4.13.2.swi

Use the show boot-config command to verify that the boot-config file is correct:

switch(config)#show boot-config
Software image: flash:/eos-4.13.2.swi
Console speed: (not set)
Aboot password (encrypted): $1$ap1QMbmz$DTqsFYeauuMSa7/Qxbi2l1

Save the configuration to the startup-config file with the write command.

switch#write

Reload

After updating the boot-config file, reset the switch to activate the new image. The reload command resets the switch, resulting in temporary downtime and packet loss on single supervisor switches.

When reloading from the console port, all rebooting messages are displayed on the terminal. From any port except the console, the CLI displays this text:

switch#reload
The system is going down for reboot NOW!
Note: The eos boot process makes a copy of the .swi image file in the internal flash while booting, so sufficient space for two copies must be present when loading the new eos image. If the switch is reloaded without adequate space on the flash drive, it will boot to the Aboot prompt from which you can delete files from /mnt/flash to free up additional space. Exiting Aboot will begin the boot process again.

Verify the New Image for Single-Supervisor switch

After the switch finishes reloading, log into the switch and use the show version command to confirm the correct image is loaded. The Software image version line displays the version of the active image file.

switch#show version
Arista DCS-7150S-64-CL-F
Hardware version:01.01
Serial number: JPE13120819
System MAC address:001c.7326.fd0c

Software image version: 4.13.2F
Architecture: i386
Internal build version: 4.13.2F-1649184.4132F.2
Internal build ID:eeb3c212-b4bd-4c19-ba34-1b0aa36e43f1

Uptime: 14 hours and 48 minutes
Total memory: 4017088 kB
Free memory:1569760 kB

switch>

Upgrading or Downgrading the eos on a Dual-Supervisor switch

Modifying the active eos image is a four-step process:

  1. Prepare switch for upgrade (Prepare the switch for Dual-Supervisor switch).
  2. Transfer image file to primary supervisor ( Transfer the Image File to the Primary Supervisor). (Not required if desired file is on switch)
  3. Use the install command to install the new eos image and update boot-config ( Install the New eos Image).
  4. Verify that the switch is running the new image ( Verify the New Image).
    Note: Due to a change in the supervisor heartbeat timeout, booting one supervisor with a post-SSO image (version 4.10.0-SSO, 4.11.X and later) while the other supervisor is running a pre-SSO image will cause the supervisor running the pre-SSO image to reload. This will cause a disruption as both supervisors will be inactive for a short time. To minimize downtime, upgrade the images on both supervisors and reload the entire chassis using the install command.

Prepare the switch for Dual-Supervisor switch

To prepare the switch for an eos upgrade, take the following steps:
  • Back up essential files.
  • Ensure that you are logged in to the primary supervisor.
  • Ensure that the primary supervisor is reachable and that the management interfaces are configured.
  • Ensure that there is enough room on both supervisors for the new image file.
  • Ensure that any extensions running on the active supervisor are also available on the standby.

Before upgrading the eos image, ensure that backup copies of the currently running eos version and the running-config file are available in case of corruption during the upgrade process. To copy the running-config file, use the copy running-config command. In this example, running-config is copied to a file called "backup2" on the flash drive.

switch#copy running-config backup2
Copy completed successfully.
switch#

Ensure that you are logged in to the primary supervisor, not the standby. Use the show redundancy status command, and verify that my state reads “ACTIVE” and not “STANDBY.”

switch#show redundancy status
my status = Active
peer state = STANDBY HOT
Unit = Secondary
Unit ID = 1
Redundancy Protocol (Operational) = Stateful switchover
Redundancy Protocol (Configured) = Stateful switchover
Communications = Up
Ready for switchover
Last switchover time = 25 days, 19:51:34 ago
Last switchover reason = Other supervisor stopped sending heartbeats

Ensure that the switch has a management interface configured with an IP addresses and default gateway. Refer the sections, Assigning a Virtual IP Address to Access the Active Ethernet Management Port and Configuring a Default Route to the Gateway (see Assigning a Virtual IP Address to Access the Active Ethernet Management Port and Configuring a Default Route to the Gateway), and confirm that both management interfaces are in the up state and can ping the default gateway by using theshow interfaces status command and ping command.

Note: If the management VRF interface is used, use the virtual management interface (management 0) instead of the IP address on the physical management interface.
switch#show interfaces status
PortName Status Vlan Duplex SpeedType
Et3/1notconnect 1 autoauto 1000BASE-T

<-------OUTPUT OMITTED FROM EXAMPLE-------->
Ma1/1connected routed unconf unconfUnknown 

switch#ping 1.1.1.10
PING 172.22.26.1 (172.22.26.1) 72(100) bytes of data.
80 bytes from 1.1.1.10: icmp_seq=1 ttl=64 time=0.180 ms
80 bytes from 1.1.1.10: icmp_seq=2 ttl=64 time=0.076 ms
80 bytes from 1.1.1.10: icmp_seq=3 ttl=64 time=0.084 ms
80 bytes from 1.1.1.10: icmp_seq=4 ttl=64 time=0.073 ms
80 bytes from 1.1.1.10: icmp_seq=5 ttl=64 time=0.071 ms

Determine the size of the new eos image. Then verify that there is enough space available on the flash drive for two copies of this image (use the dir command to check the bytes free figure).

switch#dir flash:
Directory of flash:/
-rwx 293168526Nov 422:17 eos4.11.0.swi
-rwx36Nov 810:24 boot-config
-rwx 37339Jun 16 14:18 cfg_06162014

<-------OUTPUT OMITTED FROM EXAMPLE-------->
606638080 bytes total (602841088 bytes free)
Standby supervisor:
switch#dir supervisor-peer:mnt/flash/
Directory of flash:/
-rwx 293168526 Nov 4 22:17 eos4.11.0.swi
-rwx 36 Nov 8 10:24 boot-config
-rwx 37339 Jun 16 14:18 cfg_06162014
<-------OUTPUT OMITTED FROM EXAMPLE-------->
606638080 bytes total (602841088 bytes free)

And, finally, ensure that any extensions running on the primary supervisor are also available on the secondary supervisor.

Transfer the Image File to the Primary Supervisor

Load the desired image to the file system on the primary supervisor, typically into the flash. Use the CLI copy command to load files to the flash on the primary supervisor, then confirm that the new image file has been correctly transferred.

These command examples transfer an image file to flash from various locations.

USB Memory

Command 

copy usb1:/sourcefile flash:/destfile

Example 

Sch#copy usb1:/eos-4.13.2.swi flash:/eos-4.13.2.swi

FTP Server

Command 

copy ftp:/ftp-source/sourcefile flash:/destfile

Example 

Sch#copy ftp:/user:password@10.0.0.3/eos-4.13.2.swi flash:/eos-4.13.2.swi

SCP

Command 

copy scp://scp-source/sourcefile flash:/destfile

Example 

sch#copy scp://user:password@10.1.1.8/user/eos-4.13.2.swi flash:/eos-4.13.2.swi

HTTP

Command 

copy http://http-source/sourcefile flash:/destfile

Example 

sch#copy http://10.0.0.10/eos-4.13.2.swi flash:/eos-4.13.2.swi

Once the file has been transferred, verify that it is present in the directory, then confirm the MD5 checksum using the verify command. The MD5 checksum for each available image can be found on the eos download page of the Arista website.

switch#dir flash:
Directory of flash:/
-rwx293168526 Nov 422:17 eos4.11.0.swi
-rwx 36 Nov 810:24 boot-config
-rwx37339 Jun 16 14:18 cfg_06162014
-rwx394559902 May 30 02:57 eos-4.12.2.swi

<-------OUTPUT OMITTED FROM EXAMPLE-------->

606638080 bytes total (208281186 bytes free)
switch#53#verify /md5 flash:eos-4.13.2.swi 
verify /md5 (flash:eos-4.13.2.swi) =c277a965d0ed48534de6647b12a86991

Install the New eos Image

Once the eos image has been copied to the flash drive of the primary supervisor, use the install command to update the boot-config, copy the new image to the secondary supervisor and reload both supervisors. When upgrading to a new image, both supervisors will briefly be unavailable; using the install command minimizes packet loss during reload.

switch(config)#install source eos-4.13.2.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...

Verify the New Image

After the switch finishes reloading, log into the switch and use the show version command to confirm the correct image is loaded. The Software image version line displays the version of the active image file.

switch#show version
Arista DCS-7504
Hardware version:01.01
Serial number: JPE13120819
System MAC address:001c.7326.fd0c

Software image version: 4.13.2F
Architecture: i386
Internal build version: 4.13.2F-1649184.4132F.2
Internal build ID:eeb3c212-b4bd-4c19-ba34-1b0aa36e43f1

Uptime: 1 hour and 36 minutes
Total memory: 4017088 kB
Free memory:1473280 kB

switch#