End of Support

Configuring and Viewing Environment Settings

This section contains the following topics:

Overriding Automatic Shutdown
Viewing Environment Status
Locating Components on the Switch

Overriding Automatic Shutdown

This section contains the following topics:

Overheating
Insufficient Fans
Fan Speed

Overheating

The switch can be configured to continue operating during temperature shutdown conditions. Ignoring a temperature shutdown condition is strongly discouraged because operating at high temperatures can damage the switch and void the warranty.

Temperature shutdown condition actions are specified by the environment overheat action command. The switch displays this warning when configured to ignore shutdown temperature conditions.

switch(config)# environment overheat action ignore
====================================================================
WARNING: Overriding the system shutdown behavior when the system
is overheating is unsupported and should only be done under
the direction of an Arista Networks engineer. You risk damaging
hardware by not shutting down the system in this situation, and doing
so without direction from Arista Networks can be grounds for voiding
your warranty. To re-enable the shutdown-on-overheat behavior, use
the 'environment overheat action shutdown' command.
====================================================================
switch(config)#

The running-config contains the environment overheat action command when set to ignore. When the command is not in running-config, the switch shuts down when an overheating condition exists.

The following running-config file lists the environment overheat action command.

switch# show running-config
! Command: show running-config
! device: switch (DCS-7150S-64-CL, EOS-4.13.2F)


ip route 0.0.0.0/0 10.255.255.1
!
environment overheat action ignore
!
!
end

Insufficient Fans

The switch can be configured to ignore the insufficient fan shutdown condition. This is strongly discouraged because continued operation without sufficient cooling may lead to a critical temperature condition that can damage the switch and void the warranty.

Insufficient-fans shutdown override is configured by the environment insufficient-fans action command. The switch displays this warning when configured to ignore insufficient-fan conditions.

switch(config)# environment insufficient-fans action ignore
====================================================================
WARNING: Overriding the system shutdown behavior when the system
has insufficient fans inserted is unsupported and should only be done 
under
the direction of an Arista Networks engineer. You risk damaging
hardware by not shutting down the system in this situation, and doing
so without direction from Arista Networks can be grounds for voiding
your warranty. To re-enable the shutdown-on-overheat behavior, use
the 'environment insufficient-fans action shutdown' command.
====================================================================
switch(config)#

The running-config contains the environment insufficient-fans action command when set to ignore. When running-config does not contain this command, the switch shuts down when it detects an insufficient-fans condition.

Fan Speed

The switch can be configured to override the automatic fan speed. The switch normally controls the fan speed to maintain optimal operating temperatures. The fans can be configured to operate at a constant speed regardless of the switch temperature conditions.

Fan speed override is configured by the environment fan-speed command. The switch displays this warning when its control of fan speed is overridden.

switch(config)# environment fan-speed override 50
====================================================================
WARNING: Overriding the system fan speed is unsupported and should only
be done under the direction of an Arista Networks engineer.
You can risk damaging hardware by setting the fan speed too low
and doing so without direction from Arista Networks can be grounds
for voiding your warranty.
To set the fan speed back to automatic mode, use the
'environment fan-speed auto' command
====================================================================
switch(config)#

The running-config contains the environment fan-speed override command if it is set to override. When running-config does not contain this command, the switch controls the fan speed.

Viewing Environment Status

This section contains the following topics:

Power Status
Temperature Status
Fan Status
System Status

Power Status

The show environment power command displays the status of the power supplies.

Example

This command displays the status of the power supplies.

switch> show environment power
Power Input Output Output
Supply  Model         Capacity  Current  Current  Power    Status
------- ------------- --------- -------- -------- -------- -------
1       PWR-650AC      650W      0.44A    10.50A  124.0W   Ok

Temperature Status

To display internal temperature sensor status, enter show environment temperature.

switch> show environment temperature
System temperature status is: Ok
                                               Alert      Critical
Sensor  Description               Temperature  Threshold  Threshold
------- ------------------------- ------------ ---------- ----------
1       Front-panel temp sensor   22.000C       65C        75C
2       Fan controller 1 sensor   23.000C       75C        85C
3       Fan controller 2 sensor   28.000C       75C        85C
4       Switch chip 1 sensor      40.000C       105C       115C
5       VRM 1 temp sensor         48.000C       105C       110C

System temperature status is the first line that the command displays. System temperature status values indicate the following:

Ok: All sensors report temperatures below the alert threshold.
Overheating: At least one sensor reports a temperature above its alert threshold.
Critical: At least one sensor reports a temperature above its critical threshold.
Unknown: The switch is initializing.
Sensor Failed: At least one sensor is not functioning.

Fan Status

The show system environment cooling command displays the cooling and fan status.

Example

This command displays the fan and cooling status:

switch> show system environment cooling
System cooling status is: Ok
Ambient temperature: 22C
Airflow: port-side-intake
Fan Tray  Status          Speed
--------- --------------- ------
1 Ok 35%
2 Ok 35%
3 Ok 35%
4 Ok 35%
5 Ok 35%
switch>

System Status

The show system environment all command lists the temperature, cooling, fan, and power supply information the individual show environment commands display, as described in Temperature Status, Fans, and Power.

Example

This command displays the temperature, cooling, fan, and power supply status:

switch> show system environment all
System temperature status is: Ok
                                               Alert      Critical
Sensor  Description              Temperature   Threshold  Threshold
------- ------------------------ ------------- ---------- ----------
1       Front-panel temp sensor   22.750C       65C        75C
2       Fan controller 1 sensor   24.000C       75C        85C
3       Fan controller 2 sensor   29.000C       75C        85C
4       Switch chip 1 sensor      41.000C       105C       115C
5       VRM 1 temp sensor         49.000C       105C       110C

System cooling status is: Ok
Ambient temperature: 22C
Airflow: port-side-intake
Fan Tray  Status           Speed
--------- --------------- ------
1         Ok                 35%
2         Ok                 35%
3         Ok                 35%
4         Ok                 35%
5         Ok                 35%

Power                         Input    Output   Output
Supply  Model       Capacity  Current  Current  Power    Status
------- ----------- --------- -------- -------- -------- -------
1       PWR-650AC   650W       0.44A   10.50A   124.0W   Ok

Locating Components on the Switch

When a component requires service, the switch administrator may use the locator-led command to assist a technician in finding the component. The command causes the status LED on the specified component to flash and display a “service requested” message on the LCD panel of modular switches or lights the blue locator light on the front of fixed switches. Use the show locator-led command to display all locator LEDs currently enabled on the switch.

Examples

This command enables the locator LED on fan tray 3:

switch# locator-led fantray 3
Enabling locator led for FanTray3

This command displays all locator LEDs enabled on the switch:
```
switch# show locator-led
There are no locator LED enabled
```

Environment Commands

Environment Control Configuration Commands

environment fan-speed
environment insufficient-fans action
environment overheat action
locator-led

environment fan-speed

The environment fan-speed command determines how to control the speed of the switch fans. By default, the switch automatically controls the fan speed.

The switch normally controls the fan speed to maintain optimal operating temperatures. The fans can be configured to operate at a constant speed regardless of the switch temperature conditions.

The no environment fan-speed and default environment fan-speed commands restore the default action of automatic fan-speed control by removing the environment fan-speed override statement from running-config.

Note: Overriding the system fan speed is unsupported and should only be done under the direction of an Arista Networks engineer. You can risk damaging hardware by setting the fan speed too low. Doing so without direction from Arista Networks can be grounds for voiding your warranty.

Command Mode

Global Configuration

Command Syntax

environment fan-speed ACTION

no environment fan-speed

default environment fan-speed

Parameters

ACTION Fan speed control method. Valid settings include:

auto Fan speed is controlled by the switch.
This option restores the default setting by removing the environment fan-speed override command from running-config
override percent Fan speed is set to the specified percentage of the maximum. Valid percent settings range from 30 to 100.

Examples

This command overrides the automatic fan speed control and configures the fans to operate at 50% of maximum speed.

switch(config)# environment fan-speed override 50
====================================================================
WARNING: Overriding the system fan speed is unsupported and should 
only be done under the direction of an Arista Networks engineer.
You can risk damaging hardware by setting the fan speed too low
and doing so without direction from Arista Networks can be grounds
for voiding your warranty.
To set the fan speed back to automatic mode, use the
'environment fan-speed auto' command
====================================================================
switch(config)#

This command restores control of the fan speed to the switch.
```
switch(config)# environment fan-speed auto
switch(config)#
```

environment insufficient-fans action

The environment insufficient-fans command controls the switch response to the insufficient fan condition. By default, the switch initiates a shutdown procedure when it senses insufficient fans.

The switch operates normally when one fan is not operating. Non-functioning modules should only be removed from the switch if they are immediately replaced; adequate switch cooling requires the installation of all components, including a non-functional fan.

Two non-operational fans trigger an insufficient fan shutdown condition. This condition normally initiates a power-down procedure.

The no environment insufficient-fans and default environment insufficient-fans commands restore the default shutdown response to the insufficient-fans condition by removing the environment insufficient-fans action ignore statement from running-config.

Note: Overriding the system shutdown behavior when the system has insufficient fans inserted is unsupported and should only be done under the direction of an Arista Networks engineer. You risk damaging hardware by not shutting down the system in this situation, and doing so without direction from Arista Networks can be grounds for voiding your warranty.

Command Mode

Global Configuration

Command Syntax

environment insufficient-fans action REMEDY

no environment insufficient-fans action

default environment insufficient-fans action

Parameters

REMEDY Configures action when the switch senses an insufficient fan condition. Settings include:

ignore Switch continues operating when insufficient fans are operating.
shutdown Switch shuts the power down when insufficient fans are operating.
The shutdown parameter restores default behavior by removing the environment insufficient-fans command from running-config.

Examples

This command configures the switch to continue operating after it senses insufficient fan condition.

switch(config)# environment insufficient-fans action ignore
====================================================================
WARNING: Overriding the system shutdown behavior when the system
has insufficient fans inserted is unsupported and should only be done 
under the direction of an Arista Networks engineer. You risk damaging
hardware by not shutting down the system in this situation, and doing
so without direction from Arista Networks can be grounds for voiding
your warranty. To re-enable the shutdown-on-overheat behavior, use
the 'environment insufficient-fans action shutdown' command.
====================================================================

This command configures the switch to shut down when it senses an insufficient fan condition.
```
switch(config)# environment insufficient-fans action shutdown
switch(config)#
```

environment overheat action

The environment overheat command controls the switch's response to an overheat condition. By default, the switch shuts down when it senses an overheat condition.

Note: Overriding the system shutdown behavior when the system is overheating is unsupported and should only be done under the direction of an Arista Networks engineer. You risk damaging hardware by not shutting down the system in this situation, and doing so without direction from Arista Networks can be grounds for voiding your warranty.

Arista switches include internal temperature sensors. The number and location of the sensors vary with each switch model. Each sensor is assigned temperature thresholds that denote alert and critical conditions. Temperatures that exceed the threshold trigger the following:

Alert Threshold: All fans run at maximum speed, and a warning message is logged.
Critical Threshold: The component is shut down immediately, and its Status LED flashes orange.

In modular systems, cards are shut down when their temperatures exceed the critical threshold. The switch normally shuts down if the temperature remains above the critical threshold for three minutes.

The no environment overheat action, and default environment overheat action commands restore the default shutdown response to the environment overheat condition by removing the environment overheat action ignore statement from running-config.

Command Mode

Global Configuration

Command Syntax

environment overheat action REMEDY

no environment overheat action

default environment overheat action

Parameters

REMEDY Reaction to an overheat condition. The default value is shutdown.

shutdown Switch shuts power down by an overheat condition.
ignore Switch continues operating during an overheat condition.

Examples

This command configures the switch to continue operating after it senses an overheat condition.

switch(config)# environment overheat action ignore
====================================================================
WARNING: Overriding the system shutdown behavior when the system
is overheating is unsupported and should only be done under
the direction of an Arista Networks engineer. You risk damaging
hardware by not shutting down the system in this situation, and doing
so without direction from Arista Networks can be grounds for voiding
your warranty. To re-enable the shutdown-on-overheat behavior, use
the 'environment overheat action shutdown' command.
====================================================================
switch(config)#

This command configures the switch to shut down when it senses an overheat condition.
```
switch(config)# environment overheat action shutdown
switch(config)#
```

locator-led

When a component requires service, the locator-led command activates a locator to assist a technician in finding the component. The command causes the status LED on the specified component to flash and display a “service requested” message on the LCD panel of modular switches or lights the blue locator light on the front of fixed switches. The available locators vary by platform; to see a list of the locator LEDs available on the switch, use the locator-led ? command. To trun off the locator LED, use the no locator-led command.

Command Mode

Privileged EXEC

Command Syntax

locator-led {fantray tray_num | interface interface | module module_num | powersupply supply_num}

no locator-led {fantray tray_num | interface interface | module module_num | powersupply supply_num}

Parameters

fantray tray_num Activates the locator LED on specified fan tray.
interface interface Activates the locator LED on specified interface.
module module_num Activates the locator LED on specified module.
powersupply supply_num Activates the locator LED on specified power supply.

Examples

This command enables the locator LED on fantray 3.

switch# locator-led fantray 3
Enabling locator led for FanTray3

This command disables the locator LED on fantray 3.

switch# no locator-led fantray 3
Disabling locator led for FanTray3

This command displays the locator LEDs available on the switch.

switch# locator-led ?
  fantray      Fan tray LED
  interface    Interface LED
  module       Module LED
  powersupply  Power supply LED

show environment power

The show environment power command displays the status of all power supplies in the switch.

Command Mode

EXEC

Command Syntax

show environment power [INFO_LEVEL]

Parameters

INFO_LEVEL Specifies level of detail that the command displays. Options include:

no parameter Displays current and power levels for each supply.
detail Also includes status codes that can report error conditions.

Example

This command displays the status of power supplies on the switch.

switch> show environment power
Power                        Input    Output   Output
Supply  Model      Capacity  Current  Current  Power    Status
------- ---------- --------- -------- -------- -------- -------
1       PWR-760AC  760W       0.81A    11.00A   132.8W   Ok
2       PWR-760AC  760W       0.00A    0.00A    0.0W AC  Loss

show environment temperature

The show environment temperature command displays the operating temperature of all sensors on the switch.

Command Mode

EXEC

Command Syntax

show environment temperature [MODULE_NAME] [INFO_LEVEL]

Parameters

MODULE_NAME Specifies modules for which data is displayed. This parameter is only available on modular switches. 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 Line card 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 line card (3 to 18) module.
- all All modules.
INFO_LEVEL Specifies level of detail that the command displays. Options include:
- no parameter Displays table that lists the temperature and thresholds of each sensor.
- detail Displays data block for each sensor listing the current temperature and historic data.

Display Values

System temperature status is the first line that the command displays. Values report the following:

Ok All sensors report temperatures below the alert threshold.
Overheating At least one sensor reports a temperature above its alert threshold.
Critical At least one sensor reports a temperature above its critical threshold.
Unknown The switch is initializing.
Sensor Failed At least one sensor is not functioning.

Examples

This command displays a table that lists the temperature measured by each sensor.

switch> show environment temperature
System temperature status is: Ok
                                              Alert      Critical
Sensor  Description              Temperature  Threshold  Threshold
------- ------------------------ ------------ ---------- ----------
1       Front-panel temp sensor   30.750C       65C        75C
2       Fan controller 1 sensor   32.000C       75C        85C
3       Fan controller 2 sensor   38.000C       75C        85C
4       Switch chip 1 sensor      50.000C       105C       115C
5       VRM 1 temp sensor         60.000C       105C       110C
switch>

This command lists the temperature detected by each sensor and includes the number of previous alerts, the time of the last alert, and the time of the last temperature change.

switch> show environment temperature detail
TempSensor1 - Front-panel temp sensor
                       Current State   Count    Last Change
  Temperature          30.750C
  Max Temperature      35.000C                  4 days, 23:35:24 ago
  Alert                 False           0        never

TempSensor2 - Fan controller 1 sensor
                       Current State    Count    Last Change
  Temperature           32.000C
  Max Temperature       36.000C                  4 days, 23:32:46 ago
  Alert                  False           0        never

TempSensor3 - Fan controller 2 sensor
                        Current State    Count     Last Change
  Temperature            38.000C
  Max Temperature        41.000C                   4 days, 23:37:56 ago
  Alert                  False            0        never

TempSensor4 - Switch chip 1 sensor
                         Current State    Count    Last Change
  Temperature            51.000C
  Max Temperature        53.000C                    4 days, 23:35:16 ago
  Alert                  False              0       never

TempSensor5 - VRM 1 temp sensor
                          Current State     Count    Last Change
  Temperature             60.000C
  Max Temperature         62.000C                    4 days, 22:54:51 ago
  Alert                   False             0        never

show locator-led

The show locator-led command displays the status of locator LEDs enabled on the switch.

Command Mode

Privileged EXEC

Command Syntax

show locator-led

Example

This command displays all locator LEDs enabled on the switch.

switch# show locator-led
There are no locator LED enabled
switch#

show system environment all

The show system environment all command displays temperature, cooling, and power supply status.

Command Mode

EXEC

Command Syntax

show system environment all

Example

This command displays the switch’s temperature, cooling, and power supply status

switch> show system environment all
System temperature status is: Ok
                                              Alert      Critical
Sensor  Description              Temperature  Threshold  Threshold
------- ------------------------ ------------- ---------- ----------
1       Front-panel temp sensor   31.000C       65C        75C
2       Fan controller 1 sensor   32.000C       75C        85C
3       Fan controller 2 sensor   38.000C       75C        85C
4       Switch chip 1 sensor      50.000C       105C       115C
5       VRM 1 temp sensor         60.000C       105C       110C

System cooling status is: Ok
Ambient temperature: 31C
Airflow: port-side-intake
Fan Tray  Status           Speed
--------- --------------- ------
1         Ok                 52%
2         Ok                 52%
3         Ok                 52%
4         Ok                 52%
5         Ok                 52%

Power                         Input    Output   Output
Supply  Model       Capacity  Current  Current  Power    Status
------- ----------- --------- -------- -------- -------- -------
1       PWR-760AC    760W     0.81A    11.00A    132.6W  Ok
2       PWR-760AC    760W     0.00A     0.00A      0.0W  AC Loss

show system environment cooling

The show system environment cooling command displays fan status, air flow direction, and ambient temperature on the switch.

Command Mode

EXEC

Command Syntax

show system environment cooling [INFO_LEVEL]

Parameters

INFO_LEVEL Specifies level of detail that the command displays. Options include:
- no parameter Displays the fan status, air flow direction, and ambient switch temperature.
- detail Also displays actual and configured fan speed of each fan.

Status

System Cooling Status
- Ok No more than one fan has failed or is not inserted.
- Insufficient fans More than one fan has failed or is not inserted. This status is also displayed if fans with different airflow directions are installed. The switch shuts down if the error is not resolved.
- Ambient temperature Temperature of the surrounding area.
- Airflow Indicates the direction of the installed fans:
  - port-side-intake All fans flow air from the front (port side) to the rear of the chassis.
  - port-side-exhaust All fans flow air from the rear to the front (port side) of the chassis.
  - incompatible fans Fans with different airflow directions are inserted.
  - Unknown The switch is initializing.
Fan Tray Status table Displays the status and operating speed of each fan. Status values indicate the following conditions:
- OK The fan is operating normally.
- Failed The fan is not operating normally.
- Unknown The system is initializing.
- Not Inserted The system is unable to detect the specified fan.
- Unsupported The system detects a fan that the current software version does not support.

Example

This command displays the fan status, air flow direction, and ambient switch temperature.

switch> show system environment cooling
System cooling status is: Ok
Ambient temperature: 30C
Airflow: port-side-intake
Fan Tray  Status           Speed
--------- --------------- ------
1         Ok                 51%
2         Ok                 51%
3         Ok                 51%
4         Ok                 51%
5         Ok                 51%

show system environment power budget

The show system environment power budget command displays the configured power budget for PoE switches and a table to show the current consumption.

Command Mode

EXEC

Command Syntax

show system environment power budget

Example

This command displays the configured power budget for a PoE switch and a table to show the current consumption.

switch> show system environment power budget
Budget is 300.0W out of 1425.2W of total power
Active devices using up to 60.0W

Device                  Consumed               
Name                    Power                  
----------------------- -----------------------
Ethernet37              30.0W                  
Ethernet38              30.0W                  
Total                   60.0W

Upgrades and Downgrades

This chapter describes the procedures for upgrading or downgrading the switch software.

This chapter contains these sections:

Upgrade/Downgrade Overview

Upgrading or downgrading the Arista Extensible Operating System (EOS) is accomplished by replacing the EOS image and reloading the switch. It may be possible to minimize (or virtually eliminate) downtime and packet loss during an upgrade, depending on the switch model and the software change being made. There are two upgrade methods for the EOS:

Smart System Upgrade: SSU significantly decreases downtime and packet loss during upgrades. SSU is available on selected platforms and is ideal for leaf switches and other non-redundant deployments.

Standard Upgrades and Downgrades: In cases where an accelerated upgrade is not needed or an option (such as software downgrades and on unsupported platforms), performing a standard upgrade or downgrade using the steps described here will minimize downtime and packet loss.

Note: To upgrade the software on switches participating in an MLAG, see Upgrading MLAG Peers.

Smart System Upgrade

Smart System Upgrade (SSU) dramatically speeds up system upgrades and minimizes network disruptions with:

Faster Reloads: SSU streamlines and optimizes the upgrade process, significantly reducing the reload time.
Uninterrupted Connections: Even while the system reboots, SSU keeps your network connections active by sending LACP PDUs. These PDUs are essential signals that maintain port channels, ensuring your devices stay connected.
Minimal Traffic Loss: SSU uses protocols that support "graceful restart," allowing network services to restart without dropping connections, preventing interruptions to your data flow.

Features capable of hitless restart under SSU include:

QinQ
802.3ad Link Aggregation/LACP
802.3x Flow Control
BGP (you must enable BGP graceful restart; refer to Configuring BGP.)
MP-BGP (you must enableBGP graceful restart; refer to Configuring BGP.)
128-way Equal Cost Multipath Routing (ECMP)
VRF
Route Maps
L2 MTU
MLAG (you must configure reload delay; refer to Configuring MLAG.)
QoS

Note: SSU and VRRP are not compatible. Use a different upgrade method if you have VRRP configured on the switch.

Upgrading the EOS image with Smart System Upgrade

Using SSU to upgrade the active EOS image requires a five-step process:

Preparing the Switch for SSU.
Transfer the Image File for SSU. Not required if the desired file already exists on the switch
Modify boot-config.
Start the SSU Process.
Verify Success of the Upgrade.

Preparing the Switch for SSU

To prepare the switch for SSU, use the following steps:

Note: Configuring BGP graceful restart resets BGP sessions. If configuring BGP graceful restart as part of the SSU process, ensure you have stable BGP sessions are stable and all BGP routing information has been learned and advertised before proceeding with SSU.

Backing Up Critical Software

Before upgrading the EOS image, be sure you have copies of the currently running EOS version and the running-config file available in case of corruption during the upgrade process. To copy the running-config file, use the copy running-config command. In this example, the system copies the running-config contents to a file on the switch flash drive.

switch# copy running-config flash:/cfg_06162014
Copy completed successfully.
switch#

Making Room on the Flash Drive

Determine the size of the new EOS image. Verify enough space exists on the flash drive for two copies of this image, plus a recommended 240MB (if available) for diagnostic information in case of a fatal error. Use the dir command to check the bytes free figure.

switch# dir flash:
Directory of flash:/
-rwx   293168526      Nov 4    22:17   EOS4.11.0.swi
-rwx          36      Nov 8    10:24   boot-config
-rwx       37339      Jun 16   14:18   cfg_06162014

606638080 bytes total (602841088 bytes free)

Verifying Connectivity

Ensure the switch has a management interface configured with an IP address and default gateway. See Assigning a Virtual IP Address to Access the Active Ethernet Management Port and Configuring a Default Route to the Gateway. Confirm network connectivity to the switch using the show interfaces status command and pinging the default gateway.

switch# show interfaces status
Port    Name     Status     Vlan       Duplex   Speed      Type
Et3/1            notconnect   1         auto    auto     1000BASE-T

<-------OUTPUT OMITTED FROM EXAMPLE-------->
Ma1/1            connected   routed     unconf   unconf    Unknown 

switch# ping 1.1.1.10
PING 172.22.26.1 (172.22.26.1) 72(100) bytes of data.
80 bytes from 1.1.1.10: icmp_seq=1 ttl=64 time=0.180 ms
80 bytes from 1.1.1.10: icmp_seq=2 ttl=64 time=0.076 ms
80 bytes from 1.1.1.10: icmp_seq=3 ttl=64 time=0.084 ms
80 bytes from 1.1.1.10: icmp_seq=4 ttl=64 time=0.073 ms
80 bytes from 1.1.1.10: icmp_seq=5 ttl=64 time=0.071 ms

Verifying Configuration

Verify the switch has a valid configuration for SSU using the show reload fast-boot command. If parts of the configuration block SSU execution, an error message displays explaining the issues. For SSU to proceed, correct the configuration conflicts before issuing the reload fast-boot command.

switch# show reload fast-boot
switch#'reload fast-boot' cannot proceed due to the following:
  Spanning-tree portfast is not enabled for one or more ports
  Spanning-tree BPDU guard is not enabled for one or more ports
switch#

Note: You can still use the show reload hitless and reload hitless commands, but they have the same effect as the commands shown earlier.

Configuring BGP

For hitless restart of BGP and MP-BGP, BGP graceful restart must first be enabled using the graceful-restart command. The default restart time value (300 seconds) is appropriate for most configurations.

The BGP configuration mode issuing the graceful-restart command determines which BGP connections will restart gracefully.

Note: Configuring BGP graceful restart resets BGP sessions. If configuring BGP graceful restart as part of the SSU process, be sure you have stable BGP sessions and all BGP routing information has been learned and advertised before proceeding with SSU.

For all BGP connections, use the graceful-restart command in BGP configuration mode:

switch# config
switch(config)# router bgp 64496
switch(config-router-bgp)# graceful-restart
switch(config-router-bgp)#

For all BGP connections in a specific VRF, use the graceful-restart command in BGP VRF configuration mode:

switch# config
switch(config)# router bgp 64496
switch(config-router-bgp)# vrf purple
switch(config-router-bgp-vrf-purple)# graceful-restart
switch(config-router-bgp-vrf-purple)# exit
switch(config-router-bgp)#

For all BGP connections in a specific BGP address family, use the graceful-restart command in BGP address-family configuration mode:

switch# config
switch(config)# router bgp 64496
switch(config-router-bgp)# address-family ipv6
switch(config-router-bgp-af)# graceful-restart
switch(config-router-bgp-af)# exit
switch(config-router-bgp)#

Configuring MLAG

Before performing a hitless upgrade on switches configured with MLAG, configure the reload-delay parameter to 0 using the following commands:

switch(config)# mlag
switch(config-mlag)# reload-delay 0

Note: To minimize the traffic disruption during MLAG SSU, all links remain up to let traffic flow during the upgrade process.

If performing the upgrade on the primary MLAG switch, the switch first transitions to the secondary MLAG switch and becomes the primary switch.

All MLAG port channel interfaces with STP enabled shutdown locally on the MLAG peer undergoing the upgrade.

Transfer the Image File for SSU

The target image must be copied to the file system on the switch, typically onto the flash drive:

Verify that the flash drive has enough space for two copies of the image plus an optional 240MB for diagnostic information.
Use the copy command to copy the image to the flash drive.
Confirm that the system transferred the new image file correctly.

The following command examples illustrate transferring an image file from various locations to the flash drive.

USB Memory

Command

copy usb1:/sourcefile flash:/destfile

Example

switch# copy usb1:/EOS-4.14.4.swi flash:/EOS-4.14.4.swi

FTP Server

Command

copy ftp:/ftp-source/sourcefile flash:/destfile

Example

switch# copy ftp:/user:password@10.0.0.3/EOS-4.14.4.swi flash:/EOS-4.14.4.swi

SCP

Command

copy scp://scp-source/sourcefile flash:/destfile

Example

switch# copy scp://user@10.1.1.8/user/EOS-4.13.2.swi flash:/EOS-4.13.2.swi

HTTP

Command

copy http://http-source/sourcefile flash:/destfile

Example

switch# copy http://10.0.0.10/EOS-4.14.4.swi flash:/EOS-4.14.4.swi

After transferring the file, verify that it is present in the directory, then confirm the MD5 checksum using the verify command. The MD5 checksum is available from the EOS download page of the Arista website.

switch# dir flash:
Directory of flash:/
-rwx     293168526   Nov 4     22:17     EOS4.14.2.swi
-rwx            36   Nov 8     10:24     boot-config
-rwx         37339   Jun 16    14:18     cfg_06162014
-rwx     394559902   May 30    02:57     EOS4.13.1.swi

606638080 bytes total (208281186 bytes free)
switch# verify /md5 flash:EOS-4.14.4.swi 
verify /md5 (flash:EOS-4.14.4.swi) =c277a965d0ed48534de6647b12a86991

Modify boot-config

After transferring and confirming the desired image file, use the boot system command to update the boot-config file to point to the new EOS image.

This command changes the boot-config file to point to the image file located in flash memory at EOS-4.14.4.swi.

switch# configure terminal
switch(config)# boot system flash:/EOS-4.14.4.swi

Use the show boot-config command to verify that the boot-config file is correct:

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

Save the configuration to the startup-config file with the write command.

switch# write

Start the SSU Process

After updating the boot-config file, verify that your configuration supports SSU (if you have not already done so) using the show reload fast-boot command. If parts of the configuration are blocking SSU execution, an error message will be displayed explaining what they are.

switch# show reload fast-boot
switch#'reload fast-boot' cannot proceed due to the following:
  Spanning-tree portfast is not enabled for one or more ports
  Spanning-tree BPDU guard is not enabled for one or more ports

Start the SSU process using the reload fast-boot command to reload the switch and activate the new image. The CLI will identify any changes that must be made to the configuration before starting SSU, prompt the saving of any modifications to the system configuration, and request confirmation before reloading.

switch# reload fast-boot
System configuration has been modified. Save? [yes/no/cancel/diff]:y
Copy completed successfully.
Proceed with reload? [confirm]y

Note: You can still use the show reload hitless and reload hitless commands, but they have the same effect as the commands shown earlier.

Verify Success of the Upgrade

Before making any configuration changes to the switch after reloading, verify that the SSU process is complete using the command show boot stages log. If it is, the last message should be Hitless boot stages complete.

switch# show boot stages log
Timestamp           Delta Begin Msg
2022-10-03 12:42:06 000.000000 Asu Hitless boot stages started
2022-10-03 12:42:06 000.001592 stage CriticalAgent started
2022-10-03 12:42:06 000.001834   event CriticalAgent:PhyEthtool completed

[ . . . ]

2022-10-03 12:43:02 056.316874 stage BootSanityCheck is complete
2022-10-03 12:43:02 056.317491 Asu Hitless boot stages complete

You can also verify the completion of the SSU process by checking the syslog for the following message:

LAUNCHER-6-BOOT_STATUS: 'reload fast-boot' reconciliation complete

To verify whether the SSU upgrade was successful, use the show reload cause command. Suppose a fatal error occurred during the upgrade process. In that case, the switch will have completely rebooted, and the fatal error details will be displayed along with the directory containing the diagnostic information.

If the SSU upgrade has succeeded, it will read Hitless reload requested by the user.

Fatal Error Display

switch# show reload cause
Reload Cause 1:
-------------------
Fatal error occurred during Asu Hitless boot. (stageMgr - LinkStatusUpdate timed out)

Reload Time:
------------
Reload occurred at Sun Oct 02 12:06:37 2022 PDT.

Recommended Action:
-------------------
The system rebooted due to a fatal error.
If the problem persists, contact your customer support representative.

Debugging Information:
-------------------------------
/mnt/flash/persist/fatalError-2022-10-02_120637

Successful Upgrade Display

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

Reload Time:
------------
Reload occurred at Mon Oct 03 13:29:31 2022 PDT.

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

Debugging Information:
-------------------------------
None available.

The show version command confirms whether the correct image is loaded. The Software image version: line displays the version of the active image file.

switch# show version
Arista DCS-7050QX-32-F
Hardware version: 02.00
Serial number: JPE14071098
System MAC address: 001c.7355.556f
Software image version: 4.14.5F-2353054.EOS4145F
Architecture: i386
Internal build version: 4.14.5F-2353054.EOS4145F
Internal build ID: e8748ea7-916d-4217-878f-4bfe2adc7122
Uptime: 4 minutes
Total memory: 3981328 kB
Free memory: 1342408 kB

Note: If a fatal error occurs during the SSU process, the new EOS image will still be loaded and booted.

Scheduling an SSU

SSU supports scheduling an upgrade with the reload fast-boot in command. If the switch has unsaved configuration changes, or saved configuration changes that block an SSU upgrade, the scheduled reload stops at the scheduled time.

Configuring a Scheduled SSU Upgrade

Use the reload fast-boot in command to schedule the upgrade at a specific time. The switch detects any unsaved configuration and prompts you to save the changes first. Replying no exits the command and the scheduled upgrade does not proceed.

switch# reload fast-boot in 10:00
System configuration has been modified. Save? [yes/no/cancel/diff]:yes
Copy completed successfully.
Proceed with reload? [confirm]y
Reload scheduled for Mon Jan 20 19:31:09 2025 (in 9 hours 59 minutes)
No warnings or unsupported configuration found.

Specify the time to reboot in hours, for example, 10:00, as shown in the example.

Override the confirmation prompt by adding the optional parameter force and specify a reason using the reason.

switch# reload fast-boot in 10:00 force reason scheduled maintenance
Copy completed successfully.
Reload scheduled for Mon Jun 17 19:38:12 2024 (in 9 hours 59 minutes)
Reload reason: scheduled maintenance
No warnings or unsupported configuration found.

Note: EOS supports only one pending scheduled SSU, either normal or scheduled, at a time. To schedule a new SSU, cancel the existing scheduled SSU.

Canceling a Scheduled SSU

To cancel a scheduled SSU reload, use the reload cancel command:

switch# reload cancel
Scheduled reload has been canceled.

Displaying Scheduled SSU Information

Use the following command to display information about scheduled SSU configurations:

switch# show reload fast-boot
Reload scheduled for Mon Jan 20 19:31:09 2025 (in 9 hours 59 minutes)
Reload reason: scheduled maintenance
No warnings or unsupported configuration found.

If no scheduled reload exists on the switch, the command returns the following output:

switch# show reload fast-boot
No reload is scheduled
No warnings or unsupported configuration found.

7130 Layer 1 Commands

Layer 1 Configuration Commands

l1 source

Layer 1 Show Commands

show l1 destination
show l1 matrix
show l1 path
show l1 source
show l1 source capabilities

l1 source

The l1 source command configures the source for patching Layer 1 traffic between various front panel interfaces and Switch Application (SwitchApp) ports in the Ethernet Interface configuration mode.

The no l1 source and default l1 source commands remove the source configurations and return to the default platform configurations.

Command Mode

Interface-Ethernet Configuration

Command Syntax

l1 source [interface | mac | none]

Parameters

interface patches the Layer 1 traffic from the specified interface.
- Application 1-1 - Application FPGA connector interface
- CPU 1-4 - CPU interface
- Downstream 1-255 - Downstream interface
- Ethernet 1-96 - Ethernet interface
- MuxIn 1-24 - Metamux input interface
- MuxOut 1-24 - Metamux output interface
- Ptp 1-2 - MetaWatch PIP interface
- Switch 1-7 Switch interface
- TrafficGen 1-256 - Traffic Generation interface
- Upstream 1-255 - Upstream interface
- WatchIn 1-255 - WatchIn interface
- WatchOut 1-255 - WatchOut interface
- WatchPassthrough 1-255 - Watch passthrough interface
- WhiteRabbit 1-255 - White Rabbit interface
mac patches the Layer 1 traffic from the specified MAC address.
none unpatches the Layer 1 traffic source.

Examples

This command patches the Layer 1 traffic from the Ethernet interface et2.

switch(config)# interface ethernet1
switch(config-if-Et1)# l1 source interface et2  
switch(config-if-Et1)#

This command unpatches the Layer 1 traffic source.

switch(config)# interface ethernet1
switch(config-if-Et1)# l1 source none

(config)# int sw1/1/1
(config-if-sw1/1/1)# speed 10g
(config-if-sw1/1/1)# int et1/1
(config-if-et1/1)# speed 1g
(config-if-et1/1)# l1 source int sw1/1/1
(config-if-et1/1)# show l1 source int et1/1

Interface           Source Interface       Type
------------------ ---------------------- -------
Ethernet1/1   	                     dynamic

show l1 destination

The show l1 destination command displays the list of all destinations for all interfaces.

Command Mode

Privileged EXEC

Command Syntax

show l1 destination [interface]

Parameters

interface lists the destination interfaces to connect for the specified interface.

application - Application FPGA connector interface.
cpu - CPU interface.
ethernet - Ethernet interface.
switch - Switch interface.

Examples

This command displays the list of all interfaces to connect in the crosspoint and the specific destination ports.

switch> show l1 destination

Interface             Destination Interface(s) Type
------------------    ------------------------ ------
Ethernet1             App1/1, Sw1              dynamic
Ethernet2             Ethernet3, Ethernet4     dynamic
Ethernet3
Ethernet4
Ethernet5
App1/1                Ethernet1                dynamic
App1/2                Sw17                     static
Sw1
Sw2
Sw3
Sw4
Sw5
Sw17                  App1/2                   static
Cpu1
Cpu2

Note: Interfaces without a destination port are listed, but the Destination Interface and Type columns appear as blanks.

This command displays the list of destination interfaces to connect for the Ethernet interface et1.

switch# show l1 destination interface et1
                        
Interface             Destination Interfaces   Type
--------------------- ------------------------ ------
Ethernet1             App1/1, Sw1              dynamic

show l1 matrix

The show l1 matrix command displays the matrix representation of Layer 1 paths for available interfaces in the privileged EXEC mode.

Command Mode

Privileged EXEC

Command Syntax

show l1 matrix [all | interface | detail | physical]

Parameters

all displays the matrix of Layer 1 paths for possible interface types even if they do not have a connection.
interface displays the matrix of Layer 1 paths for the specified interface.
- Application 1-1 - Application FPGA connector interface
- CPU 1-4 - CPU interface
- Downstream 1-255 - Downstream interface
- Ethernet 1-96 - Ethernet interface
- MuxIn 1-24 - Metamux input interface
- MuxOut 1-24 - Metamux output interface
- Ptp 1-2 - MetaWatch PIP interface
- Switch 1-7 Switch interface
- TrafficGen 1-256 - Traffic Generation interface
- Upstream 1-255 - Upstream interface
- WatchIn 1-255 - WatchIn interface
- WatchOut 1-255 - WatchOut interface
- WatchPassthrough 1-255 - Watch passthrough interface
- WhiteRabbit 1-255 - White Rabbit interface
detail displays the detailed matrix of Layer 1 paths.
physical displays the Layer 1 matrix for physical interfaces only.

Examples

This command displays the matrix of Layer 1 paths for all available interface types.

switch> show l1 matrix
Ethernet   Switch     App       
1 3 4      1 17       1/1 1/2      
| | |      | |        |   |            
Et1 -> -|-|-|------+-|--------+   |
Et2 -> -|-+-+        |            | 
Sw17 -> -|------------|------------+
App1/1 -> -+            |
App1/2 -> --------------+

This command displays the matrix of Layer 1 paths for all available interface types even if the interfaces do not have a connection.

switch> show l1 matrix all
Ethernet                                 Switch           
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16   1 2 3 4 5 6 7 8 9 10       
|   | |                                  |         
Et1 -> -|---|-|----------------------------------+
Et2 -> -|---+-+          
Et3 ->  |                  
Et4 ->  |                  
Et5 ->  |            
Et6 ->  |              
Et7 ->  |                   
Et8 ->  |                 
Et9 ->  |               
Et10 ->  |                 
Et11 ->  |               
Et12 ->  |                 
Et13 ->  |            
Et14 ->  |              
Et15 ->  |              
Et16 ->  |              
Sw1 ->  |                
Sw2 ->  |               
Sw3 ->  |               
Sw4 ->  |                
Sw5 ->  |      
Sw6 ->  |             
Sw7 ->  |             
Sw8 ->  |           
Sw9 ->  |            
Sw10 ->  |            
Sw11 ->  |            
Sw12 ->  |                 
Sw13 ->  |         
Sw14 ->  |          
Sw15 ->  |              
Sw16 ->  |        
Sw17 ->  |
App1/1 -> -+
App1/2 -> 
Cpu1 ->
Cpu2 ->
                        
Switch                 App       Cpu  
11 12 13 14 15 16 17   1/1 1/2   1 2 
                        |    |   |          
Et1 -> -------------------|----+   | 
Et2 ->                    |        | 
Et3 ->                    |        |
Et4 ->                    |        |
Et5 ->                    |        |
Et6 ->                    |        |
Et7 ->                    |        |
Et8 ->                    |        |
Et9 ->                    |        |
Et10 ->                    |        |
Et11 ->                    |        |
Et12 ->                    |        |
Et13 ->                    |        |
Et14 ->                    |        |
Et15 ->                    |        |
Et16 ->                    |        |
Sw1 ->                    |        |
Sw2 ->                    |        |
Sw3 ->                    |        |
Sw4 ->                    |        |
Sw5 ->                    |        |
Sw6 ->                    |        |
Sw7 ->                    |        |
Sw8 ->                    |        |
Sw9 ->                    |        |
Sw10 ->                    |        |
Sw11 ->                    |        |
Sw12 ->                    |        |
Sw13 ->                    |        |
Sw14 ->                    |        |
Sw15 ->                    |        |
Sw16 ->                    |        |
Sw17 -> -------------------|--------+
App1/1 ->                    |
App1/2 -> -------------------+
Cpu1 ->
Cpu2 ->

This command displays the matrix of Layer 1 paths for the specific Ethernet interfaces et1 and et4.

switch> show l1 matrix interface et1, et4
Ethernet   Switch   App    
1 4        1        1/1      
| |        |        |        
Et1 -> -|-|--------+--------+ 
Et2 -> -|-+           
App1/1 -> -+

show l1 path

The show l1 path command displays the source and destination paths for all interfaces in the system.

Command Mode

Privileged EXEC

Command Syntax

show l1 path [interface]

Parameters

interface lists the connections available for the specified interface.
- Application 1-1 - Application FPGA connector interface
- CPU 1-4 - CPU interface
- Downstream 1-255 - Downstream interface
- Ethernet 1-96 - Ethernet interface
- MuxIn 1-24 - Metamux input interface
- MuxOut 1-24 - Metamux output interface
- Ptp 1-2 - MetaWatch PIP interface
- Switch 1-7 Switch interface
- TrafficGen 1-256 - Traffic Generation interface
- Upstream 1-255 - Upstream interface
- WatchIn 1-255 - WatchIn interface
- WatchOut 1-255 - WatchOut interface
- WatchPassthrough 1-255 - Watch passthrough interface
- WhiteRabbit 1-255 - White Rabbit interface

Examples

This command displays the source and destination paths for all interfaces in the system.

switch# show l1 path
Source               Destination          Type
------------------   -------------------- -------
Ethernet1             App1/1              dynamic
Ethernet1             Sw1                 dynamic
Ethernet2             Ethernet3           dynamic
Ethernet2             Ethernet4           dynamic
App1/1                Ethernet1           dynamic
App1/2                Sw17                static
Sw17                  App1/2              static

This command displays the list of all connections that include the Ethernet interfaces et1 and et4.

switch# show l1 path interface et1, et4
Source                 Destination           Type
--------------------- ---------------------- -------
Ethernet1             App1/1                 dynamic
Ethernet1             Sw1                    dynamic
Ethernet2             Ethernet4              dynamic
App1/1                Ethernet1              dynamic

show l1 source

The show l1 source command displays the list of all source interfaces to connect for specific interfaces such as Ethernet ports, switch, FPGA ports, or CPU ports.

Command Mode

Privileged EXEC

Command Syntax

show l1 source [interface | capabilities]

Parameters

interface lists the source interfaces available to connect for the specified interface.
- Application 1-1 - Application FPGA connector interface
- CPU 1-4 - CPU interface
- Downstream 1-255 - Downstream interface
- Ethernet 1-96 - Ethernet interface
- MuxIn 1-24 - Metamux input interface
- MuxOut 1-24 - Metamux output interface
- Ptp 1-2 - MetaWatch PIP interface
- Switch 1-7 Switch interface
- TrafficGen 1-256 - Traffic Generation interface
- Upstream 1-255 - Upstream interface
- WatchIn 1-255 - WatchIn interface
- WatchOut 1-255 - WatchOut interface
- WatchPassthrough 1-255 - Watch passthrough interface
- WhiteRabbit 1-255 - White Rabbit interface
capabilities lists the Layer 1 source capabilities for the specified switch.

Examples

This command displays the list of all source interfaces to connect in the crosspoint and the specific interfaces.

switch# show l1 source
Interface             Source Interface    Type
--------------------- ---------------------- -------
Ethernet1             App1/1              dynamic
Ethernet2
Ethernet3             Ethernet2           dynamic
Ethernet4             Ethernet2           dynamic
Ethernet5             MAC                 dynamic
App1/1                Ethernet1           dynamic
App1/2                Sw17                static
Sw1                   Ethernet1           dynamic
Sw2
Sw3
Sw4
Sw5
Sw17                  App1/2              static
Cpu1
Cpu2

Note: Interfaces without a source port are listed as well, but the Source Interface and Type columns appear as blanks.

This command displays the list of source interfaces to connect for the Ethernet interface et1.

switch# show l1 source interface et1
Interface             Source Interface    Type
--------------------- ------------------- -------
Ethernet1             App1/1              dynamic

show l1 source capabilities

The show l1 source capabilities command displays the list of all interfaces available to connect in the crosspoint and the possible source ports.

Command Mode

Privileged EXEC

Command Syntax

show l1 source capabilities

Examples

This command displays the list of all possible source interfaces available to connect in the crosspoint and the specific interfaces.

switch# show l1 source capabilities
Interface             Possible Source Interface(s)
--------------------- ---------------------------------
Ethernet1             Ap1/1,Cpu1-2,Et1-16,Sw1-16    
Ethernet2             Ap1/1,Cpu1-2,Et1-16,Sw1-16    
Ethernet3             Ap1/1,Cpu1-2,Et1-16,Sw1-16    
Ethernet4             Ap1/1,Cpu1-2,Et1-16,Sw1-16    
Ethernet5             Ap1/1,Cpu1-2,Et1-16,Sw1-16    
Application1/1        Ap1/1,Cpu1-2,Et1-16,Sw1-16    
Application1/2        Sw17                          
Switch1               Ap1/1,Cpu1-2,Et1-16,Sw1-16    
Switch2               Ap1/1,Cpu1-2,Et1-16,Sw1-16    
Switch3               Ap1/1,Cpu1-2,Et1-16,Sw1-16    
Switch4               Ap1/1,Cpu1-2,Et1-16,Sw1-16    
Switch5               Ap1/1,Cpu1-2,Et1-16,Sw1-16    
Switch17              Ap1/2                        
Cpu1                  Ap1/1,Cpu1-2,Et1-16,Sw1-16    
Cpu2                  Ap1/1,Cpu1-2,Et1-16,Sw1-16

This command displays the list of possible source interfaces available to connect for the Ethernet interface et1.

switch# show l1 source interface et1 capabilities
Interface             Possible Source Interface(s) 
--------------------- --------------------------------
Ethernet1             Ap1/1,Cpu1-2,Et1-16,Sw1-16

This command displays the list of possible source interfaces available to connect for the FPGA port fpga.

switch# show l1 source fpga capabilities
Interface             Possible Source Interface(s) 
--------------------- ------------------------------
Application1/1        Ap1/1,Cpu1-2,Et1-16,Sw1-16    
Application1/2        Sw17

Timing Protocols

The Precision Time Protocol (PTP) provides clock accuracy for networked devices, allowing clocks to be synchronized locally in increments of less than a microsecond. PTP uses a master-slave hierarchy similar to that used by NTP. The master clock provides the most precise time, and slave devices use its signal to synchronize their clocks.

The master clock sends a sync request, called an announce message by the IEEE 1588-2008 standard, at a regular interval. The slave clock responds with a time-stamped delay request message in order to measure and compensate for packet delays between the devices. The slave then receives a message from the master specifying the time of the delay message and allows the slave to calculate final values for clock synchronization. The time maintains synchronization by regularly exchanging PTP packets between master and slave.

Note: Arista switches do not support setting the system clock using PTP. Use the NTP service on the PTP grandmaster for system clock synchronization.

EOS disables PTP globally by default. Enabling PTP on an interface requires the following steps:

Optional PTP global configurations include the following:

Optional PTP interface-level configurations include the following:

Setting the PTP Mode

To enable PTP on switch interfaces, set the PTP mode using the ptp mode command. PTP mode options include the following:

boundary - The device acts as a boundary clock and runs and participates in the best master clock algorithm.
disabled - Disables PTP, and the device forwards all PTP packets as normal traffic.
end-to-end transparent - The device acts as an end-to-end transparent clock, synchronizing all ports to a connected master clock and updating the time interval field of forwarded PTP packets using switch residence time.
peer-to-peer transparent - The device acts as a peer-to-peer transparent clock, synchronizing all ports to a connected master clock and updating the time interval field of forwarded PTP packets using switch residence time and inbound path delays.
generalized Precision Time Protocol (gPTP) - The device runs generalized Precision Time Protocol (gPTP), participating in the best master clock algorithm but also updating the interval field of forwarded PTP packets using switch residence time and inbound path delays.

To disable PTP globally on the switch, use the no or default forms of the ptp mode command.

Example

This command configures the device as a PTP boundary clock.

switch(config)# ptp mode boundary
switch(config)#

Configuring the TTL for PTP Packets

To set the Time To Live (TTL) of PTP packets, use the ptp ttl command. TTL is the maximum number of hops that a PTP packet may make.

Example

This command configures a TTL of 64 hops for PTP packets.

switch(config)# ptp ttl 64
switch(config)#

Configuring PTP Monitoring

PTP Monitoring records PTP information, including the offset from the master, mean path delay, and skew values, which you view using a show command. PTP Syslog messages generate the metrics with threshold values configured on the switch when enabled. EOS enables PTP Monitoring by default.

Enabling and Disabling PTP Monitoring

Use the ptp monitor command to enable PTP monitoring on the device. The no form of the command disables PTP monitoring and clears all of the recorded PTP data.

Example

This command disables PTP monitoring and clears all recorded PTP data from the switch.

switch(config)# no ptp monitor

Configuring the Offset-from-master Threshold

The offset is the difference in nanoseconds between master and slave time. Use the ptp monitor threshold offset-from-master command to specify the offset-from-master threshold in nanoseconds. EOS generates a Syslog message if the most recently calculated time offset from the PTP master occurs outside the configured range. The maximum offset threshold is one second. The no form of the command clears the threshold value and prevents further Syslog messages from generating for this parameter.

Example

This command sets an offset-from-master threshold value of 500 nanoseconds.

switch(config)# ptp monitor threshold offset-from-master 500

Configuring the Mean-path-delay Threshold

Mean path delay is the mean time in nanoseconds PTP packets take to travel between master and slave. Use the ptp monitor threshold mean-path-delay command to specify the mean-path-delay threshold in nanoseconds. EOS generates a Syslog message if the value of the most recently calculated mean path delay becomes greater than or equal to this threshold. The maximum mean-path-delay threshold is one second. The no form of the command clears the threshold value and prevents further Syslog messages from generating for this parameter.

Note: Mean path delay is always non-negative.

Example

This command sets a mean-path-delay threshold value of 2000 nanoseconds.

switch(config)# ptp monitor threshold mean-path-delay 2000

Configuring the Skew Threshold

PTP skew is the clock frequency difference between master and slave. Use the ptp monitor threshold skew command to configure the value of the skew-threshold percentage. A Syslog message generates if the value of the most recently calculated skew does not fall within the range (1/(1+<threshold>), 1*(1+<threshold>)). Skew threshold percentage represents a double precision (16 digit) real number ranging from 0 (0%) to 10 (1000%). The no form of the command clears the threshold value and prevents further Syslog messages from generating for this parameter.

Example

This command sets a skew threshold value of 5 (500%).

switch(config)# ptp monitor threshold skew 5

Page 12 of 16

End of Support

Configuring and Viewing Environment Settings

Overriding Automatic Shutdown

Overheating

Insufficient Fans

Fan Speed

Viewing Environment Status

Power Status

Temperature Status

Fan Status

System Status

Locating Components on the Switch

Environment Commands

Environment Control Configuration Commands

Environment Display Commands

environment fan-speed

environment insufficient-fans action

environment overheat action

locator-led

show environment power

show environment temperature

show locator-led

show system environment all

show system environment cooling

show system environment power budget

Upgrades and Downgrades

Upgrade/Downgrade Overview

Smart System Upgrade

Upgrading the EOS image with Smart System Upgrade

Preparing the Switch for SSU

Backing Up Critical Software

Making Room on the Flash Drive

Verifying Connectivity

Verifying Configuration

Configuring BGP

Configuring MLAG

Transfer the Image File for SSU

USB Memory

FTP Server

SCP

HTTP

Modify boot-config

Start the SSU Process

Verify Success of the Upgrade

Fatal Error Display

Successful Upgrade Display

Scheduling an SSU

Configuring a Scheduled SSU Upgrade

Canceling a Scheduled SSU

Displaying Scheduled SSU Information

7130 Layer 1 Commands

Layer 1 Configuration Commands

Layer 1 Show Commands

l1 source

show l1 destination

show l1 matrix

show l1 path

show l1 source

show l1 source capabilities

Timing Protocols

Setting the PTP Mode

Configuring the TTL for PTP Packets

Configuring PTP Monitoring

Enabling and Disabling PTP Monitoring

Configuring the Offset-from-master Threshold

Configuring the Mean-path-delay Threshold

Configuring the Skew Threshold