Switch Booting Commands

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
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

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

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

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

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#