Arista switching platforms are designed to work reliably in common data center environments.
To ensure their reliable operation and to monitor or diagnose the switch's health, Arista provides a set of monitoring capabilities available through the CLI or SNMP entity MIBs to monitor and diagnose potential problems with the switching platform.
In modular systems, cards are shut down when their temperatures exceed the critical threshold. The switch is shut down if the temperature remains above the critical threshold for three minutes.
The switch operates normally when one fan is not operating. Non-functioning modules should only be removed from the switch if they are immediately replaced; adequate switch cooling requires the installation of all components, including a non-functional fan.
Two non-operational fans trigger an insufficient fan shutdown condition. Under normal operations, this condition initiates a switch power-down procedure.
Fans are accessible from the rear panel.
Power supply LED indicators are visible from the rear panel.
The switch can be configured to continue operating during temperature shutdown conditions. Ignoring a temperature shutdown condition is strongly discouraged because operating at high temperatures can damage the switch and void the warranty.
Temperature shutdown condition actions are specified by the environment overheat action command. The switch displays this warning when configured to ignore shutdown temperature conditions.
switch(config)# environment overheat action ignore
====================================================================
WARNING: Overriding the system shutdown behavior when the system
is overheating is unsupported and should only be done under
the direction of an Arista Networks engineer. You risk damaging
hardware by not shutting down the system in this situation, and doing
so without direction from Arista Networks can be grounds for voiding
your warranty. To re-enable the shutdown-on-overheat behavior, use
the 'environment overheat action shutdown' command.
====================================================================
switch(config)#The running-config contains the environment overheat action command when set to ignore. When the command is not in running-config, the switch shuts down when an overheating condition exists.
The following running-config file lists the environment overheat action command.
switch# show running-config
! Command: show running-config
! device: switch (DCS-7150S-64-CL, EOS-4.13.2F)
ip route 0.0.0.0/0 10.255.255.1
!
environment overheat action ignore
!
!
endThe switch can be configured to ignore the insufficient fan shutdown condition. This is strongly discouraged because continued operation without sufficient cooling may lead to a critical temperature condition that can damage the switch and void the warranty.
Insufficient-fans shutdown override is configured by the environment insufficient-fans action command. The switch displays this warning when configured to ignore insufficient-fan conditions.
switch(config)# environment insufficient-fans action ignore
====================================================================
WARNING: Overriding the system shutdown behavior when the system
has insufficient fans inserted is unsupported and should only be done
under
the direction of an Arista Networks engineer. You risk damaging
hardware by not shutting down the system in this situation, and doing
so without direction from Arista Networks can be grounds for voiding
your warranty. To re-enable the shutdown-on-overheat behavior, use
the 'environment insufficient-fans action shutdown' command.
====================================================================
switch(config)#The running-config contains the environment insufficient-fans action command when set to ignore. When running-config does not contain this command, the switch shuts down when it detects an insufficient-fans condition.
The switch can be configured to override the automatic fan speed. The switch normally controls the fan speed to maintain optimal operating temperatures. The fans can be configured to operate at a constant speed regardless of the switch temperature conditions.
Fan speed override is configured by the environment fan-speed command. The switch displays this warning when its control of fan speed is overridden.
switch(config)# environment fan-speed override 50
====================================================================
WARNING: Overriding the system fan speed is unsupported and should only
be done under the direction of an Arista Networks engineer.
You can risk damaging hardware by setting the fan speed too low
and doing so without direction from Arista Networks can be grounds
for voiding your warranty.
To set the fan speed back to automatic mode, use the
'environment fan-speed auto' command
====================================================================
switch(config)#The running-config contains the environment fan-speed override command if it is set to override. When running-config does not contain this command, the switch controls the fan speed.
The show environment power command displays the status of the power supplies.
Example
This command displays the status of the power supplies.
switch> show environment power
Power Input Output Output
Supply Model Capacity Current Current Power Status
------- ------------- --------- -------- -------- -------- -------
1 PWR-650AC 650W 0.44A 10.50A 124.0W OkTo display internal temperature sensor status, enter show environment temperature.
switch> show environment temperature
System temperature status is: Ok
Alert Critical
Sensor Description Temperature Threshold Threshold
------- ------------------------- ------------ ---------- ----------
1 Front-panel temp sensor 22.000C 65C 75C
2 Fan controller 1 sensor 23.000C 75C 85C
3 Fan controller 2 sensor 28.000C 75C 85C
4 Switch chip 1 sensor 40.000C 105C 115C
5 VRM 1 temp sensor 48.000C 105C 110CThe show system environment cooling command displays the cooling and fan status.
Example
This command displays the fan and cooling status:
switch> show system environment cooling
System cooling status is: Ok
Ambient temperature: 22C
Airflow: port-side-intake
Fan Tray Status Speed
--------- --------------- ------
1 Ok 35%
2 Ok 35%
3 Ok 35%
4 Ok 35%
5 Ok 35%
switch>The show system environment all command lists the temperature, cooling, fan, and power supply information the individual show environment commands display, as described in Temperature Status, Fans, and Power.
Example
switch> show system environment all
System temperature status is: Ok
Alert Critical
Sensor Description Temperature Threshold Threshold
------- ------------------------ ------------- ---------- ----------
1 Front-panel temp sensor 22.750C 65C 75C
2 Fan controller 1 sensor 24.000C 75C 85C
3 Fan controller 2 sensor 29.000C 75C 85C
4 Switch chip 1 sensor 41.000C 105C 115C
5 VRM 1 temp sensor 49.000C 105C 110C
System cooling status is: Ok
Ambient temperature: 22C
Airflow: port-side-intake
Fan Tray Status Speed
--------- --------------- ------
1 Ok 35%
2 Ok 35%
3 Ok 35%
4 Ok 35%
5 Ok 35%
Power Input Output Output
Supply Model Capacity Current Current Power Status
------- ----------- --------- -------- -------- -------- -------
1 PWR-650AC 650W 0.44A 10.50A 124.0W OkWhen a component requires service, the switch administrator may use the locator-led command to assist a technician in finding the component. The command causes the status LED on the specified component to flash and display a “service requested” message on the LCD panel of modular switches or lights the blue locator light on the front of fixed switches. Use the show locator-led command to display all locator LEDs currently enabled on the switch.
switch# locator-led fantray 3
Enabling locator led for FanTray3switch# show locator-led
There are no locator LED enabledThe environment fan-speed command determines how to control the speed of the switch fans. By default, the switch automatically controls the fan speed.
The switch normally controls the fan speed to maintain optimal operating temperatures. The fans can be configured to operate at a constant speed regardless of the switch temperature conditions.
The no environment fan-speed and default environment fan-speed commands restore the default action of automatic fan-speed control by removing the environment fan-speed override statement from running-config.
Command Mode
Global Configuration
Command Syntax
environment fan-speed ACTION
no environment fan-speed
default environment fan-speed
Parameters
This option restores the default setting by removing the environment fan-speed override command from running-config
switch(config)# environment fan-speed override 50
====================================================================
WARNING: Overriding the system fan speed is unsupported and should
only be done under the direction of an Arista Networks engineer.
You can risk damaging hardware by setting the fan speed too low
and doing so without direction from Arista Networks can be grounds
for voiding your warranty.
To set the fan speed back to automatic mode, use the
'environment fan-speed auto' command
====================================================================
switch(config)#switch(config)# environment fan-speed auto
switch(config)#The environment insufficient-fans command controls the switch response to the insufficient fan condition. By default, the switch initiates a shutdown procedure when it senses insufficient fans.
The switch operates normally when one fan is not operating. Non-functioning modules should only be removed from the switch if they are immediately replaced; adequate switch cooling requires the installation of all components, including a non-functional fan.
Two non-operational fans trigger an insufficient fan shutdown condition. This condition normally initiates a power-down procedure.
The no environment insufficient-fans and default environment insufficient-fans commands restore the default shutdown response to the insufficient-fans condition by removing the environment insufficient-fans action ignore statement from running-config.
Command Mode
Global Configuration
Command Syntax
environment insufficient-fans action REMEDY
no environment insufficient-fans action
default environment insufficient-fans action
Parameters
The shutdown parameter restores default behavior by removing the environment insufficient-fans command from running-config.
switch(config)# environment insufficient-fans action ignore
====================================================================
WARNING: Overriding the system shutdown behavior when the system
has insufficient fans inserted is unsupported and should only be done
under the direction of an Arista Networks engineer. You risk damaging
hardware by not shutting down the system in this situation, and doing
so without direction from Arista Networks can be grounds for voiding
your warranty. To re-enable the shutdown-on-overheat behavior, use
the 'environment insufficient-fans action shutdown' command.
====================================================================switch(config)# environment insufficient-fans action shutdown
switch(config)#The environment overheat command controls the switch's response to an overheat condition. By default, the switch shuts down when it senses an overheat condition.
In modular systems, cards are shut down when their temperatures exceed the critical threshold. The switch normally shuts down if the temperature remains above the critical threshold for three minutes.
The no environment overheat action, and default environment overheat action commands restore the default shutdown response to the environment overheat condition by removing the environment overheat action ignore statement from running-config.
Command Mode
Global Configuration
Command Syntax
environment overheat action REMEDY
no environment overheat action
default environment overheat action
Parameters
switch(config)# environment overheat action ignore
====================================================================
WARNING: Overriding the system shutdown behavior when the system
is overheating is unsupported and should only be done under
the direction of an Arista Networks engineer. You risk damaging
hardware by not shutting down the system in this situation, and doing
so without direction from Arista Networks can be grounds for voiding
your warranty. To re-enable the shutdown-on-overheat behavior, use
the 'environment overheat action shutdown' command.
====================================================================
switch(config)#switch(config)# environment overheat action shutdown
switch(config)#When a component requires service, the locator-led command activates a locator to assist a technician in finding the component. The command causes the status LED on the specified component to flash and display a “service requested” message on the LCD panel of modular switches or lights the blue locator light on the front of fixed switches. The available locators vary by platform; to see a list of the locator LEDs available on the switch, use the locator-led ? command. To trun off the locator LED, use the no locator-led command.
Command Mode
Privileged EXEC
Command Syntax
locator-led {fantray tray_num | interface interface | module module_num | powersupply supply_num}
no locator-led {fantray tray_num | interface interface | module module_num | powersupply supply_num}
switch# locator-led fantray 3
Enabling locator led for FanTray3switch# no locator-led fantray 3
Disabling locator led for FanTray3switch# locator-led ?
fantray Fan tray LED
interface Interface LED
module Module LED
powersupply Power supply LEDThe show environment power command displays the status of all power supplies in the switch.
Command Mode
EXEC
Command Syntax
show environment power [INFO_LEVEL]
Parameters
Example
switch> show environment power
Power Input Output Output
Supply Model Capacity Current Current Power Status
------- ---------- --------- -------- -------- -------- -------
1 PWR-760AC 760W 0.81A 11.00A 132.8W Ok
2 PWR-760AC 760W 0.00A 0.00A 0.0W AC LossThe show environment temperature command displays the operating temperature of all sensors on the switch.
Command Mode
EXEC
Command Syntax
show environment temperature [MODULE_NAME] [INFO_LEVEL]
Display Values
switch> show environment temperature
System temperature status is: Ok
Alert Critical
Sensor Description Temperature Threshold Threshold
------- ------------------------ ------------ ---------- ----------
1 Front-panel temp sensor 30.750C 65C 75C
2 Fan controller 1 sensor 32.000C 75C 85C
3 Fan controller 2 sensor 38.000C 75C 85C
4 Switch chip 1 sensor 50.000C 105C 115C
5 VRM 1 temp sensor 60.000C 105C 110C
switch>
switch> show environment temperature detail
TempSensor1 - Front-panel temp sensor
Current State Count Last Change
Temperature 30.750C
Max Temperature 35.000C 4 days, 23:35:24 ago
Alert False 0 never
TempSensor2 - Fan controller 1 sensor
Current State Count Last Change
Temperature 32.000C
Max Temperature 36.000C 4 days, 23:32:46 ago
Alert False 0 never
TempSensor3 - Fan controller 2 sensor
Current State Count Last Change
Temperature 38.000C
Max Temperature 41.000C 4 days, 23:37:56 ago
Alert False 0 never
TempSensor4 - Switch chip 1 sensor
Current State Count Last Change
Temperature 51.000C
Max Temperature 53.000C 4 days, 23:35:16 ago
Alert False 0 never
TempSensor5 - VRM 1 temp sensor
Current State Count Last Change
Temperature 60.000C
Max Temperature 62.000C 4 days, 22:54:51 ago
Alert False 0 neverThe show locator-led command displays the status of locator LEDs enabled on the switch.
Command Mode
Privileged EXEC
Command Syntax
show locator-led
Example
switch# show locator-led
There are no locator LED enabled
switch#The show system environment all command displays temperature, cooling, and power supply status.
Command Mode
EXEC
Command Syntax
show system environment all
Example
switch> show system environment all
System temperature status is: Ok
Alert Critical
Sensor Description Temperature Threshold Threshold
------- ------------------------ ------------- ---------- ----------
1 Front-panel temp sensor 31.000C 65C 75C
2 Fan controller 1 sensor 32.000C 75C 85C
3 Fan controller 2 sensor 38.000C 75C 85C
4 Switch chip 1 sensor 50.000C 105C 115C
5 VRM 1 temp sensor 60.000C 105C 110C
System cooling status is: Ok
Ambient temperature: 31C
Airflow: port-side-intake
Fan Tray Status Speed
--------- --------------- ------
1 Ok 52%
2 Ok 52%
3 Ok 52%
4 Ok 52%
5 Ok 52%
Power Input Output Output
Supply Model Capacity Current Current Power Status
------- ----------- --------- -------- -------- -------- -------
1 PWR-760AC 760W 0.81A 11.00A 132.6W Ok
2 PWR-760AC 760W 0.00A 0.00A 0.0W AC LossThe show system environment cooling command displays fan status, air flow direction, and ambient temperature on the switch.
Command Mode
EXEC
Command Syntax
show system environment cooling [INFO_LEVEL]
Example
switch> show system environment cooling
System cooling status is: Ok
Ambient temperature: 30C
Airflow: port-side-intake
Fan Tray Status Speed
--------- --------------- ------
1 Ok 51%
2 Ok 51%
3 Ok 51%
4 Ok 51%
5 Ok 51%The show system environment power budget command displays the configured power budget for PoE switches and a table to show the current consumption.
Command Mode
EXEC
Command Syntax
show system environment power budget
Example
switch> show system environment power budget
Budget is 300.0W out of 1425.2W of total power
Active devices using up to 60.0W
Device Consumed
Name Power
----------------------- -----------------------
Ethernet37 30.0W
Ethernet38 30.0W
Total 60.0W This chapter describes the procedures for upgrading or downgrading the switch software.
Upgrading or downgrading the Arista Extensible Operating System (EOS) is accomplished by replacing the EOS image and reloading the switch. It may be possible to minimize (or virtually eliminate) downtime and packet loss during an upgrade, depending on the switch model and the software change being made. There are two upgrade methods for the EOS:
Smart System Upgrade: SSU significantly decreases downtime and packet loss during upgrades. SSU is available on selected platforms and is ideal for leaf switches and other non-redundant deployments.
Standard Upgrades and Downgrades: In cases where an accelerated upgrade is not needed or an option (such as software downgrades and on unsupported platforms), performing a standard upgrade or downgrade using the steps described here will minimize downtime and packet loss.
Smart System Upgrade (SSU) dramatically speeds up system upgrades and minimizes network disruptions with:
Before upgrading the EOS image, be sure you have copies of the currently running EOS version and the running-config file available in case of corruption during the upgrade process. To copy the running-config file, use the copy running-config command. In this example, the system copies the running-config contents to a file on the switch flash drive.
switch# copy running-config flash:/cfg_06162014
Copy completed successfully.
switch#Determine the size of the new EOS image. Verify enough space exists on the flash drive for two copies of this image, plus a recommended 240MB (if available) for diagnostic information in case of a fatal error. Use the dir command to check the bytes free figure.
switch# dir 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
606638080 bytes total (602841088 bytes free)Ensure the switch has a management interface configured with an IP address and default gateway. See Assigning a Virtual IP Address to Access the Active Ethernet Management Port and Configuring a Default Route to the Gateway. Confirm network connectivity to the switch using the show interfaces status command and pinging the default gateway.
switch# show interfaces status
Port Name Status Vlan Duplex Speed Type
Et3/1 notconnect 1 auto auto 1000BASE-T
<-------OUTPUT OMITTED FROM EXAMPLE-------->
Ma1/1 connected routed unconf unconf Unknown
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 msVerify the switch has a valid configuration for SSU using the show reload fast-boot command. If parts of the configuration block SSU execution, an error message displays explaining the issues. For SSU to proceed, correct the configuration conflicts before issuing the reload fast-boot command.
switch# show reload fast-boot
switch#'reload fast-boot' 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#For hitless restart of BGP and MP-BGP, BGP graceful restart must first be enabled using the graceful-restart command. The default restart time value (300 seconds) is appropriate for most configurations.
The BGP configuration mode issuing the graceful-restart command determines which BGP connections will restart gracefully.
switch# config
switch(config)# router bgp 64496
switch(config-router-bgp)# graceful-restart
switch(config-router-bgp)#switch# config
switch(config)# router bgp 64496
switch(config-router-bgp)# vrf purple
switch(config-router-bgp-vrf-purple)# graceful-restart
switch(config-router-bgp-vrf-purple)# exit
switch(config-router-bgp)#switch# config
switch(config)# router bgp 64496
switch(config-router-bgp)# address-family ipv6
switch(config-router-bgp-af)# graceful-restart
switch(config-router-bgp-af)# exit
switch(config-router-bgp)#Before performing a hitless upgrade on switches configured with MLAG, configure the reload-delay parameter to 0 using the following commands:
switch(config)# mlag
switch(config-mlag)# reload-delay 0If performing the upgrade on the primary MLAG switch, the switch first transitions to the secondary MLAG switch and becomes the primary switch.
All MLAG port channel interfaces with STP enabled shutdown locally on the MLAG peer undergoing the upgrade.
The target image must be copied to the file system on the switch, typically onto the flash drive:
The following command examples illustrate transferring an image file from various locations to the flash drive.
Command
copy usb1:/sourcefile
flash:/destfile
Example
switch# copy usb1:/EOS-4.14.4.swi flash:/EOS-4.14.4.swiCommand
copy
ftp:/ftp-source/sourcefile
flash:/destfile
Example
switch# copy ftp:/user:password@10.0.0.3/EOS-4.14.4.swi flash:/EOS-4.14.4.swiCommand
copy
scp://scp-source/sourcefile
flash:/destfile
Example
switch# copy scp://user@10.1.1.8/user/EOS-4.13.2.swi flash:/EOS-4.13.2.swiCommand
copy
http://http-source/sourcefile
flash:/destfile
Example
switch# copy http://10.0.0.10/EOS-4.14.4.swi flash:/EOS-4.14.4.swiAfter transferring the file, 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.14.2.swi
-rwx 36 Nov 8 10:24 boot-config
-rwx 37339 Jun 16 14:18 cfg_06162014
-rwx 394559902 May 30 02:57 EOS4.13.1.swi
606638080 bytes total (208281186 bytes free)
switch# verify /md5 flash:EOS-4.14.4.swi
verify /md5 (flash:EOS-4.14.4.swi) =c277a965d0ed48534de6647b12a86991After 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.14.4.swi.
switch# configure terminal
switch(config)# boot system flash:/EOS-4.14.4.swiUse the show boot-config command to verify that the boot-config file is correct:
switch(config)# show boot-config
Software image: flash:/EOS-4.14.4.swi
Console speed: (not set)
Aboot password (encrypted): $1$ap1QMbmz$DTqsFYeauuMSa7/Qxbi2l1Save the configuration to the startup-config file with the write command.
switch# writeAfter updating the boot-config file, verify that your configuration supports SSU (if you have not already done so) using the show reload fast-boot command. If parts of the configuration are blocking SSU execution, an error message will be displayed explaining what they are.
switch# show reload fast-boot
switch#'reload fast-boot' 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 portsStart the SSU process using the reload fast-boot command to reload the switch and activate the new image. The CLI will identify any changes that must be made to the configuration before starting SSU, prompt the saving of any modifications to the system configuration, and request confirmation before reloading.
switch# reload fast-boot
System configuration has been modified. Save? [yes/no/cancel/diff]:y
Copy completed successfully.
Proceed with reload? [confirm]yBefore making any configuration changes to the switch after reloading, verify that the SSU process is complete using the command show boot stages log. If it is, the last message should be Hitless boot stages complete.
switch# show boot stages log
Timestamp Delta Begin Msg
2022-10-03 12:42:06 000.000000 Asu Hitless boot stages started
2022-10-03 12:42:06 000.001592 stage CriticalAgent started
2022-10-03 12:42:06 000.001834 event CriticalAgent:PhyEthtool completed
[ . . . ]
2022-10-03 12:43:02 056.316874 stage BootSanityCheck is complete
2022-10-03 12:43:02 056.317491 Asu Hitless boot stages completeYou can also verify the completion of the SSU process by checking the syslog for the following message:
LAUNCHER-6-BOOT_STATUS: 'reload fast-boot' reconciliation completeTo verify whether the SSU upgrade was successful, use the show reload cause command. Suppose a fatal error occurred during the upgrade process. In that case, the switch will have completely rebooted, and the fatal error details will be displayed along with the directory containing the diagnostic information.
If the SSU upgrade has succeeded, it will read Hitless reload requested by the user.
switch# show reload cause
Reload Cause 1:
-------------------
Fatal error occurred during Asu Hitless boot. (stageMgr - LinkStatusUpdate timed out)
Reload Time:
------------
Reload occurred at Sun Oct 02 12:06:37 2022 PDT.
Recommended Action:
-------------------
The system rebooted due to a fatal error.
If the problem persists, contact your customer support representative.
Debugging Information:
-------------------------------
/mnt/flash/persist/fatalError-2022-10-02_120637switch# show reload cause
Reload Cause 1:
-------------------
Hitless reload requested by the user.
Reload Time:
------------
Reload occurred at Mon Oct 03 13:29:31 2022 PDT.
Recommended Action:
-------------------
No action necessary.
Debugging Information:
-------------------------------
None available.The show version command confirms whether the correct image is loaded. The Software image version: line displays the version of the active image file.
switch# show version
Arista DCS-7050QX-32-F
Hardware version: 02.00
Serial number: JPE14071098
System MAC address: 001c.7355.556f
Software image version: 4.14.5F-2353054.EOS4145F
Architecture: i386
Internal build version: 4.14.5F-2353054.EOS4145F
Internal build ID: e8748ea7-916d-4217-878f-4bfe2adc7122
Uptime: 4 minutes
Total memory: 3981328 kB
Free memory: 1342408 kBSSU supports scheduling an upgrade with the reload fast-boot in command. If the switch has unsaved configuration changes, or saved configuration changes that block an SSU upgrade, the scheduled reload stops at the scheduled time.
Use the reload fast-boot in command to schedule the upgrade at a specific time. The switch detects any unsaved configuration and prompts you to save the changes first. Replying no exits the command and the scheduled upgrade does not proceed.
switch# reload fast-boot in 10:00
System configuration has been modified. Save? [yes/no/cancel/diff]:yes
Copy completed successfully.
Proceed with reload? [confirm]y
Reload scheduled for Mon Jan 20 19:31:09 2025 (in 9 hours 59 minutes)
No warnings or unsupported configuration found.Specify the time to reboot in hours, for example, 10:00, as shown in the example.
Override the confirmation prompt by adding the optional parameter force and specify a reason using the reason.
switch# reload fast-boot in 10:00 force reason scheduled maintenance
Copy completed successfully.
Reload scheduled for Mon Jun 17 19:38:12 2024 (in 9 hours 59 minutes)
Reload reason: scheduled maintenance
No warnings or unsupported configuration found.To cancel a scheduled SSU reload, use the reload cancel command:
switch# reload cancel
Scheduled reload has been canceled.Use the following command to display information about scheduled SSU configurations:
switch# show reload fast-boot
Reload scheduled for Mon Jan 20 19:31:09 2025 (in 9 hours 59 minutes)
Reload reason: scheduled maintenance
No warnings or unsupported configuration found.If no scheduled reload exists on the switch, the command returns the following output:
switch# show reload fast-boot
No reload is scheduled
No warnings or unsupported configuration found.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, you must install the EOS image on both supervisors. Using the following procedures will minimize packet loss during a standard upgrade or downgrade.
These sections describe standard switch upgrade and downgrade procedures:
Before upgrading the EOS image, be sure you have copies of the currently running EOS version and the running-config file available in case of corruption during the upgrade process. To copy the running-config file, use the copy running-config command. In this example, the system copies the running-config contents to a file on the switch flash drive.
switch# copy running-config flash:/cfg_06162014
Copy completed successfully.
switch#Determine the size of the new EOS image. Verify enough space exists on the flash drive for two copies of this image, plus a recommended 240MB (if available) for diagnostic information in case of a fatal error. Use the dir command to check the bytes free figure.
switch# dir 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
606638080 bytes total (602841088 bytes free)Ensure the switch has a management interface configured with an IP address and default gateway. See Assigning a Virtual IP Address to Access the Active Ethernet Management Port and Configuring a Default Route to the Gateway. Confirm network connectivity to the switch using the show interfaces status command and pinging the default gateway.
switch# show interfaces status
Port Name Status Vlan Duplex Speed Type
Et3/1 notconnect 1 auto auto 1000BASE-T
<-------OUTPUT OMITTED FROM EXAMPLE-------->
Ma1/1 connected routed unconf unconf Unknown
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 msVerify the switch has a valid configuration for SSU using the show reload fast-boot command. If parts of the configuration block SSU execution, an error message displays explaining the issues. For SSU to proceed, correct the configuration conflicts before issuing the reload fast-boot command.
switch# show reload fast-boot
switch#'reload fast-boot' 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#For hitless restart of BGP and MP-BGP, BGP graceful restart must first be enabled using the graceful-restart command. The default restart time value (300 seconds) is appropriate for most configurations.
The BGP configuration mode issuing the graceful-restart command determines which BGP connections will restart gracefully.
switch# config
switch(config)# router bgp 64496
switch(config-router-bgp)# graceful-restart
switch(config-router-bgp)#switch# config
switch(config)# router bgp 64496
switch(config-router-bgp)# vrf purple
switch(config-router-bgp-vrf-purple)# graceful-restart
switch(config-router-bgp-vrf-purple)# exit
switch(config-router-bgp)#switch# config
switch(config)# router bgp 64496
switch(config-router-bgp)# address-family ipv6
switch(config-router-bgp-af)# graceful-restart
switch(config-router-bgp-af)# exit
switch(config-router-bgp)#Before performing a hitless upgrade on switches configured with MLAG, configure the reload-delay parameter to 0 using the following commands:
switch(config)# mlag
switch(config-mlag)# reload-delay 0If performing the upgrade on the primary MLAG switch, the switch first transitions to the secondary MLAG switch and becomes the primary switch.
All MLAG port channel interfaces with STP enabled shutdown locally on the MLAG peer undergoing the upgrade.
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 system transferred the new image file correctly.
The following command examples illustrate transferring an image file from various locations to the flash drive.
Command
copy usb1:/sourcefile
flash:/destfile
Example
switch# copy usb1:/EOS-4.13.2.swi flash:/EOS-4.13.2.swiCommand
copy
ftp:/ftp-source/sourcefile
flash:/destfile
Example
switch# copy ftp:/user:password@10.0.0.3/EOS-4.13.2.swi flash:/EOS-4.13.2.swiCommand
copy
scp://scp-source/sourcefile
flash:/destfile
Example
switch# copy scp://user@10.1.1.8/user/EOS-4.13.2.swi flash:/EOS-4.13.2.swiCommand
copy
http://http-source/sourcefile
flash:/destfile
Example
switch# copy http://10.0.0.10/EOS-4.13.2.swi flash:/EOS-4.13.2.swiAfter transferring the file, 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
-rwx 36 Nov 8 10:24 boot-config
-rwx 37339 Jun 16 14:18 cfg_06162014
-rwx 394559902 May 30 02: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 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.swiUse 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/Qxbi2l1Save the configuration to the startup-config file with the write command.
switch# writeAfter 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.
The terminal displays all rebooting messages when reloading from the console port. From any port except the console, the CLI displays this text:
switch# reload
The system is going down for reboot NOW!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 kBTo prepare the switch for an EOS upgrade, take the following steps:
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 the following example, the running-config file is copied to a file called backup2 on the flash drive.
switch# copy running-config backup2
Copy completed successfully.
switch#Be sure you log into the primary supervisor, not the standby. Use the show redundancy status command, and verify that my status 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 heartbeatsBe sure the switch has a management interface configured with an IP address and default gateway. Refer to the sections 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 have an Up state and can ping the default gateway by using the show interfaces status command and ping command.
switch# show interfaces status
Port Name Status Vlan Duplex Speed Type
Et3/1 notconnect 1 auto auto 1000BASE-T
<-------OUTPUT OMITTED FROM EXAMPLE-------->
Ma1/1 connected routed unconf unconf Unknown
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 msDetermine 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 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)
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)Finally, ensure that any extensions running on the primary supervisor are also available on the secondary 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 system transferred the new image file correctly.
The following command examples illustrate transferring an image file from various locations to the flash drive.
Command
copy usb1:/sourcefile
flash:/destfile
Example
switch# copy usb1:/EOS-4.13.2.swi flash:/EOS-4.13.2.swiCommand
copy
ftp:/ftp-source/sourcefile
flash:/destfile
Example
switch# copy ftp:/user:password@10.0.0.3/EOS-4.13.2.swi flash:/EOS-4.13.2.swiCommand
copy
scp://scp-source/sourcefile
flash:/destfile
Example
switch# copy scp://user@10.1.1.8/user/EOS-4.13.2.swi flash:/EOS-4.13.2.swiCommand
copy
http://http-source/sourcefile
flash:/destfile
Example
switch# copy http://10.0.0.10/EOS-4.13.2.swi flash:/EOS-4.13.2.swiAfter transferring the file, 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:/
-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
-rwx 394559902 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) =c277a965d0ed48534de6647b12a86991After the EOS image has been copied to the primary supervisor's flash drive, use the install command to update the boot-config, copy the new image to the secondary supervisor, and reload both supervisors. Both supervisors will briefly be unavailable when upgrading to a new image; 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...After the switch finishes reloading, log in to 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#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]
Example
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...Smart System Upgrade (SSU) allows critical switches to be upgraded with minimal downtime and packet loss by optimizing the reload procedure and leveraging protocols capable of graceful restart. The reload fast-boot command starts the SSU process using the EOS image specified by the boot-config file configured by the boot system command.
When entering the reload fast-boot command, 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.
Command Mode
Privileged EXEC
Command Syntax
reload fast-boot
switch# reload fast-boot
Proceed with reload? [confirm]switch# reload fast-boot
switch#'reload fast-boot' 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 portsswitch# reload fast-boot
System configuration has been modified. Save? [yes/no/cancel/diff]:y
Copy completed successfully.
Proceed with reload? [confirm]yThe reload hitless command is a legacy command now identical to the reload fast-boot command. It starts the Smart System Upgrade (SSU) process using the EOS image specified by the boot-config file configured by the using the boot system command.
Command Mode
Privileged EXEC
Command Syntax
reload hitless
switch# reload hitless
Proceed with reload? [confirm]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 portsswitch# reload hitless
System configuration has been modified. Save? [yes/no/cancel/diff]:y
Copy completed successfully.
Proceed with reload? [confirm]y