When you replace an Arista top-of-rack (ToR) or spine switch in a rack, you must replace it with a Arista switch that has the same identical specifications as the one you are replacing. The replacement ToR or spine switch must be the same model and have the same version of the Arista switch operating system as the one it is replacing.
Before you begin
Verify your Cloud Foundation environment is operational. You can do this by verifying that the workload domains you have in the environment are running.
Verify that backups have been taken of the component configurations. If the backups have not been taken, take the backups as described in Back Up Component Configurations Using the SoS Tool.
Verify you have the following items:
The backup file of the to-be-replaced Arista ToR or switch's configuration. In the set of backups taken by the SoS tool for the rack, this file is named ToR-or-spine-switch-IP-address-arista-running-config.gz where ToR-or-spine-switch-IP-address is the switch's IP address, such as 192.168.0.20-arista-running-config.gz for a ToR switch with IP address of 192.168.0.20. For the location of this file within the SoS tool's output, see Back Up Component Configurations Using the SoS Tool.
The credentials for the management switch of the rack which has the ToR or spine switch you are replacing. Steps in the replacement procedure require copying files to and from the management switch. For steps on how to look up this password, see Look Up Account Credentials Using the Lookup-Password Command.
A replacement Arista switch of the same model as the Arista switch you are replacing.
A diagram or photo of the to-be-replaced switch's wiring, so that you can refer to it after you have disconnected the switch. See the Cloud Foundation VIA User's Guide for the switch wiremaps.
Verify the replacement switch has the same version of the Arista OS installed on it that is supported for use in this Cloud Foundation release. For the Arista OS version that is supported in this release, see the Release Notes.
About this task
For a list of the Arista switch models that are supported for use as a ToR or spine switch in this release, see VMware Cloud Foundation Compatibility Guide.
The goal of this procedure is to restore the previously taken backup configuration of the working state of the system on to the replacement ToR or spine switch.
- Copy the to-be-replaced switch's backup configuration file to its rack's management switch's /var/tmp directory.
scp ToR-or-spine-switch-IP-address-arista-running-config.gz firstname.lastname@example.org:/var/tmp
As an example, when replacing the Arista ToR switch with IP address 192.168.0.20, you copy the backup configuration file named 192.168.0.20-arista-running-config.gz to the management switch in that ToR switch's rack.
- Disconnect the switch you are replacing and remove it from the rack.
- Install the replacement switch into the rack and wire it according to the same wiring connections the previous one had.
Refer to the diagram or photo you took of the previous switch before removing it or to the wiring diagrams in the Cloud Foundation VIA User's Guide.
- Boot the newly installed switch and cancel the Zero Touch Provisioning (ZTP) mode.
AristaSwitch# zerotouch cancel
- Log in to the replacement switch, using the default credentials that came with your replacement switch.
- Using the original switch's IP address, configure that same IP address with subnet mask /24 on the new switch on the interface named management1.
As an example, when replacing a ToR switch that has IP address 192.168.0.20, you configure the management1 interface as:
interface management1 ip address 192.168.0.20/24
When replacing a spine switch that has IP address 192.168.0.31, you configure the management1 interface as:
interface management1 ip address 192.168.0.31/24
- Verify the newly installed switch can reach the management switch (at IP 192.168.100.1) by using the ping command.
AristaSwitch# ping 192.168.100.1 PING 192.168.100.1 (192.168.100.1): 56 data bytes 64 bytes from 192.168.100.1: icmp seq=0 ttl=63 time=1.574 ms ...
- Copy the previous switch's backup configuration file to the newly installed switch from the location on the rack's management switch where you copied it in 1.
As an example, when replacing the Arista ToR switch that has the backup configuration file named 192.168.0.20-arista-running-config.gz that was copied to the /var/tmp location on the rack's management switch at IP address 192.168.100.1:
AristaSwitch#copy scp:email@example.com/var/tmp/192.168.0.20-arista-running-config.gz flash:/ 192.168.0.20-arista-running-config.gz firstname.lastname@example.org's password: ******* 192.168.0.20-arista-running-config.gz 100% 1761 1.7KB/s 00:00 Copy completed successfully. AristaSwitch#
- Use the dir flash command to verify the backup configuration file was copied to the flash.
- Go into bash and decompress the copied backup configuration file .
Using the example from the previous step:
AristaSwitch# bash Arista Networks EOS shell [admin@ AristaSwitch ~]$ cd /mnt/flash [admin@ AristaSwitch flash]$ gunzip 192.168.0.20-arista-running-config.gz
As a result of this step, the extension .gz is removed from the file.
- Exit out of bash.
[admin@ AristaSwitch flash]$ exit AristaSwitch#
- Copy the backup configuration file that resulted from the decompression to the switch's startup configuration.
Using the example from the previous step:
AristaSwitch# copy flash: 192.168.0.20-arista-running-config startup-config
- Copy the switch's startup configuration to its running configuration.
AristaSwitch# copy startup-config running-config
The replacement switch is in place and has the backup configuration from the switch it replaced.
What to do next
Verify the new switch is operating correctly by seeing if all hosts and virtual machines are reachable from both ToR switches or both spine switches, depending on which type you replaced.