End of Support

Configuration Files

Three files define boot and running configuration parameters.

boot-config: contains the location and name of the image to be loaded.
running-config: contains the current switch configuration.
startup-config: contains the switch configuration that is loaded when the switch boots.

The running-config and startup-config are different since the configuration changes have not changed since the last boot.

boot-config

The boot-config file is an ASCII file that Aboot uses to configure console communication settings, locate the EOS flash image, and specify initial network configuration settings.

Aboot boots the EOS flash software image (extension .swi) referenced by boot-config if the user does not interrupt the boot process. See Aboot Shell, which describes how Aboot uses boot-config.

You can view and edit the boot-config file contents. Viewing and editing options include:

View boot-config file contents with the more boot-config command:

switch(config)# more boot-config
SWI=flash:/EOS.swi
CONSOLESPEED=2400
Aboot password (encrypted): $1$A8dZ3GLZ$knKrBpTyg5dhmtGdCdwNM.
switch(config)#

View boot-config settings with the show boot-config command:

switch(config)# show boot-config
Software image: flash:/EOS.swi
Console speed: 2400
Aboot password (encrypted): $1$A8dZ3GLZ$knKrBpTyg5dhmtGdCdwNM.
Memory test iterations: (not set)
switch(config)#

Modify file settings from the command line with EOS boot commands.
See Programming boot-config from the Programming boot-config from the CLI for a list of boot commands.
Edit the file directly by using vi from the Bash shell.

See boot-config Command Line Content for a list of boot-config parameters.

boot-config File Structure

Each line in the boot-config file specifies a configuration setting and has this format:

NAME=VALUE

NAME is the parameter label.
VALUE indicates the parameter’s bootup setting.

The NAME and VALUE fields cannot contain spaces.

Aboot ignores blank lines and lines that begin with a # character.

boot-config Command Line Content

Aboot configuration commands that boot-config files can contain include:

SWI specifies the location and file name of the EOS image file that Aboot loads when booting, using the same format as the boot command to designate a local or network path.

Example

SWI=flash:EOS.swi             <---flash drive location
SWI=usb1:/EOS1.swi            <---USB drive location
SWI=file:/tmp/EOSexp.swi      <---switch directory location
SWI=/mnt/flash/EOS.swi
SWI=http://foo.com/images/EOS.swi
SWI=ftp://foo.com/images/EOS.swi
SWI=tftp://foo.com/EOS.swi
SWI=nfs://foo.com/images/EOS.swi

CONSOLESPEED specifies the console baud rate. The connected terminal must match the specified rate to communicate with the switch. Baud rates options include 1200, 2400, 4800, 9600, 19200, 38400, 57600, and 115200. The default baud rate is 9600.
Example
```
CONSOLESPEED=19200
```
PASSWORD (ABOOT) specifies the Aboot password, as described in Accessing the Aboot Shell. The Aboot shell does not require a password when boot-config does not contain a PASSWORD command.
Example
```
PASSWORD=$1$CdWp5wfe$pzNtE3ujBoFEL8vjcq7jo/
```
Aboot uses NET commands during switch booting to configure the network interface for the switch. You can enter this manually in Aboot.
NETDEV indicates the configured network interface. If boot-config does not contain a NETDEV command, the booting process does not attempt to configure a network interface. Other NET commands specify settings that Aboot uses to configure the interface.

Examples

This NETDEV command specifies management port 1 as the network interface to be configured by boot-config:
```
NETDEV=ma1
```
This NETAUTO command instructs the switch to configure the network interface through a DHCP server, ignoring other NET settings:
```
NETAUTO=dhcp
```

These NET commands configure the network interface:

NETIP=10.12.15.10
NETMASK=255.255.255.0
NETGW=10.12.15.24
NETDOMAIN=mycompany.com
NETDNS=10.12.15.13

Programming boot-config from the CLI

The switch CLI provides boot commands for editing boot-config content. The boot commands are not accessible from a console port CLI. You can modify parameters by directly editing the boot-config file, which is not configurable from a boot command.

Commands that configure boot parameters include boot system, boot secret, and boot console.

boot system

The boot system command provides the EOS image file location to Aboot.

Examples

This command specifies EOS1.swi as the software image load file on USB flash memory.
```
switch(config)# boot system usb1:EOS1.swi
switch(config)#
```
The boot system command adds this line to boot-config.
```
SWI=usb1:/EOS1.swi
```
This command designates EOS.swi as the EOS software image load file on the switch flash.
```
switch(config)# boot system flash:EOS.swi
switch(config)#
```
The boot system command adds this line to boot-config respectively:
```
SWI=flash:/EOS.swi
```

boot secret

The boot secret command sets the Aboot password.

Examples

These equivalent commands set the Aboot password to xr19v.

switch(config)# boot secret xr19v
switch(config)#

switch(config)# boot secret 0 xr19v
switch(config)#

This command shows the set password.

switch(config)# show boot-config
Software image: flash:/EOS.swi
Console speed: (not set)
Aboot password (encrypted): $1$k9YHFW8D$cgM8DSN.e/yY0p3k3RUvk.
switch(config)#

The boot secret commands earlier add this line to boot-config:

PASSWORD=$1$k9YHFW8D$cgM8DSN.e/yY0p3k3RUvk.

The user must enter xr19v at the login prompt to access the Aboot shell.

This command sets the Aboot password to xr123. The encrypted string generated previously is xr123 as the clear-text seed.
```
switch(config)# boot secret 5 $1$QfbYkVWb$PIXG0udEquW0wOSiZBN3D/
switch(config)#
```

This command shows the set password.

switch(config)# show boot-config
Software image: flash:/EOS.swi
Console speed: (not set)
Aboot password (encrypted): $1$QfbYkVWb$PIXG0udEquW0wOSiZBN3D/
switch(config)#

The boot secret command earlier adds this line to boot-config:
```
PASSWORD=$1$QfbYkVWb$PIXG0udEquW0wOSiZBN3D/
```
The user must enter xr123 at the login prompt to access the Aboot shell.
This command removes the Aboot password; it does not authenticate subsequent Aboot access.
```
switch(config)# no boot secret
switch(config)#
```

This command shows that there is now no Aboot password.

switch(config)# show boot-config
Software image: flash:/EOS.swi
Console speed: (not set)
Aboot password (encrypted): (not set)
switch(config)#

boot console

The boot console command sets console settings for attaching devices.

Examples

This command sets the console speed to 4800 baud:

switch(config)# boot console speed 4800
switch(config)#

This command shows the console speed.

switch(config)# show boot-config
Software image: flash:/EOS.swi
Console speed: 4800
Aboot password (encrypted): (not set)
switch(config)#

The boot console command earlier adds this line to boot-config:
```
CONSOLESPEED=4800
```

install bios source

The install bios source command loads an Aboot Update File (AUF) to provide a signed method of upgrading Aboot.

Examples

This command installs the file update.auf stored in /mnt/flash:

switch# install bios source flash:/update.auf
switch(config)#

This command performs a reboot directly after the installation:

switch# install bios source flash:/update.auf reload
switch(config)#

This command skips the prompts and performs the installation automatically:
```
switch# install bios source flash:/update.auf now
switch(config)#
```
This command performs the installation only on the standby supervisor:
```
switch# install bios source flash:/update.auf standby
switch(config)#
```
Note: On a modular system with two supervisors, Aboot gets upgraded on both by default.

running-config

The running-config is a virtual file that contains the system’s operating configuration, formatted as a command sequence. Commands entered from the CLI modify the running-config, and copying a file to running-config updates the operating configuration by executing the commands in the copied file.

Commands for viewing and copying running-config include:

show running-config displays the contents of running-config.
copy running-config startup-config copies running-config contents to startup-config.
write copies running-config contents to startup-config.

startup-config

The startup-config file is stored in flash memory and contains the configuration the switch loads when booting. During a switch boot, startup-config replaces the running-config. When the system reboots, changes to running-config that are not in startup-config are lost.

Commands affecting startup-config include:

show startup-config displays the contents of startup-config.
copy file_name startup-config copies contents of the specified file to startup-config.
delete startup-config deletes the startup-config file.

Supervisor Redundancy

On modular switches with redundant supervisor modules, the standby supervisor switch can take control to minimize downtime and data loss in the case of an active supervisor's reset, reload, or failure. The redundancy protocol configured on the active supervisor determines the switchover.

Use the show redundancy status command to display both the supervisors' state and the current redundancy protocol. Use the show redundancy file-replication command to display the state of configuration file synchronization between the supervisors,

Redundancy Supervisor Protocols

There are three available supervisor redundancy protocols.

Route Processor Redundancy (RPR)

The default redundancy protocol is Route Processor Redundancy (RPR), which synchronizes startup-config files between the supervisor modules and partially boots the standby supervisor to a standby warm state but does not synchronize running-config. If the active supervisor fails or a manual switchover initiates with the redundancy manual switchover command, the standby supervisor will become active. The running state, including the spanning tree, is lost, bringing down all links temporarily.

Under RPR, you can access the CLI of the standby supervisor by SSH or through the console port, but the available command set is limited. Any configuration changes made to the standby supervisor will be lost when the supervisor reboots.

Stateful Switchover (SSO)

In the Stateful Switchover (SSO) protocol, the switch synchronizes startup-config and running-config files between the supervisor modules. It fully boots the standby module to a standby hot state to speed up the switchover process and minimize packet loss. If the active supervisor fails or a manual switchover initiates, the standby supervisor immediately becomes active, and the L2 running state is maintained. An SSO switchover is largely transparent from the outside. Still, because the L3 state is not synchronized, the switchover can result in traffic loss for traffic forwarded on routes learned by a dynamic routing protocol. Enabling nonstop forwarding can eliminate most packet loss for BGP and OSPF.

Under SSO, the console port can access the CLI of the standby supervisor, and the command set is limited. Any configuration changes made on the standby supervisor will be lost when the supervisor reboots.

Note: When upgrading the EOS on a dual-supervisor switch to an SSO-capable version (4.11.0 or higher) from a version that does not support SSO, both supervisors will reset simultaneously, causing several seconds of system downtime.

Simplex

When a simplex protocol is on the switch, the standby supervisor is disabled, and switchover will not occur even if the active supervisor fails. To reload the active supervisor results in system downtime while the supervisor reboots and the standby supervisor remains disabled. The redundancy protocol must change to RPR or SSO to transfer control of the switch to the standby supervisor.

Under the simplex protocol, the console port can access the CLI of the disabled supervisor, and the command set is limited. Any configuration changes made on the standby supervisor will be lost when the supervisor reboots.

Configuring Supervisor Redundancy

To configure the supervisor redundancy protocol, use the protocol command in redundancy configuration mode (accessed with the redundancy command).

Changing the redundancy protocol on the active supervisor resets the standby supervisor regardless of redundancy protocol, and executing the write command on the active supervisor synchronizes the startup-config files between supervisors in RPR and SSO modes.

Examples

These commands display the current redundancy state of the switch and the most recent file synchronization information.

switch# show redundancy state
  my state = ACTIVE
peer state = STANDBY WARM
      Unit = Primary
   Unit ID = 1

Redundancy Protocol (Operational) = Route Processor Redundancy
Redundancy Protocol (Configured) = Route Processor Redundancy
Communications = Up
Ready for switchover

  Last switchover time = 7:23:56 ago
Last switchover reason = Supervisor has control of the active supervisor lock
switch# show redundancy file-replication
0 files unsynchronized, 2 files synchronized, 0 files failed, 2 files total.

File                   Status         Last Synchronized
---------------------- -------------- -------------------
file:persist/sys       Synchronized   0:10:04 ago
flash:startup-config   Synchronized   0:10:04 ago
switch#

These commands set the redundancy protocol for the active supervisor to stateful switchover (SSO).

switch# config
switch(config)# redundancy
switch(config-redundancy)# protocol sso
Peer supervisor will be restarted.
switch(config-redundancy)#

System Reset

When a reset condition exists, Aboot can either reset the switch without user intervention or facilitate a manual reset through the Aboot shell. A reset operation clears the switch, including memory states and other hardware logic.

Fixed systems: The power supply remains powered up during the reset. All other switch components lose power for two to five seconds.
Modular systems: The power supply on the active supervisor remains powered up during the reset. All other supervisor components lose power for at least one second. In Stateful Switchover (SSO) and Route Processor Redundancy (RPR) modes, resetting the standby supervisor does not affect the active supervisor. However, resetting the active supervisor causes the standby supervisor to become active immediately. After the supervisor becomes functional, it manages the power cycling of all line cards.

The reload command initiates an immediate reset, terminating all CLI instances not running through the console port. The console port CLI displays messages that the switch generates during a reset. The standby supervisor does not terminate CLI sessions on modular switches with redundant supervisors.

The reload (scheduled) command schedules a reset operation to initiate at a specific time or after a specified period.

Typical Reset Sequence

The reload command power cycles the switch and resets it under Aboot control. The hard reset clears the switch, including memory states and other hardware logic.

By default, the reload command triggers a request to store unsaved running-config commands and an option to open the Aboot shell before starting the reboot when accessing the CLI through the console port. The switch then begins the reboot process, which Aboot controls.

The following procedure is an example of a typical restart.

Begin the reboot process by typing the reload command:
```
switch# reload
```
The switch sends a message to confirm the reload request:
```
Proceed with reload? [confirm]
```
Select enter or type y to confirm the requested reload. Pressing any other key terminates the reload operation.
The switch sends a series of messages, including a notification that a message was broadcast to all open CLI instances, informing them that the system rebooted. The reload pauses when the CLI displays the Aboot shell notification line.
```
Broadcast message from root@mainStopping sshd: [ OK ] 
SysRq : Remount R/O 
Restarting system 
 
Aboot 1.9.0-52504.EOS2.0 
 
Press Control-C now to enter Aboot shell
```
To continue the reload process, do nothing. Typing Ctrl-C opens the Aboot shell; see Aboot Commands for Aboot editing instructions.

The switch continues the reset process, displaying messages indicating the completion of individual tasks. The reboot is complete when the CLI displays a login prompt.

Booting flash:/EOS.swi 
Unpacking new kernel 
Starting new kernel 
Switching to rooWelcome to Arista Networks EOS 4.4.0 
Mounting filesystems: [ OK ] 
Entering non-interactive startup 
Starting EOS initialization stage 1: [ OK ] 
ip6tables: Applying firewall rules: [ OK ] 
iptables: Applying firewall rules: [ OK ] 
iptables: Loading additional modules: nf_conntrack_tftp [ OK ] 
Starting system logger: [ OK ] 
Starting system message bus: [ OK ] 
Starting NorCal initialization: [ OK ] 
Starting EOS initialization stage 2: [ OK ] 
Starting ProcMgr: [ OK ] 
Completing EOS initialization: [ OK ] 
Starting Power On Self Test (POST): [ OK ] 
Generating SSH2 RSA host key: [ OK ] 
Starting isshd: [ OK ] 
Starting sshd: [ OK ] 
Starting xinetd: [ OK ] 
[ OK ] crond: [ OK ] 
 
switch login:

Switch Recovery

Aboot can automatically erase the internal flash and copy the contents of a USB drive inserted before powering up or rebooting the switch. This recovery method does not require access to the switch console or Aboot password entry, even if the boot-config file lists one.

Aboot invokes the recovery mechanism only in each of these two conditions:

The USB drive must contain a file called “fullrecover.”
It ignores the file’s contents; an empty text file is sufficient.
If the USB drive contains a boot-config file, its timestamp must differ from the timestamp of the boot-config file on the internal flash.
This prevents Aboot from invoking the recovery mechanism again on every boot if you leave the flash key inserted.

To use this recovery mechanism, set up and install the USB drive with the current EOS software image, a customized or empty boot-config, and an empty file named “fullrecover.”

Check that the boot-config timestamp is current to meet the earlier conditions.

Display Reload Cause

The show reload cause command displays the cause of the most recent system reset and lists recommended actions, if any exist, to avoid future spontaneous resets or resolve other issues that may have caused the reset.

Example

To display the 'reset cause', type show reload cause at the prompt.

switch# show reload cause
Reload Cause 1:
-------------------
Reload requested by the user.

Recommended Action:
-------------------
No action necessary.

Debugging Information:
----------------------
None available.
switch#

Configuring Zero Touch Provisioning

Zero Touch Provisioning (ZTP) is a switch configuration method that uses files referenced by a DCHP server to initially provision the switch without user intervention. A switch enters ZTP mode if flash memory does not reload a startup-config or zerotouch-config file.

ZTP cancelation boots the switch without using a startup-config file. Flash memory does not store a startup-config file for a canceled ZTP mode. The switch returns to ZTP mode on subsequent reboots until the startup-config file stores to flash. This section describes the steps to implement, monitor, and cancel ZTP.

Configuring the Network for ZTP

A switch performs the following after booting in ZTP mode:

It configures each physical interface to no switchport mode.
It sends a DHCP query packet on all Ethernet and management interfaces.

After the switch receives a DHCP offer, it responds with a DHCP request for Option 66 (TFTP server name), Option 67 (bootfile name), and dynamic network configuration settings. When the switch receives a valid DHCP response, it configures the network settings and fetches the file from the location listed in Option 67. If Option 67 returns a network URL (http:// or ftp://), the switch obtains the file from the network. If Option 67 returns a file name, the switch retrieves the file from the TFTP server listed in Option 66.

The Option 67 file can be a startup-config file or a boot script. The switch distinguishes between a startup-config file and a boot script by examining the first line in the file:

The first line of a boot file must consist of the #! characters followed by the interpreter path. The switch executes the code in the script and then reboots. The boot script may fetch an EOS software image or perform customization tasks.
The following boot file fetches an EOS software image and stores a startup configuration file to flash.
```
#!/usr/bin/Cli -p2
copy http://company.com/startup-config flash:startup-config
copy http://company.com/EOS-2.swi flash:EOS-2.swi
config
boot system flash:EOS-2.swi
```
The switch identifies any other file as a startup-config file. The switch copies the startup-config file into flash as mnt/flash/startup-config, then reboots.
The switch uses its system MAC address as the DHCP client identifier and Arista as the Vendor Class Identifier (Option 60). When the switch receives an HTTP URL through Option 67, it sends the following HTTP headers in the GET request:
```
X-Arista-SystemMAC:
X-Arista-HardwareVersion:
X-Arista-SKU:
X-Arista-Serial:
X-Arista-Architecture:
```

Monitoring ZTP Progress

A switch displays the following message after rebooting when it does not contain a startup-config file:

No startup-config was found.

The device is in Zero Touch Provisioning mode and is attempting to
download the startup-config from a remote system. The device will not  
be fully functional until a valid startup-config is downloaded
from a remote system or Zero Touch Provisioning is canceled. To cancel
Zero Touch Provisioning, login as admin and type 'zerotouch cancel'
at the CLI.

switch login:

After successfully downloading a startup-config file, the switch displays a CONFIG_DOWNLOAD_SUCCESS message and continues the reload process described in the Typical Reset Sequence.

===============================================================================

Successful download
--------------------


Apr 15 21:36:46 switch ZeroTouch: %ZTP-5-DHCP_QUERY: Sending DHCP request on  [ 
Ethernet10, Ethernet13, Ethernet14, Ethernet17, Ethernet18, Ethernet21, 
Ethernet22, Ethernet23, Ethernet24, Ethernet7, Ethernet8, Ethernet9, 
Management1, Management2 ]
Apr 15 21:36:56 switch ZeroTouch: %ZTP-5-DHCP_SUCCESS: DHCP response received on 
Ethernet24  [ Mtu: 1500; Ip Address: 10.10.0.4/16; Nameserver: 10.10.0.1; Domain: 
aristanetworks.com; Gateway: 10.10.0.1; Boot File: 
http://10.10.0.2:8080/tmp/172.17.11.196-startup-config.1 ]
Apr 15 21:37:01 switch ZeroTouch: %ZTP-5-CONFIG_DOWNLOAD: Attempting to download 
the startup-config from http://10.10.0.2:8080/tmp/172.17.11.196-startup-config.1
Apr 15 21:37:02 switch ZeroTouch: %ZTP-5-CONFIG_DOWNLOAD_SUCCESS: Successfully 
downloaded startup-config from 
http://10.10.0.2:8080/tmp/172.17.11.196-startup-config.1
Apr 15 21:37:02 switch ZeroTouch: %ZTP-5-RELOAD: Rebooting the system
Broadcast messagStopping sshd: [  OK  ]
watchdog is not running
SysRq : Remount R/O
Restarting system


Aboot 1.9.0-52504.EOS2.0


Press Control-C now to enter Aboot shell

ZTP Failure Notification

The switch displays a DHCP_QUERY_FAIL message when it does not receive a valid DHCP response within 30 seconds of sending the query. The switch then sends a new DHCP query and waits for a response. The switch sends queries until it receives a valid response or cancels ZTP mode.

switch login: admin
admin
switch>Apr 15 21:28:21 localhost ZeroTouch: %ZTP-5-DHCP_QUERY: Sending DHCP 
request on  [ Ethernet10, Ethernet13, Ethernet14, Ethernet17, Ethernet18, 
Ethernet21, E-thernet22, Ethernet23, Ethernet24, Ethernet7, Ethernet8, 
Ethernet9, Management1, Management2 ]
Apr 15 21:28:51 localhost ZeroTouch: %ZTP-5-DHCP_QUERY_FAIL: Failed to get a 
valid DHCP response
Apr 15 21:28:51 localhost ZeroTouch: %ZTP-5-RETRY: Retrying Zero Touch 
Provisioning from the beginning (attempt 1)
Apr 15 21:29:22 localhost ZeroTouch: %ZTP-5-DHCP_QUERY: Sending DHCP request on  
[ Ethernet10, Ethernet13, Ethernet14, Ethernet17, Ethernet18, Ethernet21, 
Ethernet22, Ethernet23, Ethernet24, Ethernet7, Ethernet8, Ethernet9, 
Management1, Management2 ]

Canceling ZTP Mode

Log into the console to boot the switch without a startup-config file, then cancel ZTP mode. After the switch boots, it uses all factory default settings. Flash memory prevents the switch from entering ZTP mode on subsequent boots when a startup-config file exits.

Configuring the Networks

If the boot-config file contains a NETDEV statement, Aboot attempts to configure the network interface as specified by Network configuration commands. See boot-config Command Line Content for a list of commands that define the network configuration.

Aboot Shell

The Aboot shell is an interactive command-line interface used to manually boot a switch, restore the internal flash to its factory-default state, run hardware diagnostics, and manage files. The Aboot shell resembles the Linux Bourne Again Shell (Bash).

The Aboot shell provides commands for restoring the state of the internal flash to factory defaults or a customized default state. You can select these recovery methods to:

Restore the factory-default flash contents before transferring the switch to another owner.
Restore Aboot shell access if the Aboot password is lost or forgotten.
Restore console access ifthe baud rate or other settings are incompatible with the terminal.
Replace the internal flash contents with configuration or image files stored on a USB flash drive.

Aboot Shell Operation

When the switch is powered on or rebooted, Aboot reads its configuration from boot-config on the internal flash and attempts to boot a configured EOS software image (with the extension .swi).

You can monitor the automatic boot process or enter the Aboot shell only from the console port. You can connect a PC or terminal directly to the port and run a terminal emulator to interact with the serial port or access it through a serial concentrator device.

The boot-config stores the console settings; the factory-default settings for Arista switches are 9600 baud, no parity, 8 character bits, and 1 stop bit. If you do not know the current settings, perform a full flash recovery to restore the factory default settings.When the console port is connected and the configured terminal settings are proper, the terminal displays a message similar to the following a few seconds after powering up the switch:

Aboot 1.0.0

Press Control-C now to enter the Aboot shell

To abort the automatic boot process and enter the Aboot shell, select Ctrl-C (ASCII 3 in the terminal emulator) after the Press Control-C now to enter Aboot shell message appears. Pressing Ctrl-C can interrupt the boot process up through the starting of the new kernel.

If the boot-config file does not contain a password command, the Aboot shell starts immediately. Otherwise, you must enter the password using the password prompt to start the shell. If you enter the wrong password three times, Aboot displays this message:

Type "fullrecover" and press Enter to revert /mnt/flash to factory default 

state, or just press Enter to reboot:

Selecting Enter continues a normal soft reset without entering the Aboot shell.
Typing fullrecover and pressing Enter performs a full flash recovery to restore the factory-default settings, removing all previous flash drive contents.

The Aboot shell starts by printing:

Welcome to Aboot.

Aboot then displays the Aboot# prompt.

Aboot reads its configuration from boot-config on the internal flash.

Accessing the Aboot Shell

This procedure accesses the Aboot Shell.

Reload the switch and select enter or type y when prompted, as described in the Typical Reset Sequence.
The command line displays this Aboot entry prompt.
```
Press Control-C now to enter Aboot shell
```
Type Ctrl-C.
If the boot-config file does not contain a PASSWORD command, the CLI displays an Aboot welcome banner and prompt.
```
^C Welcome to Aboot.
Aboot#
```
The CLI displays a password prompt if the boot-config file contains a PASSWORD command. In this case, proceed to Step 3. Otherwise, the CLI displays the Aboot prompt.
If prompted, enter the Aboot password.
```
Press Control-C now to enter Aboot shell 
 ^CAboot password: 
Welcome to Aboot. 
Aboot#
```
Aboot allows three attempts to enter the correct password. After the third attempt, the CLI prompts the user to continue the reboot process without entering the Aboot shell or restoring the flash drive to the factory default state.
```
Press Control-C now to enter Aboot shell 
^CAboot password: 
incorrect password 
Aboot password: 
incorrect password 
Aboot password: 
incorrect password 
Type "fullrecover" and press Enter to revert /mnt/flash to factory default 
state, or just press Enter to reboot: fullrecover 
All data on /mnt/flash will be erased; type "yes" and press Enter to proceed, 
or just press Enter to cancel:
```
The fullrecover operation replaces the flash contents with a factory default configuration. The CLI displays text similar to the following when performing a fullrecover, finishing with another entry option in the Aboot shell.
Note: For hardware purchased after June 2017, the factory default partition will not have the backup EOS software image. It increases the flash size on smaller flash size disks, and other options are available in the fullrecover command functionality to restore the factory default EOS image applicable to both fixed system and modular system hardware.
```
Erasing /mnt/flash
Writing recovery data to /mnt/flash
boot-config
startup-config
EOS.swi
210770 blocks
Restarting system.


Aboot 1.9.0-52504.EOS2.0


Press Control-C now to enter Aboot shell
```

Aboot File Structure

When you enter the Aboot CLI, the current working directory is the root directory on the switch. Switch image and configuration files are at /mnt/flash. When exiting the Aboot shell, only /mnt/flash preserves the contents. The /mnt directory contains the file systems of storage devices. Aboot mounts the internal flash device at /mnt/flash.

When you insert a USB flash drive in one of the flash ports, Aboot mounts its file system on /mnt/usb1. The file system is unmounted when you remove the USB flash drive from the port. Most USB drives contain an LED that flashes when the system is accessing it; wait to remove the drive from the flash port until the LED stops flashing.

Booting From the Aboot Shell

Aboot boots the EOS software image (with the extension .swi), which is available in boot-config automatically if you take no action during the boot process. Suppose the boot process fails for any reason, such as an incorrectly configured software image. In that case, Aboot enters the shell, allowing you to manually correct the configuration or boot a software image. The boot command loads and boots an EOS software image file.

The boot command syntax is

boot SWI

where SWI lists the location of the EOS image that the command loads. SWI options include:

device:path loads the image file from the specified storage device. The default device value is flash; other values include file and usb1.
/PATH loads the image file from the specified path in the switch directory.
http://server/path loads the image file from the HTTP server on the host server.
ftp://server/path loads the image file from the FTP server on the host server.
tftp://server/path loads the image file from the TFTP server on the host server.
nfs://server/path mounts the path’s parent directory from the host server and loads the image file from the loaded directory.

It accepts the same commands as the SWI variable in the boot-config file. See boot-config Command Line Content for a list of boot command formats.

Suppose the boot-config does not have a specified image or booting the image results in an error condition (for example, an incorrect path or unavailable HTTP server). In that case, Aboot halts the boot process and drops into the shell.

Example

To boot EOS.swi from internal flash, enter one of these commands on the Aboot command line:

boot flash:EOS.swi

boot /mnt/flash/EOS.swi

Aboot Commands

To list the contents of the internal flash, enter ls /mnt/flash at the Aboot# prompt.

Example

Aboot# ls /mnt/flash
EOS.swi boot-config startup-config

Commonly used commands include:

ls prints a list of the files in the current working directory.
cd changes the current working directory.
cp copies a file.
more prints the contents of a file one page at a time.
vi edits a text file.
boot boots a software image file.
swiinfo prints information about a software image.
recover recovers the factory-default configuration.
reboot reboots the switch.
udhcpc configures a network interface automatically via DHCP.
ifconfig prints or alters network interface settings.
wget downloads a file from an HTTP or FTP server.
showtech prints device hardware information.

Busybox, an open-source implementation of UNIX utilities, provides many Aboot shell commands. Busybox command help is available at http://www.busybox.net/downloads/BusyBox.html. Aboot provides access to only a subset of the documented commands.

Aboot can access networks through the Ethernet management ports. Aboot provides network interfaces mgmt1 and mgmt2 unconfigured by default; you can configure management port settings using Aboot shell commands like ifconfig and udhcpc. After configuring a management interface, use wget to transfer files from an HTTP or FTP server, tftp to transfer files from a TFTP server, or mount to mount an NFS filesystem.

Aboot Configuration Commands

This section describes the Aboot configuration commands that a boot-config file can contain.

CONSOLESPEED
NET commands

CONSOLESPEED

The CONSOLESPEED command in the boot-config file specifies the console baud rate when the switch is booted. The connected terminal must match the specified rate to communicate with the switch. Baud rate options include 1200, 2400, 4800, 9600, 19200, 38400, 57600, and 115200.

The default baud rate is 9600.

Command Syntax

CONSOLESPEED= baud_rate

Parameters

baud_rate specifies the console speed. Values include 1200, 2400, 4800, 9600, 19200, 38400, 57600, and 115200.

Example

This command in a boot-config file sets the baud rate to 2400 when the switch boots.

CONSOLESPEED=2400

NET Commands

Aboot uses NET commands in the boot-config file during switch booting to configure the network interface used for switch configuration. You can enter these commands manually in Aboot.

NETDEV indicates the configured network interface. If boot-config does not contain a NETDEV command, the booting process does not attempt to configure a network interface. Other NET commands specify settings that Aboot uses to configure the interface.

Command Syntax

NETDEV=device_interface

NETAUTO=auto_setting

NETIP=interface_address

NETMASK=interface_mask

NETGW=gateway_address

NETDOMAIN=domain_name

NETDNS=dns_address

Parameters

device_interface the network interface. Options include:
- ma1 management port 1.
- ma2 management port 2.
auto_setting the configuration method. Options include:
- dhcp interface is configured through a DHCP server; other NET commands are not.
- If the NETAUTO command is omitted, the interface configures with other NET commands.
interface_address interface IP address, in dotted-decimal notation.
interface_mask interface subnet mask, in dotted-decimal notation.
gateway_address default gateway IP address, in dotted decimal notation.
domain_name interface domain name.
dns_address IP address of the Domain Name Server, in dotted decimal notation.

Examples

This command specifies management port 1 as the network interface configured for management traffic.
```
NETDEV=ma1
```
This command instructs the switch to configure the network interface through a DHCP server, ignoring other NET commands.
```
NETAUTO=dhcp
```

These NET commands configure the network interface.

NETIP=10.12.15.10
NETMASK=255.255.255.0
NETGW=10.12.15.24
NETDOMAIN=mycompany.com
NETDNS=10.12.15.13

install bios source

install bios source command is used to install an Aboot Update File (AUF) to upgrade Aboot firmware.

install bios source indicates the location of the source file and the actions taken.

Command Syntax

install bios source SOURCE [active | standby] [reload | now]

Parameters

SOURCE the file location.

Examples

This command installs an AUF file update.auf stored in /mnt/flash.
```
switch# install bios source flash:/update.auf
```
Note: Follow the prompts after executing the command during the installation process.
This command performs a reboot directly after installation.
```
switch# install bios source flash:/update.auf reload
```
This command skips the prompts and performs the reboot automatically after installation.
```
switch# install bios source flash:/update.auf now
```
This command performs the installation only on the standby supervisor.
```
switch# install bios source flash:/update.auf standby
```
Note: By default, the active supervisor gets upgraded, followed by the standby where applicable.

PASSWORD (ABOOT)

PASSWORD specifies the Aboot password, as described in Accessing the Aboot Shell. The Aboot shell does not require a password when boot-config does not contain a PASSWORD command.

The boot-config file stores the password as an MD5-encrypted string generated from a clear-text seed by the UNIX password program or the crypt library function. When entering the Aboot password, the user types the clear-text seed.

There is no method of recovering the password from the encrypted string. If the clear-text password is lost, delete the corresponding PASSWORD command line from the boot-config file.

Note:

The EOS boot secret command adds or modifies the PASSWORD configuration line.

Command Syntax

PASSWORD = encrypted_string

Parameters

encrypted_string, the encrypted string that corresponds to the clear-text Aboot password.

Example

This line is a PASSWORD command example in which the encrypted string corresponds to the clear-text password abcde.

PASSWORD=$1$CdWp5wfe$pzNtE3ujBoFEL8vjcq7jo/

SWI

SWI specifies the location and file name of the EOS image file that Aboot loads when booting, using the same format as boot-config to designate a local or network path.

Command Syntax

SWI = SWI_PATH

Parameters

SWI_PATH specifies the location of the EOS image file. Options include:

file_path specifies a file location on the internal flash drive.
file:file_path specifies a file location in the switch directory.
usb1:file_path specifies a file location on the USB drive.
http:file_path specifies an HTTP path to the image file.
ftp:file_path specifies an FTP path to the image file.
tftp:file_path specifies a TFTP path to the image file.
nfs:file_path specifies an NFS path to the image file.

Examples

This SWI command in boot-config causes Aboot to boot the switch from the file EOS.swi on the switch’s internal flash drive.
```
SWI=flash:EOS.swi
```
This SWI command in boot-config causes Aboot to boot the switch from the file EOS.swi at the specified location on foo.com.
```
SWI=http://foo.com/images/EOS.swi
```

Switch Booting Commands

boot console
boot secret
boot system
delete startup-config
protocol
redundancy
redundancy manual switchover
reload
reload (scheduled)
show platform bios
show redundancy file-replication
show redundancy status
show redundancy switchover sso
show reload
show reload cause
show reload fast-boot

boot console

The boot console command configures terminal settings for serial devices connecting to the console port. The only console setting specified from boot-config is speed.

The factory-default console settings are 9600 baud, no parity, 8 character bits, and 1 stop bit. If you do not know the current settings, restore the factory default settings described in Restoring the Factory Default EOS Image and Startup Configuration.

The no boot console and default boot console commands restore the factory default settings on the switch and remove the corresponding CONSOLESPEED command from the boot-config file.

Command Mode

Global Configuration

Command Syntax

boot console speed baud_rate

Parameters

baud_rate console baud rate. Options include 1200, 2400, 4800, 9600, 19200, 38400, 57600, and 115200.

Examples

This command sets the console speed to 57600 baud.

switch(config)# boot console speed 57600
switch(config)#

This command displays the result of the console speed change.

switch(config)# show boot-config
Software image: flash:/EOS.swi
Console speed: 57600
Aboot password (encrypted): (not set)
switch(config)#

The above boot console command adds the following line to boot-config.
```
CONSOLESPEED=57600
```

boot secret

The boot secret command creates or edits the Aboot shell password and stores the encrypted string in the PASSWORD command line of the boot-config file.

The no boot secret and default boot secret commands remove the Aboot password from the boot-config file. When the Aboot password does not exist, no password is required to enter the Aboot shell.

Command Mode

Global Configuration

Command Syntax

boot secret [ENCRYPT_TYPE] password

no boot secret

default boot secret

Parameters

ENCRYPT_TYPE indicates the encryption level of the password parameter. Settings include:
- no parameter and the password is clear text.
- 0 the password is clear text. Equivalent to the no parameter case.
- 5 the password is an MD5-encrypted string.
- sha512, the password is entered as a sha512 encrypted string.
password specifies the boot password.
- password must be in clear text if ENCRYPT_TYPE specifies clear text.
- password must be an appropriately encrypted string if ENCRYPT_TYPE specifies encryption.

Restrictions

The sha512 encryption option is not available on Trident platform switches.

Examples

These equivalent commands set the Aboot password to xr19v.

switch(config)# boot secret xr19v
switch(config)#

switch(config)# boot secret 0 xr19v
switch(config)#

This command displays the result:

switch(config)# show boot-config
Software image: flash:/EOS.swi
Console speed: (not set)
Aboot password (encrypted): $1$k9YHFW8D$cgM8DSN.e/yY0p3k3RUvk.
switch(config)#

The boot secret commands earlier add this line to boot-config:

PASSWORD=$1$k9YHFW8D$cgM8DSN.e/yY0p3k3RUvk.

The user must enter xr19v at the login prompt to access the Aboot shell.

These commands set the Aboot password to xr123 and display the resulting boot-config code. In the past, the encrypted string uses xr123 as the clear-text seed.
```
switch(config)# boot secret 5 $1$QfbYkVWb$PIXG0udEquW0wOSiZBN3D/
switch(config)# show boot-config
Software image: flash:/EOS.swi
Console speed: (not set)
Aboot password (encrypted): $1$QfbYkVWb$PIXG0udEquW0wOSiZBN3D/
switch(config)#
```
The boot secret command above adds this line to boot-config:
```
PASSWORD=$1$QfbYkVWb$PIXG0udEquW0wOSiZBN3D/
```
The user must enter xr123 at the login prompt to access the Aboot shell.
This command removes the Aboot password, allowing access to the Aboot shell without a password.
```
switch(config)# no boot secret
switch(config)#
```

boot system

The boot system command specifies the location of the EOS software image that Aboot loads when the switch boots. The command can refer to files on Flash or a module in the USB flash port.

Command Mode

Global Configuration

Command Syntax

boot system DEVICE file_path

Parameters

DEVICE location of the image file. Options include:
- file: file is located in the switch file directory.
- flash: file is located in flash memory.
- usb1: file is located on a drive inserted in the USB flash port. Available if a drive is in the port.
- file_path path and name of the file.

Examples

This command designates EOS1.swi, on USB flash memory, as the EOS software image load file.
```
switch(config)# boot system usb1:EOS1.swi
switch(config)#
```
The boot system command earlier adds this line to boot-config.
SWI=usb1:/EOS1.swi
This command designates EOS1.swi, on the switch flash, as the EOS software image load file.
```
switch(config)# boot system flash:EOS.swi
switch(config)#
```
The boot system command earlier adds this line to boot-config:
```
s
```

delete startup-config

The delete startup-config command erases or deletes the startup-config file.

Command Mode

Privileged EXEC

Command Syntax

delete startup-config [CONFIRMATION]

Parameters

CONFIRMATION confirmation for immediate erasure. Options include:

no parameter the switch requires a confirmation before starting the erasure.
now the erasure begins immediately without prompting the user to confirm the request.

Examples

This command deletes the startup configuration from the switch. When the delete startup-config command is entered, the switch sends a message prompting the user to confirm the request.
```
switch# delete startup-config
Proceed with erasing startup configuration? [confirm] y
switch#
```
This command deletes the startup configuration from the switch immediately without prompting.
```
switch# delete startup-config now
switch#
```

protocol

The protocol command configures how the supervisors on a modular switch will handle switchover events. By default, the switch is set to route processor redundancy (RPR), which synchronizes startup-config files between the supervisor modules and partially boots the standby supervisor. You can set the mode to simplex (manual switchover only) or to stateful switchover (SSO), which synchronizes both startup-config and running-config files between the supervisor modules, fully boots the standby module to speed the switchover process, and minimizes packet loss. SSO synchronizes the L2 state between the supervisors, but the L3 state is not synchronized. This can result in traffic loss for traffic forwarded on routes learned by a dynamic routing protocol. Enabling nonstop forwarding can eliminate most packet loss for BGP and OSPF.

The no protocol and default protocol commands set the redundancy protocol to the default value (rpr) by removing the protocol command from running-config.

Command Mode

Redundancy Configuration

Command Syntax

protocol {rpr | simplex | sso}

no protocol

default protocol

Parameters

rpr route processor redundancy protocol (RPR, the default).
simplex no redundancy. Switchover must be initiated manually.
sso stateful switchover (SSO).

Related Commands

redundancy places switch in redundancy configuration mode.

Example

These commands enter redundancy configuration mode and set the redundancy protocol to SSO.

switch(config)# redundancy
switch(config-redundancy)# protocol sso
switch(config-redundancy)#

redundancy

The redundancy command places the switch in redundancy configuration mode.

Command Mode

Global Configuration

Command Syntax

redundancy

Commands Available in Redundancy Configuration Mode

protocol

Related Commands

redundancy manual switchover manually initiates a switchover.

Example

These commands enter redundancy configuration mode and set the redundancy protocol to stateful switchover.

switch(config)# redundancy
switch(config-redundancy)# protocol sso
switch(config-redundancy)#

redundancy manual switchover

The redundancy manual switchover command immediately switches control of the switch to the standby supervisor. If the redundancy mode is set to simplex or the standby supervisor is unavailable for any other reason, this command will not function.

Command Mode

Privileged EXEC

Command Syntax

redundancy manual switchover

Related Command

redundancy places the switch in redundancy configuration mode.

Example

This command forces a switchover to the standby supervisor. The switchover is executed immediately without further confirmation from the user.

switch# redundancy manual switchover
This supervisor will be restarted.
switch#

reload

The reload command power cycles the switch and resets it under Aboot control. The hard reset clears the switch, including memory states and other hardware logic.

Note: The reload fast-boot and reload hitless commands initiate Smart System Upgrade (SSU); for a description of this feature and the appropriate command syntax, refer to the Smart System Upgrade (Leaf SSU) section.

The command behaves differently in fixed and modular systems.

Fixed 1-RU systems: the power supply remains powered up through the reset. All other switch components lose power for two to five seconds.
Modular systems: the power supply on the active supervisor remains powered up through the reset. xAll other supervisor components lose power for at least one second. After the supervisor becomes functional, it manages the power-cycling of all line cards.

Command Mode

Privileged EXEC

Command Syntax

reload [TARGET] [CONFIRMATION]

Parameters

TARGET specifies which supervisor(s) to reset. Some options are available only on dual-supervisor switches. Options include:
- no parameter the active supervisor is reset.
- all supervisors are reset.
- peer the peer supervisor is reset.
- power the active supervisor is reset.
CONFIRMATION confirmation for immediate reset. Options include:
- no parameter the switch requires a confirmation before starting the reset.
- now the reset begins immediately without prompting the user to confirm the request.

Related Commands

reload (scheduled) schedules a pending reload operation.
show reload cause displays cause of most recent reload.

Examples

Begin the reboot process by typing the reload command:
```
switch# reload
switch#
```
When the reload 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. In this example, the user does not save modifications to the system before reloading.
```
System configuration has been modified. Save? [yes/no/cancel/diff]:n
Proceed with reload? [confirm]y
```
The switch responds by broadcasting messages, including a notification about the system rebooted to all open CLI instances. The reload pauses to provide an option for the user to enter Aboot shell; the Aboot shell supports commands that restore the state of the internal flash to factory defaults or create a customized default state.
```
Broadcast message from root@mainStopping sshd: [  OK  ]
SysRq : Remount R/O
Restarting system

Aboot 1.9.0-52504.EOS2.0

Press Control-C now to enter Aboot shell
```

No action is required to continue the reset process. The switch displays messages to indicate the completion of individual tasks. The reboot is complete when the CLI displays a login prompt.

Booting flash:/EOS.swi
Unpacking new kernel
Starting new kernel
Switching to rooWelcome to Arista Networks EOS 4.4.0
Mounting filesystems:  [  OK  ]
Entering non-interactive startup
Starting EOS initialization stage 1: [  OK  ]
ip6tables: Applying firewall rules: [  OK  ]
iptables: Applying firewall rules: [  OK  ]
iptables: Loading additional modules: nf_conntrack_tftp [  OK  ]
Starting system logger: [  OK  ]
Starting system message bus: [  OK  ]
Starting NorCal initialization: [  OK  ]
Starting EOS initialization stage 2: [  OK  ]
Starting ProcMgr: [  OK  ]
Completing EOS initialization: [  OK  ]
Starting Power On Self Test (POST): [  OK  ]
Generating SSH2 RSA host key: [  OK  ]
Starting isshd: [  OK  ]
Starting sshd: [  OK  ]
Starting xinetd: [  OK  ]
[  OK  ] crond: [  OK  ]

switch login:

reload (scheduled)

The reload (scheduled) command configures the switch to reset at a specified time or after a specified interval. Refer to reload for the functional details of the reset operation.

The switch prompts to save the configuration and confirm the reload request. Once the request is confirmed, the switch resumes normal operation until the reload initiates.

The reload cancel, no reload, and default reload commands cancel the pending reload operation.

Command Mode

Privileged EXEC

Command Syntax

reload [all | power | peer] {at hh:mm [month | day] | in hh:mm} [force | reason]

reload cancel

no reload

default reload

Parameters

All reloads all supervisors.
Power resets the active supervisor.
Peer resets the peer supervisor.
At performs reload at specified times.
- hh:mm specifies reload time in hours (0 to 23) and minutes (0 to 59). If no month and day are specified, reload occurs at the specified time on the day the command is issued.
  - Month optionally specifies the month of the year (Jan, Feb, etc.)
    - Day day of the month. Values range from 1 to 31.
In performs the reload after a specified delay.
- hh:mm specifies delay before reload in hours (0 to 23) and minutes (0 to 59).
Force performs action immediately without prompting.
Reason enter text to display explaining the purpose of the reload.
Cancel cancels any existing reload request.

Related Commands

reload initiates an immediate reload operation.
show reload displays time and reason of any pending reload operation.

Examples

This command schedules a switch reset to begin in 12 hours.

switch# reload in 12:00
System configuration has been modified. Save? [yes/no/cancel/diff]:y
Proceed with reload? [confirm]
Reload scheduled for Tue Mar 27 05:57:25 2012 (in 11 hours 59 minutes)
switch#

This command cancels a scheduled reset.

switch# no reload
Scheduled reload has been cancelled
switch#

This command schedules a reload of the active supervisor to begin in 12 hours.

switch# reload power in 12:00
Reload scheduled for Thu Feb 13 18:56:01 2020 (in 11 hours 59 minutes)
switch#

show platform bios

The show platform bios [history | detail] command displays the BIOS versions on the switch.

Command Mode

EXEC

Command Syntax

show platform bios

Examples

This command displays the Running, Programmed, and Fallback versions of Aboot.

switch# show platform bios
FixedSystem BIOS versions
  Location   Version                       	 
  ---------- ----------------------------------
  Running	  Aboot-norcal9-9.0.5-13882759  	 
  Programmed Aboot-norcal9-9.0.3-4core-13882759
  Fallback   Aboot-norcal9-9.0.3-4core-13882759
switch#

This command displays the BIOS installation history.

switch# show platform bios history
Supervisor-1 BIOS version history

Timestamp           Version
------------------- ----------------------------------
2020-04-07 04:20:22 Aboot-norcal9-9.0.5-13882759
2020-04-05 08:32:03 Aboot-norcal9-9.0.3-4core-13882759  	 

Supervisor-2 BIOS version history

Last update failed on 2020-04-15: Compatibility check failed.

Timestamp           Version 
------------------- ----------------------------------
2020-04-05 08:32:09 Aboot-norcal9-9.0.5-13882759
switch#

This command displays the BIOS installation history details.

switch# show platform bios history detail
Supervisor-1 BIOS version history

Timestamp           Version                            Checksum
------------------- ---------------------------------- ---------
2020-04-07 04:20:22 Aboot-norcal9-9.0.5-13882759       3fa8...
2020-04-05 08:32:03 Aboot-norcal9-9.0.3-4core-13882759 bb39...

Supervisor-2 BIOS version history

Last update failed on 2020-04-15: Compatibility check failed.

Timestamp           Version                            Checksum
------------------- ---------------------------------- ---------
2020-04-05 08:32:09 Aboot-norcal9-9.0.3-13882759       3fa8...
switch#

show redundancy file-replication

The show redundancy file-replication command displays the status and last synchronization date of file replication between the supervisors on the switch.

Command Mode

EXEC

Command Syntax

show redundancy file-replication

Related Commands

show redundancy status status and redundancy protocol of supervisors.
show redundancy switchover sso displays stateful switchover information since last reload.

Example

This command displays the supervisors' current file replication status.

switch# show redundancy file-replication
0 files unsynchronized, 2 files synchronized, 0 files failed, 2 files total.

File                   Status         Last Synchronized
---------------------- -------------- -----------------------
file:persist/sys       Synchronized   25 days, 19:48:26 ago
flash:startup-config   Synchronized   25 days, 19:48:26 ago
switch#

show redundancy status

The show redundancy status command displays the current status (active or standby) and the configured redundancy protocol of both supervisors, and summary information about the latest switchover event.

Command Mode

EXEC

Command Syntax

show redundancy status

Related Commands

show redundancy file-replication displays status of file replication between supervisors.
show redundancy switchover sso displays stateful switchover information since last reload.

Example

This command displays redundancy information for both supervisors and a summary of the latest switchover.

switch# show redundancy status
  my state = ACTIVE
peer state = STANDBY HOT
      Unit = Primary
   Unit ID = 1

Redundancy Protocol (Operational) = Stateful Switchover
Redundancy Protocol (Configured) = Stateful Switchover
Communications = Up
switchover completion timeout = 720.0 seconds (default)
Ready for switchover

  Last switchover time = 0:32:15 ago
Last switchover reason = Supervisor has control of the active supervisor lock
switch#

show redundancy switchover sso

The show redundancy switchover sso command displays the number of stateful switchovers since the last reload and a log of the events in the latest stateful switchover.

Command Mode

EXEC

Command Syntax

show redundancy switchover sso

Related Commands

show redundancy file-replication displays status of file replication between supervisors.
show redundancy status displays status and redundancy protocol of supervisors.

Example

This command displays stateful switchover information.

switch# show redundancy switchover sso
Total number of Stateful Switchover completed since reload: 4

Latest Stateful Switchover occured 29 days, 12:48:22 ago @ 2012-06-09 19:47:50 
(completed)
  0.000000: switchover started
  0.000235: stage PCIEAcquired started
  0.000349:   event PCIEAcquired:__dummyInternal1__ completed
  0.000394:   event PCIEAcquired:PlxPcie-system started
  0.027738:   event PCIEAcquired:PlxPcie-system completed
  0.027829: stage PCIEAcquired is complete
  0.027935: stage DmaReady started
  0.028042:   event DmaReady:ForwardingAgent started
  0.079620:   event DmaReady:ForwardingAgent completed
  0.079699: stage DmaReady is complete
  0.079781: stage TimeCriticalServices started
  0.079887:   event TimeCriticalServices:__dummyInternal1__ completed
  0.079928:   event TimeCriticalServices:Stp started
  0.208035:   event TimeCriticalServices:Stp completed
  0.208120: stage TimeCriticalServices is complete
                <-------OUTPUT OMITTED FROM EXAMPLE------->
 39.675076: stage NonCriticalServices started
 39.675145:   event NonCriticalServices:__dummyInternal1__ completed
 39.675183: stage NonCriticalServices is complete
 39.675399: switchover is complete
switch#

show reload

The show reload command displays the time and reason for any pending reload operation. The reload (scheduled) command schedules a reload operation and can be used to cancel a pending reload.

Command Mode

EXEC

Command Syntax

show reload

Related Commands

reload (scheduled) schedules a pending reload operation.
show reload cause displays cause of most recent reload.

Example

These commands schedule a reload for 2:45 pm, display the time of the pending reload, and then cancel the scheduled reload.

switch# reload at 14:45
Proceed with reload? [confirm]
Reload scheduled for Tue Mar 27 14:45:00 2012 ( in 4 hours 11 minutes )
switch# show reload
Reload scheduled for Tue Mar 27 14:45:00 2012 ( in 4 hours 11 minutes )
switch# reload cancel
Scheduled reload has been cancelled
switch#

show reload cause

The show reload cause command displays the reason for the most recent reload operation. The command displays recommended actions and debug information related to the executed reload.

Command Mode

EXEC

Command Syntax

show reload cause

Related Commands

reload initiates an immediate reload operation.
show reload displays time and reason of all pending reload operations.

Example

This command displays the cause of the most recent reload operation.

switch# show reload cause
Reload Cause 1:
-------------------
Reload requested by the user.

Recommended Action:
-------------------
No action necessary.

Debugging Information:
----------------------
None available.
switch#

show reload fast-boot

The show reload fast-boot command verifies that the switch configuration is valid for Smart System Upgrade (SSU).

Command Mode

EXEC

Command Syntax

show reload fast-boot

Related Commands

reload initiates an immediate reload operation.
show reload displays time and reason of all pending reload operations.

Example

This command displays why SSU cannot be initiated and which features must be reconfigured to allow SSU to proceed.

switch# show reload fast-boot
'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#

Initial Configuration and Recovery

This chapter describes initial configuration and recovery tasks. Subsequent chapters provide details about features introduced in this chapter.

This chapter contains these sections:

Initial Switch Access

Arista network switches provide two initial configuration methods:

Zero Touch Provisioning (ZTP) configures the switch without user interaction ( Zero Touch Provisioning.)
Manual provisioning configures the switch through commands entered by a user through the CLI ( Manual Provisioning.)

Zero Touch Provisioning

Zero Touch Provisioning (ZTP) configures a switch without user intervention by downloading a startup configuration file (startup-config) or a boot script from a location specified by a DHCP server. Configuring the Network for ZTP describes network tasks required to set up ZTP.

The switch enters ZTP mode when it boots if flash memory does not contain a startup-config or zerotouch-config file. It remains in ZTP mode until a user cancels ZTP mode or until the switch retrieves a startup-config or a boot script. After downloading a file through ZTP, the switch reboots again, using the retrieved file.

Security Considerations

The ZTP process cannot distinguish an approved DHCP server from a rogue DHCP server. For secure provisioning, you must ensure that only approved DHCP servers can communicate with the switch until after the complete ZTP process. Arista also recommends validating the EOS image on your ZTP server by confirming that its MD5 checksum matches the MD5 checksum found on the EOS download page of the Arista website.

On a UNIX server, the md5sum command calculates this checksum:

% md5sum EOS.swi
3bac45b96bc820eb1d10c9ee33108a25  EOS.swi

This command is available on Arista switches from the CLI or within the Bash shell.

switch# bash md5sum /mnt/flash/EOS-4.18.0F.swi 
73435f0db3af785011f88743f4c01abd  /mnt/flash/EOS-4.18.0F.swi

switch#[admin@switch ~]$ md5sum /mnt/flash/EOS-4.18.0F.swi
73435f0db3af785011f88743f4c01abd /mnt/flash/EOS-4.18.0F.swi
[admin@switch ~]$

To provision the switch through Zero Touch Provisioning:

Mount the switch in its permanent location.
Connect at least one management or Ethernet port to a network that can access the DHCP server and the configuration file.
Provide power to the switch.

Note: ZTP will not initiate if flash memory contains either a startup-config or zerotouch-config file.

You can monitor ZTP provisioning progress on the console port. Console Port provides information for setting up the console port. Canceling Zero Touch Provisioning provides information for monitoring ZTP progress and canceling ZTP mode.

Manual Provisioning

Initial manual switch provisioning requires the cancellation of ZTP mode, the assignment of an IP address to a network port, and the establishment of an IP route to a gateway. The serial console and Ethernet management ports perform the initial provisioning.

The console port is used for serial access to the switch. These conditions may require serial access:
- Management ports are not assigned IP addresses.
- The network is inoperable.
- The password for the user's login is not available.
- The password to access the enable mode is not available.
It uses the Ethernet management ports for out-of-band network management tasks. That port must have IP address before using a management port for the first time.

Console Port

The console port is a serial port located on the front of the switch. Figure 1 shows the console port on the DCS-7050T-64 switch. Use a serial or RS-232 cable to connect to the console port. The accessory kit also includes an RJ-45 to DB-9 adapter cable connecting to the switch.

Port Settings

Use these settings when connecting the console port:

9600 baud
no flow control
1 stop bit
no parity bits
8 data bits

Admin Username

The initial configuration provides one username, admin, that is not assigned a password. You can only log into the switch through the console port using the admin username without a password. After assigning a password to the admin username, it can log into the switch through any port.

The username command modifies a specified username and can be used to create or delete usernames, including admin.

Example

This command assigns the password pxq123 to the admin username:

switch(config)# username admin secret pxq123
switch(config)#

When the switch reboots, it will lose the passwords unless startup configuration saves the new or altered passwords.

Note: It accesses the Aboot shell through the console port to log in to the switch when all usernames get deleted from the configuration.

Canceling Zero Touch Provisioning

Zero Touch Provisioning (ZTP) installs a startup-config file from a network location if flash memory does not contain a startup-config or zerotouch-config file when the switch reboots. Canceling ZTP is required if the switch cannot download a startup-config or boot script file.

When the switch boots without a startup-config or zerotouch-config file, it displays the following message through the console port:

No startup-config was found.

The device is in Zero Touch Provisioning mode and is attempting to
download the startup-config from a remote system. The device will not
be fully functional until a valid startup-config is downloaded
from a remote system or Zero Touch Provisioning is cancelled. To cancel
Zero Touch Provisioning, login as admin and type 'zerotouch cancel'
at the CLI.

localhost login:

To cancel ZTP mode, log into the switch with the admin password, then enter the zerotouch cancel command. The switch immediately boots without installing a startup-config file.

localhost login: admin
admin
localhost>Apr 15 21:28:21 localhost ZeroTouch: %ZTP-5-DHCP_QUERY: Sending DHCP 
request on  [ Ethernet10, Ethernet13, Ethernet14, Ethernet17, Ethernet18, 
Ethernet21, E-thernet22, Ethernet23, Ethernet24, Ethernet7, Ethernet8, 
Ethernet9, Management1, Management2 ]
Apr 15 21:28:51 localhost ZeroTouch: %ZTP-5-DHCP_QUERY_FAIL: Failed to get a 
valid DHCP response
Apr 15 21:28:51 localhost ZeroTouch: %ZTP-5-RETRY: Retrying Zero Touch 
Provisioning from the beginning (attempt 1)
Apr 15 21:29:22 localhost ZeroTouch: %ZTP-5-DHCP_QUERY: Sending DHCP request on  
[ Ethernet10, Ethernet13, Ethernet14, Ethernet17, Ethernet18, Ethernet21, 
Ethernet22, Ethernet23, Ethernet24, Ethernet7, Ethernet8, Ethernet9, 
Management1, Management2 ]

localhost>zerotouch cancel
zerotouch cancel
localhost>Apr 15 21:29:39 localhost ZeroTouch: %ZTP-5-CANCEL: Canceling Zero 
Touch Provisioning
Apr 15 21:29:39 localhost ZeroTouch: %ZTP-5-RELOAD: Rebooting the system
Broadcast messagStopping sshd: [  OK  ]
watchdog is not running
SysRq : Remount R/O
Restarting system

Aboot 1.9.0-52504.EOS2.0
Press Control-C now to enter the Aboot shell

To avoid entering ZTP mode on subsequent reboots, create a startup-config file described in Step 8 of the Ethernet Management Port.

Ethernet Management Port

Arista switches provide one or more Ethernet management ports for configuring the switch and managing the network out of the band. Figure 1 shows the location of the Ethernet management ports on a DCS-7050T-64 switch. Only one port is required to manage the switch.

You can access the Ethernet management port(s) remotely over a common network or locally through a connected PC. Before you can access the switch through a remote connection, an IP address and a static route to the default gateway are required. You can configure a virtual IP address on a modular switch with dual supervisors to access the management port on whichever supervisor is active.

Assigning a Virtual IP Address to Access the Active Ethernet Management Port

This procedure assigns a virtual IP address on modular switches with dual supervisors, which connects to the Ethernet management port of the active supervisor. (See the following section to assign a physical IP address to an Ethernet management port.)

Connect a PC or terminal server to the console port. Use the settings listed in Console Port under Port Settings.
Type admin at the login prompt to log into the switch. Initial login through the console port does not require a password.
```
Arista EOS
switch login: admin 
Last login: Fri Apr 9 14:22:18 on Console
switch>
```
Type enable at the command prompt to enter Privileged EXEC mode.
```
switch> enable 
switch#
```
Type configure terminal (or config) to enter global configuration mode.
```
switch# configure terminal 
switch(config)#
```
Type interface management 0 to enter interface configuration mode for the virtual interface which accesses management port 1 on the currently active supervisor.
```
switch(config)# interface management 0
switch(config-if-Ma0)#
```
Type ip address, followed by the desired address, to assign a virtual IP address to access to the active management port. This command assigns IP address 10.0.2.5 to management port 0.
```
switch(config-if-Ma0)# ip address 10.0.2.5/24
```
Type exit at both the interface and global configuration prompts to return to Privileged EXEC mode.
```
switch(config-if-Ma0)# exit 
switch(config)# exit 
switch#
```
Type write (or copy running-config startup-config) to save the new configuration to the startup-config file.
```
switch# write 
switch#
```

Assigning an IP Address to a Specific Ethernet Management Port

This procedure assigns an IP address to a specific Ethernet management port:

Connect a PC or terminal server to the console port. Use the settings listed in Console Port under Port Settings.
Type admin at the login prompt to log into the switch. The initial login does not require a password.
```
Arista EOS
switch login: admin 
Last login: Fri Apr 9 14:22:18 on Console
switch>
```
Type enable at the command prompt to enter Privileged EXEC mode.
```
switch> enable
switch# 
```
Type configure terminal (or config) to enter global configuration mode.
```
switch# configure terminal
```
Type interface management 1 to enter interface configuration mode. (Use the available management port for management port 1.)
```
switch(config)# interface management 1
switch(config-if-Ma1)# 
```
Type ip address, followed by the desired address, to assign an IP address to the port. This command assigns the IP address 10.0.2.8 to management port 1.
```
switch(config-if-Ma1)# ip address 10.0.2.8/24
```
Type exit at both the interface and global configuration prompts to return to Privileged EXEC mode.
```
switch(config-if-Ma1)# exit
 switch(config)# exit 
switch#
```
Type write (or copy running-config startup-config) to save the new configuration to the startup-config file.
```
switch# write
switch# 
```

Configuring a Default Route to the Gateway

This procedure configures a default route to a gateway located at 10.0.2.1.

Enter global configuration mode.

switch> enable
switch# configure terminal

Create a static route to the gateway with the IP route command.
```
switch(config)# ip route 0.0.0.0/0 10.0.2.1
```
Save the new configuration.
```
switch# write 
switch#
```

Overview

Arista Networks features switches with high-density, non-blocking Ethernet ports controlled through an extensible, Linux-based, modular network operating system. The intended audience for this manual is network administrators who configure Arista switches. A working knowledge of network administration is assumed.

New Features

This guide may not describe the features added in the most recent EOS version. For information on undocumented features, consult the TOI documents here: https://www.arista.com/en/support/toi.

Switch Platforms

A list of Arista switches and detailed information about each is available here: https://www.arista.com/en/products.

Recently released switches may not appear in the list but can be found in the most recent Release Notes (found under Active Releases here: https://www.arista.com/en/support/software-download).

Open-Source Licenses

Portions of Arista Networks software are covered by open-source licenses, including the GNU General Public License (GNU GPL).

See https://www.arista.com/en/support/product-documentation/gpl.

CloudVision

The configuration tasks required to deploy CloudVision, CVX, and CVP are in the CloudVision Configuration Guide. The latest version is available here: https://www.arista.com/en/cg-cv/.

Supported Features

For the complete supported features list in the latest EOS release, see https://www.arista.com/en/support/product-documentation/supported-features.

For details on a specific release, see the Release Notes (found under Active Releases here: https://www.arista.com/en/support/software-download).

This section contains the following topic:

Command-Line Interface (CLI)

User Manual

Arista Networks

www.arista.com

Arista EOS version 4.33.1F

DOC-03495-37

Headquarters

5453 Great America Parkway
Santa Clara, CA 95054, USA
+1-408 547-5500

www.arista.com

Support

+1-408 547-5502
+1-866 476-0000

This email address is being protected from spambots. You need JavaScript enabled to view it.

Sales

+1-408 547-5501
+1-866 497-0000

This email address is being protected from spambots. You need JavaScript enabled to view it.

© Copyright 2024 Arista Networks, Inc. The information contained herein is subject to change without notice. Arista Networks and the Arista logo are trademarks of Arista Networks, Inc., in the United States and other countries. Other product or service names may be trademarks or service marks of others.

Page 15 of 15

End of Support

Configuration Files

boot-config

boot-config File Structure

boot-config Command Line Content

Programming boot-config from the CLI

boot system

boot secret

boot console

install bios source

running-config

startup-config

Supervisor Redundancy

Redundancy Supervisor Protocols

Route Processor Redundancy (RPR)

Stateful Switchover (SSO)

Simplex

Configuring Supervisor Redundancy

Examples

System Reset

Typical Reset Sequence

Switch Recovery

Display Reload Cause

Example

Configuring Zero Touch Provisioning

Configuring the Network for ZTP

Monitoring ZTP Progress

ZTP Failure Notification

Canceling ZTP Mode

Configuring the Networks

Aboot Shell

Aboot Shell Operation

Accessing the Aboot Shell

Aboot File Structure

Booting From the Aboot Shell

Example

Aboot Commands

Example

Aboot Configuration Commands

Installation Commands (Aboot)

CONSOLESPEED

NET Commands

install bios source

PASSWORD (ABOOT)

SWI

Switch Booting Commands

boot console

boot secret

boot system

delete startup-config

protocol

redundancy

redundancy manual switchover

reload

reload (scheduled)

show platform bios

show redundancy file-replication

show redundancy status

show redundancy switchover sso

show reload

show reload cause

show reload fast-boot

Initial Configuration and Recovery

Initial Switch Access

Zero Touch Provisioning

Manual Provisioning

Console Port

Port Settings

Admin Username

Example

Canceling Zero Touch Provisioning

Ethernet Management Port

Assigning a Virtual IP Address to Access the Active Ethernet Management Port

Assigning an IP Address to a Specific Ethernet Management Port

Configuring a Default Route to the Gateway

Overview

New Features

Switch Platforms

Open-Source Licenses

CloudVision