Tag :: TOI

This feature adds IPv6 VRF support to Open Shortest Path First(OSPF) Protocol version 3. It allows for OSPFv3

EOS 4.15.0F is introducing support of IPv6 management capabilities inside a VRF. This means existing management

This feature adds the support for IPv6 unicast in a VRF context in EOS. This entails static routing and dynamic

IS IS adjacency uptime describes the uptime or downtime of neighbors since the last state change.

Bidirectional Forwarding Detection(BFD) is a low overhead protocol designed to provide rapid detection of

The IS-IS BFD Damping feature allows IS-IS to delay adjacency establishment on a link that experiences frequent BFD flaps.

The IS-IS BFD TLV feature implements RFC 6213. When this feature is enabled, IS-IS will prevent adjacency establishment on a link if the BFD peering is down.

This feature introduces a way for IS-IS to advertise its IP reachability and SID for loopback interfaces only when routes matching an RCF function are present. One example use-case is to use IS-IS Segment Routing to attract traffic to a router only when routes towards the ultimate destination are present. The RCF function is matched against winning routes in the Unicast RIB (seen with 'show rib route …').

Link State IGPs such as IS-IS depend upon having a consistent LSDB across all the Intermediate Systems (ISs or nodes) in the network in order to provide correct forwarding of data packets. When topology change occurs due to various network events, new/updated LSPs are propagated network-wide. The speed of propagation is key for a faster network convergence.

IS-IS flexible algorithm (FlexAlgo) provides a lightweight, simplified mechanism for performing basic traffic engineering functions within a single IS-IS area. FlexAlgo requires the cooperation of all nodes within the IS-IS area but does not require an external controller. Paths are computed by each node within the area, resulting in an MPLS-switched forwarding path to nodes that are advertising a node Segment Identifier (SID) for the algorithm. The results of the path computation are placed in the colored tunnel RIB or system tunnel RIB, which simplifies route resolution.

The difference between the two forms of authentication is in the level of security provided. In case of clear text authentication, the password is specified as text in the authentication TLV, making it possible for an attacker to break the authentication by sniffing and capturing IS-IS PDUs on the network.

IS IS Graceful Restart adds support for Restart Signaling for IS IS, IETF RFC 5306. When IS IS is used

By default if there's a hostname configured on the switch, it is used as the IS IS hostname. It is also possible to

An IS IS router can be configured as Level 1 2 which can form adjacencies and exchange routing information with both

IS-IS LSP out-delay is a feature implemented to mitigate transient micro-loops that can occur during topology changes in an IS-IS network.When a topology change occurs (e.g., a link state or metric change), different routers in the network receive and process the updated Link State PDUs (LSPs) at slightly different times. This can lead to a transient state where some routers have updated their Forwarding Information Base (FIB) based on new LSPs, while others have not, causing traffic to be incorrectly forwarded and forming micro-loops.

IS IS Multi Topology support enables an IS IS router to compute a separate topology for IPv4 and IPv6 links in the

Support for Multiple Router Capability TLVs (Type 242) in IS-IS LSPs. In modern segment-routed networks, a single router often needs to advertise a vast amount of capability data, including Segment Routing (SR) blocks, SRv6 capabilities, Node Maximum Stack Depth (MSD), Flexible Algorithm Definitions (FAD),  etc.

This feature enables an Arista switch to run the IS IS routing protocol over a tunnel interface to another IS IS

Segment Routing provides mechanism to define end-to-end paths within a topology by encoding paths as sequences of sub-paths or instructions. These sub-paths or instructions are referred to as “segments”. IS-IS Segment Routing (henceforth referred to as IS-IS SR) provides means to advertise such segments through IS-IS protocol.

Level 1 2 routers set attached bit in their Level 1 LSPs to indicate their reachability to the rest of the network. A

This document describes two features that allow dynamic metric change for IS-IS based on interface speed.

SPF Timers can be used in IS-IS to throttle the frequency of shortest-path-first (SPF) computations. In networks with a lot of churn, using these timers will help in containing the effect of network disruptions arising out of frequent SPF runs.

In modern networks, especially those handling real-time data, network performance metrics like bandwidth and latency are as crucial for data-path selection as traditional routing metrics. Incorporating this performance data into path selection offers an advantageous, scalable, and cost-effective method for network optimization.

The default behavior of a level 1 router running IS IS is to install a default route to a level 1 2 router present in a

This feature adds Intermediate System to Intermediate System (IS IS) support for IP version 6 (IPv6) address family

This feature provides a way to export non ISIS routes into level 1, level 2 or both by using route map's set clause. The

This feature extends the IS IS set overload bit command to support wait for BGP option. In scenarios

Data entries from journald can be viewed through the CLI and the REST API. If the REST API is used the data is returned to the user in the form of a list of structured entries. This API is only for viewing journal data contained on the node being queried. The user is given the option to pass parameters to the API that can be used for pagination and for filtering the data that gets returned, e.g. only returning entries that were written by a specific application or after a specific start time.

The routing table is not available on the standby supervisor in EOS, hence running any diagnostics or scripts that talk to the standby supervisor through the forwarding plane is not possible. This feature adds a new Cli command that configures a default route on a standby supervisor. This default route will offload routing to the forwarding plane. Therefore it behaves the same way as the routing table on the active supervisor. The default route is installed on all VRFs.

At a high level, L1 profiles are a set of configurations which allow EOS users to change the numbering scheme and default L1 configurations of all front panel interfaces across their network switch. On Arista network switches, front panel transceiver cages are exposed as ports which are numbered sequentially: 1, 2, 3, 4, etc. These identifiers are usually marked on the front panel to allow for easier identification.

Arista’s 7135 Connect Series of Layer 1+ switches are powerful network devices that allow for dynamic connections between various layer 1 components on the system, such as the front panel and FPGA. These connections are driven by an underlying CLOS network of crossbar switches. The following commands provide the ability to configure middle stage crossbar switches within the system to create dynamic layer 1 connections.

This feature allows transport of multicast frames to an endpoint across an IP network by tunneling them through MPLSoGRE or MPLSoGUE. The tunneling of multicast frames is achieved with a traffic policy applied on the ingress interface which will match on all packets destined to a multicast IP address and redirect that traffic to a MoG nexthop group. The traffic policy will also specify “forced routing” in order to set the fwd_layer_index to 1 so that the L2 header is removed before encapsulation.

Normally, a switch traps L2 protocol frames to the CPU. However, certain use-cases may require these frames to be forwarded or dropped. And in cases where the L2 protocol frames are forwarded (eg: Pseudowire), we may require the frames to be trapped to the CPU or dropped. The L2 Protocol Forwarding feature provides a mechanism to control the behavior of L2 protocol frames received on a port or subinterface.

L2 protocol frames - LLDP, LACP and STP are trapped to the CPU by default. This feature allows for disabling the per protocol trap on a given set of interfaces.

L2 support for CloudEOS and AWE is added.

In our current implementation, on a switch with default startup config or no config, all ports come up in access

This feature is used to connect a Layer 3 EVPN VXLAN network to an Adaptive Virtual Topology (AVT) WAN network using dynamic path selection (DPS) tunnels. One or a pair of WAN routers are configured to serve as the VXLAN gateway. On the control plane, the configured VXLAN gateway handles EVPN IP-PREFIX route exchanges between the VXLAN network and the WAN network. On the data plane, the configured VXLAN gateway decapsulates the VXLAN packets received from the VXLAN network and encapsulates them into the DPS tunnels and sends them to the AVT WAN network. 

This feature is available when configuring BGP in the multi agent routing protocol model. Ethernet

L3 interface ingress counters can be used to count routable traffic coming into the box on sub interfaces and vlan

Subinterfaces divide a single ethernet or port channel interface into multiple logical L3 interfaces based on the 802.1q tag (VLAN ID) of incoming traffic. Subinterfaces are commonly used in the L2/L3 boundary device, but they can also be used to isolate traffic with 802.1q tags between L3 peers by assigning each subinterface to a different VRF. L3 subinterface shaping + VRF is also supported.

LACP on Loopback Interfaces allows for Active Port Channels on one or more interfaces whose link endpoints terminate

LACP State Transition Event Monitoring on Arista switches allows for quick and filterable viewing of LACP state

Introduced in EOS-4.20.1F, “selectable hashing fields” feature controls whether a certain header’s field is used in the hash calculation for LAG and ECMP.

Control Plane Policing (CoPP) classifies control plane traffic into protocol classes (e.g., IGMP, LLDP, BGP) and applies rate limiting per class using queue shaping. On supported platforms, all control plane traffic for a given protocol class is directed to a single queue regardless of the ingress port. As a result, a high-rate flow from a single port or host can consume the entire bandwidth allocated to that class, starving legitimate control plane traffic arriving on other ports.

LAGs are allocated hardware resources on transition from one member (software LAG) to two members (hardware LAG) and deallocated hardware resources on transition from two member to one member. This allocation/deallocation causes some traffic disruption. Starting with EOS4.15.4F, the option to configure all LAGs to use hardware resources is supported on the 7500E platform.

This document addresses LAG hashing improvements across different platforms. In DANZ Monitoring Fabric (DMF) 8.7, the Controller applies the default hash configuration if no hash fields are configured or the configuration contains an error. If the Controller detects any hash error, DMF reports it as a fabric error.

Switches can now use two LAG partitions (A and B) to support double the number of available Port Channels dictated by the chosen LAG mode. This is useful if the selected LAG mode does not allow the creation of the desired number of Port Channels on a single partition.

Arista switches use the hashing algorithm to load balance traffic among LAG (Link Aggregation Group) members

LANZ Mirroring feature allows users to automatically mirror traffic queued as a result of congestion to either CPU or a different interface.

This document describes the current status of LANZ on DCS 7500R, DCS 7280R and DCS 7020R, for both polling and