End of Support

Managing EOS Extensions

The most simple and efficient way to make the most of the extensibility in EOS through the use of extensions. An extension provides a pre-packaged optional feature or a set of scripts in an RPM Package Manager (RPM) or Software image extension (SWIX) format. Arista provides a variety of extensions on the EOS Software Downloads page.

These sections describe basic EOS extension tasks:

Installing EOS Extensions
Installing EOS Extensions on a Dual-Supervisor Switch
Verifying EOS Extensions Installation
Uninstalling an EOS Extension

Installing EOS Extensions

Complete the following steps to install an EOS extension.

Download the desired extension and copy it onto the devices flash storage.

switch# dir 
Directory of flash:/  
-rwx 479183792 Jun 23 09:46 EOS-4.13.3F.swi  
-rwx 21280296 Feb 6 16:48 arista-splunk-extension.swix  
-rwx 27 Jun 23 10:08 boot-config  drwx 4096 Sep 26 2012 schedule  
-rwx 1481 Jun 27 05:54 startup-config

Copy the file from the flash storage to the extensions partition.

switch# copy flash:arista-splunk-extension.swix extension: 
Copy completed successfully.

Install the EOS extension.

switch# extension arista-splunk-extension.swix 
If this extension modifies the behavior of the Cli, any running Cli sessions will 
need to be reset in order for the Cli modifications to take effect.

If you require extension persistence across rebooting the switch, the extension should also be copied into the boot-extensions partition.
```
switch# copy installed-extensions boot-extensions
```
Run the extension. As the CloudVision extension adds additional CLI commands to EOS, the CLI session must be restarted so that the additional commands become available. To achieve this, close the SSH or the Telnet session and open a new session.

Installing EOS Extensions on a Dual-Supervisor Switch

Complete the following steps to install an EOS extension on a dual-supervisor switch.

Copy the extension from the primary supervisor to the standby supervisors flash directory.
```
switch(s1)# copy flash:<filename>.swix supervisor-peer://mnt/flash/
```

Establish a session to the standby supervisor from the primary.

switch(s1)# session peer-supervisor 
Warning: Permanently added '[127.1.0.2]:3601' (RSA) to the list of known hosts. 
Last login: Mon Aug 27 17:32:00 2018 from supervisor1

WARNING - you are currently logged in to the standby supervisor. 
Not all cli commands are available or supported. Any configuration 
done from this cli will not be reflected in the active supervisor's 
running config and will be lost when the active supervisor writes 
its startup config. 
switch(s2)#

Repeat the steps listed in the Installing EOS Extensions to install the EOS extension.
Repeat the steps listed in the Verifying EOS Extensions Installation to verify the extension installation.

Exit standby supervisor.

switch(s2)# exit 
Connection to 127.1.0.1 closed. 
switch(s1)#

Verifying EOS Extensions Installation

Complete the steps to verify that the EOS extensions installed correctly.

Run the show extensions command to verify that the EOS extensions are available and installed correctly.

switch# show extensions 
Name Version/Release Status Extension 
------------------------------------------ -------------------------  
EosSdk-1.2.1-fl.boca-1943435.i686.rpm 1.2.1/1943435.flbocaeossd A, NI 1 
arista-splunk-extension.swix 0.95/1498976.2013ltdsplun A, I 2 
fping-2.4b2-10.fc12.i686.rpm 2.4b2/10.fc12 A, I 1 
gnuplot.swix 1.10.0/1.fc14 A, I 16 
splunkforwarder-5.0.9-213964.i386.rpm 5.0.9/213964 A, NI 1

A: available | NA: not available | I: installed | NI: not installed | F: forced

Run the show boot-extensions command to verify that the EOS extensions are enabled for boot persistence.

switch# show boot-extensions 
arista-splunk-extension.swix 
fping-2.4b2-10.fc12.i686.rpm 
gnuplot.swix

Uninstalling an EOS Extension

Complete the following steps to uninstall an EOS extension.

Uninstall the existing EOS extension using the no extension command.

switch# no extension fping-2.4b2-10.fc12.i686.rpm 
switch#show extensions 
Name                                       Version/Release              Status extension 
------------------------------------------ -------------------------    ---------- 
EosSdk-1.2.1-fl.boca-1943435.i686.rpm      1.2.1/1943435.flbocaeossd A,  NI 1 
arista-splunk-extension.swix               0.95/1498976.2013ltdsplun A,  I 2 
fping-2.4b2-10.fc12.i686.rpm               2.4b2/10.fc12 A,              NI 1 
gnuplot.swix                               1.10.0/1.fc14 A,              I 16 
splunkforwarder-5.0.9-213964.i386.rpm      5.0.9/213964 A,               NI 1

A: available | NA: not available | I: installed | NI: not installed | F: forced

Remove the extension from the boot-extension using the copy installed-extensions boot-extensions command.
```
switch# copy installed-extensions boot-extensions
```
Note: If you have a Dual-Supervisor Switch, connect to the secondary supervisor using the session peer-supervisor command, repeat steps 1 and 2, and finally exit from the secondary supervisor.

Switch Administration Commands

Banner Configuration Commands

banner login
banner motd
show banner

Prompt Configuration Command

prompt

Event Manager Commands

event-monitor
event-monitor backup max-size
event-monitor backup path
event-monitor buffer max-size
event-monitor clear
event-monitor sync
no event-monitor
show event-monitor arp
show event-monitor igmpsnooping
show event-monitor mac
show event-monitor mroute
show event-monitor neighbor
show event-monitor route6
show event-monitor route
show event-monitor sqlite
show event-monitor stpunstable

Email Configuration Command

System Clock Commands

clock set
clock timezone
show clock

NTP Commands

ntp authenticate
ntp authentication-key
ntp local-interface
ntp serve
ntp serve all
ntp server
ntp trusted-key
show ntp associations
show ntp status

Syslog Configuration Commands

logging format
logging persistent
logging repeat-messages

Power Configuration Commands

power enable module

banner login

The banner login command configures a message that the switch displays before login and password prompts. The login banner is available on console, telnet, and ssh connections.

The no banner login and default banner login commands delete the login banner.

Command Mode

Global Configuration

Command Syntax

banner login

no banner login

default banner login

Parameters

banner_text To configure the banner, enter a message when prompted. The message may span multiple lines. Banner text supports the following keywords:
- $(hostname) displays the switch's host name.
EOF To end the banner editing session, type EOF on its own line and press enter.

Examples

These commands create a two-line login banner.

switch(config)# banner login
Enter TEXT message. Type 'EOF' on its own line to end.
This is a login banner for $(hostname).
Enter your login name at the prompt.
EOF
switch(config)#

This output displays the login banner.

This is a login banner for switch.
Enter your login name at the prompt.
switch login:john
Password:
Last login: Mon Jan 14 09:05:23 2013 from adobe-wrks.aristanetworks.com
switch>

banner motd

The banner motd command configures a message of the day (motd) that the switch displays after a user logs in. The motd banner is available on console, telnet, and ssh connections.

The no banner motd and default banner motd commands delete the motd banner.

Command Mode

Global Configuration

Command Syntax

banner motd

no banner motd

default banner motd

Parameters

banner_text To configure the banner, enter a message when prompted. The message may span multiple lines. Banner text supports this keyword:
- $(hostname) displays the switch's host name.
EOF To end the banner editing session, type EOF on its own line and press enter.

Examples

These commands create an motd banner.

switch(config)# banner motd
Enter TEXT message. Type 'EOF' on its own line to end.
This is an motd banner for $(hostname)
EOF
switch(config)#

This output displays the motd banner.

switch login: john
Password:
Last login: Mon Jan 14 09:17:09 2013 from adobe-wrks.aristanetworks.com
This is an motd banner for Switch
switch>

clear ptp interface counters

The clear ptp interface counters command resets the Precision Time Protocol (PTP) packet counters.

Command Mode

Privileged EXEC

Command Syntax

clear ptp interface [INTERFACE_NAME] counters

Parameters

INTERFACE_NAMEInterface type and numbers. Options include:

no parameter Displays information for all interfaces.
- ethernet e_range Ethernet interface range specified by e_range.
- loopback l_range Loopback interface specified by l_range.
- management m_range Management interface range specified by m_range.
- port-channel p_range Port-Channel Interface range specified by p_range.
- vlan v_range VLAN interface range specified by v_range.
- VXLAN vx_range VXLAN interface range specified by vx_range.
Valid parameter formats include number, number range, or comma-delimited list of numbers and ranges.

Example

This command clears all PTP counters.

switch# clear ptp counters
switch#

clock set

The clock set command sets the system clock time and date. If the switch is configured with an NTP server, NTP time synchronizations override manually entered time settings.

Time entered by this command is local, as configured by the clock timezone command.

Command Mode

Privileged EXEC

Command Syntax

clock set hh:mm:ss date

Parameters

hh:mm:ss is the current time (24-hour notation).
date is the current date. Date formats include:
- mm/dd/yy example: 05/15/2012
- example: May 15 2012
- example: 15 May 2012

Example

This command manually sets the switch time.

switch# clock set 08:15:24 14 Jan 2013
Mon Jan 14 08:15:25 2013
timezone is US/Central

clock timezone

The clock timezone command specifies the UTC offset that converts system time to local time. The switch uses local time for time displays and to time-stamp system logs and messages.

The no clock timezone and default clock timezone commands delete the timezone statement from running-config, setting local time to UTC.

Command Mode

Global Configuration

Command Syntax

clock timezone zone_name

no clock timezone

default clock timezone

Parameters

zone_name the time zone. Settings include a list of predefined time zone labels.

Examples

This command configures the switch for the United States Central Time Zone.

switch(config)# clock timezone US/Central
switch(config)# show clock
Fri Jan 11 18:42:49 2013
timezone is US/Central
switch(config)#

To view the predefined time zone labels, enter clock timezone with a question mark.

switch(config)# clock timezone ?
  Africa/Abidjan                    Africa/Accra
  Africa/Addis_Ababa                Africa/Algiers
  Africa/Asmara                     Africa/Asmera
  Africa/Bamako                     Africa/Bangui

  W-SU                              W-SU timezone
  WET                               WET timezone
  Zulu                              Zulu timezone

switch(config)#clock timezone

This command displays all time zone labels that start with America.

switch(config)# clock timezone AMERICA?
America/Adak                    America/Anchorage
America/Anguilla                America/Antigua
America/Araguaina               America/Argentina/Buenos_Aires

America/Virgin                  America/Whitehorse
America/Winnipeg                America/Yakutat
America/Yellowknife

switch(config)#clock timezone AMERICA

dns domain

The dns domain command configures the switchs domain name. The switch uses this name to complete unqualified host names.

The no dns domain and default dns domain commands delete the domain name by removing the dns domain command from running-config.

Command Mode

Global Configuration

Command Syntax

dns domain string

no dns domain

default dns domain

Parameter

string domain name (text string).

Example

This command configures aristanetworks.com as the switchs domain name.

switch(config)# dns domain aristanetworks.com
switch(config)#

email

The email command places the switch in email client configuration mode. If you configure a from-user and an outgoing SMTP server on the switch, you can then use an email address as an output modifier to a show command and receive the output as email.

Command Mode

Global Configuration

Command Syntax

Example

This command places the switch in email client configuration mode.

switch(config)# email
switch(config)#

event-monitor backup max-size

The event-monitor backup max-size command specifies the quantity of event monitor backup files the switch maintains. Values range from 1 to 200 files with a default of ten files.

The event-monitor backup path command specifies the path/name of these files. The switch appends an extension to the file name that tracks the creation order of backup files. When the quantity of files exceeds the configured limit, the switch deletes the oldest file.

The no event-monitor backup max-size and default event-monitor backup max-size command restores the default maximum number of backup files the switch can store to ten by removing the corresponding event-monitor backup max-size command from running-config.

Command Mode

Global Configuration

Command Syntax

event-monitor backup max-size file_quantity

no event-monitor backup max-size

default event-monitor backup max-size

Parameter

file_quantity maximum number of backup files. Value ranges from 1 to 200. Default is 10.

Example

These commands configure the switch to back up the event buffer to a series of files named sw-event.log. The switch can store a maximum of four files.

switch(config)# event-monitor backup path sw-event.log
switch(config)# event-monitor backup max-size 4
switch(config)#

The first five files that the switch creates to store event monitor buffer contents are:

sw-event.log.0

sw-event.log.1

sw-event.log.2

sw-event.log.3

sw-event.log.4

The switch deletes sw-event.log.0 the first time it verifies the number of existing backup files after the creation of sw-event.log.4.

event-monitor backup path

The event-monitor backup path command enables the storage of the event monitor buffer to switch files and specifies the path/name of these files. The command references the file location either from the flash drive root directory (/mnt/flash) where the CLI operates or from the switch root directory (/).

The event monitor buffer is circular after the buffer is filled, new data is written to the beginning of the buffer, replacing old data. At the conclusion of each buffer writing cycle, it is copied into a new backup file before the switch starts re-writing the buffer. The switch appends a extension number to the file name when it creates a new file. After every 500 events, the switch deletes the oldest backup file if the file limit specified by the event-monitor backup max-size command is exceeded.

running-config can contain a maximum of one event-monitor backup path statement. Subsequent event-monitor backup path commands replace the existing statement in running-config, changing the name of the file where event monitor backup files are stored.

The no event-monitor backup path and default event-monitor backup path commands disable the storage of the event monitor buffer to switch files by deleting the event-monitor backup path command from running-config.

Command Mode

Global Configuration

Command Syntax

event-monitor backup path URL_FILE

no event-monitor backup path

default event-monitor backup path

Parameters

URL_FILE path and file name of the backup file:

path_string specified path is appended to /mnt/flash/.
file: path_string specified path is appended to /.
flash: path_string specified path is appended to /mnt/flash/.

Example

These commands configure the switch to store the event monitor buffer in sw-event.log, then display the new file in the flash directory.

switch(config)# event-monitor backup path eventmon_backup_dir/event.log
switch(config)#
bash-4.3# ls /mnt/flash/eventmon_backup_dir/

arpevent.log.1  lacpevent.log.1  neighborevent.log.1  routeevent.log.1
igmpsnoopingevent.log.1  macevent.log.1   route6event.log.1    
stpunstableevent.log.1

event-monitor buffer max-size

The event-monitor buffer max-size command specifies the size of the event monitor buffer. The event monitor buffer is a fixed-size circular data structure that receives event records from the event monitor. When event monitor backup is enabled (event-monitor backup path), the buffer is copied to a backup file before each rollover.

Buffer size ranges from 6 Kb to 50 Kb. The default size is 32 Kb.

The no event-monitor buffer max-size and default event-monitor buffer max-size commands restore the default buffer size of 32 Kb by removing the event-monitor buffer max-size command from running-config.

Command Mode

Global Configuration

Command Syntax

event-monitor buffer max-size buffer_size

no event-monitor buffer max-size

default event-monitor buffer max-size

Parameters

buffer_size buffer capacity (Kb). Values range from 6 to 50. Default value is 32.

Example

This command configures a buffer size of 48 Kb.

switch(config)# event-monitor buffer max-size 48
switch(config)#

event-monitor clear

The event-monitor clear command removes the contents of the event monitor buffer. If event monitor backup is enabled, this command removes the contents from all event monitor backup files.

Command Mode

Privileged EXEC

Command Syntax

event-monitor clear

Example

This command clears the contents of the event monitor buffer.

switch# event-monitor clear
switch#

event-monitor sync

The event-monitor buffer sync command combines the event monitor buffer and all backup logs and synchronizes them into a single SQLite file, which is stored at /var/log/eventMon.db.

Command Mode

Privileged EXEC

Command Syntax

event-monitor sync

Example

This command synchronizes the buffer and backup logs into a single SQLite file.

switch(config)# event-monitor sync
switch(config)#

event-monitor

The event-monitor command enables the event monitor and specifies the types of events that are logged. The event monitor is an event logging service that records system events to a local database.

The database maintains a separate table for each event type.

The event monitor is disabled by default.

The no event-monitor all command disables the event monitor.
The no event-monitor command, followed by a log type parameter, disables event recording for the specified type.
The event-monitor command enables the specified event logging type by removing the corresponding no event-monitor command from running-config.

The no event-monitor and default event-monitor commands, without a LOG_TYPE parameter, restore the default event monitor settings by deleting all event monitor related commands from running-config.

Command Mode

Global Configuration

Command Syntax

event-monitor LOG_TYPE

no event-monitor LOG_TYPE

default event-monitor LOG_TYPE

Parameters

LOG_TYPE specifies the event logging type. Options include:

all all event logging types.
arp changes to ARP table.
backup backed up log files.
buffer changes to the local buffer settings.
igmpsnooping changes to IGMP snooping table.
lacp changes to the LACP table events.
mac changes to MAC address table.
mroute changes to multicast routing table.
neighbor changes to the neighbor routing table.
route changes to IP routing table.
route6 changes to IP route6 table.
stpunstable events that cause STP instability.

Related Command

no event-monitor

Examples

This command disables the event monitor for all types of events.
```
switch(config)# no event-monitor all
switch(config)#
```
This command enables the event monitor for routing table changes.
```
switch(config)# event-monitor route
switch(config)#
```

hostname

The hostname command assigns a text string as the switch's host name. The default host name is localhost.

The prompt displays the host name when appropriately configured through the prompt command.

The no hostname and default hostname commands return the switch's host name to the default value of localhost.

Command Mode

Global Configuration

Command Syntax

hostname string

no hostname

default hostname

Parameter

string host name assigned to the switch.

Example

This command assigns the string main-host as the switchs host name.

switch(config)# hostname main-host
main-host(config)#

The prompt was previously configured to display the host name.

ip domain lookup

The ip domain lookup command specifies the source interface for all DNS requests sent from the specified VRF.

The no ip domain lookup and default ip domain lookup commands return the switch to its default state, in which the switch selects source IP addresses for each DNS request from the specified VRF.

Command Mode

Global Configuration

Command Syntax

ip domain lookup [VRF_INSTANCE] source-interface INTF_NAME

no ip domain lookup [VRF_INSTANCE] source-interface

default ip domain lookup [VRF_INSTANCE] source-interface

Parameters

VRF_INSTANCE specifies the VRF instance being modified.
- no parameter changes are made to the default VRF.
- vrf vrf_name changes are made to the specified VRF.
INTF_NAME name of source interface to be used for DNS requests. Options include:
- ethernet e_num Ethernet interface specified by e_num.
- loopback l_num Loopback interface specified by l_num.
- management m_num Management interface specified by m_num.
- port-channel p_num Port-channel interface specified by p_num.
- vlan v_num VLAN interface specified by v_num.

Examples

This command specifies VLAN 5 as the source interface for DNS requests originating from the default VRF.
```
switch(config)# ip domain lookup source-interface Vlan5
switch(config)#
```
This command specifies VLAN 10 as the source interface for DNS requests originating from VRF purple.
```
switch(config)# ip domain lookup vrf purple source-interface Vlan10
switch(config)#
```

ip domain-list

The ip domain-list command specifies a domain name to add to the IP domain list.

The no ip domain-list and default ip domain-list commands return the IP domain list to its default state, in which the switch selects source IP addresses for each DNS request from the specified VRF.

Command Mode

Global Configuration

Command Syntax

ip domain-list [IP_DOMAIN_NAME]

no ip domain-list [IP_DOMAIN_NAME]

default ip domain-list [IP_DOMAIN_NAME]

Parameter

IP_DOMAIN_NAME specifies the IP domain name.

Examples

This command specifies foo.com as the IP domain name to add to the IP domain list.
```
switch(config)# ip domain-list foo.com
switch(config)#
```
This command removes foo.com and returns the IP domain list to its default state.
```
switch(config)# no ip domain-list foo.com
switch(config)#
```

ip host

The ip host command associates a hostname to an IPv4 address. This command supports local hostname resolution based on local hostname IP address maps. Multiple hostnames can be mapped to an IP address. IPv4 and IPv6 addresses can be mapped to the same hostname. To map an IPv6 address to a hostname, use the ipv6 host command. The show hosts command displays the local hostname IP address mappings.

The no ip host and default ip host commands remove hostname IP address maps by deleting the corresponding ip host command from running-config, as specified by the following command parameters:

no parameters -Removes all hostname IP address maps.
hostname - Removes all IP address maps for the specified hostname.
hostname and IP address - Removes specified hostname IP address maps.

Command Mode

Global Configuration

Command Syntax

ip host hostname hostadd_1 [hostadd_2] ...[hostadd_X]

no ip host [hostname] [hostadd_1 [hostadd_2] [hostadd_X]

default ip host [hostname] [hostadd_1 [hostadd_2] [hostadd_X]

Parameters

hostname - hostname (text).
hostadd_N - IPv4 address associated with hostname in dotted decimal notation.

Related Commands

ipv6 host
show hosts

Examples

This command associates the hostname MyTestLab with the IP addresses 10.24.18.5 and 10.24.16.3.
```
switch(config)#ip host MyTestLab 10.24.18.5 10.24.16.3
```
This command removes all IP address maps for the hostname production_lab.
```
switch(config)#no ip host production_lab
switch(config)#
```

ip name-server

The ip name-server command adds name server addresses to running_config. The switch uses name servers for name and address resolution. The switch can be configured with up to three name servers. Although a command can specify multiple name server addresses, running_config stores each address in a separate statement. Name server addresses can be IPv4 and IPv6; each command can specify both address types.

Attempts to add a fourth server generate an error message. All name server addresses must be configured in the same VRF. When name servers were previously configured in a VRF, they must all be removed before adding new name server entries.

The no ip name-server and default ip name-server commands remove specified name servers from running_config. Commands that do not list an address remove all name servers.

Command Mode

Global Configuration

Command Syntax

ip name-server [VRF_INSTANCE] [SERVER_1] [SERVER_2] [SERVER_3]

no ip name-server [VRF_INSTANCE] [SERVER_1] [SERVER_2] [SERVER_3]

default ip name-server [VRF_INSTANCE] [SERVER_1] [SERVER_2] [SERVER_3]

Parameters

VRF_INSTANCE specifies the VRF instance containing the addresses.
- no parameter default VRF.
- vrf vrf_name a user-defined VRF.
SERVER_X IP address of the name server (dotted decimal notation). Options include:
- ipv4_addr (A.B.C.D)
- ipv6_addr (A:B:C:D:E:F:G:H)
A command can contain both (IPv4 and IPv6) address types.

Guidelines

All configured name server addresses must come from the same VRF. To use a user defined VRF for connection to a name server, first remove any name servers configured in the default VRF.

Examples

This command adds two name servers to the configuration.

switch(config)# ip name-server 172.0.14.21 3:4F21:1902::
switch(config)#

This command attempts to add a name server when the configuration already lists three servers.

switch(config)# ip name-server 172.1.10.22
% Maximum number of nameservers reached. '172.1.10.22' not added
switch(config)#

ipv6 host

The ipv6 host command associates a hostname to an IPv6 address. This command supports local hostname resolution based on local hostname IP address maps. Multiple hostnames can be mapped to an IPv6 address. IPv4 and IPv6 addresses can be mapped to the same hostname. To map IPv4 addresses to a hostname, use the ip host command. The show hosts command displays the local hostname IP address mappings.

The no ipv6 host and default ipv6 host commands remove hostname IP address maps by deleting the corresponding ipv6 host command from running-config, as specified by command parameters:

no parameters - Removes all hostname IPv6 address maps.
hostname - Removes all IPv6 address maps for the specified hostname.
hostname and IP address - Removes specified hostname IP address maps.

Command Mode

Global Configuration

Command Syntax

ipv6 host hostname hostadd1 [hostadd2] ...[hostaddX]

no ipv6 host [hostname] [hostadd1 [hostadd2] [hostaddX]

default ipv6 host [hostname] [hostadd1 [hostadd2] [hostaddX]

Parameters

hostname - hostname in a text format.
hostaddN IPv6 addresses associated with the hostname in dotted decimal notation.

Related Commands

ip host
show hosts

Example

This command associates the hostname MySupportLab with the IPv6 address 2001:0DB8:73:ff:ff:26:fd:90.

switch(config)#ipv6 host MySupportLab 2001:0DB8:73:ff:ff:26:fd:90
switch(config)#

logging format

The logging format command configures formatting options for syslog messages.

The no logging format and default logging format commands remove the corresponding logging format command from running-config and restore the specified formatting to its default setting.

Command Mode

Global Configuration

Command Syntax

logging format {hostname{fqdn|ipv4}|rfc5424|sequence-numbers|timestamp{high-resolution|traditional[timezone][year]}}

no logging format {hostname|rfc5424|sequence-numbers|timestamp}

default logging format {hostname|rfc5424|sequence-numbers|timestamp}

Parameters

hostname {fqdn\ipv4} specifies the formatting for the hostname in syslog messages as either fqdn (fully qualified domain name) or ipvr (IPv4 address).

rfc5424 causes syslogs generated locally to include high-resolution timestamps, and syslogs forwarded to remote servers to be sent in RFC5424 format.

sequence-numbers causes the sequence numbers of syslog messages to be visible when the messages are displayed.

timestamp {high-resolution|traditional[timezone][year]} specifies the formatting for syslog timestamps as either high-resolution (high-resolution RFC3339 timestamps) or traditional (traditional syslog timestamps as specified in RFC3164).When using the traditional timestamp format, timezone and year can also be included.

Examples

This command enables sequence numbering that can been seen when Syslog messages are displayed.
```
switch(config)# logging format sequence-numbers
switch(config)#
```

To display the sequence numbers, issue the show logging command.

switch# show logging
    Syslog logging: enabled
    Buffer logging: level debugging
    Console logging: level informational
    Synchronous logging: disabled
    Trap logging: level informational
    Sequence numbers: enabled
    Syslog facility: local4
    Hostname format: Hostname only
    Repeat logging interval: disabled

Log Buffer:

Nov 12 14:03:34 switch1 SuperServer: 1: %SYS-7-CLI_SCHEDULER_LOG_STORED: Logfile for scheduled CLI execution job 'tech-support' is stored in 
flash:/schedule/tech-support/tech-support_2012-11-12.1402.log.gz
Nov 12 14:06:52 switch1 Cli: 2: %SYS-5-CONFIG_I: Configured from console by admin on con0 (0.0.0.0)
Nov 12 14:07:26 switch1 Cli: 3: %SYS-5-CONFIG_E: Enter configuration mode from console by admin on con0 (0.0.0.0)
Nov 12 14:14:29 switch1 Cli: 4: %SYS-5-CONFIG_I: Configured from console by admin on con0 (0.0.0.0)
Nov 12 14:15:55 switch1 Cli: 5: %SYS-5-CONFIG_E: Enter configuration mode from console by admin on con0 (0.0.0.0)
Nov 12 14:33:05 switch1 Cli: 6: %SYS-5-CONFIG_I: Configured from console by admin on con0 (0.0.0.0)
Nov 12 14:45:13 switch1 Cli: 7: %SYS-5-CONFIG_E: Enter configuration mode from console by admin on con0 (0.0.0.0)
switch#

logging persistent

The logging persistent command logs the files stored on the flash disk. It can store upto 30MB logs.

The no logging persistent command disables the logging from the running-config.

Command Mode

Global Configuration Mode

Command Syntax

logging persistent logging file size

no logging persistent logging file size

Parameter

logging file size The maximum size (in bytes) of logging file stored on flash disk. The value ranges from 1024 to 2147483647.

Example

This command configures logging persistent on the switch.

switch# config
switch(config)# logging persistent 1024
! Note: writing system log message on non-volatile flash will affect the life 
expectancy of the flash drive due to heavy writing. Please disable persistent logging unless needed.

logging repeat-messages

The logging repeat-messages command configures repetition of syslog messages instead of summarizing the count of repeats.

The no logging repeat-messages and default logging repeat-messages commands disable the functionality to repeat logging messages in running-config.

Command Mode

Global Configuration

Command Syntax

logging repeat-messages

no logging repeat-messages

default logging repeat-messages

Examples

This command repeats syslog messages instead of summarizing the count of repeats.
```
switch(config)# logging repeat-messages
switch(config)#
```

This command displays the status of logging repeat messages command.

switch(config)# show logging
Syslog logging: enabled
    Buffer logging: level debugging
    Console logging: level debugging
    Monitor logging: level debugging
    Synchronous logging: disabled
    Trap logging: level informational
    Sequence numbers: disabled
    Syslog facility: local4
    Hostname format: Hostname only
    Repeat logging interval: disabled
    Repeat messages: enabled

Facility             Severity            Effective Severity
--------------       -------------       ------------------
aaa                  debugging           debugging
accounting           debugging           debugging

switch(config)#

no event-monitor

The no event-monitor and default event-monitor commands remove the specified event-monitor configuration statements from running-config, returning the switch to the specified default state.

no event-monitor with no parameters, restores all default setting states:
- event monitor is enabled.
- buffer backup is disabled.
The no event-monitor backup disables the backup.

To disable the event monitor, enter the no event-monitor all command (event-monitor).

Command Mode

Global Configuration

Command Syntax

no event-monitor [PARAMETER]

default event-monitor [PARAMETER]

Parameters

PARAMETER the event monitor property that is returned to the default state.

no parameter all event monitor properties.
backup event monitor buffer backup is disabled.

Example

This command removes all event monitor configuration statements from running-config.

switch(config)# no event-monitor
switch(config)#

ntp authenticate

The ntp authenticate command enables the authentication of incoming NTP packets. When authentication is enabled, NTP packets will be used to synchronize time on the switch only if they include a trusted authentication key. Authentication keys are created on the switch using the ntp authentication-key command, and the ntp trusted-key command is used to specify which keys are trusted. NTP authentication is disabled by default.

The no ntp authenticate and default ntp authenticate commands disable NTP authentication on the switch by removing the corresponding ntp authenticate command from running-config.

Command Mode

Global Configuration

Command Syntax

ntp authenticate

no ntp authenticate

default ntp authenticate

Examples

This command enables NTP authentication on the switch.
```
switch(config)# ntp authenticate
switch(config)#
```
This command disables NTP authentication on the switch.
```
switch(config)# no ntp authenticate
switch(config)#
```

ntp authentication-key

The ntp authentication-key command creates an authentication key for use in authenticating incoming NTP packets. For the key to be used in authentication:

It must be configured as a trusted key using the ntp trusted-key command.
NTP authentication must be enabled on the switch using the ntp authenticate command.
The same key must be configured on the NTP server.

The no ntp authentication-key and default ntp authentication-key commands remove the specified authentication key by removing the corresponding ntp authentication-key command from running-config.

Command Mode

Global Configuration

Command Syntax

ntp authentication-keykey_id ENCRYPT_TYPE password_text

no ntp authentication-key key_id

default ntp authentication-key key_id

Parameters

key_id key ID number. Value ranges from 1 to 65534.
ENCRYPT_TYPE encryption method. Values include:
- md5 key_text is MD5 encrypted.
- sha1 key_text is SHA-1 encrypted.
password_text the authentication-key password.

Examples

This command creates an NTP authentication key with ID 234 and password timeSync using MD5 encryption.
```
switch(config)# ntp authentication-key 234 md5 timeSync 
```
Running-config stores the password as plain text.
This command removes NTP authentication key 234.
```
switch(config)# no ntp authentication-key 234
```

ntp local-interface

The ntp local-interface command configures an interface as the local NTP source. The IP address of that interface will then be used as the source address in NTP packets sent by the switch. If the switch is acting as an NTP server and a server-specific source interface has been configured using the source option of the ntp server command, the server-specific source address will take precedence.

The no ntp local-interface and default ntp local-interface commands remove the ntp local-interface command from running-config.

Command Mode

Global Configuration

Command Syntax

ntp local-interface [VRF_INSTANCE] INT_PORT

no ntp local-interface

default ntp local-interface

Parameters

VRF_INSTANCE the VRF instance to be used for connection to the specified server. Options include:
- no parameter connects using the default VRF.
- vrf vrf_name connects using the specified user-defined VRF.
INT_PORT the interface port that specifies the NTP local interface. Settings include:
- ethernet e_range Ethernet interface list.
- loopback l_range loopback interface list.
- management m_range management interface list.
- port-channel c_range port channel interface list.
- vlan v_range VLAN interface list.

Examples

This command configures ntp local-interface vlan 25 as the local NTP source. NTP packets exiting the switch use the IP address of VLAN interface 25 as their source address.
```
switch(config)# ntp local-interface vlan 25
switch(config)#
```
This command removes the ntp local-interface command from the configuration.
```
switch(config)# no ntp local-interface
switch(config)#
```

ntp serve all

The ntp serve all command configures the switch to act as an NTP server by accepting incoming NTP requests.

Using this command also causes the switch to re-synchronize with its upstream NTP server.

Individual interfaces can be configured separately to accept or deny NTP requests by using the ntp serve command, and these settings override the global setting.

Command Mode

Global Configuration

Command Syntax

ntp serve all

no ntp serve all

default ntp serve all

Example

This command configures the switch to accept incoming NTP requests.
```
switch(config)# ntp serve all
switch(config)#
```
This command configures the switch to deny incoming NTP requests.
```
switch(config)# no ntp serve all
switch(config)#
```

ntp serve

The ntp serve command configures the command mode interface to accept incoming NTP requests regardless of the global setting.

The no ntp serve command configures the command mode interface to refuse incoming NTP requests regardless of the global setting. The default ntp serve command configures the command mode interface to follow the global setting.

Using this command also causes the switch to re-synchronize with its upstream NTP server.

Command Modes

Interface-Ethernet Configuration

Interface-Loopback Configuration

Interface-Management Configuration

Interface-Port-channel Configuration

Interface-VLAN Configuration

Interface-VXLAN Configuration

Command Syntax

ntp serve

no ntp serve

default ntp serve

Examples

These commands configure interface ethernet 5 to accept incoming NTP requests regardless of global settings.
```
switch(config)# interface ethernet 5
switch(config-if-Et5)# ntp serve
switch(config-if-Et5)#
```
These commands configure interface ethernet 5 to deny incoming NTP requests regardless of global settings.
```
switch(config)# interface ethernet 5
switch(config-if-Et5)# no ntp serve
switch(config-if-Et5)#
```
These commands configure interface ethernet 5 to use global settings in responding to incoming NTP requests.
```
switch(config)# interface ethernet 5
switch(config-if-Et5)#default ntp serve
switch(config-if-Et5)#
```

ntp server

The ntp server command adds a Network Time Protocol (NTP) server to the running-config. If the command specifies an existing server in the running-config, it modifies the server settings. The switch synchronizes the system clock with an NTP server when running-config contains at least one valid NTP server.

The switch supports NTP versions 1 through 4. The default is version 4.

The prefer option specifies a preferred NTP server to use as the NTP server if not discarded by NTP.

The no ntp server and default ntp server commands remove the specified NTP server from running-config. To remove an NTP server configured in a user-defined VRF, include the VRF name in the no ntp server command.

Command Mode

Global Configuration

Command Syntax

ntp server [ vrfvrf_instance | host_name] refresh [version ntp_version] [source-address [ [ipv4_address | ipv6_address] burst [iburst [ key auth_key ][ maxpoll max_poll_interval][] [ minpoll min_poll_interval ] prefer source interface_name

no ntp server [vrf_instance] host_name

default ntp server [vrf_instance] host_name

All parameters except vrf and hostname can be placed in any order.

Parameters

vrf vrf_instance - Specify the VRF instance to use for the connection to the specified server.
host_name Specify the name or IP address of the NTP server. Options include:
- ip_address - Specify an IPv4 or IPv6 address in dotted decimal notation.
- host_name - Specify the hostname of the NTP server.
prefer - Indicates the priority of this server when the switch selects a synchronizing server.
- no parameter - The server has no special priority.
- prefer - This server has priority when the switch selects a synchronizing server.
refresh - Specifies sending periodic DNS queries for the NTP server. If the DNS response doesn't include the resolved IP address of the NTP server, then a request selects the next available IP address and restarts the service with an updated configuration.
version ntp_version - Specifies the NTP version. Settings include:
- no parameter - Sets NTP version to 4 (default).
- version number - Specify a version number from 1 to 4.
source-address ip_source - Specifies the source IPv4 address or IPv6 address for NTP updates for the specified NTP server. This option overrides global settings created by the ntp local-interface command.
burst - Indicates that when the switch reaches the NTP server, the switch sends packets to the server in bursts of eight instead of the usual one. Recommended only for local servers. Disabled by default.
iburst - Indicates that the switch sends packets to the server in bursts until reaching the server. Recommended for general use to speed synchronization. Disabled by default.
key auth_key - Specify the authentication key to use when authenticating NTP packets from the server.
- no parameter - Specify no authentication key.
- key 1 to 65534 - The switch uses the specified key to authenticate NTP packets from the server.
max_poll_interval - Specifies the maximum polling interval for the server as the base-2 logarithm of the interval in seconds. Settings include the following:
- no parameter - Sets the maximum polling interval to 10. (1,024 seconds, the default).
- maxpoll number - Specifies to use the number as the base-2 logarithm of the interval in seconds. Values range from 3 (8 seconds) to 17 (131,072 seconds, approximately 36 hours).
minpoll min_poll_interval - Specifies the minimum polling interval for the server as the base-2 logarithm of the interval in seconds. Settings include the following:
- no parameter - Sets the minimum polling interval to 6 (64 seconds, the default).
- number, where number is the base-2 logarithm of the interval in seconds. Values range from 3 (8 seconds) to 17 (131,072 seconds, approximately 36 hours).

Guidelines

To configure multiple parameters for a single server, include them all in a single ntp server command. Using the command again for the same server overwrites parameters previously configured in running-config.

All NTP servers must use the same VRF. If you do not specify a VRF, the server uses the default VRF. To use a user-defined VRF for connection to an NTP server, first use the no ntp server command to remove any NTP servers configured in the default VRF.

When specifying a source interface, choose an interface in the same VRF as the server. If the source interface does not exists on the same VRF, the running-config includes the source data but does not add it to the NTP packets.

An NTP server may be configured using an invalid or inactive VRF, but the status of the NTP server remains inactive until the VRF becomes active.

Examples

This command configures the switch to update the time with the NTP server at address 172.16.0.23 and designates it as a preferred NTP server.
```
switch(config)# ntp server 172.16.0.23 prefer
```
This command configures the switch to update the time through an NTP server named local-nettime.
```
switch(config)# ntp server local-nettime
```
This command configures the switch to update the time through a version 3 NTP server.
```
switch(config)# ntp server 171.18.1.22 version 3
```

These commands reconfigure the switch to access the above NTP servers through VRF magenta.

switch(config)# no ntp server 172.16.0.23
switch(config)# no ntp server local-nettime
switch(config)# no ntp server 171.18.1.22
switch(config)# ntp server vrf magenta 172.16.0.23 prefer
switch(config)# ntp server vrf magenta local-nettime
switch(config)# ntp server vrf magenta 171.18.1.22 version 3
switch(config)#

ntp trusted-key

The ntp trusted-key command specifies which authentication keys will be trusted for authentication of NTP packets. A packet with a trusted key will be used to update the local time if authenticated.

The no ntp trusted-key and default ntp trusted-key commands remove the specified authentication keys from the trusted key list by removing the corresponding ntp trusted-key command from running-config.

Command Mode

Global Configuration

Command Syntax

ntp trusted-key key_list

no ntp trusted-key

default ntp trusted-key

Parameter

key_list specified one or more keys. Formats include a number (1 to 65534), number range, or comma-delimited list of numbers and ranges.

Example

This command configures the switch to trust authentication keys 234 and 237 for authentication of NTP packets.

switch(config)# ntp trusted-key 234,237
switch(config)#

power enable module

The power enable module command powers up the specified module. The no power enable module command powers down the specified module.

Command Mode

Global Configuration

Command Syntax

power enable module {fabric|linecard|supervisor|switchcard} module_number

no power enable module {fabric|linecard|supervisor|switchcard} module_number

default power enable module {fabric|linecard|supervisor|switchcard} module_number

Parameters

fabric specifies a fabric card

linecard specifies a linecard

supervisor specifies a supervisor

switchcard specifies a switch card

module_number specifies the number of the module

Examples

This command powers down linecard 3.

switch(config)# no power enable module linecard 3
switch(config)#

These commands reload fabric module 2.

switch(config)# no power enable module fabric 2
switch(config)# power enable module fabric 2
switch(config)#

prompt

The prompt command specifies the contents of the CLI prompt. Characters allowed in the prompt include A-Z, a-z, 0-9, and these punctuation marks:

! @ # $ % & * ( ) - = + f g [ ] ; : < > , . ? / n

The prompt supports these control sequences:

%s – space character
%t – tab character
%% – percent character
%D – time and date
%D{f_char} – time and date, format specified by the BSD strftime (f_char) time conversion function.
%H – host name
%h – host name up to the first ‘.’
%P – extended command mode
%p – command mode
%r ^¹ – redundancy status on modular systems.
%R ^² – extended redundancy status on modular systems – includes status and slot number.

Table 1. Command Mode Prompt Examples
Command Mode	Command Mode Prompt	Extended Command Mode Prompt
Exec	>	>
Privileged Exec	#	#
Global Configuration	(config)#	(config)#
Ethernet Interface Configuration	(config-if)#	(config-if-ET15)#
VLAN Interface Configuration	(config-if)#	(config-if-Vl24)#
Port Channel Interface Configuration	(config-if)#	(config-if-Po4)#
Management Interface Configuration	(config-if)#	(config-if-Ma1)
Access List Configuration	(config-acl)#	(config-acl-listname)#
OSPF Configuration	(config-router)#	(config-router-ospf)#
BGP Configuration	(config-router)#	(config-router-bgp)#

The no prompt and default prompt commands return the prompt to the default of %H%R%P.

Command Mode

Global Configuration

Command Syntax

prompt p_string

no prompt

default prompt

Parameters

p_string prompt text (character string). Elements include letters, numbers, and control sequences.

Examples

This command creates a prompt that displays system 1 and the command mode.
```
host-name.dut103(config)# prompt system%s1%P
system 1(config)#
```
This command creates a prompt that displays the command mode.
```
host-name.dut103(config)# prompt %p
(config)#
```

These equivalent commands create the default prompt.

% prompt %H%P
host-name.dut103(config)#

% no prompt
host-name.dut103(config)#

show banner

The show banner command displays the specified banner.

Command Mode

Privileged EXEC

Command Syntax

show banner BANNER_TYPE [login | motd]

Parameters

BANNER_TYPE banner that the command displays. Options include:

login command displays login banner.
motd command displays message of the day banner.

Example

These commands configure and display the message of the day banner.

switch(config)# banner motd
Enter TEXT message. Type 'EOF' on its own line to end.
This is an motd banner for $(hostname)
EOF

switch(config)# show banner motd
This is an motd banner for $(hostname)
switch(config)#

show clock

The show clock command displays the current system clock time and configured time zone. The switch uses the system clock for system log messages and debugging traces.

Command Mode

EXEC

Command Syntax

show clock

Example

This command displays the current system clock time and configured time zone.

switch> show clock
Wed Nov  2 10:29:32 2011
timezone is America/Los_Angeles
switch>

show event-monitor arp

The show event-monitor arp command performs an SQL-style query on the event monitor database and displays ARP table events as specified by command parameters. The event monitor buffer and all backup logs are synchronized into a single SQLite file.

Command Mode

Privileged EXEC

Command Syntax

show event-monitor arp [GROUP] [MESSAGES] [INTERFACE] [IP] [MAC] [TIME] [VRF]

Optional parameters can be placed in any order.

Parameters

GROUP used with aggregate functions to group results. Analogous to SQL group by command.
- no parameter results are not grouped.
- group by interface results are grouped by interface.
- group by ip results are grouped by IP address.
- group by mac results are grouped by MAC address.
- group by vrf results are grouped by VRF.
MESSAGES number of messages returned from query. Analogous to SQL limit command.
- no parameter result-set size is not limited.
- limit msg_quantity number of results that are displayed. Values range from 1 to 15,000.
INTERFACE restricts result-set to events that include specified interface (SQL Like command).
- no parameter result-set not restricted by interface.
- match-interface ethernet e_range Ethernet interface list.
- match-interface loopback l_range loopback interface list.
- match-interface management m_range management interface list.
- match-interface port-channel c_range port channel interface list.
- match-interface tunnel t_range tunnel interface list.
- match-interface VXLAN vx_range VXLAN interface list.
- match-interface port-channel c_range port channel interface list.
IP restricts result-set to events that include specified IP address (SQL Like command).
- no parameter result-set not restricted to specific IP addresses.
- match-ip ip_address_rex IP address, as represented by regular expression.
MAC restricts result-set to events that include specified MAC address (SQL Like command).
- no parameter result-set not restricted to specific MAC addresses.
- match-mac mac_address_rex MAC address, as represented by regular expression.
TIME restricts result-set to events generated during specified period.
- no parameter result-set not restricted by time of event.
- match-time last-minute includes events generated during last minute.
- match-time last-day includes events generated during last day.
- match-time last-hour includes events generated during last hour.
- match-time last-week includes events generated during last week.
VRF restricts result-set to events that include a specific VRF.
- no parameter result-set not restricted by time of event.
- match-vrf vrf_name the VRF name.

Example

This command displays ARP table events listed in the event monitor database.

switch# show event-monitor arp
% Writing 220017 Arp, 234204 Route, 1732559 Mac events to the database
2012-11-06 12:36:10|10.33.6.159|Vlan1417|0000.00dc.cc0d|0|added|2186271
2012-11-06 12:38:20|10.33.7.150|Vlan1417|0000.00f7.e25f|0|added|2186292
2012-11-06 12:38:34|10.33.6.62|Vlan1417|0000:00:01:c2:ac|0|added|2186295
2012-11-06 12:39:13|10.33.7.162|Vlan1417|00:00:00:45:c2:79|0|added|2186299
2012-11-06 12:39:50|10.33.12.54|Vlan1417|||removed|2186303
2012-11-06 12:39:51|10.33.6.218|Vlan1417|00:00:00:e9:36:46|0|added|2186305
2012-11-06 12:40:00|10.33.6.140|Vlan1417|00:00:00:4a:36:c3|0|added|2186308
2012-11-06 12:40:02|10.33.6.239|Vlan1417|00:00:00:5b:a7:21|0|added|2186312
2012-11-06 12:41:16|10.33.7.11|Vlan1417|00:00:00:3f:94:59|0|added|2186320
2012-11-06 12:41:50|10.33.7.60|Vlan1417|00:00:00:1f:3c:8e|0|added|2186346
2012-11-06 12:43:34|10.33.7.81|Vlan1417|00:00:00:e3:0d:9c|0|added|2186762
2012-11-06 12:43:42|10.33.6.214|Vlan1417|00:00:00:7b:09:7d|0|added|2186765
2012-11-06 12:43:59|10.33.7.149|Vlan1417|00:00:00:8d:a6:d8|0|added|2186768
switch#

show event-monitor igmpsnooping

The show event-monitor igmpsnooping command performs an SQL-style query on the event-monitor database, using the statement specified in the command.

Command Mode

Privileged EXEC

Command Syntax

show event-monitor igmpsnooping [GROUP] [MESSAGES] [MAC] [INTERFACE] [VLAN] [TIME]

Parameters

GROUP used with aggregate functions to group results. Analogous to SQL group by command.
- no parameter results are not grouped.
- group-by interface results are grouped by interface.
- group-by mac results are grouped by MAC address.
- group-by vlan results are grouped by VLAN.
MESSAGES number of messages returned from query. Analogous to SQL limit command.
- no parameter result-set size is not limited.
- limit msg_quantity number of results that are displayed. Values range from 1 to 15,000.
MAC restricts result-set to events that include specified MAC address (SQL Like command).
- no parameter result-set not restricted to specific MAC addresses.
- match-mac mac_address_rex MAC address, as represented by regular expression.
INTERFACE restricts result-set to events that include specified interface (SQL Like command).
- no parameter result-set not restricted by interface.
- match-interface ethernet e_range Ethernet interface list.
- match-interface loopback l_range loopback interface list.
- match-interface management m_range management interface list.
- match-interface port-channel c_range port channel interface list.
- match-interface vlan v_range VLAN interface list.
- match-interface tunnel t_range tunnel interface list.
- match-interface VXLAN vx_range VXLAN interface list.
TIME restricts result-set to events with specified period.
- no parameter result-set not restricted by time of event.
- match-time last-minute includes events generated during last minute.
- match-time last-day includes events generated during last day.
- match-time last-hour includes events generated during last hour.
- match-time last-week includes events generated during last week.
VLAN restricts result-set to events that include a specific VLAN (SQL Like command).
- no parameter result-set not restricted by time of event.
- match-vlan vlan VLAN interface number.

Example

switch# show event-monitor igmpsnooping
switch#

show event-monitor mac

The show event-monitor mac command performs an SQL-style query on the event monitor database and displays MAC address table events as specified by command parameters. The event monitor buffer and all backup logs are synchronized into a single SQLite file.

Command Mode

Privileged EXEC

Command Syntax

show event-monitor mac [GROUP] [MESSAGES] [INTERFACE] [MAC] [TIME]

Optional parameters can be placed in any order.

Parameters

GROUP used with aggregate functions to group results. Analogous to SQL group by command.
- no parameter results are not grouped.
- group-by interface results are grouped by interface.
- group-by mac results are grouped by MAC address.
MESSAGES number of messages returned from query. Analogous to SQL limit command.
- no parameter result-set size is not limited.
- limit msg_quantity number of results that are displayed. Values range from 1 to 15,000.
INTERFACE restricts result-set to events that include specified interface (SQL Like command).
- no parameter result-set not restricted by interface.
- match-interface ethernet e_range Ethernet interface list.
- match-interface loopback l_range loopback interface list.
- match-interface management m_range management interface list.
- match-interface port-channel c_range port channel interface list.
- match-interface vlan v_range VLAN interface list.
- match-interface tunnel t_range tunnel interface list.
- match-interface VXLAN vx_range VXLAN interface list.
MAC restricts result-set to events that include specified MAC address (SQL Like command).
- no parameter result-set not restricted to specific MAC addresses.
- match-mac mac_address_rex MAC address, as represented by regular expression.
TIME restricts result-set to events with specified period.
- no parameter result-set not restricted by time of event.
- match-time last-minute includes events generated during last minute.
- match-time last-day includes events generated during last day.
- match-time last-hour includes events generated during last hour.
- match-time last-week includes events generated during last week.

Examples

This command displays all events triggered by MAC address table events.

switch# show event-monitor mac
% Writing 0 Arp, 0 Route, 1 Mac events to the database
2012-01-19 13:57:55|1|0808.0808.0808|Ethernet1|configuredStaticMac|added|0

This command displays events triggered by MAC address table changes.

switch# show event-monitor mac match-mac 08:08:08:%
2012-01-19 13:57:55|1|0808.0808.0808|Ethernet1|configuredStaticMac|added|0

show event-monitor mroute

The show event-monitor mroute command performs an SQL-style query on the event-monitor database, using the statement specified in the command.

Command Mode

Privileged EXEC

Command Syntax

show event-monitor mroute [GROUP] [MESSAGES] [IP] [INTERFACE] [SRC_IP] [TIME]

Optional parameters can be placed in any order.

Parameters

GROUP used with aggregate functions to group results. Analogous to SQL group by command.
- no parameter results are not grouped.
- group-by interface results are grouped by interface.
- group-by ipv6 results are grouped by IPv6 address.
- group-by mac results are grouped by MAC address.
- group-by vrf results are grouped by VRF.
MESSAGES number of messages returned from query. Analogous to SQL limit command.
- no parameter result-set size is not limited.
- limit msg_quantity number of results that are displayed. Values range from 1 to 15,000.
IP restricts result-set to events that include specified IP address (SQL Like command).
- no parameter result-set not restricted to specific IP addresses.
- match-ipv6 ip_address_rex IP address, as represented by regular expression.
INTERFACE restricts result-set to events that include specified interface (SQL Like command).
- no parameter result-set not restricted by interface.
- match-interface ethernet e_range Ethernet interface list.
- match-interface loopback l_range loopback interface list.
- match-interface management m_range management interface list.
- match-interface port-channel c_range port channel interface list.
- match-interface vlan v_range VLAN interface list.
- match-interface tunnel t_range tunnel interface list.
- match-interface VXLAN vx_range VXLAN interface list.
SRC_IP restricts result-set to events that include specified Source IP address (SQL Like command).
- no parameter result-set not restricted to specific IP addresses.
- match-ip ip_address_rex IP address, as represented by regular expression.
TIME restricts result-set to events with specified period.
- no parameter result-set not restricted by time of event.
- match-time last-minute includes events generated during last minute.
- match-time last-day includes events generated during last day.
- match-time last-hour includes events generated during last hour.
- match-time last-week includes events generated during last week.

Example

This command displays neighbor table events listed in the event monitor database.

switch# show event-monitor mroute
2011-07-28 12:33:28|default|16.17.18.19/32|225.0.0.1/32|||added|30
2011-07-28 12:33:28|default|16.17.18.19/32|225.0.0.1/32|Vlan2|iif|join|31
2011-07-28 12:33:28|default|16.17.18.19/32|225.0.0.1/32|Vlan3|oif|join|32
2011-07-28 12:33:28|default|16.17.18.19/32|225.0.0.1/32|Vlan4|oif|join|33
2011-07-28 12:33:28|default|10.11.12.13/32|225.0.0.2/32|||added|34
2011-07-28 12:33:28|default|10.11.12.13/32|225.0.0.2/32|Vlan3|iif|join|35
2011-07-28 12:33:28|default|10.11.12.13/32|225.0.0.2/32|Vlan2|oif|join|36
2011-07-28 12:33:28|default|16.17.18.19/32|225.0.0.1/32|Vlan4||leave|37
2011-07-28 12:33:28|default|16.17.18.19/32|225.0.0.1/32|||deleted|38
2011-07-28 12:33:28|default|10.11.12.13/32|225.0.0.2/32|||deleted|39

show event-monitor neighbor

The show event-monitor neighbor command performs an SQL-style query on the event monitor database and displays neighbor table events as specified by command parameters. The event monitor buffer and all backup logs are synchronized into a single SQLite file.

Command Mode

Privileged EXEC

Command Syntax

show event-monitor neighbor [GROUP][MESSAGES][INTERFACE][IP6][MAC][TIME][VRF]

Optional parameters can be placed in any order.

Parameters

GROUP used with aggregate functions to group results. Analogous to SQL group by command.
- no parameter results are not grouped.
- group-by interface results are grouped by interface.
- group-by ip6 results are grouped by IPv6 address.
- group-by mac results are grouped by MAC address.
- group-by vrf results are grouped by VRF.
MESSAGES number of messages returned from query. Analogous to SQL limit command.
- no parameter result-set size is not limited.
- limit msg_quantity number of results that are displayed. Values range from 1 to 15,000.
INTERFACE restricts result-set to events that include specified interface (SQL Like command).
- no parameter result-set not restricted by interface.
- match-interface ethernet e_range Ethernet interface list.
- match-interface loopback l_range loopback interface list.
- match-interface management m_range management interface list.
- match-interface port-channel c_range port channel interface list.
- match-interface vlan v_range VLAN interface list.
- match-interface tunnel t_range tunnel interface list.
- match-interface VXLAN vx_range VXLAN interface list.
IP6 restricts result-set to events that include specified IP address (SQL Like command).
- no parameter result-set not restricted to specific IP addresses.
- match-ipv6 ip6_address_rex IPv6 address, as represented by regular expression.
MAC restricts result-set to events that include specified MAC address (SQL Like command).
- no parameter result-set not restricted to specific MAC addresses.
- match-mac mac_address_rex MAC address, as represented by regular expression.
TIME restricts result-set to events with specified period.
- no parameter result-set not restricted by time of event.
- match-time last-minute includes events generated during last minute.
- match-time last-day includes events generated during last day.
- match-time last-hour includes events generated during last hour.
- match-time last-week includes events generated during last week.
VRF restricts result-set to events that include a specific VRF (SQL Like command).
- no parameter result-set not restricted by time of event.
- match-vrf vrf_name VRF name, as represented by a regular expression.

Example

This command displays neighbor table events listed in the event monitor database.

switch# show event-monitor neighbor
2019-09-30 14:37:32.894147|def0::1|Vlan1|default|0005.0005.0005|1|added|1
2019-09-30 14:37:32.894395|def0::2|Vlan1|default|0005.0005.0005|1|added|2
2019-09-30 14:37:32.894607|def0::3|Vlan1|default|0005.0005.0005|1|added|3
2019-09-30 14:37:32.894815|def0::4|Vlan1|default|0005.0005.0005|1|added|4
2019-09-30 14:37:32.895071|def0::5|Vlan1|default|0005.0005.0005|1|added|5
2019-09-30 14:37:32.895303|def0::6|Vlan1|default|0005.0005.0005|1|added|6
2019-09-30 14:37:32.895527|def0::7|Vlan1|default|0005.0005.0005|1|added|7
2019-09-30 14:37:32.895732|def0::8|Vlan1|default|0005.0005.0005|1|added|8
2019-09-30 14:37:32.895968|def0::9|Vlan1|default|0005.0005.0005|1|added|9
2019-09-30 14:37:32.896194|def0::a|Vlan1|default|0005.0005.0005|1|added|10

show event-monitor route6

The show event-monitor route6 command performs an SQL-style query on the event monitor database and displays routing6 table events as specified by command parameters. The event monitor buffer and all backup logs are synchronized into a single SQLite file.

Command Mode

Privileged EXEC

Command Syntax

show event-monitor route6 [GROUP][MESSAGES][IP6][TIME]

Optional parameters can be placed in any order.

Parameters

GROUP used with aggregate functions to group results. Analogous to SQL group by command.
- no parameter results are not grouped.
- group by interface results are grouped by interface.
- group by ip6 results are grouped by IPv6 address.
- group by mac results are grouped by MAC address.
- group by vrf results are grouped by VRF.
MESSAGES number of messages returned from query. Analogous to SQL limit command.
- no parameter result-set size is not limited.
- limit msg_quantity number of results that are displayed. Values range from 1 to 15,000.
IP6 restricts result-set to events that include specified IP address (SQL Like command).
- no parameter result-set not restricted to specific IP addresses.
- match-ipv6 ip6_address_rex IPv6 address, as represented by regular expression.
TIME restricts result-set to events with specified period.
- no parameter result-set not restricted by time of event.
- match-time last-minute includes events generated during last minute.
- match-time last-day includes events generated during last day.
- match-time last-hour includes events generated during last hour.
- match-time last-week includes events generated during last week.

Example

This command displays neighbor table events listed in the event monitor database.

switch# show event-monitor route6
2019-09-30 14:59:30.660447|def1::1:0/128|default|receive|0|1|updated|41
2019-09-30 14:59:30.660720|def1::2:0/128|default|attached|0|1|updated|42
2019-09-30 14:59:30.660983|def1::3:0/128|default|staticConfig|0|1|updated|43
2019-09-30 14:59:30.661226|def1::4:0/128|default|kernel|0|1|updated|44
2019-09-30 14:59:30.661469|def1::5:0/128|default|rip|0|1|updated|45
2019-09-30 14:59:30.661706|def1::6:0/128|default|connected|0|1|updated|46
2019-09-30 14:59:30.661968|def1::7:0/128|default|redirect|0|1|updated|47
2019-09-30 14:59:30.662207|def1::8:0/128|default|bgpAggregate|0|1|updated|48
2019-09-30 14:59:30.662451|def1::9:0/128|default|ospfAggregate|0|1|updated|49
2019-09-30 14:59:30.662694|def1::a:0/128|default|ospf|0|1|updated|50
2019-09-30 14:59:30.662935|def1::b:0/128|default|bgp|0|1|updated|51
2019-09-30 14:59:30.663174|def1::c:0/128|default|unknown|0|1|updated|52
switch#

show event-monitor route

The show event-monitor route command performs an SQL-style query on the event monitor database and displays routing table events as specified by command parameters. The event monitor buffer and all backup logs are synchronized into a single SQLite file.

Command Mode

Privileged EXEC

Command Syntax

show event-monitor route [GROUP][MESSAGES][IP][TIME]

Optional parameters can be placed in any order.

Parameters

GROUP used with aggregate functions to group results. Analogous to SQL group by command.
- no parameter results are not grouped.
- group-by ip results are grouped by IPv4 address.
MESSAGES number of messages returned from query. Analogous to SQL limit command.
- no parameter result-set size is not limited.
- limit msg_quantity number of results that are displayed. Values range from 1 to 15,000.
IP restricts result-set to events that include specified IP address (SQL Like command).
- no parameter result-set not restricted to specific IP addresses.
- match-ip ip_address_rex IP address, as represented by regular expression.
TIME restricts result-set to events with specified period.
- no parameter result-set not restricted by time of event.
- match-time last-minute includes events generated during last minute.
- match-time last-day includes events generated during last day.
- match-time last-hour includes events generated during last hour.
- match-time last-week includes events generated during last week.

Example

This command displays 10 routing table events listed in the event monitor database.

switch# show event-monitor route limit 10
2019-09-30 14:01:21.659428|16.16.16.255/32|default|receiveBcast|0|0|updated|20
2019-09-30 14:01:21.659464|192.168.201.12/30|default|connected|1|0|updated|21
2019-09-30 14:01:21.659497|192.168.1.255/32|default|receiveBcast|0|0|updated|22
2019-09-30 14:01:21.659503|192.168.201.8/32|default|receiveBcast|0|0|updated|23
2019-09-30 14:01:21.659512|16.16.16.0/32|default|receiveBcast|0|0|updated|24
2019-09-30 
14:01:21.659517|192.168.201.12/32|default|receiveBcast|0|0|updated|25
2019-09-30 
14:01:21.659524|192.168.201.15/32|default|receiveBcast|0|0|updated|26
2019-09-30 14:01:21.659541|192.168.201.8/30|default|connected|1|0|updated|27
2019-09-30 14:01:21.659564|16.16.16.0/24|default|connected|1|0|updated|28
2019-09-30 14:01:21.659578|192.168.201.9/32|default|receive|0|0|updated|29
switch#

show event-monitor sqlite

The show event-monitor sqlite command performs an SQL-style query on the event monitor database, using the statement specified in the command.

Command Mode

Privileged EXEC

Command Syntax

show event-monitor sqlite statement

Parameter

statement SQLite statement.

Example

This command displays all entries from the route table.

switch# show event-monitor sqlite select * from route;
2019-09-30 14:01:21.659428|16.16.16.255/32|default|receiveBcast|0|0|updated|20
2019-09-30 14:01:21.659464|192.168.201.12/30|default|connected|1|0|updated|21
2019-09-30 14:01:21.659497|192.168.1.255/32|default|receiveBcast|0|0|updated|22
2019-09-30 14:01:21.659503|192.168.201.8/32|default|receiveBcast|0|0|updated|23
2019-09-30 14:01:21.659512|16.16.16.0/32|default|receiveBcast|0|0|updated|24
2019-09-30 
14:01:21.659517|192.168.201.12/32|default|receiveBcast|0|0|updated|25
2019-09-30 
14:01:21.659524|192.168.201.15/32|default|receiveBcast|0|0|updated|26
2019-09-30 14:01:21.659541|192.168.201.8/30|default|connected|1|0|updated|27
2019-09-30 14:01:21.659564|16.16.16.0/24|default|connected|1|0|updated|28
2019-09-30 14:01:21.659578|192.168.201.9/32|default|receive|0|0|updated|29
switch#

show event-monitor stpunstable

The show event-monitor stpunstable command performs an SQL-style query on the event-monitor database, using the statement specified in the command.

Command Mode

Privileged EXEC

Command Syntax

show event-monitor stpunstable [MESSAGES][TIME]

Optional parameters can be placed in any order.

Parameters

MESSAGES number of messages returned from query. Analogous to SQL limit command.
- no parameter result-set size is not limited.
- limit msg_quantity number of results that are displayed. Values range from 1 to 15,000.
TIME restricts result-set to events with specified period.
- no parameter result-set not restricted by time of event.
- match-time last-minute includes events generated during last minute.
- match-time last-day includes events generated during last day.
- match-time last-hour includes events generated during last hour.
- match-time last-week includes events generated during last week.

Example

switch# show event-monitor stpunstable limit 5
2019-02-07 07:22:10.286164|Cist|Ethernet5|forward-delay-while|1
2019-02-07 07:22:10.286651|Cist|Ethernet6|forward-delay-while|2
2019-02-07 07:22:10.286844|Cist|Ethernet8|forward-delay-while|3
2019-02-07 07:22:10.287030|Cist|Ethernet14|forward-delay-while|4
2019-02-07 07:22:10.287215|Cist|Ethernet21|forward-delay-while|5
switch#

show hostname

The show hostname command displays the hostname and the Fully Qualified Domain Name (FQDN) of the switch.

Command Mode

EXEC

Command Syntax

show hostname

Example

This command displays the hostname and FQDN of the switch.

switch> show hostname
Hostname: switch_1
FQDN:     switch_1.aristanetworks.com

switch>

show hosts

The show hosts command displays the default domain name, name lookup service style, a list of name server hosts, and the static hostname-IP address maps.

Command Mode

EXEC

Command Syntax

show hosts

Example

This command displays the switch's IP domain name:

switch> show hosts
Default domain is: aristanetworks.com
Name/address lookup uses domain service
Name servers are: 172.22.22.40, 172.22.22.10

Static Mappings:

Hostname                       IP     Addresses

TEST_LAB                      IPV4    10.24.18.6
PRODUCTION_LAB                IPV4    10.24.18.7
SUPPORT_LAB                   IPV6    2001:0DB8:73:ff:ff:26:fd:90
switch>

show ip domain-name

The show ip domain-name command displays the switchs IP domain name that is configured with the ip domain name command.

Command Mode

EXEC

Command Syntax

show ip domain-name

Example

This command displays the switch's IP domain name:

switch> show ip domain-name
aristanetworks.com
switch>

show ip name-server

The show ip name-server command displays the ip addresses of name-servers in running-config. The name servers are configured by the ip name-server command.

Command Mode

EXEC

Command Syntax

show ip name-server

Example

This command displays the IP address of name servers that the switch is configured to access.

switch> show ip name-server
172.22.22.10
172.22.22.40
switch>

show local-clock time-properties

The show local-clock time-properties command displays the Precision Time Protocol (PTP) clock properties.

Command Mode

Privileged EXEC

Command Syntax

show local-clock time-properties

Example

This command shows the PTP clock properties.

switch# show local-clock time-properties
Current UTC offset valid: False
Current UTC offset: 0
Leap 59: False
Leap 61: False
Time Traceable: False
Frequency Traceable: False
PTP Timescale: False
Time Source: 0x0
switch#

show ntp associations

The show ntp associations command displays the status of connections to NTP servers.

Command Mode

EXEC

Command Syntax

show ntp associations

Display Values

refid (reference ID): the reference ID of the configured NTP server’s time source. The reference ID is either the IPv4 address of the source or (if the source has an IPv6 address) the first four octets of the MD5 hash of the IPv6 address.
st (stratum): number of steps between the switch and the reference clock.
t (transmission type): u unicast; b broadcast; l local.
when: interval since reception of last packet (seconds unless unit is provided).
poll: interval between NTP poll packets. Maximum (1024) reached as server and client syncs.
reach: octal number that displays status of last eight NTP messages (377 - all messages received).
delay: round-trip delay of packets to the NTP server.
offset: difference between local clock and the server’s clock.
jitter: nominal offset estimation error.

Example

This command displays the status of the switch’s NTP associations.

switch> show ntp associations 
     remote          refid      st t when  poll reach   delay   offset  jitter 
==============================================================================
+l.ntp.arista.co 125.157.10.11   2 u  539  1024  377  121.748   -0.345   0.893
-3.ntp.arista.co 127.31.152.34   2 u  868  1024  377  101.671    2.434   1.529
+2.ntp.arista.co 176.131.12.185  2 u  676  1024  377  116.505     0.03   0.768
*4.ntp.arista.co 120.181.192.192 2 u  696  1024  377   48.431   -0.416    0.15
switch#

show ntp status

The show ntp status command displays the status of NTP on the switch. If the switch clock is not synchronized to an NTP server, the status reads “unsynchronised” and shows the server polling interval. If the clock is synchronized to an NTP server, the status shows the IP address and stratum of the server, the precision of the synchronization, and the polling interval.

Note: In EOS releases prior to 4.23.2, this command identified system peers with IPv6 addresses by their reference IDs (the first four octets of the MD5 hash of the IPv6 address). In later releases, this command always shows the IP address of the system peer (whether IPv4 or IPv6).

Command Mode

EXEC

Command Syntax

show ntp status

Example

This command displays the switch’s NTP status.

switch> show ntp status
synchronised to NTP server (192.168.78.62) at stratum 3
   time correct to within 66 ms
   polling server every 1024 s
switch>

¹ When logged into a fixed system or a supervisor on a modular system, this option has no effect.

² When logged into a fixed system, this option has no effect.

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)

The command-line interface (CLI) is one tool for controlling the switch and displaying information about its status and configuration. This chapter describes the use of the CLI.

This chapter includes these sections:

Accessing the EOS CLI
Processing Commands
Kernel-based Virtual Machine Commands and Configuration
Switch Platforms
Command Modes
Managing Switch Configuration Settings
Other Command-Line Interfaces
Directory Structure
Command-Line Interface Commands

Accessing the EOS CLI

You can open an EOS CLI session through these connections:

Ethernet management ports
console port
Telnet connections
Secure Shell (SSH)

The following figure displays the EOS CLI in a Secure Shell connection.

Processing Commands

Command Execution

Command keywords are not case-sensitive. The CLI also accepts truncated keywords that uniquely correspond to one command.

The command abbreviation con does not execute a command in Privileged EXEC mode because the names of two commands begin with these letters: configure and connect.
```
switch# con
% Ambiguous command
```
The command abbreviation conf executes configure in Privileged EXEC mode because no other command name begins with conf.
```
switch# conf
switch(config)#
```

Creating an Alias

The alias command creates an alias for a CLI command. Entering the alias in the CLI executes the corresponding command.

Example

This command makes srie an alias for the command show running-config interface ethernet 1-5.

switch(config)# alias srie show running-config interface ethernet 1-5
switch(config)# srie
interface Ethernet1
   switchport access vlan 33
   storm-control broadcast level 1
   spanning-tree portfast
   spanning-tree bpduguard enable
interface Ethernet2
   switchport access vlan 33
   spanning-tree portfast
interface Ethernet3
   switchport access vlan 33
   spanning-tree portfast
   spanning-tree bpduguard enable
interface Ethernet4
interface Ethernet5
   shutdown

Cursor Movement Keystrokes

EOS supports these cursor movement keystrokes:

Ctrl-B or the Left Arrow key: moves cursor to the left.
Ctrl-F or the Right Arrow key: moves cursor to the right.
Ctrl-A: moves cursor to beginning of line.
Ctrl-E: moves cursor to end of line.
Esc-B: moves cursor left one word.
Esc-F: moves cursor right one word.

History Substitution Keystrokes

The history buffer retains the last 20 commands entered. History substitution keystrokes that access previously entered commands include:

Ctrl-P or the Up Arrow key: Recalls the most recent buffered commands. Repeat to recall older commands.
Ctrl-N or the Down Arrow key: Recalls more recent commands after using the Ctrl-P or the Up Arrow. Repeat to recall newer commands.

The show history command in Privileged EXEC mode displays the history buffer contents.

switch# show history
  en
  config
  exit
  show history

Command Lists and Syntax Assistance

EOS CLI uses widely followed conventions for providing command lists and syntax assistance. These conventions are available in all command modes.

To display all commands available at this level, type a question mark (?):

switchName> ?
  clear       Reset functions
  connect     Open a terminal connection
  default     Set a command to its defaults
  disable     Turn off privileged commands
  enable      Turn on privileged commands
  exit        Exit from the EXEC
  logout      Exit from the EXEC
  no          Negate a command or set its defaults
  ping        Send echo messages
  show        Show running system information
  ssh         Open ssh connection
  tcpdump     Monitor packets with tcpdump
  telnet      Open a telnet connection
  terminal    Configure the terminal
  traceroute  Trace route to destination
  watch       Execute a command repeatedly
  who         Display information about terminal lines
  zerotouch   ZeroTouch configuration

To display a list of commands beginning with a specific character sequence, type the sequence followed by a question mark.
```
switch# di?
diff  dir  disable
```

To display a command’s keywords or arguments, type a question mark as an argument.

switch> ping ?
WORD  Ping destination address or hostname
ip    IPv4 echo
ipv6  IPv6 echo
mpls  Send echo messages for LSP
vrf   Ping in a VRF

The switch accepts an address-mask or CIDR notation (address-prefix) in commands that require an IP address and mask. For example, these commands are processed identically:
```
switch(config)# ip route 0.0.0.0 255.255.255.255 10.1.1.254
switch(config)# ip route 0.0.0.0/32 10.1.1.254
```
The switch accepts an address-wildcard or CIDR notation in commands requiring an IP address and wildcard. Wildcards use zeros to mask portions of the IP address and are found in some protocol configuration statements, including OSPF. The switch processes these commands identically:
```
switch(config-router-ospf)# network 10.255.255.1 0.0.0.255 area 15
switch(config-router-ospf)# network 10.255.255.1/24 area 15
```

Regular Expressions

A regular expression is a search pattern composed of symbols, letters and numbers. Some CLI parameters are defined as regular expressions for specifying more expressive search criteria. The switch uses regular expression pattern matching in several BGP commands.

The functionality of a regular expression for an AS-Path varies based on BGP regex asn and string mode configurations in the ip as-path regex-mode command.

The following tables describe the behavior of special characters in asn and string modes respectively.

Table 1. Functionality of Special Characters in ASN Mode
Special Characters	Characters Names	Description	Examples
.	Period	Matches any AS number.	‘.’ matches ‘200’. ‘10.20’ matches ‘10 30 20’, but does not match ‘10 20’.
^	Caret	Matches the specified expression at the beginning of an input string. Also used to exclude expressions in brackets while matching.	‘^123’ matches ‘123’, ‘123 456’, ‘123 456 789’, and so on; but does not match ‘1234’. ‘[^12]’ matches ‘1’, ‘2’, ‘3’, and so on; but does not match ‘12’.
*	Asterisk	Matches an entire AS number that appears either zero or more times.	‘200_100_300’ matches '200 300', ‘200 100 300’, ‘200 100 100 300’, and so on. '^100$' matches empty AS path, '100', '100 100', '100 100 100', and so on.
+	Plus sign	Matches an entire AS number appearing either one or more times.	‘10_20+_30’ matches ‘10 20 30’, ‘10 20 20 30’ and so on; but does not match ‘10 200 30’.
$	Dollar sign	Matches the specified expression at the end of an input string.	‘1_2_3$’ matches ‘1 2 3’, but does not match ‘1 2 3 4’.
[]	Brackets	Matches either an AS number, or a range of AS numbers separated by a hyphen.	‘[10_20_30-39]’ matches ‘10’, ‘20’, ‘30’, ‘31’,...’39’.
?	Question mark	Matches either zero or one occurrence of the pattern but the previous operand or entire AS number may appear zero or one time.	‘100_200?’ matches ‘100’ and ‘100 200’. ‘100_200?$’ does not match with ‘100 20’.
\|	Pipe	Matches the specified AS number on either side of the vertical bar.	‘6400\|6500’ matches either ‘6400’ or ‘6500’.
( )	Parenthesis	Nests specified AS numbers for matching.	‘^(100(200\|300))$’ matches either ‘100 200’ or ‘100 300’. ‘^100_200\|300_400$’ matches AS path either “100 200” or “300 400”.
_	Underscore	Matches specified AS numbers that are converted into AS number delimiters.	‘_123_456_’ matches ‘123 456’. ‘_333_444_’ matches ‘111 222 {333 444}’.

Note: Precede the question mark (?) with Ctrl+V sequence to prevent it from being interpreted as a help command.

Table 2. Functionality of Special Characters in String Mode
Special Characters	Characters Names	Description	Examples
.	Period	Matches any single character.	‘1.2’ matches ‘102’.
^	Caret	Matches the specified expression at the beginning of an input string.	‘^123’ matches ‘123’, ‘1234’, ‘12345’, and so on. It also matches ‘123 456’, ‘123 456 789’, and so on.
*	Asterisk	Matches either zero or more sequences of the expression preceding the asterisk.	'^5*$' matches an empty AS path, '5', '55', '555', and so on.
+	Plus sign	Matches either one or more sequences of the expression preceding the plus sign.	‘5+’ matches to ‘5’, ‘55’, ‘555’, and so on.
$	Dollar sign	Matches the expression at the end of an input string.	‘123$’ matches ‘123’, but does not match ‘1234’.
[]	Brackets	Matches either characters or a range of characters separated by a hyphen, within left and right brackets.	‘[025-7]’ matches ‘0’, ‘2’, and digits from ‘5’ to ‘7’; but does not match digits from ‘1’, ‘3’, ‘4’, ‘8’, and ‘9’.
?	Question mark	Matches either zero or one occurrence of the pattern.	'12?3' matches '13' and '123'.
\|	Pipe	Matches either one of the expressions or expression patterns on either side of the vertical bar.	‘14(36\|75)12’ matches either ‘143612’ or ‘147512’; but does not match ‘1412’, ‘14367512’, ‘14363612’ or ‘14757512’.
( )	Parenthesis	Nests specified expressions for matching.	‘(17)*’ matches any number of the two-character string ‘17’.
_	Underscore	For AS-Path regex, '_' matches curly brackets '{}', the beginning of input string, the end of input string, or space.	‘_1300_’ matches ‘100 {1300 1400}’, ‘100 1300 200’, and so on.
{}	Braces	Matches repetitions of the previous expression with the number of repetitions provided in braces.	'10{2,3}' matches '100' and '1000'.
\	Backslash	Matches the character following the backslash and special characters.	‘\(42’ matches ‘(42’.

Precede the question mark (?) with Ctrl+V sequence to prevent it from being interpreted as a help command.

Scheduling CLI Commands

The schedule command facilitates the periodic execution of the specified CLI command. Command parameters configure the time to start script execution, the interval between consecutive execution instances, the maximum time to execute the script, and the maximum number of files log that needs to be created.

The schedule config command sets configuration parameters to the CLI scheduler.

The show schedule command lists the commands currently scheduled for periodic execution and displays the summary of the specified scheduled command.

Examples

This command schedules the execution of a script once every 12 hours and the script execution is terminated if it exceeds 40 minutes. When max-log-files is set to zero, the script output is not logged.
```
switch# schedule ms_1 interval 720 timeout 40 max-log-files 0 command bash /mnt/flash/myscript.sh
```
This command saves the running configuration contents to a log file every hour, terminates the script execution if it exceeds 30 minutes and creates up to 24 log files.
```
 switch# schedule backup-test interval 60 max-log-files 24 command show running-config 
```
This command allows the switch to concurrently execute up to 2 scheduled commands.
```
switch(config)# schedule config max-concurrent-jobs 2
switch(config)#
```

This command lists the commands that are scheduled for periodic execution.

switch(config)# schedule config max-concurrent-jobs 3
switch(config)# show schedule summary
Maximum concurrent jobs  3
Prepend host name to logfile: No
Name            At time      Last    Interval   Timeout   Max     Logfile Location               Status
                             time     (mins)    (mins)    log
                                                         files
------------- ------------- ------- ---------- -------- -------- ------------------------------- ------
tech-support      now        00:29      60        30      100     flash:schedule/tech-support/   Success
thelp           12:02:00     00:02      60        40      100     flash:schedule/thelp/          Fail
                06/05/2018
switch(config)#

Running Bash Shell Commands Automatically with Event Handlers

Event handlers execute a Linux Bash shell command in response to a specific system event. An event handler consists of a Bash command, a trigger and a delay; when the trigger event occurs, the action is scheduled to run after delay seconds.

To create an event handler, use the event-handler command. This creates a new event handler and places the CLI in event handler configuration mode for that handler. Use the action bash command to configure a Bash command to run when the handler is triggered, and the trigger command to specify the trigger. Event handlers can be triggered by various events, including:

system booting
a change in a specified interface’s operational status or IP address
a change in the startup-config file
a state change in a virtual machine monitored by VM Tracer

To change the delay period between the trigger and the action, use the delay command.

When an action is run, certain information is passed to it through environment variables. For the boot trigger, no variables are set. For the interface triggers, the following variables are set and passed to the action:

$INTF interface name.
$OPERSTATE current operational status of the specified interface.
$IP-PRIMARY current primary IP address of the specified interface.

To execute more than one Bash command in response to a trigger, create a script containing the desired commands and enter the file path to the script as the argument of the action bash command.

To display information about all event handlers or about a specific event handler, use the show event-handler command.

The no event-handler command deletes an event handler.

Examples

These commands create an event handler named eth_4 which sends anemail to a specified address when there is a change in the operational status of Ethernet interface 4:

switch(config)# event-handler eth_4
switch(config-event-eth_4)# action bash email This email address is being protected from spambots. You need JavaScript enabled to view it. -s "Et4 $OPERSTATE"
switch(config-event-eth_4)# trigger on-intf ethernet 4 operstatus
switch(config-event-eth_4)# delay 60
switch(config-event-eth_4)# exit
switch(config)#

The above handler uses the $OPERSTATE variable to include the current operational state (“linkup” or “linkdown”) in the subject of the email. Note that the action will only function if email has been configured on the switch.

These commands create an event handler named onStartup which executes a user-defined script 60 seconds after the system boots.

switch(config)# event-handler onStartup
switch(config-event-onStartup)# action bash /mnt/flash/startupScript1
switch(config-event-onStartup)# trigger onboot
switch(config-event-onStartup)# delay 60
switch(config-event-onStartup)# exit
switch(config)#

The above handler will also be executed on exiting from event-handler configuration mode.

This command displays information about all event handlers configured on the system.

switch# show event-handler
Event-handler onStartup
Trigger: onBoot delay 60 seconds
Action: /mnt/flash/startupScript1
Last Trigger Activation Time: 1 minutes 51 seconds ago
Total Trigger Activations: 1
Last Action Time: 51 seconds ago
Total Actions: 1

switch#

This command deletes the event handler named onStartup.

switch(config)# no event-handler onStartup
switch(config)#

Running Adverse Drop Counters Monitor with Event Handlers

A monitoring capability for adverse drop counters can be used as a warning that the system is encountering an abnormal condition. The adverse drop counter monitor runs periodically (with a default of 60 seconds) and performs the following actions:

Reads the values of adverse drop counters.
Compares each value to the value read in the previous run.
If counter values increase more than a certain threshold (with a default of 100), it is considered as a threshold violation.
If any counter has more than a certain number of threshold violations within a specific time window (with a default of 3 violations within 15 minutes) a syslog message is logged.

No configuration is required to enable adverse drop counters monitor with event handlers. It is enabled by default and can be disabled, and can be customized for duration of time window and threshold levels. To customize the delay, polling interval, and condition for width, violation count, and threshold of this event handler, use the event-handler DropCountersHandler command. To display details of this event handler, use the show event-handler DropCountersHandler command.

Examples

These commands customize the delay, polling interval, and condition for width, violation count, and threshold of this event handler. Each parameter may be customized separately, with all other parameters remaining unchanged.

switch(config)# event-handler DropCountersHandler
switch(config-DropCountersHandler)# action bash DropCounterLog.py -l
switch(config-DropCountersHandler)# delay 0
switch(config-DropCountersHandler)# trigger on-counters
switch(config-DropCountersHandler-counters)# poll interval 60
switch(config-DropCountersHandler-counters)# condition 
bashCmd."DropCounterMonitor.py" -w 800" > 0
switch(config-DropCountersHandler-counters)# condition 
bashCmd."DropCounterMonitor.py" -c 5" > 0
switch(config-DropCountersHandler-counters)# condition 
bashCmd."DropCounterMonitor.py" -t 200" > 0
switch(config-DropCountersHandler-counters)#

This command disables this event handler.

switch(config)# no event-handler DropCountersHandler
switch(config)#

This command displays details of this event-handler.

switch(config)# show event-handler DropCountersHandler
Event-handler DropCountersHandler (BUILT-IN)
Trigger: on-counters delay 0 seconds
  Polling Interval: 60 seconds
  Condition: bashCmd."DropCounterMonitor.py" > 0
Threshold Time Window: 0 Seconds, Event Count: 1 times
Action: DropCounterLog.py -l
Action expected to finish in less than 20 seconds
Total Polls: 39
Last Trigger Detection Time: 38 minutes 22 seconds ago
Total Trigger Detections: 1
Last Trigger Activation Time: 38 minutes 22 seconds ago
Total Trigger Activations: 1
Last Action Time: Never
Total Actions: 1

switch(config)#

Kernel-based Virtual Machine Commands and Configuration

Arista’s EOS has leveraged its unmodified Linux kernel, and embraced open source standards-based technology that has brought operating system virtualization to Ethernet switching, utilizing the kernel-based virtual machine (KVM) as follows:

The hypervisor is the Linux kernel.
The core virtualization infrastructure is provided by the kernel module.
The CPU-specific implementation is provided by the processor-specific module (Intel or AMD).
The generic machine emulator and virtualizer KVM is provided by a Modified Quick Emulator (QEMU), which transforms the Linux kernel into the hypervisor.

The standard Linux kernel is the hypervisor, resulting in changes to the standard kernel (such as memory support and scheduler). Optimizations to these Linux components (such as a new scheduler in the 2.6 kernel) benefit both the hypervisor (host operating system) and Linux guest operating systems. With the kernel acting as the hypervisor, the switch can run other operating systems, such as Windows or Linux.

All components required are pre-installed with the Arista EOS software image, requiring only the download of the image. A few additional configuration steps get the KVM fully operational.

This chapter contains the following sections:

KVM Commands
KVM Configuration

KVM Commands

The following table covers KVM commands used throughout the configuration.

Table 3. KVM Commands
Command	Description
comment	Up to 240 character comment for this mode.
default	Set a command to its defaults.
disk-image	Add Virtual Machine disk image.
enable	Enable VM.
exit	Exit from Virtual Machine configuration mode.
memory-size	Set memory size.
no	Negate a command or set its defaults.
show	Show running system information.
virtual-nic	Add virtual NIC.
vnc-port	Set VNC server port.
! !	Append to comment.

CLI Commands

The following KVN CLI commands are used throughout the configuration.

vm

In config mode, the vm CLI command creates or deletes a KVM configuration, or enters config-vm mode. A newly created KVM will have an empty config file path and is disabled.

The CLI command syntax is as follows:

[no] vm NAME

config-file

In config-vm mode, the config-file CLI command sets the path of the libvirt config file, using standard file syntax (e.g. flash:vm/NetscalerVPX.xml or sata1:vm/NetscalerVPX.xml or /mnt/sata1/vm/NetscalerVPX.xml). Changing this value does not affect the state of a currently enabled KVM. To use the new file, the user must disable and then re-enable the KVM.

The CLI command syntax is as follows:

config-file [PATH]

enabled

In config-vm mode, the enabled CLI command allows enabling a currently disabled VM, causing it to start up immediately. If a VM is enabled in the startup-config, it starts up automatically when EOS boots (or when VirtAgent starts).

The CLI command syntax is as follows:

[no] enabled

Disabling a currently enabled VM initiates a shutdown process in the following sequence:

Attempt to shut down the VM politely if the guest OS supports ACPI.
If the VM is still running after 30 seconds, terminate it.

show vm

In enable mode, the show vm CLI command prints information about the configuration and status of a KVM, or of all KVMs if NAME is omitted, as follows:

Configuration: Name, config file path, and enabled.
Status: PID, log file path, and serial console pty path.
Current resource usage: RES, CPU%.
(Detailed only) contents of the log file.

(Detailed only) contents of the config file.

The CLI command syntax is as follows:

show vm [detailed] [NAME]

attach vm

In enable mode, the attach vm CLI command connects to a KVM's serial console pty (using virsh console).

Note: Press Ctrl-] to exit to the CLI.

The CLI command syntax is as follows:

attach vm [NAME]

show tech-support

The CLI command syntax is as follows:

show tech-support [detailed] [NAME]

reload

In enable mode, the reload CLI command is executed before restarting the system, and will shut down currently enabled KVMs using the same process as the no enabled command in config-vm mode.

The CLI command syntax is as follows:

reload

KVM Configuration

Arista EOS enables kernel-based virtual machine (KVM) instances by running KVM on the control-plane CPU of the switch. KVM instances can be defined from the CLI.

To configure a KVM, you must download the virtual machine image and configure the EOS.

This section contains the following topics:

Configuring a KVM
Configuring a Guest KVM

Configuring a KVM

To configure a KVM, perform the following steps:

Download the Virtual Machine Image to /mnt/flash
Name the virtual machine: switch(config)# virtual-machine [kvm_name]
Example:
```
switch(config)# virtual-machine foo 
```
Provide a pointer to the image: switch(config-vm-foo)# disk-image [file:[path] image-format [format]
Example:
```
switch(config-vm-foo)# disk-image file:/mnt/flash/fedora.img image-format qcow2
```
Define the amount of memory allocated: switch(config-vm-foo)#memory-size [size in bytes]
Bind the virtual NIC to an SVI (or management interface): switch(config-vm-foo)#virtual-nic 1 vlan [1-4] switch(config-vm-foo)# virtual-nic 1 management [1-4]
Create the VNC server’s tcp port (display): switch(config-vm-foo)# vnc-port [vnc-port number]
Enable the virtual machine: switch(config-vm-foo)# enable
Optionally attach to the virtual machine via VNC client pointed to the switch’s IP address. However, if Kernel hair-pinning is currently not enabled, preventing communication directly with the local switch, all traffic must have a destination on another networked device (such as a router, switch, or server).

For specifics about KVM visit http://www.linux-kvm.org/.

Note: In the Real VNC Viewer for Options, Expert, and ColorLevel, if the default value is pal8, establishing a session may fail. If this occurs, set this value to full and reconnect.

Example

switch# copy http://berrange.fedorapeople.org/images/2012-02-
29/f16-x86_64-openstack-sda.qcow2
(http://berrange.fedorapeople.org/images/2012-02-29/f16-x86_64-
openstack-sda.qcow2) flash:
...
switch(config)# virtual-machine foo
switch(config-vm-foo)# disk-image file:/mnt/flash/fedora.img image-format qcow2
switch(config-vm-foo)# memory-size 512
switch(config-vm-foo)# virtual-nic 1 vlan 1
switch(config-vm-foo)# virtual-nic 2 management 1
switch(config-vm-foo)# vnc-port 5900
switch(config-vm-foo)# enable

Configuring a Guest KVM

To configure a guest KVM, perform the following steps:

Download the Virtual Machine Image to /mnt/flash
Name the virtual machine: switch(config)# virtual-machine [guest_name]
Example
```
switch(config)# virtual-machine guest123
```

Provide a pointer to the image: switch(config-vm-guest123)# disk-image [file:[path] image-format [format]

Example

switch(config-vm-guest123)# disk-image flash:f16-x86_64-openstack-sda.qcow2 image-format ? 
iso iso image format   qcow qcow image format   qcow2 qcow2 image format   raw raw image format   
vmdk vmdk image format 
switch(config-vm-guest123)# disk-image 
flash:f16-x86_64-openstack-sda.qcow2 image-format qcow2

Define the amount of memory allocated: switch(config-vm-guest123)#memory-size [size in bytes]
Bind the virtual NIC to an SVI (or management interface): switch(config-vm-guest123)# virtual-nic 1 vlan [1-4] switch(config-vm-guest123)# virtual-nic 2 management [1-4]
Create the VNC server’s tcp port (display): switch(config-vm-guest123)# vnc-port [vnc-port number]

Enable the virtual machine: switch(config-vm-guest123)# enable

Example

switch# copy http://berrange.fedorapeople.org/images/2012-02-
29/f16-x86_64-openstack-sda.qcow2
(http://berrange.fedorapeople.org/images/2012-02-29/f16-x86_64-
openstack-sda.qcow2) flash:
...
switch# config terminal
switch(config)# virtual-machine ?
    WORD Virtual Machine name
switch(config)# virtual-machine foo
switch(config-vm-foo)# disk-image flash:f16-x86_64-openstack-sda.qcow2 image-format ?
    iso           iso image format
    qcow          qcow image format
    qcow2         qcow2 image format
    raw             raw image format
    vmdk          vmdk image format
switch(config-vm-foo)# disk-image flash:f16-x86_64-openstack-sda.qcow2 image-format qcow2
switch(config-vm-foo)# memory-size 1024
switch(config-vm-foo)# virtual-nic ?
    <1-4>         Virtual NIC Id
switch(config-vm-foo)# virtual-nic 1 ?
    Management    Management interface
    Vlan          Vlan interface
switch(config-vm-foo)# virtual-nic 1 vlan 1
switch(config-vm-foo)# virtual-nic 2 management 1
switch(config-vm-foo)# enable
switch(config-vm-foo)#
switch(config-vm-foo)# ^Z
switch# write mem
switch#
switch# show virtual-machine detail
Virtual Machine: foo
    Enabled:           Yes
    State:             Running
    Disk Image:        /mnt/flash/f16-x86_64-openstack-sda.qcow2
    Disk Image Format: qcow2
    Memory Size: 1024MB
    VNC port: 5900
    Virtual Nic: vnic1
        Mac Address:   52:54:00:ee:11:c9
        Device:        Vlan1
        Model Type:    e1000
    Virtual Nic:       vnic2
        Mac Address:   52:54:00:df:2a:e1
        Device:        Management1
        Model Type:    e1000
switch#

Switch Platforms

Features and CLI commands vary by switch platform. CLI options may also vary by switch platform for commands that are available on all platforms. Command descriptions in this manual describe feature availability and command parameters on the basis of switch platform, noting exceptions that exist among models that use a common platform.

https://www.arista.com/en/products/switches lists the Arista switches and platforms upon which they operate.
https://www.arista.com/en/support/product-documentation/supported-features lists Arista switch feature availability by switch platform. For the latest features, also consult the Release Notes, available at https://www.arista.com/en/support/software-download.

These sections describe the following topics:

Viewing the Model Number
Modular System Platforms – 7500 and 7500E Series Switches
Viewing Modules on 7300 Series Modular Switches
Multi-Chip Devices

Viewing the Model Number

To view the switch’s model number through the CLI, enter the show version command.

Example

This command displays the model number, serial number, system MAC address, and manufacturing information of a DCS-7150S-64 switch.

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

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

Uptime:                 16 hours and 39 minutes
Total memory:           4017088 kB
Free memory:            1348228 kB

switch>

Modular System Platforms – 7500 and 7500E Series Switches

Modular switch platforms depend on their installed modules along with the fabric and forwarding software modes. The show module command displays the fabric modules in the switch. System performance in switches containing both module types is based on first-generation fabric capabilities. Best practice is to avoid switch configurations with mixed fabric modules.

These sections describe modular switch components and software modes that program their capacities.

Fabric Modules and Fabric Mode – 7500 and 7500E Series Switches

Each modular switch fabric module is categorized as first-generation or E-Series:

First-generation fabric modules support all basic switch functions.
E-Series fabric modules support faster fabric link speeds, greater internal table capacities, and advanced encoding formatting.

Fabric mode determines the switch’s fabric performance capabilities. This mode must match the fabric modules in the switch. Fabric mode settings include:

fe600: Supports first-generation fabric modules.
fe1600: Supports E-Series fabric modules.

E-series fabric modules can operate in fe600 mode, but are limited to first-generation fabric performance. First-generation modules cannot operate in fe1600 mode. Switches containing both types of modules must be set to fe600 mode. Best practice is to avoid switch configurations with mixed fabric modules.

When a switch reloads, fabric mode is determined by the following (in order of precedence):

Switches reloading in petraA forwarding compatibility mode( Linecard Modules and Forwarding Compatibility Mode – 7500 and 7500E Series)also reload in fe600 fabric mode.
As specified by the platform sand fabric mode (7500 and 7500E Series) statement in running-config.
The first fabric module that becomes operational as the switch reloads.

In switches with a homogeneous module set, the fabric mode matches its fabric modules. Switches with a mixed set of modules are typically reloaded in fe600 mode because first generation modules are usually operational before E-Series modules. However, the fabric mode in mixed module switches that are reloading cannot be guaranteed in the absence of the first two conditions.

Example

This command configures the switch to reload in fe1600 fabric mode to support E-series fabric modules. After issuing this command, the switch should be reset only after exchanging all switch fabric modules to E-series modules.

switch(config)# platform sand fabric mode fe1600
switch(config)# exit
switch# show platform sand compatibility
                     Configuration        Status
Forwarding mode      None                 Arad
Fabric mode          Fe1600               Fe600
switch#

Determining a Switch’s Operating Platform

FM6000 Platforms

To determine the operating platform on switch, display platform command options from Global Configuration command mode.

This command displays the operating platform of a switch operating on the FM6000 platform (7150 Series switches).

switch(config)# platform ?
  fm6000  FM6000 chip

switch(config)#platform

Arad and Petra Platforms

The platform ? command displays the same options on Arad and Petra platform switches. Refer to Viewing the Model Number to determine the switch’s model number.

Fixed system switches (DCS-7048 Series) operate on the Petra platform.
Modular switches (DCS-7500 Series) operate on Arad and Petra platforms. Modular System Platforms – 7500 and 7500E Series Switches describe platform usage on these switches.

Arad and Petra platform switch typically utilize multiple chips.Multi-Chip Devices describe methods of determining the port distribution on multi-chip platforms.

Example

These commands display platform options of a switch operating on either Petra or Arad platforms.

switch(config)# platform ?
  arad    Arad switch chip
  fe1600  Fe1600 chip
  fe600   Fe600 fabric chip
  petraA  PetraA switch chip
  ptp     Precision Time Protocol
  sand    Sand platform

switch(config)#platform

Trident and Trident II Platforms

The platform ? command returns trident on switches that operate on Trident or Trident II platforms. Trident II platform switches include options that configure the forwarding and routing tables. To determine the Trident platform that a switch uses, display platform trident options.

These commands indicate that the switch is operating on the Trident II platform:

switch(config)# platform ?
  ptp      Precision Time Protocol
  trident  Trident chip

switch(config)# platform trident ?
  fabric            Fabric configuration
  forwarding-table  Forwarding table configuration
  mmu               Trident MMU configuration
  routing-table     Routing table configuration

switch(config)#platform trident

Fixed and Modular switches are available that operate on the Trident II platform. Refer to Viewing the Model Number to determine the switch’s model number. Viewing Modules on 7300 Series Modular Switches displays the modules on a Trident II platform modular switch.

Trident II platform switches typically utilize multiple chips. Multi-Chip Devices describes methods of determining port distribution on multi-chip platforms.

Linecard Modules and Forwarding Compatibility Mode – 7500 and 7500E Series

Each modular switch linecard module is categorized as first-generation or E-Series:

First-generation linecard modules support all basic switch functions.
E-Series linecard modules support provide faster data processing, greater internal table capacities, and advanced encoding formatting.

The forwarding compatibility mode determines the switch’s performance capabilities when forwarding data between linecard interfaces. Forwarding compatibility mode settings include:

PetraA: Supports first-generation linecard modules.
Arad: Supports E-Series linecard modules.

Forwarding compatibility mode determines the operational capacity of installed linecards. The following table lists the affect of the forwarding compatibility mode on linecard module types.

Table 4. Linecard Module and Forwarding Mode Performance
Linecard Module Type	Forwarding Compatibility Mode	Linecard Operating Capacity
First-generation	petraA	First-generation performance capacity.
First-generation	arad	Linecard is powered-down.
E-Series	petraA	First-generation performance capacity.
E-Series	arad	E-series performance capacity.

Note: Switches must contain E-Series fabric modules to operate at E-Series performance capacities.

The forwarding compatibility mode is configured by the platform sand forwarding mode (7500 and 7500E Series) command. This command may be required after exchanging a linecard for a different module type or in switches containing first-generation and E-series linecards.

Without a platform sand forwarding mode (7500 and 7500E Series) command, forwarding compatibility mode is determined by the first linecard that is operational after reloading the switch. In a switch that is reloaded with a homogeneous module set, forwarding compatibility mode matches its linecards. Switches with a mixed set of modules are typically reloaded in petraA mode because first generation modules are usually operational before E-Series modules. However, forwarding compatibility mode in mixed module switches that are reloading is not guaranteed without a platform sand forwarding mode command.

Example

This command changes the forwarding software mode to support E-series linecard modules. This command should be run only after exchanging all linecards to E-series modules.

switch(config)# platform sand forwarding mode arad
switch(config)#

Viewing Modules – 7500 and 7500E Series

The show module command displays the model number of all installed modules.

This command displays the modules of a 7504 switch that contains first-generation modules.

switch> show module
Module    Ports Card Type                            Model           Serial No.
--------- ----- ------------------------------------ --------------- -----------
1         2     DCS-7500 Series Supervisor Module    7500-SUP        JSH11440327
2         1     Standby supervisor                   Unknown         Unknown
3         48    48-port SFP+ 10GigE Linecard         7548S-LC        JSH10449938
4         48    48-port SFP+ 10GigE Linecard         7548S-LC        JSH11091247
5         48    48-port SFP+ 10GigE Linecard         7548S-LC        JSH11211614
6         48    48-port SFP+ 10GigE Linecard         7548S-LC        JSH11520288
Fabric1   0     DCS-7504 Fabric Module               7504-FM         JSH11451230
Fabric2   0     DCS-7504 Fabric Module               7504-FM         JSH11451210
Fabric3   0     DCS-7504 Fabric Module               7504-FM         JSH11410115
Fabric4   0     DCS-7504 Fabric Module               7504-FM         JSH11380318
Fabric5   0     DCS-7504 Fabric Module               7504-FM         JSH11340955
Fabric6   0     DCS-7504 Fabric Module               7504-FM         JSH11410128

Module    MAC addresses                          Hw      Sw      Status
--------- -------------------------------------- ------- ------- -------
1         00:1c:73:03:06:ac - 00:1c:73:03:06:ac  07.06   4.12.1  Active
2                                                        4.12.1  Standby
3         00:1c:73:03:80:44 - 00:1c:73:03:80:73  06.00           Ok
4         00:1c:73:03:e4:34 - 00:1c:73:03:e4:63  07.10           Ok
5         00:1c:73:12:0b:3f - 00:1c:73:12:0b:6e  07.30           Ok
6         00:1c:73:12:b6:3f - 00:1c:73:12:b6:6e  08.00           Ok
Fabric1                                          05.03           Ok
Fabric2                                          05.03           Ok
Fabric3                                          05.02           Ok
Fabric4                                          05.02           Ok
Fabric5                                          05.02           Ok
Fabric6                                          05.02           Ok
switch>

This command displays modules of a 7504 switch that contains E-Series modules.

switch> show module
Module    Ports Card Type                            Model           Serial No.
--------- ----- ------------------------------------ --------------- -----------
1         3     DCS-7500E-SUP Supervisor Module      7500E-SUP       JAS13060306
3         72    48 port 10GbE SFP+ & 2x100G Linecard 7500E-72S-LC    JAS12410019
4         72    48 port 10GbE SFP+ & 2x100G Linecard 7500E-72S-LC    JPE13041458
5         72    48 port 10GbE SFP+ & 2x100G Linecard 7500S-72S-LC    JAS12380089
Fabric1   0     DCS-7504-E Fabric Module             7504E-FM        JAS12370008
Fabric2   0     DCS-7504-E Fabric Module             7504E-FM        JAS12380012
Fabric3   0     DCS-7504-E Fabric Module             7504E-FM        JAS12370014
Fabric4   0     DCS-7504-E Fabric Module             7504E-FM        JAS12380008
Fabric5   0     DCS-7504-E Fabric Module             7504E-FM        JAS12380017
Fabric6   0     DCS-7504-E Fabric Module             7504E-FM        JAS12370009

Module    MAC addresses                          Hw      Sw      Status
--------- -------------------------------------- ------- ------- -------
1         00:1c:73:00:f4:cd - 00:1c:73:00:f4:ce  00.00   4.12.3  Active
3         00:1c:73:00:9c:7b - 00:1c:73:00:9c:c2  00.00           Ok
4         00:1c:73:28:a0:57 - 00:1c:73:28:a0:9e  00.00           Ok
5         00:1c:73:00:9a:cb - 00:1c:73:00:9b:12  02.07           Ok
Fabric1                                          00.00           Ok
Fabric2                                          00.00           Ok
Fabric3                                          00.00           Ok
Fabric4                                          00.00           Ok
Fabric5                                          00.00           Ok
Fabric6                                          00.00           Ok
switch>

Viewing Modules on 7300 Series Modular Switches

7300 Series Modular switches operate on Trident II platform. The show module command displays the model number of all installed modules.

switch> show module
Module    Ports Card Type                            Model           Serial No.
--------- ----- ------------------------------------ --------------- -----------
1         3     Supervisor 7300X SSD                 DCS-7300-SUP-D  JAS13340024
3         128   32 port 40GbE QSFP+ LC               7300X-32Q-LC    JPE13440416
4         64    48 port 10GbE SFP+ & 4 port QSFP+ LC 7300X-64S-LC    JAS13310113
5         64    48 port 10GbE SFP+ & 4 port QSFP+ LC 7300X-64S-LC    JAS13340033
6         64    48 port 10GbE SFP+ & 4 port QSFP+ LC 7300X-64S-LC    JAS13310103
Fabric1   0     7304X Fabric Module                  7304X-FM        JAS13320077
Fabric2   0     7304X Fabric Module                  7304X-FM        JAS13350043
Fabric3   0     7304X Fabric Module                  7304X-FM        JAS13350050
Fabric4   0     7304X Fabric Module                  7304X-FM        JAS13350056

Module    MAC addresses                          Hw      Sw      Status
--------- -------------------------------------- ------- ------- -------
1         00:1c:73:36:4b:71 - 00:1c:73:36:4b:72  01.01   4.13.3F Active
3         00:1c:73:58:d4:68 - 00:1c:73:58:d4:87  03.04           Ok
4         00:1c:73:36:05:61 - 00:1c:73:36:05:94  02.02           Ok
5         00:1c:73:36:0a:e1 - 00:1c:73:36:0b:14  02.03           Ok
6         00:1c:73:36:02:e1 - 00:1c:73:36:03:14  02.02           Ok
Fabric1                                          00.00           Ok
Fabric2                                          00.00           Ok
Fabric3                                          00.00           Ok
Fabric4                                          00.00           Ok
switch>

Multi-Chip Devices

Trident II, Petra, and Arad platform switches and linecards utilize multiple chips, with Ethernet ports evenly distributed among the chips. Creating multi-port data structures (including port channels) that include ports from multiple chips protects against the failure of an individual chip on a device.

The following sections describe methods of determining port distribution on various switch platforms

Petra Fixed Switches

7048-Series switches are Petra platform devices that distribute ports among two PetraA chips. The show platform petraA port-info routing command displays the ports that are controlled by each chip.

Example

This command displays the following Ethernet port distribution on a DCS-7048-T switch:

Petra0 chip controls Ethernet 1 through Ethernet 32.

Petra1 chip controls Ethernet 33 through Ethernt 52.

switch# show platform petraA port-info routing
Petra0 Port Routing Information:
========================================================================
                         sys     fap                       routing
 intfName              port-id port-id intfType  portType   v4 v6
========================================================================
 CpuTm                     2       0    Cpu       Tm          1  1
 
 Ethernet1                29       2    Nif       Ethernet    1  1
 Ethernet2                30       3    Nif       Ethernet    1  1

 Ethernet31               59      32    Nif       Ethernet    1  1
 Ethernet32               60      33    Nif       Ethernet    1  1

 RawPetra0/70            2118      70    Recycling Raw         1  1
Petra1 Port Routing Information:
========================================================================
                         sys     fap                       routing
 intfName              port-id port-id intfType  portType   v4 v6
========================================================================
 CpuTm                     2       0    Cpu       Tm          1  1

 Ethernet33               66       2    Nif       Ethernet    1  1

 Ethernet52               85      21    Nif       Ethernet    1  1
 L3SecondHop1Petra1       86      22    Recycling Ethernet    1  1

 RawPetra1/70            2118      70    Recycling Raw         1  1
switch#

Petra Modular Switches

Linecards on 7500-Series modular switches distribute Ethernet ports among multiple petraA chips. The show platform petraA port-info routing command displays the ports that are controlled by each chip on all PetraA linecards or on a single linecard.

Example

This command displays the following Ethernet port distribution on linecard 4 of a DCS-7504 switch:

Petra4/0 chip controls Ethernet 4/1 through Ethernet 4/8.
Petra4/1 chip controls Ethernet 4/9 through Ethernet 4/16.
Petra4/2 chip controls Ethernet 4/17 through Ethernet 4/24.
Petra4/3 chip controls Ethernet 4/25 through Ethernet 4/32.
Petra4/4 chip controls Ethernet 4/33 through Ethernet 4/40.

Petra4/5 chip controls Ethernet 4/41 through Ethernet 4/48.

switch(s1)# show platform petra module 4 port-info routing
Petra4/0 Port Routing Information:
========================================================================
                         sys     fap                       routing
 intfName              port-id port-id intfType  portType   v4 v6
========================================================================
 CpuTm                     2       0    Cpu       Tm          1  0

 Ethernet4/1             221       2    Nif       Ethernet    1  0
 Ethernet4/2             222       3    Nif       Ethernet    1  0
 Ethernet4/3             223       4    Nif       Ethernet    1  0
 Ethernet4/4             224       5    Nif       Ethernet    1  0
 Ethernet4/5             225       6    Nif       Ethernet    1  0
 Ethernet4/6             226       7    Nif       Ethernet    1  0
 Ethernet4/7             227       8    Nif       Ethernet    1  0
 Ethernet4/8             228       9    Nif       Ethernet    1  0

 RawPetra4/0/70          2118      70    Recycling Raw         1  0
Petra4/1 Port Routing Information:
========================================================================
                         sys     fap                       routing
 intfName              port-id port-id intfType  portType   v4 v6
========================================================================
 CpuTm                     2       0    Cpu       Tm          1  0

 Ethernet4/9             253       2    Nif       Ethernet    1  0

Petra4/5 Port Routing Information:
========================================================================
                         sys     fap                       routing
 intfName              port-id port-id intfType  portType   v4 v6
========================================================================

 Ethernet4/41            381       2    Nif       Ethernet    1  0
 Ethernet4/42            382       3    Nif       Ethernet    1  0
 Ethernet4/43            383       4    Nif       Ethernet    1  0
 Ethernet4/44            384       5    Nif       Ethernet    1  0
 Ethernet4/45            385       6    Nif       Ethernet    1  0
 Ethernet4/46            386       7    Nif       Ethernet    1  0
 Ethernet4/47            387       8    Nif       Ethernet    1  0
 Ethernet4/48            388       9    Nif       Ethernet    1  0

switch(s1)#

Arad Modular Switches

7500-E Series linecards distribute Ethernet ports among multiple Arad chips. The show platform arad port-info routing command displays the ports that are controlled by each chip on all Arad linecards.

Example

This command displays the following Ethernet port distribution on the 7500E-72S-LC linecard that is inserted as module 3 in a DCS-7508E switch:

Arad3/0 chip: Ethernet 3/1– Ethernet 3/20.
Arad3/1 chip: Ethernet 3/21 – Ethernet 3/34 and Ethernet 3/49/1 – Ethernet 3/49/12.

Arad3/2 chip: Ethernet 3/35 – Ethernet 3/48 and Ethernet 3/50/1 – Ethernet 3/50/12.

switch# show platform arad mapping

Arad3/0            Port                        SysPhyPort Voq  (Fap,FapPort)   
Xlge  Serdes
----------------------------------------------------------------------------------------
                   CpuTm                              2    32    (0  ,  0)     n/a   n/a

                   Ethernet3/1                       28   240    (0  ,  2)     n/a   (16)
                   Ethernet3/2                       29   248    (0  ,  3)     n/a   (17)
                   Ethernet3/3                       30   256    (0  ,  4)     n/a   (18)
                   Ethernet3/4                       31   264    (0  ,  5)     n/a   (19)
                   Ethernet3/5                       32   272    (0  ,  6)     n/a   (20)
                   Ethernet3/6                       33   280    (0  ,  7)     n/a   (21)
                   Ethernet3/7                       34   288    (0  ,  8)     n/a   (22)
                   Ethernet3/8                       35   296    (0  ,  9)     n/a   (23)
                   Ethernet3/9                       36   304    (0  , 10)     n/a   (24)
                   Ethernet3/10                      37   312    (0  , 11)     n/a   (25)
                   Ethernet3/11                      38   320    (0  , 12)     n/a   (26)
                   Ethernet3/12                      39   328    (0  , 13)     n/a   (27)
                   Ethernet3/13                      40   336    (0  , 14)     n/a   (4)
                   Ethernet3/14                      41   344    (0  , 15)     n/a   (5)
                   Ethernet3/15                      42   352    (0  , 16)     n/a   (6)
                   Ethernet3/16                      43   360    (0  , 17)     n/a   (7)
                   Ethernet3/17                      44   368    (0  , 18)     n/a   (0)
                   Ethernet3/18                      45   376    (0  , 19)     n/a   (1)
                   Ethernet3/19                      46   384    (0  , 20)     n/a   (2)
                   Ethernet3/20                      47   392    (0  , 21)     n/a   (3)
 
                   RawArad3/0/56                   2104 16848    (0  , 56)     n/a   n/a

Arad3/1            Port                        SysPhyPort Voq  (Fap,FapPort)   
Xlge  Serdes
-------------------------------------------------------------------------------

                   Ethernet3/21                      60   496    (1  ,  2)     n/a   (16)

                   Ethernet3/34                      73   600    (1  , 15)     n/a   (13)
                   Ethernet3/49/1                    74   608    (1  , 16)     n/a   (0)
 
                   Ethernet3/49/12                   85   696    (1  , 27)     n/a   (11)
 

Arad3/2            Port                        SysPhyPort Voq  (Fap,FapPort)   
Xlge  Serdes
-------------------------------------------------------------------------------

                   Ethernet3/35                      92   752    (2  ,  2)     n/a   (16)

                   Ethernet3/48                     105   856    (2  , 15)     n/a   (13)
                   Ethernet3/50/1                   106   864    (2  , 16)     n/a   (0)

                   Ethernet3/50/12                  117   952    (2  , 27)     n/a   (11)

switch#

Trident II Fixed Switches

Trident II platform devices distribute their ports among multiple Trident II chips. The show platform trident system port command displays the ports that are controlled by each chip.

Example

This command displays the following Ethernet port distribution on a DCS-7250QX-64-F switch:

Trident 0 chip controls Ethernet 1/1 through Ethernet 16/4.
Trident 1 chip controls Ethernet 17/1 through Ethernet 32/4.
Trident 2 chip controls Ethernet 33/1 through Ethernet 48/4.

Trident 3 chip controls Ethernet 49/1 through Ethernet 64/4.

switch# show platform trident system port

                                                                  Port
      Intf              Chip            ModId       Logical       Physical   MMU
--------------------- ----------------- ----------- ------------- ---------- ---
      Ethernet1/1       Linecard0/0      1           1             17         9
      Ethernet1/2       Linecard0/0      1           2             18         10

      Ethernet16/3      Linecard0/0      1           60            107        98
      Ethernet16/4      Linecard0/0      1           61            108        99

      Ethernet64/2      Linecard0/3      4           62            106        97
      Ethernet64/3      Linecard0/3      4           63            107        98
      Ethernet64/4      Linecard0/3      4           64            108        99

--------------------------------------------------------------------------------
switch#

Trident II Modular Switches

Linecards on 7300-Series modular switches distribute Ethernet ports among multiple Trident II chips. The show platform trident system port command can display the ports that are controlled by each chip on all linecards or on a single chip.

This command displays the following Ethernet port distribution on DCS-7304-F switch that contains a 7300X-32Q-LC linecard as module 3:

Trident 0 chip controls Ethernet 1/1 through Ethernet 16/4 (on module 3).

Trident 1 chip controls Ethernet 17/1 through Ethernet 32/4 (on module 3).

switch# show platform trident system port

------------------------------------------------------------------------------------
                                                                  Port
     Intf              Chip             ModId       Logical       Physical       MMU
--------------------- ----------------- ----------- ------------- -------------  ---
    Ethernet3/1/1      Linecard3/0       5           1             17            4
    Ethernet3/2/1      Linecard3/0       5           2             21            5

    Ethernet3/16/3     Linecard3/0       5           51            111           102
    Ethernet3/16/4     Linecard3/0       5           52            112           103

    Ethernet3/32/3     Linecard3/1       6           63            111           102
    Ethernet3/32/4     Linecard3/1       6           64            112           103

-------------------------------------------------------------------------------------

switch#

Command Modes

Command modes define the user interface state. Each mode is associated with commands that perform a specific set of network configuration and monitoring tasks.

Mode Types lists the available modes.
Navigating Through Command Modes lists mode entry and exit commands.
Command Mode Hierarchy describes the mode structure.
Group-Change Configuration Modes describes editing aspects of these modes.

Mode Types

The switch includes these command modes:

EXEC: EXEC mode commands display system information, perform basic tests, connect to remote devices, and change terminal settings. When logging into EOS, you enter EXEC mode.
EXEC mode prompt: switch>
Privileged EXEC: Privileged EXEC mode commands configure operating and global parameters. The list of Privileged EXEC commands is a superset of the EXEC command set. You can configure EOS to require password access to enter Privileged EXEC from EXEC mode.
Privileged EXEC mode prompt: switch#
Global Configuration: Global Configuration mode commands configure features that affect the entire system, such as system time or the switch name.
Global Configuration mode prompt: switch(config)#
Interface Configuration: Interface configuration mode commands configure or enable Ethernet, VLAN, and Port-Channel interface features.
Interface Configuration mode prompt: switch(config-if-Et24)#
Protocol specific mode: Protocol specific mode commands modify global protocol settings. Protocol specific mode examples include ACL Configuration and Router BGP Configuration.
The prompt indicates the active command mode. For example, the Router BGP command prompt is switch(config-router-bgp)#

Navigating Through Command Modes

To change the active command mode, perform one of these actions:

To enter EXEC mode, log into the switch.
To enter Privileged EXEC mode from EXEC, type enable (or en) followed, if prompted, by the enable password:
```
switch> en
Password:
switch#
```
To enter Global Configuration mode from Privileged EXEC, type configure (or config):
```
switch# config
switch(config)#
```
To enter Interface Configuration mode from Global Configuration, type interface and the name of the interface to be modified:
```
switch(config)# interface Et24
switch(config-if-Et24)#
```
To enter a protocol specific configuration mode from Global Configuration, type the required command for the desired mode.
```
switch(config)# router bgp 100
switch(config-router-bgp)#
```
To return one level from any configuration mode, type exit.
```
switch(config)# exit
switch#
```
To return to Privileged EXEC mode from any configuration mode, type end or Ctrl-Z.
```
switch(config-if-Et24)# <Ctrl-z>
switch#
```
To return to EXEC mode from Privileged EXEC mode, type disable (or dis).
```
switch# dis
switch>
```
To exit EOS and log out of the CLI, type exit from EXEC mode or Privileged EXEC mode.
```
switch# exit

login:
```

Command Mode Hierarchy

Command modes are hierarchical. The parent mode of a specified command mode is the mode that contains the command that enters the specified mode.

Example

EXEC mode contains the enable command, which enters Privileged EXEC mode. Therefore, EXEC is the parent mode of Privileged EXEC.

Commands that are executable in a specified command mode include all commands available in the specified mode plus all commands executable from its parent mode.

Example

EXEC mode includes the ping command. EXEC mode is the parent mode of Privileged EXEC mode. Therefore, Privileged EXEC mode includes ping.

Additionally, Privileged EXEC is the parent mode of Global Configuration mode. Therefore, Global Configuration mode also includes ping.

Executing a configuration mode command from a child mode may change the active command mode.

Example

Global Configuration mode contains interface ethernet and ip access-list commands, which enter Interface Configuration and Access Control List (ACL) Configuration modes, respectively. When the switch is in Interface Configuration mode, the ip access-list command is available and changes the active mode to ACL Configuration.

switch(config)# interface ethernet 1
switch(config-if-Et1)# ip access-list master-list
switch(config-acl-master-list)#

The exit command changes the active command mode to its parent mode. When executed from Privileged EXEC or EXEC modes, the exit command terminates the session.

Example

This command exits Global Configuration mode to Privileged EXEC mode.
```
switch(config)#exit
switch#
```
This command terminates the user session.
```
switch# exit
```

Group-Change Configuration Modes

Group-change modes apply all changes made during an edit session only after exiting the mode. Changes are stored when the user exits the mode, either through an exit or end command or through a command that enters a different configuration mode.

The abort command discards all changes not previously applied.

Access Control List (ACL) and Multiple Spanning Tree (MST) configuration modes are examples of group-change modes.

Managing Switch Configuration Settings

Verifying Settings for the Current Mode

To display only the lines of running-config that affect the current mode, use the active option of the show (various configuration modes) command. This command option is available in all configuration modes except global configuration.

Example

Type show active to display the content of running-config that affects the current mode. To include default settings in the display, type show active all.

switch(config-router-ospf3)# show active all
ipv6 router ospf 9
   router-id 0.0.0.0
   default-metric 10
   distance ospf intra-area 10
   area 0.0.0.200 default-cost 10
   area 0.0.0.200
   no log-adjacency-changes
   timers spf 5
switch(config-router-ospf3)#

To display any comments associated with the current mode, use the comment option of the show (various configuration modes) command.

Example

Type show comment to display any comments attached to the current mode.

switch(config-router-ospf3)# show comment
Comment for router-ospf3:
    Consult Thomas Morton before making changes to the OSPF configuration.
switch(config-router-ospf3)#

Verifying the Running Configuration Settings

The running-config command is the virtual file that stores the operating configuration. The show running-config command displays the running-config. The command is supported in Privileged EXEC mode.

Example

Type show running-config in Privileged EXEC mode. The response in the example is truncated to display only the ip route configured.

switch# show running-config 
! Command: show running-config

!
ip route 0.0.0.0/0 192.0.2.1
!

end
switch#

Adding a Comment to a Configuration Mode

To add a comment to most switch configuration modes, use the comment (various configuration modes) command. Comments cannot be modified, but can be replaced by entering the comment command again and entering new text. Comments cannot be added to global configuration mode

To append to an existing comment, enter !! followed by additional comment text. To display comments for the active mode, use the show comment command. The no comment and default comment commands remove the comment from running-config.

Examples

These commands enter a comment in Router OSPF3 Mode.

switch(config-router-ospf3)# comment
Enter TEXT message. Type 'EOF' on its own line to end.
Consult Thomas Morton before making changes to the OSPF configuration.
EOF
switch(config-router-ospf3)#

These commands append additional information to the comment entered above.

switch(config-router-ospf3)# !! x2735
switch(config-router-ospf3)# show comment
Comment for router-ospf3:
    Consult Thomas Morton before making changes to the OSPF configuration.
    x2735
switch(config-router-ospf3)#

Saving the Running Configuration Settings

startup-config is the file, stored in internal flash memory, that the switch loads when it boots. Configuration changes that are not saved to startup-config are lost the next time the switch is booted.

The write and copy running-config startup-config commands store the operating configuration to startup-config.Both commands are supported in Privileged EXEC mode.

Example

These equivalent commands save the current operating configure to the startup-config file.

switch# write  

switch# copy running-config startup-config

The show startup-config command displays the startup configuration file. The command is supported in Privileged EXEC mode.

Example

Type show startup-config to display the startup configuration file. The response in the example is truncated to display only the ip route configured in Admin Username.

switch# show startup-config
! Command: show startup-config
! Startup-config last modified at  Wed Feb 19 08:34:31 2014 by admin
!

!
ip route 0.0.0.0/0 192.0.2.1
!

end
switch#

Other Command-Line Interfaces

EOS can access other CLIs that provide switch commands, files, and services.

Aboot Command-Line Interface describes the boot-loader CLI.
Bash Shell describes the Bash shell CLI.

Aboot Command-Line Interface

Aboot is the switch boot loader. It reads a configuration file from the internal flash or a USB flash drive and attempts to boot a software image.

The switch opens an Aboot shell if the switch does not find a software image, the configuration is corrupted, or the user terminates the boot process. The Aboot shell provides a CLI for manually booting a software image, recovering the internal flash to its default factory state, running hardware diagnostics, and managing files.

Bash Shell

The switch provides a Linux Bash shell for accessing the underlying Linux operating system and extensions. The Bash shell is accessible in all command modes except EXEC. Mode Types describes EOC command modes.

To enter the Bash, type bash at the prompt.

switch# bash

Arista Networks EOS shell

[admin@Switch ~]$

To exit the Bash, type logout, exit, or Ctrl-D at the Bash prompt.
```
[admin@Switch ~]$ logout
switch#
```

Directory Structure

EOS operates from a flash drive root mounted as the /mnt/flash directory on the switch. The EOS CLI supports these file and directory commands:

delete: Delete a file or directory tree.
copy: Copy a file.
more: Display the file contents.
diff: Compares the contents of files located at specified URLs.
rename: Rename a file.
cd: Change the current working directory.
dir: Lists directory contents, including files and subdirectories.
mkdir: Create a directory.
rmdir: Remove a directory.
pwd: Display the current working directory.

Verify flash memory space before copying a file. When a file is copied to flash, it is first written to a temporary file and then renamed to the destination rather than directly overwriting the destination file. This protects the integrity of the existing file if the copy command is interrupted, but requires more free space to complete the process.

Switch directory files are accessible through the Bash shell and Aboot. When entering the Bash shell from the switch, the working directory is located in /home and has the name of the user name from which Bash was entered.

Example

These commands were entered from the user name john:

switch# bash
[john@switch ~]$ pwd
/home/john
[john@switch ~]$

In this instance, the working directory is /home/john.

When a flash drive is inserted in the USB flash port, flash drive contents are accessible through /mnt/usb1.

When entering Aboot, the working directory is the root directory of the boot.

Command-Line Interface Commands

action bash

The action bash command specifies a Bash shell command to be run when an event handler is triggered. When an event handler is triggered, execution of the associated shell command is delayed by a configurable period set by the delay command. Only a single Bash command may be configured for an event handler, but the command may have multiple arguments. If more than one Bash command must be executed in response to a trigger, create a script containing the desired commands and enter the file path to the script as the argument of the action bash command.

To specify the event that will trigger the action, use the trigger command.

If the event handler uses an on-intf trigger, the following environment variables are passed to the action and can be used as arguments to the Bash command:

$INTF interface name.
$OPERSTATE current operational status of the specified interface.
$IP-PRIMARY current primary IP address of the specified interface.

Command Mode

Event-Handler Configuration

Command Syntax

action bash command

Parameters

command Bash shell command to be executed when the event handler is triggered.

Examples

This command configures the event handler “onStartup” to run a script on the flash drive.

switch(config-handler-onStartup)# action bash /mnt/flash/myScript1
switch(config-handler-onStartup)#

This command configures the event handler “eth_4” to send email to the specified address when there is a change in the operational status of Ethernet interface 4.

switch(config-event-eth_4)# action bash email This email address is being protected from spambots. You need JavaScript enabled to view it. -s "Et4 $OPERSTATE"
switch(config-event-eth_4)#

The above action uses the $OPERSTATE variable to include the current operational state (“linkup” or “linkdown”) in the subject of the email. Note that the action will only function if email has been configured on the switch.

alias

The alias command creates an alias for a CLI command. Entering the alias in the CLI executes the corresponding command. Once created, an alias is accessible in all modes and all user sessions, but is subject to all the restrictions of the original command.

When using a command alias, no tokens may precede the alias except the no and default keywords. However, an alias can incorporate positional parameters.

In online help, aliases are preceded by an asterisk (*) in this format:

*alias_name=command_name

The no alias and default alias commands remove the specified alias.

Command Mode

Global Configuration

Command Syntax

alias alias_name command_name

no alias alias_name

default alias alias_name

Parameters

alias_name the string which is to be substituted for the original command. The string can include letters, numbers, and punctuation, but no spaces. If the alias_name string is identical to an existing command, the alias will supercede the original command.
command_name the command which is to be executed when the alias is entered in the CLI. If the original command requires additional parameters, they must be included in the command_name string in the following manner:
Positional parameters are of the form “%n” and must be whitespace-delimited. The first parameter is represented by “%1” and any additional parameters must be numbered sequentially. When executing the alias a value must be entered for each parameter or the CLI will display the error “% incomplete command”.

Examples

This command makes e an alias for the command enable.
```
switch(config)#alias e enable
```
This command makes srie an alias for the command show running-config interface ethernet 1-6.
```
switch(config)#alias srie show running-config interface ethernet 1-6
```

These commands make ss an alias for the command show interfaces ethernet <range> status with a positional parameter for the port range, then use the alias to display the status of ports 4/1-4/5.

switch(config)#alias ss show interfaces ethernet %1 status
switch(config)#ss 4/1-4/5
Port      Name            Status       Vlan       Duplex  Speed Type
Et4/1                     connected    in Po1       full  10000 10GBASE-SRL
Et4/2                     notconnect   in Po1       full  10000 10GBASE-SRL
Et4/3                     notconnect   1            full  10000 10GBASE-SRL
Et4/4                     notconnect   1            full  10000 10GBASE-SRL
Et4/5                     notconnect   1            full  10000 10GBASE-SRL

bash

The bash command starts the Linux Bash shell. The Bash shell gives you access to the underlying Linux operating system and system extensions.

To exit the Bash, type logout, exit, or Ctrl-D at the Bash prompt.

Command Mode

Privileged EXEC

Command Syntax

bash

Examples

This command starts the Bash shell.

switch#bash

Arista Networks EOS shell

[admin@switch ~]$

This command, executed within Bash, exits the Bash shell.
```
[admin@switch ~]$ logout
switch#
```

comment (various configuration modes)

The comment command adds a comment for the active configuration mode to running-config. Comments cannot be modified, but can be replaced by entering the comment command again and entering new text. To append to an existing comment, enter !! followed by additional comment text. To display comments, use the comment option of the show (various configuration modes) command.

The no comment and default comment commands remove the comment from running-config.

Comments cannot be added to the global configuration mode through the EOS.

Command Mode

All configuration modes except Global Configuration

Command Syntax

comment comment_text EOF

no comment

default comment !! comment_text

Parameters

comment_text To create a comment, enter a message when prompted. The message may span multiple lines.
EOF To end a comment, type EOF on its own line (case sensitive) and press enter.

Examples

This command adds a comment to the active configuration mode.

switch(config-sg-radius-RAD-SV1)# comment
Enter TEXT message. Type 'EOF' on its own line to end.
Consult Thomas Morton before making changes to the RADIUS configuration.
EOF
switch(config-sg-radius-RAD-SV1)#

This command appends a line to the comment for the active configuration mode.

switch(config-sg-radius-RAD-SV1)# !! x3452
switch(config-sg-radius-RAD-SV1)#

configure (configure terminal)

The configure command places the switch in the Global Configuration mode to configure features at the system level. You can move to Interface Configuration mode and protocol-specific mode from the Global Configuration mode. The command may also be entered as configure terminal.

Command Mode

Privileged EXEC

Command Syntax

configure [terminal]

Example

This command places the switch in the Global Configuration mode.

switch> enable 
switch# configure 
switch(config)#

configure checkpoint

The configure checkpoint command saves the running configuration to a checkpoint file. This checkpoint file can be used for restoring the current running configuration in future, if required.

Command Mode

Privileged EXEC

Command Syntax

configure checkpoint {restore checkpoint_name | save [checkpoint_name]}

Parameters

restore checkpoint_name restores the running configuration from the specified checkpoint file.
save checkpoint_name saves running configuration to the specified checkpoint file.

Guidelines

If the filename already exists, EOS overwrites the filename. If the command is entered without a checkpoint name, the switch automatically saves the checkpoint under the name ckp-date-number where date is the date in YYYYMMDD format and number increments by one for each automatically named checkpoint file.

Examples

This command saves running-config to the ca_test checkpoint file.
```
switch# configure checkpoint save ca_test
```

This command restores the running-config from the ca_test checkpoint file.

switch# configure checkpoint restore ca_test
! Preserving static routes. Use 'no ip routing delete-static-routes' to clear
them.

This command saves running-config to the 13Aug2018 checkpoint file. The dir command shows the contents of the checkpoint directory.

switch# configure checkpoint save
switch# dir checkpoint:
Directory of checkpoint:/

       -rw-        7426           Aug 13 12:00  ckp-20180813-17
       -rw-        7588           Aug 13 12:10  ckp-20180813-18
       -rw-        8499           Aug 13 12:13  ckp-20180813-19
       -rw-        8499           Aug 13 12:13  ckp-20180813-20

configure convert

The configure convert command converts the current configuration syntax to the specified syntax.

Command Mode

Privileged EXEC

Command Syntax

configure convert new-syntax

Parameter

new-syntax converts running-config to the current version of EOS.

Example

This command converts running-config to the current version of EOS.

switch# configure convert new-syntax

WARNING!
Converting existing configuration to new syntax will lose backward compatibility.
Make sure you won't downgrade to releases that only support the old syntaxes.

Proceed [ y/n ]

configure network

The configure network command is deprecated. Use the copy <url> running-config command to configure the switch from a local file or network location.

copy running-config

The current operating configuration of the switch is stored in a virtual file called running-config. The copy running-config command saves the contents of the running-config virtual file to a new location.

Command Mode

Privileged EXEC

Command Syntax

copy running-config DESTINATION

Parameters

DESTINATION destination for the contents of the running-config file. Values include:
- startup-config the configuration file that the switch loads when it boots.
The copy running-config, startup-config, and write commands are equivalent.
- file: a file in the switch file directory.
- flash: a file in flash memory.
- url any valid URL.

The copy running-config url and write network url commands are equivalent.

Examples

This command copies running-config to the startup-config file.
```
switch# copy running-config startup-config
switch#
```
This command copies running-config to a file called rc20110617 in the dev subdirectory of the switch directory.
```
switch# copy running-config file:dev/rc20110617
switch#
```

daemon

The daemon command accesses daemon configuration mode for adding or removing external daemons and scripts, which are then managed by ProcMgr.

The no daemon and default daemon commands delete the daemon by removing the corresponding daemon command from running-config.

Command Mode

Global Configuration

Command Syntax

daemon daemon_name

no daemon daemon_name

default daemon daemon_name

Parameters

daemon_name label that references the daemon configuration mode.

Example

These commands enters daemon configuration mode and initiates the daemon script.

switch(config)# daemon process1
switch(config-daemon-process1)# command process-script -i -m
switch(config-daemon-process1)#

delay

The delay command specifies the time in seconds the system will delay between a triggering event and the execution of an event handler action. The default delay is 20 seconds.

Command Mode

Event-Handler Configuration

Command Syntax

delay seconds

Parameters

seconds number of seconds to delay before executing the action. The default is 20.

Example

This command configures the event handler Eth5 to delay 10 seconds before executing.

switch(config-handler-Eth5)# delay 10
switch(config-handler-Eth5)#

dir

The dir command displays a list of files on a file system.

Command Mode

Privileged EXEC

Command Syntax

dir [SCOPE][FILE TYPE]

Parameters

SCOPE the files to display. Options include:
- no parameter lists normal files in current directory.
- /all list all files, including hidden files.
- /recursive list files recursively.
FILE TYPE The options include:
- no parameter lists undeleted files.
- all_filesystems list files on all filesystems including deleted files, undeleted files, and files with errors.
- extensions directory or file name.
- file directory or file name.
- flash directory or file name.
- supervisor-peer directory or file name.
- usb1 directory or file name.
- system directory or file name.

Example

This command displays the flash directory.

switch# dir flash:
Directory of flash:/

       -rwx   293409892           Oct 23 08:55  EOS-4.11.0.swi
       -rwx   221274543            Sep 6 13:37  EOS-4.7.5.swi
       -rwx   271453650            Sep 4 19:13  EOS_4.10.1-SSO.swi
       -rwx      135168           Dec 31  1979  FSCK0000.REC
       -rwx          26           Oct 23 13:51  boot-config
       -rwx        8570           Sep 10 12:22  cfg_sso_mst
       -rwx        5642           Sep 20 10:35  config.reset
       drwx        4096           Oct 23 13:59  debug
       -rwx          12           Oct 23 13:56  kernel-params
       drwx        4096           Oct 23 14:59  persist
       drwx        4096            Sep 6 14:50  schedule
       -rwx        5970           Oct 23 13:53  startup-config
switch#

disable

The disable command exchanges the session’s current command mode with the specified privilege level.

Command Mode

Privileged EXEC

Command Syntax

disable [PRIVILEGE_LEVEL]

Parameters

PRIVILEGE_LEVEL Session’s new privilege level. Value ranges from 0 to 15. Levels 2 through 15 place the switch in Privileged EXEC mode. Values of 0 or 1 leave the switch in EXEC mode.

no parameter Session is assigned default level of 1.
<0 to 15> Specifies session level.

Restrictions

New privilege level must be less than the session’s current level.

Example

This command exits Privileged EXEC mode level of 15 to enter EXEC mode level 1.

switch# disable
switch>

enable

The enable command places the switch in Privileged EXEC mode. If an enable password is set, the CLI displays a password prompt when a user enters the enable command. If the user enters an incorrect password three times, the CLI displays the EXEC mode prompt.

To set a local enable password, use the enable password command.

Command Mode

EXEC

Command Syntax

enable [PRIVILEGE_LEVEL]

Parameters

PRIVILEGE_LEVEL Session’s privilege level. Values range from 0 to 15. Values of 0 or 1 places the switch in EXEC mode. Any level above 1 leaves the switch in Privileged EXEC mode.
- no parameter Session is assigned default level of 15.
- <0 to 15> Specifies session level.

Example

This command places the switch in Privileged EXEC mode with the default privilege level of 15.

switch> enable
switch#

end

The end command exits to Privileged Exec mode from any Configuration mode. If the switch is in a group-change mode (such as ACL-Configuration mode or MST-Configuration mode), the end command also saves all pending changes made in that mode to running-config.

Command Mode

All configuration modes

Command Syntax

end

Example

This command exits to Privileged Exec mode.

switch(config-if-Et25)# end
switch#

event-handler DropCountersHandler

The event-handler DropCountersHandler command enables the adverse drop counters monitor with event handlers. The DropCountersHandler event handler is enabled by default, and can be customized for duration of time window and threshold levels.

The no event-handler DropCountersHandler command disables the adverse drop counters monitor with event handlers. The default event-handler DropCountersHandler command resets the DropCountersHandler event handler to the system default.

Command Mode

Global Configuration

Command Syntax

event-handler DropCountersHandler

no event-handler DropCountersHandler

default event-handler DropCountersHandler

Examples

These commands customize the delay, polling interval, and condition for width (-w), violation count (-c), and threshold (-t) of this event handler. Each parameter may be customized separately, with all other parameters remaining unchanged.

switch(config)# event-handler DropCountersHandler
switch(config-DropCountersHandler)# action bash DropCounterLog.py -l
switch(config-DropCountersHandler)# delay 0
switch(config-DropCountersHandler)# trigger on-counters
switch(config-DropCountersHandler-counters)# poll interval 60
switch(config-DropCountersHandler-counters)# condition 
bashCmd."DropCounterMonitor.py" -w 800" > 0
switch(config-DropCountersHandler-counters)# condition 
bashCmd."DropCounterMonitor.py" -c 5" > 0
switch(config-DropCountersHandler-counters)# condition 
bashCmd."DropCounterMonitor.py" -t 200" > 0
switch(config-DropCountersHandler-counters)#

This command disables this event handler.

switch(config)# no event-handler DropCountersHandler
switch(config)#

event-handler

An event handler executes a Linux Bash shell command in response to a specific system event. An event handler consists of a Bash command, a trigger and a delay; when the trigger event occurs, the action is scheduled to run after delay seconds.

The event-handler command places the switch in event-handler configuration mode for the specified event handler. If the named event handler does not already exist, this command creates it. Event-handler configuration mode is a group change mode that configures event handlers.

Changes made in a group change mode are saved by leaving the mode through the exit command or by entering another configuration mode.

These commands are available in event-handler configuration mode:

action bash
delay
trigger

The no event-handler and default event-handler commands delete the specified event handler by removing it from running config.

Command Mode

Global Configuration

Command Syntax

event-handler name

no event-handler name

default event-handler name

Parameters

name name of the event handler to be configured. If the named event handler does not already exist, this command will create it.

Example

This command places the switch in event-handler configuration mode for an event handler called Eth_5.

switch(config)# event-handler Eth_5
switch(config-handler-Eth_5)#

exit

The exit command places the switch in the parent of the command mode from which the exit command was entered.

When used in Global configuration, the switch enters Privileged EXEC mode.
When used in EXEC or Privileged EXEC mode, the exit command terminates the user session.
When the command is used in a group-change mode (such as ACL-Configuration mode or MST-Configuration mode), the exit command also applies all pending changes made in that mode.

Command Mode

All modes

Command Syntax

exit

Examples

This command exits Global Configuration mode to Privileged EXEC mode.
```
switch(config)# exit
switch#
```
This command terminates the user session.
```
switch# exit 
```

ip ftp client source-interface

By default, the FTP (File Transfer Protocol) source IP address is selected by the switch (the IP address of the source interface if one is assigned). The ip ftp client source-interface command allows the user to override the default FTP source address.

The ip ftp client source-interface and ip ftp source-interface commands are functionally equivalent. In each case, ip ftp client source-interface is stored in running-config.

The no ip ftp client source-interface and default ip ftp client source-interface commands restore default behavior by removing the ip ftp client source-interface statement from running-config.

Command Mode

Global Configuration

Command Syntax

ip ftp [client] source-interface INTERFACE [vrf vrf_name]

no ip ftp [client] source-interface

default ip ftp [client] source-interface

Parameters

client Parameter has no functional effect.
INTERFACE Interface providing the IP address. Options include:
- ethernet e_num Ethernet interface specified by e_num.
- loopback l_num Loopback interface specified by l_num.
- management m_num Management interface specified by m_num.
- port-channel p_num Port-channel interface specified by p_num.
- tunnel t_num Tunnel interface specified by t_num.
- vlan v_num VLAN interface specified by v_num.
- vrf vrf_name Uses the specified user-defined VRF.

Examples

These commands configure the 10.10.121.15 as the source IP address the switch uses when communicating with FTP servers.

switch(config)# interface ethernet 17
switch(config-if-Et17)# ip address 10.10.121.15/24
switch(config-if-Et17)# ip ftp client source-interface ethernet 17
switch(config)#

This command configures the switch to use interface tunnel 45 and vrf vrf01 when communicating with FTP servers.
```
switch(config)#ip ftp client source-interface tunnel 45 vrf vrf01
switch(config)#
```

ip http client local-interface

The ip http client local-interface command specifies the source IP address for hypertext transfer protocol (HTTP) connections. By default, the source IP address is selected by the switch when this command is not configured or when the specified interface is not assigned an IP address.

The no ip http client local-interface and default ip http client local-interface commands restore default behavior by removing the ip http client local-interface statement from running-config .

Command Mode

Global Configuration

Command Syntax

ip http client local-interface INTERFACE [vrf vrf_name]

no ip http client local-interface

default ip http client local-interface

Parameters

INTERFACE Interface providing the IP address. Options include:
- ethernet e_num Ethernet interface specified by e_num.
- loopback l_num Loopback interface specified by l_num.
- management m_num Management interface specified by m_num.
- port-channel p_num Port-channel interface specified by p_num.
- vlan v_num VLAN interface specified by v_num.
vrf vrf_name Uses the specified user-defined VRF.

Examples

These commands configure the 10.15.17.9 as the source IP address the switch uses when communicating with HTTP servers.

switch(config)# interface vlan 10
switch(config-if-Vl10)# ip address 10.15.17.9/24
switch(config-if-Vl10)# ip http client local-interface vlan 10
switch(config)#

This command configures the switch to use interface tunnel 45 and vrf vrf01 when communicating with HTTP servers.
```
switch(config)# ip http client local-interface tunnel 45 vrf vrf01
switch(config)#
```

ip ssh client source-interface

The ip ssh client source-interface command specifies the source IP address for secure shell (SSH) connections. By default, the source IP address is selected by the switch when this command is not configured or when the specified interface is not assigned an IP address.

The ip ssh client source-interface and ip ssh source-interface commands are functionally equivalent. In each case, ip ssh client source-interface is stored in running-config.

The no ip ssh client source-interface and default ip ssh client source-interface commands restore default behavior by removing the ip ssh client source-interface statement from running-config.

Command Mode

Global Configuration

Command Syntax

ip ssh [client] source-interface INTERFACE [vrf vrf_name]

no ip ssh [client] source-interface

default ip ssh [client] source-interface

Parameters

client Parameter has no functional effect.
INTERFACE Interface providing the IP address. Options include:
- ethernet e_num Ethernet interface specified by e_num.
- loopback l_num Loopback interface specified by l_num.
- management m_num Management interface specified by m_num.
- port-channel p_num Port-channel interface specified by p_num.
- vlan v_num VLAN interface specified by v_num.
vrf vrf_name Uses the specified user-defined VRF.

Examples

These commands configure the 10.17.17.9 as the source IP address the switch uses when communicating with SSH servers.

switch(config)# interface vlan 10
switch(config-if-Vl10)# ip address 10.17.17.9/24
switch(config-if-Vl10)# ip ssh client source-interface vlan 10
switch(config)#

This command configures the switch to use interface tunnel 45 and vrf vrf01 when communicating with SSH servers.
```
switch(config)#ip ssh client source-interface tunnel 45 vrf vrf01
switch(config)#
```

ip tftp client source-interface

The ip tftp client source-interface command specifies the source IP address for Trivial File Transfer Protocol (TFTP) connections. By default, the source IP address is selected by the switch when this command is not configured or when the specified interface is not assigned an IP address.

The ip tftp client source-interface and ip tftp source-interface commands are functionally equivalent. In each case, ip tftp client source-interface is stored in running-config.

The no ip tftp client source-interface and default ip tftp client source-interface commands restore default behavior by removing the ip tftp client source-interface statement from running-config.

Command Mode

Global Configuration

Command Syntax

ip tftp [client] source-interface INTERFACE [vrf vrf_name]

no ip tftp [client] source-interface

default ip tftp [client] source-interface

Parameters

client Parameter has no functional effect.
INTERFACE Interface providing the IP address. Options include:
- ethernet e_num Ethernet interface specified by e_num.
- loopback l_num Loopback interface specified by l_num.
- management m_num Management interface specified by m_num.
- port-channel p_num Port-channel interface specified by p_num.
- vlan v_num VLAN interface specified by v_num.
vrf vrf_name Uses the specified user-defined VRF.

Examples

These commands configure the 10.15.17.9 as the source IP address the switch uses when communicating with TFTP servers.

switch(config)# interface vlan 10
switch(config-if-Vl10)# ip address 10.15.17.9/24
switch(config-if-Vl10)# ip tftp client source-interface vlan 10
switch(config)#

This command configures the switch to use interface tunnel 45 and vrf vrf01 when communicating with TFTP servers.
```
switch(config)# ip tftp client source-interface tunnel 45 vrf vrf01
switch(config)#
```

platform arad lag mode

The platform arad lag mode command allows configuration of LAGs with more than 16 members.

Command Mode

Global Configuration

Command Syntax

platform arad lag mode [1024x16 | 256x64 | 512x32]

Examples

This command configures 1024 LAGs with 16 members each.

switch(config)# platform arad lag mode 1024x16
! Change will take effect only after switch reboot.
switch(config)#

This command configures 256 LAGs with 64 members each.

switch(config)# platform arad lag mode 256x64
! Change will take effect only after switch reboot.
switch(config)#

This command configures 512 LAGs with 32 members each.

switch(config)# platform arad lag mode 512x32
! Change will take effect only after switch reboot.
switch(config)#

platform sand fabric mode (7500 and 7500E Series)

The platform sand fabric mode command specifies the fabric mode under which the switch operates after the next system reload. The command has no operational effect until the switch reloads.

The fabric mode determines the modular switch’s fabric performance capabilities and must be compatibile with the installed fabric modules. Fabric mode settings include:

fe600: Supports first-generation fabric modules.
fe1600: Supports E-Series fabric modules.
Note: Switches that reload in petraA forwarding compatibility mode (platform sand forwarding mode (7500 and 7500E Series)) also reload in fe600 fabric mode regardless of the presence of a platform sand fabric mode statement in running-config.

The switch’s fabric mode setting must match the capabilities of its installed fabric modules. Reloading the switch in a different mode may be required after exchanging fabric modules for a different module type. The show module command displays the fabric modules in the switch.

Each fabric module is categorized as first-generation or E-Series:

First-generation fabric modules support all basic switch functions.
E-Series fabric modules support faster fabric link speeds, greater internal table capacities, and advanced encoding formatting.

E-series fabric modules can operate in fe600 mode, but are limited to first-generation fabric performance. First-generation modules cannot operate in fe600 mode. Switches containing both types of modules must be set to fe600 mode. Best practice is to avoid switch configurations with mixed fabric modules.

When a switch reloads, fabric mode is determined by the following (in order of precedence):

Switches reloading in petraA forwarding compability mode also reload in fe600 fabric mode .
As specified by the platform sand fabric mode statement in running-config.
The first fabric module that becomes operational as the switch reloads.

The no platform sand fabric mode and default platform sand fabric mode commands remove the platform sand fabric mode command from running-config.

Command Mode

Global Configuration

Command Syntax

platform sand fabric mode [MODE_SETTING]

no platform sand fabric mode

default platform sand fabric mode

Parameters

MODE_SETTING Specifies the switch’s fabric mode. Options include:
- fe16000 E-Series fabric mode.
- fe600 First-generation fabric mode.

Example

switch(config)# platform sand fabric mode fe1600
switch(config)# exit
switch# show platform sand compatibility
                     Configuration        Status
Forwarding mode      None                 Arad
Fabric mode          Fe1600               Fe600
switch#

platform sand forwarding mode (7500 and 7500E Series)

The platform sand forwarding mode command specifies the forwarding compatibility mode under which the switch operates after the next system reload. The command has no operational effect until the switch reloads.

Forwarding compatibility mode specifies switch forwarding capabilities and configures performance capacity of installed linecards. Forwarding compatibility modes settings include:

petraA: Supports first-generation fabric modules.
arad: Supports E-Series fabric modules.
Note: Switches that reload in petraA forwarding compatibility mode also reload in fe600 fabric mode regardless of the presence of a platform sand fabric mode (7500 and 7500E Series) statement in running-config.

This command may be required after exchanging a linecard for a different module type or in switches containing first-generation and E-series linecards. The show module command displays the linecard modules in the switch.

Each modular switch linecard module is categorized as first-generation or E-Series:

First-generation linecards support all basic switch functions.
E-Series linecards support provide faster data processing, greater internal table capacities, and advanced encoding formatting.

The forwarding compatibility mode determines the operational capacity of installed linecards. The following table lists the affect of the forwarding compatibility mode on all linecard module types.

Table 5. Linecard Module and Forwarding Mode Performance
Linecard Module Type	Forwarding Software Mode	Linecard Operating Capacity
First-generation	petraA	Linecard performs at first-generation performance capacity.
First-generation	arad	Linecard is powered-down.
E-Series	petraA	Linecard performs at first-generation performance capacity.
E-Series	arad	Linecard performs at E-series performance capacity.

Note: Linecards operate at E-Series performance capacities only on switches that contain E-Series fabric modules and have a fabric mode setting of fe1600 fabric mode (platform sand fabric mode (7500 and 7500E Series)).

Without a platform sand fabric mode (7500 and 7500E Series) command, forward compatibility mode is determined by the first linecard that becomes operational after reloading the switch. In a switch that is reloaded with a homogeneous module set, forwarding compatibility mode matches its linecards. Switches with a mixed set of modules are typically reloaded in petraA mode because first generation modules are usually operational before E-Series modules. However, forwarding compatibility mode in mixed module switches that are reloading is not guaranteed without a platform sand forwarding mode command.

The no platform sand forwarding mode and default platform sand forwarding mode commands restore the platform sand forwarding mode command from running-config.

Command Mode

Global Configuration

Command Syntax

platform sand forwarding mode [MODE_SETTING]

no platform sand forwarding mode

default platform sand forwarding mode

Parameters

MODE_SETTING Specifies the switch’s software forwarding mode. Options include:
- arad the switch supports E-Series linecard capabilities.
- petraA the switch supports first-generation linecard capabilities.

Example

This command changes the forwarding software mode to support E-series linecard modules. This command should be run only after exchanging all linecards to E-series modules.

switch(config)# platform sand forwarding mode arad
switch(config)#

platform sand lag hardware-only

The platform sand lag hardware-only command specifies that all LAGs will use hardware resources including single member LAGs. Hardware resource allocation and deallocation traffic disruption occurs on the first member addition or deletion, rather than the second member addition or deletion.

The no platform sand lag hardware-only and default platform sand lag hardware-only commands specify that LAGs are not required to be implemented in hardware, and therefore some LAGs may be implemented in software. Permitting both hardware and software LAGs may increase the total number of port-channels because we have no resource limit on the number of software LAGs.

Command Mode

Global Configuration

Command Syntax

platform sand lag hardware-only

no platform sand lag hardware-only

default platform sand lag hardware-only

Examples

This command configures all LAGs to use hardware resources. All existing one member LAGs will be allocated hardware resources, when available.
```
switch(config)# platform sand lag hardware-only
switch(config)#
```
This command allows certain LAGs (single member LAGs) to not consume hardware resources. All existing one member LAGs will release their hardware resources.
```
switch(config)# no platform sand lag hardware-only
switch(config)#
```

platform sand lag mode

The platform sand lag mode configures two Link Aggregation Groups (LAG) partitions, Partition A and Partition B, to support twice as many available Port Channels. Use this command if the current LAG mode does not allow creating a large number of Port Channels on a single partition. Disable the usage of Partion B using the platform sand lag mode 1024x16 command.

Note: Changing the configuration of the LAG mode requires the switch to restart and apply the configuration.

Command Mode

Global Configuration

Command Syntax

platform sand lag mode [2048x8 | 1024x16 | 512x32 | 256x64 | 128x128 | 64x256]

Parameters

2048x8 - Specify 2048 LAGs with 8 members each.
1024x16 - Specify 1024 LAGs with 16 members each.
512x32 - Specify 512 LAGs with 32 members each.
256x64 - Specify 256 LAGs with 64 members each.
128x128 - Specify 128 LAGs with 128 members each.
64x256 - Specify 64 LAGs with 256 members each.

Example

To configure a switch with 512 LAGS and 32 members each, use the following command:

switch(config)# platform sand lag mode 512x32

Use the show platform sand lag mode to display the LAG mode for Partition A and B:

switch(config)# show platform sand lag mode
Partition     Configuration        Status              
A             1024x16              1024x16             
B             1024x16              1024x16

pwd

The pwd command displays the working directory.

Command Mode

Privileged EXEC

Command Syntax

pwd

Example

This command shows that the working is Flash.

switch# pwd
flash:/
switch#

schedule config

The schedule config command sets configuration parameters to the CLI scheduler.

The no schedule config max-concurrent-jobs and default schedule config max-concurrent-jobs commands reset the limit of maximum concurrent jobs to the default value of 1 by removing the corresponding schedule config max-concurrent-jobs statement from running-config.

The no schedule config prepend-hostname-logfile and default schedule config prepend-hostname-logfile commands reset the log filenames to the default state.

Command Mode

Global Configuration

Command Syntax

schedule config{max-concurrent-jobs limit | prepend-hostname-logfile}

no schedule config {max-concurrent-jobs limit | prepend-hostname-logfile}

default schedule config {max-concurrent-jobs limit | prepend-hostname-logfile}

Parameters

max-concurrent-jobs limit specifies the maximum number of concurrent commands that can run on the switch. The maximum concurrent jobs ranges from 1 to 4. The default value is 1.
prepend-hostname-logfile enables prepending hostnames to log filenames. By default, this option is enabled.

Examples

This command configures to concurrently run a maximum of three commands on the switch.

switch(config)# schedule config max-concurrent-jobs 3
switch(config)# show schedule summary
Maximum concurrent jobs  3
Prepend host name to logfile: No
Name            At time      Last    Interval   Timeout   Max     Logfile Location               
Status
                             time     (mins)    (mins)    log
                                                         files
------------- ------------- ------- ---------- -------- -------- ------------------------------- ------
tech-support      now        00:29      60        30      100     flash:schedule/tech-support/   Success
thelp           12:02:00     00:02      60        40      100     flash:schedule/thelp/          
Fail
                06/05/2018
switch(config)#

This command enables prepending the hostname to log filenames.

switch(config)# schedule config prepend-hostname-logfile
switch(config)# show schedule summary
Maximum concurrent jobs  3
Prepend host name to logfile: Yes
Name            At time      Last    Interval   Timeout   Max     Logfile Location               
Status
                             time     (mins)    (mins)    log
                                                         files
------------- ------------- ------- ---------- -------- -------- ------------------------------- ------
tech-support      now        00:29      60        30      100     flash:schedule/tech-support/   Success
thelp           12:02:00     00:02      60        40      100     flash:schedule/thelp/          
Fail
                06/05/2018
switch(config)#

schedule

The schedule command facilitates the periodic execution of a specified CLI command. Command parameters configure the start time of periodic execution, the interval between consecutive execution instances, the maximum time allotted for command execution, and the maximum number of log files that can be created.

The no schedule and default schedule commands disable execution of the specified command.

Command Mode

Global Configuration

Command Syntax

schedule schedule_name PERIOD {max-log-files count | timeout timeout_interval}{command cmd | logging verbose | loglocation flash:}

no schedule schedule_name

default schedule schedule_name

Parameters

schedule_name Label associated with the scheduled command.
PERIOD Start time for execution and interval between consecutive execution instances. The interval ranges from 2 to 1440 minutes. The default interval while scheduling the show tech-support command is 60 minutes. Options include:
- at Start time for execution. Options include:
  - hh:mm:ss interval interval The command execution starts at the specified time and repeats at the specified interval.
  - hh:mm:ss mm/dd/yyyy interval interval The command execution starts at the specified time on the specified day and repeats at the specified interval.
  - hh:mm:ss once The command execution starts at the specified time and does not repeat.
  - hh:mm:ss mm/dd/yyyy once The command execution starts at the specified time on the specified day and does not repeat.
  - hh:mm:ss yyyy-mm-dd interval interval The command execution starts at the specified time on the specified day and repeats at the specified interval.
  - hh:mm:ss yyyy-mm-dd once The command execution starts at the specified time on the specified day and does not repeat.
- interval interval The command execution starts immediately and repeats at the specified interval.
- now interval hh:mm:ssinterval intervalhh:mm:ss mm/dd/yyyyinterval intervaloncehh:mm:sshh:mm:ss mm/dd/yyyyoncehh:mm:ss yyyy-mm-ddinterval intervaloncehh:mm:ss yyyy-mm-ddinterval intervalnow interval interval The command execution starts immediately and repeats at the specified interval.
max-log-files count Maximum number of log files command generates for command output. The count of maximum log files ranges from 1 to 10000. The default count of maximum log files while scheduling the show tech-support command is 100.
timeout timeout_interval Maximum time allotted for the script execution. The timeout interval ranges from 1 to 480 minutes. The default timeout is 30 minutes.
Note: The command execution is terminated if it exceeds the specified timeout interval. The timeout allotted for the scheduled command must not be greater than the corresponding interval.
command cmd The command that needs to be executed.
logging verbose Sets the logging level to “verbose.” A syslog entry is added after the execution of the scheduled command, regardless of whether the scheduled command has succeeded or failed. In the absence of logging verbose, the syslog entry is added only if the execution of the scheduled command fails with an error.
loglocation destination The flash destination for scheduled command output files.

Guidelines

Log files created by the command are stored in the flash:/schedule/ scheduled_name / directory. Empty log files are created for commands that do not generate any output.

Examples

This command saves the running configuration contents to the log file every hour with immediate effect and creates a maximum of 24 log files.
```
switch(config)# schedule backup-test interval 60 max-log-files 24 command show running-config
```
This command starts the script execution at 12:00:00 and repeats every 720 minutes. The script execution is terminated if it exceeds 20 minutes. It generates a maximum of one log file because the specified bash command does not have an output.
```
switch(config)# schedule ms1 at 12:00:00 interval 720 timeout 20 max-log-files 1 command bash /mnt/flash/myscript.sh
```

The show schedule command lists the commands currently scheduled for periodic execution and displays the summary of the specified scheduled command.

switch# show schedule summary
Maximum concurrent jobs  1
Prepend host name to logfile: Yes

Name At time Last  Interval Timeout  Max    Logfile Location    Status
             time  (mins)   (mins)   log     
                                     files
---- ------- ----- -------- -------- ------ -------------------  -------
ms1   now    23:03   720       20      1    flash:/schedule/ms1 Success

switch#

show (various configuration modes)

The show command, when executed within a configuration mode, can display data in running-config for the active configuration mode.

Command Mode

All configuration modes except Global Configuration

Command Syntax

show [DATA_TYPE]

Parameters

DATA_TYPE Specifies display contents. Values include:
- active Displays running-config settings for the configuration mode.
- active all Displays running-config plus defaults for the configuration mode.
- active all detail Displays running-config plus defaults for the configuration mode.
- comment Displays comment entered for the configuration mode.

Related Commands

The show commands in ACL-configuration mode and MST-configuration mode include the active and comment options along with additional mode-specific options.

Example

This command shows the server-group-TACACS+ configuration commands in running-config.

switch(config-sg-tacacs+-TAC-GR)# show active
   server TAC-1
   server 10.1.4.14
switch(config-sg-tacacs+-TAC-GR)#

show event-handler DropCountersHandler

The show event-handler command displays details of the DropCountersHandler event handler.

Command Mode

Privileged EXEC

Command Syntax

show event-handler DropCountersHandler

Example

This command displays details of this event handler.

switch(config)# show event-handler DropCountersHandler
Event-handler DropCountersHandler (BUILT-IN)
Trigger: on-counters delay 0 seconds
  Polling Interval: 60 seconds
  Condition: bashCmd."DropCounterMonitor.py" > 0
Threshold Time Window: 0 Seconds, Event Count: 1 times
Action: DropCounterLog.py -l
Action expected to finish in less than 20 seconds
Total Polls: 39
Last Trigger Detection Time: 38 minutes 22 seconds ago
Total Trigger Detections: 1
Last Trigger Activation Time: 38 minutes 22 seconds ago
Total Trigger Activations: 1
Last Action Time: Never
Total Actions: 1

switch(config)#

show event-handler

The show event-handler command displays the contents and activation history of a specified event handler or all event handlers.

Command Mode

Privileged EXEC

Command Syntax

show event-handler [handler_name]

Parameters

handler_name optional name of an event handler to display. If no parameter is entered, the command displays information for all event handlers configured on the system.

Example

This command displays information about an event handler called “eth_5”.

switch# show event-handler Eth_5
Event-handler Eth_5
Trigger: on-intf Ethernet5 on ip delay 20 seconds
Threshold Time Window: 0 Seconds, Event Count: 1 times
Action: :
Device-health Action: None
Action expected to finish in less than 10 seconds
Last Trigger Detection Time: 15 days 2 hours 19 minutes ago
Total Trigger Detections: 1
Last Trigger Activation Time: 15 days 2 hours 19 minutes ago
Total Trigger Activations: 1
Last Action Time: 15 days 2 hours 19 minutes ago
Total Actions: 1
switch#

show module

The show module command displays information that identifies the supervisor, fabric, and linecard modules in a modular switch, including model number, serial number, hardware version number, software version (supervisors only), MAC address (supervisors and linecards), and operational status.

Command Mode

EXEC

Command Syntax

show module [MODULE_NAME]

Parameters

MODULE_NAME Specifies modules for which data is displayed. Options include:
- no parameter All modules (identical to all option).
- fabric fab_num Specified fabric module. Number range varies with switch model.
- linecard line_num Linecard module. Number range varies with switch model.
- supervisor super_num Supervisor module. Number range varies with switch model.
- mod_num Supervisor (1 to 2) or linecard (3 to 18) module.
- all All modules.

Related Command

show version displays model and serial numbers of modular system components.

Examples

This command displays information about all installed modules on a DCS-7504 switch.

switch# show module
Module    Ports Card Type                            Model           Serial No.
--------- ----- ------------------------------------ --------------- -----------
1         2     DCS-7500 Series Supervisor Module    7500-SUP        JSH11440327
2         1     Standby supervisor                   Unknown         Unknown
3         48    48-port SFP+ 10GigE Linecard         7548S-LC        JSH10315938
4         48    48-port SFP+ 10GigE Linecard         7548S-LC        JSH11665247
5         48    48-port SFP+ 10GigE Linecard         7548S-LC        JSH11834614
6         48    48-port SFP+ 10GigE Linecard         7548S-LC        JSH11060688
Fabric1   0     DCS-7504 Fabric Module               7504-FM         JSH11244430
Fabric2   0     DCS-7504 Fabric Module               7504-FM         JSH11892120
Fabric3   0     DCS-7504 Fabric Module               7504-FM         JSH11941115
Fabric4   0     DCS-7504 Fabric Module               7504-FM         JSH11661618
Fabric5   0     DCS-7504 Fabric Module               7504-FM         JSH11757555
Fabric6   0     DCS-7504 Fabric Module               7504-FM         JSH11847728

Module    MAC addresses                          Hw      Sw      Status
--------- -------------------------------------- ------- ------- -------
1         00:1c:23:03:06:ac - 00:1c:23:03:06:ac  07.06   4.12.1  Active
2                                                        4.12.1  Standby
3         00:1c:23:03:80:44 - 00:1c:23:03:80:73  06.00           Ok
4         00:1c:23:03:e4:34 - 00:1c:23:03:e4:63  07.10           Ok
5         00:1c:23:12:0b:3f - 00:1c:23:12:0b:6e  07.30           Ok
6         00:1c:23:12:b6:3f - 00:1c:23:12:b6:6e  08.00           Ok
Fabric1                                          05.03           Ok
Fabric2                                          05.03           Ok
Fabric3                                          05.02           Ok
Fabric4                                          05.02           Ok
Fabric5                                          05.02           Ok
Fabric6                                          05.02           Ok
switch#

This command displays information about all installed modules on a DCS-7304 switch.

switch# show module
Module    Ports Card Type                            Model           Serial No.
--------- ----- ------------------------------------ --------------- -----------
1         3     Supervisor 7300X SSD                 DCS-7300-SUP-D  JAS13340024
3         128   32 port 40GbE QSFP+ LC               7300X-32Q-LC    JPE13440416
4         64    48 port 10GbE SFP+ & 4 port QSFP+ LC 7300X-64S-LC    JAS13310113
5         64    48 port 10GbE SFP+ & 4 port QSFP+ LC 7300X-64S-LC    JAS13340033
6         64    48 port 10GbE SFP+ & 4 port QSFP+ LC 7300X-64S-LC    JAS13310103
Fabric1   0     7304X Fabric Module                  7304X-FM        JAS13320077
Fabric2   0     7304X Fabric Module                  7304X-FM        JAS13350043
Fabric3   0     7304X Fabric Module                  7304X-FM        JAS13350050
Fabric4   0     7304X Fabric Module                  7304X-FM        JAS13350056

Module    MAC addresses                          Hw      Sw      Status
--------- -------------------------------------- ------- ------- -------
1         00:1c:73:36:4b:71 - 00:1c:73:36:4b:72  01.01   4.13.3F Active
3         00:1c:73:58:d4:68 - 00:1c:73:58:d4:87  03.04           Ok
4         00:1c:73:36:05:61 - 00:1c:73:36:05:94  02.02           Ok
5         00:1c:73:36:0a:e1 - 00:1c:73:36:0b:14  02.03           Ok
6         00:1c:73:36:02:e1 - 00:1c:73:36:03:14  02.02           Ok
Fabric1                                          00.00           Ok
Fabric2                                          00.00           Ok
Fabric3                                          00.00           Ok
Fabric4                                          00.00           Ok
switch#

show platform sand compatibility

The show sand platform compatibility command displays the fabric and forwarding modes. These modes determine switch forwarding capabilities and programs performance capacity of installed linecards

Information that identifies the supervisor, fabric, and linecard modules in the modular switch, including model number, serial number, hardware version number, software version (supervisors only), MAC address (supervisors and linecards), and operational status.

Command Mode

Privileged EXEC

Command Syntax

show platform sand compatibility

Related Commands

platform sand fabric mode (7500 and 7500E Series) specifies the fabric software mode.
platform sand forwarding mode (7500 and 7500E Series) specifies the forwarding software mode.

Example

This command indicates that the switch is in Fe600 fabric mode and PetraA forwarding mode.

switch# show platform sand compatibility
                     Configuration        Status
Forwarding mode      None                 PetraA
Fabric mode          None                 Fe600
switch#

show platform sand lag hardware-only

The show platform sand lag hardware-only command displays whether or not LAGs are hardware-only.

Command Mode

Privileged EXEC

Command Syntax

show platform sand lag hardware-only

Examples

This command indicates that LAGs are hardware-only.

switch(config)# platform sand lag hardware-only
switch(config)# exit
switch# show platform sand lag hardware-only
Hardware resources are used for all LAGs: True
switch#

This command indicates that LAGs are not hardware-only.

switch(config)# no platform sand lag hardware-only
switch(config)# exit
switch# show platform sand lag hardware-only
Hardware resources are used for all LAGs: False
switch#

show schedule

The show schedule command displays logging output on the terminal during the current terminal session. This command affects only the local monitor. The no terminal monitor command disables direct monitor display of logging output for the current terminal session.

The show schedule command displays the list of active scheduled commands and the summary of specified scheduled command.

Command Mode

Global Configuration

Command Syntax

show schedule {schedule_name |summary}

Parameters

schedule_name displays the summary of the specified scheduled command.
summary displays the list of active scheduled commands.

Examples

This command displays the summary of the thelp schedule.

switch(config)# show schedule thelp
The last CLI command failed with exit status 1
CLI command "show THelp" is scheduled next at "02:02:35 06/19/2018", interval is 
60 minutes
Timeout is 40 minutes
Maximum of 100 log files will be stored
Verbose logging is off
100 log files currently stored in flash:/schedule/thelp

Start time                 Size          Filename
----------------------- ---------------- ----------------------------------
Jun 19 2018 01:02       60.0 bytes       ro301_thelp_2018-06-19.0102.log.gz
Jun 19 2018 00:02       60.0 bytes       ro301_thelp_2018-06-19.0002.log.gz
Jun 18 2018 23:02       60.0 bytes       ro301_thelp_2018-06-18.2302.log.gz
Jun 18 2018 22:02       60.0 bytes       ro301_thelp_2018-06-18.2202.log.gz
Jun 18 2018 21:02       60.0 bytes       ro301_thelp_2018-06-18.2102.log.gz

switch(config)#

This command displays the summary of scheduled commands.

switch(config)# show schedule summary
Maximum concurrent jobs  1
Prepend host name to logfile: Yes
Name            At time      Last    Interval   Timeout   Max     Logfile Location               
Status
                             time     (mins)    (mins)    log
                                                         files
------------- ------------- ------- ---------- -------- -------- ------------------------------- ------
tech-support      now        00:29      60        30      100     flash:schedule/tech-support/   Success
thelp           12:02:00     00:02      60        40      100     flash:schedule/thelp/          
Fail
                06/05/2018
switch(config)#

show version

The show version command displays information that identifies the switch, including its model number, serial number, and system MAC address. The command also provides hardware and software manufacturing information, along with the available memory and elapsed time from the most recent reload procedure.

Command Mode

EXEC

Command Syntax

show version [INFO_LEVEL]

Parameters

INFO_LEVEL Specifies information the command displays. Options include:

no parameter Model and serial numbers, manufacturing data, uptime, and memory.
detail Data listed no parameter option plus version numbers of internal components.

Related Command

show module displays model and serial numbers of modular system components.

Example

This command displays the switch’s model number, serial number, hardware and software manufacturing information, uptime, and memory capacity.

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

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

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

switch>

terminal length

The terminal length command overrides automatic pagination and sets pagination length for all show commands on a terminal. If the output of a show command is longer than the configured terminal length, the output will be paused after each screenful of output, prompting the user to continue.

To disable pagination for an SSH session, set terminal length to 0. By default, all console sessions have pagination disabled.

The no terminal length and default terminal length commands restore automatic pagination by removing the terminal length command from running-config.

The pagination setting is persistent if configured from Global Configuration mode. If configured from EXEC mode, the setting applies only to the current CLI session. Pagination settings may also be overridden when you adjust the size of the SSH terminal window, but can be reconfigured by running the terminal length command again.

Command Mode

EXEC

Command Syntax

terminal length lines

no terminal length

default terminal length

Parameters

lines number of lines to be displayed at a time. Values range from 0 through 32767. A value of 0 disables pagination.

Examples

This command sets the pagination length for the current terminal session to 10 lines.
```
switch# terminal length 10
Pagination set to 10 lines.
```
This command configures the switch to paginate terminal output automatically based on screen size for the current terminal session.
```
switch# no terminal length
```

These commands disable pagination globally.

switch# configure
switch(config)# terminal length 0
Pagination disabled.

terminal monitor

The terminal monitor command enables the display of logging output on the terminal during the current terminal session. This command affects only the local monitor. The no terminal monitor command disables direct monitor display of logging output for the current terminal session.

Command Mode

Privileged EXEC

Command Syntax

terminal monitor

no terminal monitor

default terminal monitor

Example

This command enables the display of logging to the local monitor during the current terminal session.

switch# terminal monitor
switch#

trigger

The trigger command specifies what event will trigger the event handler. Handlers can be triggered either by the system booting or by a change in a specified interface’s IP address or operational status.

To specify the action to be taken when the handler is triggered, use the action bash command.

Command Mode

Event-Handler Configuration

Command Syntax

trigger EVENT

Parameters

EVENT event which will trigger the configuration mode event handler. Values include:
- onboot triggers when the system reboots, or when you exit event-handler configuration mode. This option takes no further arguments, and passes no environment variables to the action triggered.
  - on-intf INTERFACE CHANGE triggers when a change is made to the specified interface.
  - on-startup-config triggers when a change is made to the startup-config file.
  - vm-tracer vm triggers when a virtual machine monitored by VM Tracer changes state.
INTERFACE the triggering interface. Values include:
- ethernet number Ethernet interface specified by number.
- loopback number loopback interface specified by number.
- management number management interface specified by number.
- port-channel number channel group interface specified by number.
- vlan numver VLAN interface specified by number.
CHANGE the change being watched for in the triggering interface. Values include:
- ip triggers when the IPv4 address of the specified interface is changed.
- ip6 triggers when the IPv6 address of the specified interface is changed.
- operstatus triggers when the operational status of the specified interface changes.

Examples

This command configures the event handler Eth5 to be triggered when there is a change in the operational status or IP address of Ethernet interface 5.
```
switch(config-handler-Eth5)# trigger on-intf Ethernet 5 operstatus ip
switch(config-handler-Eth5)#
```
This command configures the event handler “onStartup” to be triggered when the system boots, or on exiting event-handler configuration mode.
```
switch(config-handler-onStartup)# trigger onboot
switch(config-handler-onStartup)#
```

Boot LoaderAboot

Aboot is the boot loader for Arista switches. In addition to booting the switch EOS, Aboot provides a shell for changing boot parameters, restoring default switch settings, diagnosing hardware problems, and managing switch files. Aboot Shell describes the Aboot shell.

The boot process loads an EOS image file, initiates switch processes, performs self-tests, restores interface settings, and configures other network parameters. The replacement image file can be in the switch’s flash or on a device in the flash drive port. Configuration files stored in flash memory specify boot parameters.

Aboot supports most available USB flash drive models. The flash drive must be formatted using the FAT or VFAT file system. Windows NT File System (NTFS) is not supported.

Aboot initiates a system reboot upon a reload command or by restoring power to the switch. Before loading the EOS image file, Aboot provides an option to enter the Aboot shell. The user can either enter the shell to modify boot parameters or allow the switch to boot.

You can monitor the boot process through a terminal connected to the console port. Configuration file settings configure the console port to interact with the terminal.

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:

It ignores the file contents. Providing an empty text file is sufficient.
If the USB drive contains a boot-config file, the 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 has a current timestamp 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

Installation Commands (Aboot)

install bios source
PASSWORD (ABOOT)
SWI

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

Page 15 of 16

End of Support

EOS 4.34.0F User Manual - Managing EOS Extensions

Managing EOS Extensions

Installing EOS Extensions

Installing EOS Extensions on a Dual-Supervisor Switch

Verifying EOS Extensions Installation

Uninstalling an EOS Extension

EOS 4.34.0F User Manual - Switch Administration Commands

Switch Administration Commands

Switch Name Configuration Commands

Banner Configuration Commands

Prompt Configuration Command

Event Manager Commands

Email Configuration Command

System Clock Commands

NTP Commands

Syslog Configuration Commands

Power Configuration Commands

banner login

banner motd

clear ptp interface counters

clock set

clock timezone

dns domain

email

event-monitor backup max-size

event-monitor backup path

event-monitor buffer max-size

event-monitor clear

event-monitor sync

event-monitor

hostname

ip domain lookup

ip domain-list

ip host

ip name-server

ipv6 host

logging format

logging persistent

logging repeat-messages

no event-monitor

ntp authenticate

ntp authentication-key

ntp local-interface

ntp serve all

ntp serve

ntp server

ntp trusted-key

power enable module

prompt

show banner

show clock

show event-monitor arp

show event-monitor igmpsnooping

show event-monitor mac

show event-monitor mroute

show event-monitor neighbor

show event-monitor route6

show event-monitor route

show event-monitor sqlite

show event-monitor stpunstable

show hostname

show hosts

show ip domain-name

show ip name-server

show local-clock time-properties

show ntp associations

show ntp status

EOS 4.34.0F User Manual - Overview

Overview

New Features

Switch Platforms

Open-Source Licenses

CloudVision

Supported Features

EOS 4.34.0F User Manual - Command-Line Interface (CLI)

Command-Line Interface (CLI)

Accessing the EOS CLI

Processing Commands

Command Execution