Tag :: CLI

The current workflow for installing extensions involves multiple manual steps: copying, installing, and setting to install at boot, and on dual supervisor systems these steps have to be repeated in a peer supervisor CLI session. This feature introduces new CLI commands automating this process, improving EOS extension management for both dual supervisor and fixed system devices, and easing set up of EOS devices at scale. They are modeled to resemble existing install source commands and should behave similarly for EOS extensions. Both commands are available in enable mode.

CLI extension allows for custom CLIs commands/modes to be defined in EOS. It also integrates with EOS SDK to be able to control a daemon’s configuration and read a daemon’s status from the CLI command handlers. This feature is intended to have more customization compared to the “daemon cli” feature, which only allows for key/value pairs as cli commands, and doesn’t allow for custom CLI commands. It does this by using a statically defined YAML file that contains the daemon definition (EOS SDK or not), CLI mode, and CLI commands, very much akin to what is provided by the via configuration in the daemon cli mode.

Common Management Interface Specification (CMIS) defines, starting with revision 4.0, a standard mechanism for managing the firmware of compliant transceivers. This mechanism allows for transceivers’ firmware to be updated without having to remove the transceiver from the switch. Firmware updates may be necessary in a testing or production environment to resolve potential firmware bugs. Some transceivers may also support firmware management operations in a hitless manner (without impacting traffic).

This mechanism allows a session to lock the configuration of the switch to prevent any other session from altering the

By default when a configuration session is committed everything modified in the configuration session will be committed to the running configuration, even if the running-configuration has also changed since the configuration session was created. This means that if the running-config has been modified since the start of the configuration session then those modifications could be overridden when the configuration session is committed. 

Text running-config commands can be converted into a snapshot (JSON snapshot). A new keyword is added to the ‘copy running-config snapshot://sample’ command: the ‘transaction’ CLI keyword can be used to perform the conversion, which can also be used to create a snapshot with specific commands included.

EosSdkRpc is an agent built on top of the Arista EOS SDK. It uses gRPC as a mechanism to provide remote access to the EOS SDK. The gRPC interface that EosSdkRpc supports closely matches the interface provided by EOS SDK, and the intent is that the .proto interface can be publicly supported. EosSdkRpc allows for remote access and using protobuf to specify the interface isolates user code from the Linux ABI issues that come with building C++ applications on different compiler, libc, and kernel versions. EosSdkRpc is built using C++ but supports clients written in any of the languages currently supported by the gRPC framework.

Using the show switch <switch name/all> interface details or show switch <switch name/all> interface <interface name> details commands in the CLI will now include a Description column, which provides the configured description (if any) for the corresponding interface. This is a CLI-only change.

Measured boot is an anti-tamper mechanism. It calculates the cryptographic signatures for software system components and extends the signatures into the Trusted Platform Module (TPM) security chip. Upon startup, with the feature turned on, the Aboot bootloader and EOS calculate the hash of various system components and extend the hashes into the Platform Configuration Registers (PCRs), which is one of the resources of the Trusted Platform Module (TPM) security chip. The calculation and extension event is called the measured boot event, and the event is associated with a revision number to help the user identify changes to the event.

A new configuration model for the BFD (Bidirectional Forwarding Detection) agent was added in order to more

Support for running multiple CLI commands in one line separated by semicolons. Multiple CLI commands

This feature adds support for making the various OSPFv3 counters accessible via CLI.

A router keeps track of the total number of LSAs for each OSPFv3 instance. The LSA Limit feature provides a mechanism to

This feature introduces a command to enable or disable USB ports, specifically designed to address strict security requirements in hardened environments. By restricting port functionality, administrators can prevent unauthorized access or booting from external USB storage.

A remark is a user specified comment that is written within an IP prefix-list. Remarks allow documentation to be added directly into the configuration of an IP prefix-list. Both IPv4 and IPv6 prefix-lists are supported.

A secure erase is generally defined as a command (or set of commands) that deliberately, permanently and

In EVPN, when configuring the member VLANs for a VLAN aware bundle, the existing configuration command only allows