Tag :: TOI

This is an infrastructure that provides management of SSL certificates, keys and profiles. SSL/TLS is an application-layer protocol that provides secure transport between client and server through a combination of authentication, encryption and data integrity. SSL/TLS uses certificates and private-public key pairs to provide this security. A user can manage certificates, keys and also multiple SSL profiles. An SSL profile is a configuration which includes certificate, key and trusted CA certificates used in SSL/TLS communication. An SSL profile configuration can be attached to another EOS configuration which supports SSL/TLS communication. Individual EOS features that use this infrastructure will document the details of using an SSL profile in their configuration.

EOS 4.22.1F release adds support for secure In band connection between CVX and Arista switches. Prior to this

This TOI describes the features details and any caveats of Stateful Switchover (SSO) support for Sand modular

This TOI describes details and limitations of Stateful Switchover on Modular chassis with 7500R3, 7800R3, 7800R3A, 7800R4, 7800R4C based line cards.

The EOS-4.36.1 release introduces SSU support for SRv6 uN. This allows for SSU with SRv6 uN configuration, with negligible impact on active traffic flows.

Before this feature was introduced, any daemon agent needing to interface with Sysdb for configuration retrieval and status updates had to go through the agent manager within the EOS SDK. Usage of the EOS SDK introduced various ABI issues due to constraints on which compiler, libc and kernel versions the daemon must be built with. This feature offers an alternative mechanism via gRPC, providing more flexibility in how daemon executables are built and used to programmatically interact with and monitor the EOS device.

Stateful switchover is a redundancy mode available on systems with 2 supervisor cards. One supervisor card is active

Static ARP inspection is a security feature that verifies the source IP and the source MAC addresses of each received

The Static Configuration Studio is used to manage static configuration for devices, provide configuration not created by any other studio, and reconcile differences between CloudVision’s designed configuration and device running configuration. Devices are assigned to containers using tags that can identify one or more devices by hostname, role, or location in the network. Each container has configlets of EOS configuration, which are pushed to the EOS devices.

Currently, EOS supports the receiving and transmitting of BGP Flowspec rules. Rules received can be installed locally as ACLs and/or transmitted to other BGP peers/route reflectors. EOS relies on external controllers to inject these flowspec rules. The feature will allow flowspec rules to be defined via CLI in a similar fashion as traffic-policies is currently done. These policies would then be redistributed into BGP. Once redistributed, the rules can be advertised to other BGP peers and optionally installed locally on the configured system.

This feature enables configuring static IPv4 routes that specify the next hop by using an IPv6 address instead of an

Static multicast feature brings in capability to statically configure multicast routes on any Arista platform

A number of L4 7 appliances use the same MAC address to load balance services across two or more appliances that form the

Packet counters for Static and Twice NAT connections are now supported on the DCS 7150 series. This is a debug

Static NAT allows a switch to modify the source or destination IP address, and optionally the Layer 4 port, of packets traversing it. Each static NAT rule is explicitly defined by the user and specifies a one-to-one mapping between an original IP address and a translated IP address.

Static VRF label termination can be enabled at the egress PE to provide pop and route behavior. It allows one to one

The feature exposes metrics and health status of storage devices on controllers and all managed nodes, but not switches.

The feature exposes metrics and health status of storage devices on controllers and all managed nodes, but not switches. Metrics and health status are updated every minute and exposed through the Telemetry collector

The feature exposes metrics and health status of storage devices on controllers and all managed nodes, but not switches. Metrics and health status are updated every minute and exposed through the Telemetry collector

Storm Control is a flood containment mechanism that limits BUM (broadcast, unknown-unicast, and multicast) traffic. This feature introduces policing BUM traffic via a single policer per interface instead of having independent policers for each of the stream - broadcast, unknown-unicast, multicast.

Storm control is a feature that allows the data plane to drop excess broadcast, unknown unicast, and/or multicast packets if the ingress packet rate exceeds a user-configurable threshold.

Storm control enables traffic policing on floods of packets on L2 switching networks. Support for counting dropped packets and bytes on interfaces where storm control metering is provisioned. Both packet and bytes count are supported and will be displayed. Drop logging on storm-control discards is also supported.

The existing storm control interface configuration mode CLI commands have been extended to support the new

Storm control enables traffic policing on floods of packets on L2 switching networks. Support was enabled for Front panel ports and Lag in eos-4-25-2f with storm-control-speed-rate-support. Now, storm control will be supported per subinterfaces( both ethernet and port-channel). Scale of subinterfaces is 4095. 

A traffic storm is a flood of packets entering a network, resulting in excessive traffic and degraded performance. Storm control prevents network disruptions by limiting traffic beyond specified thresholds on individual physical LAN interfaces. Storm control monitors inbound traffic levels over one-second intervals and compares the traffic level with a specified benchmark. The storm-control command configures and enables storm control on the configuration mode physical interface.

A traffic storm is a flood of packets entering a network, resulting in excessive traffic and degraded performance.

This feature enables ACL functionality on subinterfaces. ACLs on subinterfaces are configured using the

Subinterfaces are logical L3 interfaces that enable the division of a single Ethernet or Port-channel interface into multiple logical L3 interfaces based on the incoming 802.1q tag.  They are commonly used in the L2/L3 boundary.  They can also be used in the context of VRF-lite, by configuring each subinterface in a different VRF.

The CCS-750X-48ZXP is a 48 port 10GBASE-T linecard, capable of several full-duplex link speeds to support connecting to a variety of compatible devices of varying capabilities. All supported linkup speeds on this card can be automatically selected during the linkup process using IEEE 802.3 Clause 28 auto-negotiation. Note that IEEE 802.3 also allows for speeds lower than 1Gbps to link up without clause 28 auto-negotiation.

This feature introduces support for the SFP-10G-MRA-T SFP transceiver. This is a rate adapting transceiver, meaning it can convert the system side interface to a lower rate on the line side. This module can provide 100M, 1G, 2.5G, and 5G support over BASE-T media for Arista switches that do not natively support these data rates.

This feature adds support for the following IPFIX keys TCP Source Port, TCP Destination Port, UDP Source Port, UDP Destination Port

The guaranteed bandwidth feature ensures minimum bandwidth for outgoing lower priority traffic from a

The aggregate address minimum contributors feature adds the capability to specify a minimum number of contributor routes that must be present and advertisable in order for the BGP speaker to generate the route for the aggregate address.

A fundamental business requirement for any network operator is to reduce costs where possible. For network operators, deploying devices to many locations can be a high cost, as sending trained specialists to each site for installations is both time-consuming and expensive. Arista devices support Zero Touch Provisioning (ZTP), a bootstrapping strategy that enables devices to obtain configuration data with no installer action beyond physical placement and connecting network and power cables. Secure Zero Touch Provisioning (SZTP) builds on ZTP and securely supports provisioning as defined in RFC 8572.

A fundamental business requirement for any network operator is to reduce costs where possible. For network operators, deploying devices to many locations can be a significant cost as sending trained specialists to each site for installations is both time-consuming and expensive.

This feature extends the existing UDP payload hashing support to allow an alternative set of bytes to be used in the calculation of the LAG and ECMP hash if an 16 bit field of the payload matches a provided pattern.

The support for configurable dynamic authorization port for different clients has been added to proxy the radius dynamic authorization (CoA) requests. By default, all radius dynamic authorization requests are only proxied to clients at port 3799, which is configurable now.

This feature adds support for configurable max sFlow datagram size. The current default max datagram size is 1400 bytes, which can cause some sFlow datagrams to be dropped when there is an MTU set. This feature enables the configuration of the max datagram payload size within the range of 200 to 1500 bytes to help avoid fragmentation. Note that this feature only configures software sFlow and is not supported on hardware-accelerated sFlow.

This feature adds support for CPU traffic policy capable of matching and acting on IP traffic which would otherwise hit the CPU. This policy is capable of permitting traffic from trusted sources, while rejecting untrusted traffic. It supports matching on a variety of IP packet header information such as DSCP, L4 port values, fragmentation bits, etc. as well as a number of actions such as permit, deny, and police. To prevent a malicious source from overloading the CPU, this traffic policy will take effect in the switching hardware, before the traffic is processed by the kernel. This feature provides a shorthand syntax for securing L3 protocol peers, in particular, BGP neighbors.

Prior to 4.32.2F, the “reset system storage secure” CLI command can be used to perform a best-effort storage device wipe of all sensitive data. However, this command has the limitation that it wipes EOS from the storage device, leaving the system “stuck” in Aboot. The “reset system storage secure rollback” command provides the same secure erase functionality, but additionally allows the user to preserve a subset of files on the main flash device by copying them into RAM during the secure erase procedure. The set of files that are preserved is configurable. After a successful wipe, the system will return to EOS after the erase is complete if the EOS SWI image and adequate configuration files are preserved (such as boot-config and startup-config).

This feature adds support to configure the following decap group OpenConfig models via gNMI. GRE decap group for incoming traffic with IPv4 or IPv6 inner packets , UDP decap group for incoming traffic with IPv4 or IPv6 inner packets , UDP decap group for incoming traffic with MPLS inner packets

Dot1q (802.1Q) is a tunneling protocol that encapsulates traffic from multiple customer (c-tag) VLANs in an additional single outer service provider (s-tag) VLAN for transit across a larger network structure that includes traffic from all customers. Tunneling eliminates the service provider requirement that every VLAN be configured from multiple customers, avoiding overlapping address space issues.

This feature adds support for “Dynamic Load Balancing (DLB)” on Equal Cost Multi Path (ECMP) groups.

Dynamic NAT is a feature which dynamically allocates an IP address to an incoming or outgoing flow. This address will replace source or destination IP for all packets of the flow. The new IP address given to the flow is from a pool of addresses called NAT pool. L4 port can also be replaced by a new one in case of NAPT (Network Address Port Translation). In address only NAT only the IP address is translated. NAPT is not supported in masquerade or overload mode.

Dynamic NAT Priority feature, which extends the Dynamic NAT feature,  allows you to configure the order in which dynamic NAT rules are evaluated by the switch.

Dynamic NAT Priority feature, which extends the Dynamic NAT feature,  allows you to configure the order in which dynamic NAT rules are evaluated by the switch.

Dynamic Twice NAT is a variant of the dynamic NAT feature where both the source and destination IP can be modified while forwarding a packet. One of the IP addresses will be dynamically assigned, while the other will be statically assigned.

enrollz/attestz defines a set of gRPC-based services for TPM enrollment and attestation of network devices. Enrollz: provides the capability to verify the switch’s TPM-rooted identities and rotate switch owner certificates on the device. Attestz: provides the capability to attest the device by inspecting the contents of the different PCR ensuring no malicious tampering.

In EVPN deployments, MAC address reachability is ascertained using both (i) MAC only routes, and (ii) MAC-IP routes. If all EVPN peers in the network are guaranteed to advertise a MAC-only route for MACs, then it is redundant to compute MAC reachability based on MAC-IP routes for the same MAC. With higher scale of the number of IPs mapped to the same MAC address, BGP best path work experiences a higher load.

gNOI (gRPC Network Operations Interface) defines a set of gRPC-based microservices for executing operational commands on network devices.