Tag :: TOI

The Analytics Node (AN) enables the correlation of 5-tuple data from Flows and DMF metadata with the corresponding packets retrieved from the Recorder Node (RN). Previously, the system displayed Egress sFlow® to indicate potentially recorded flow packets.

The Recorder Node (RN) supports being managed by CloudVision (CV) on-prem starting DMF 8.7.0. This feature extends support to CVaaS starting DMF 8.8.0. Recorder Node was not supported with CVaaS before 8.8.0 because of an RN requirement to store the query results file in CV while archiving the query results. However, this was not permitted on CVaaS as these files might contain data that cannot be stored in a cloud service. This feature supports CVaaS by allowing the RN to store query result files.

This document provides a comprehensive overview of the redesigned Alerts page, detailing its features and how to use them to monitor and manage Fabric health effectively. The new design improves clarity, usability, and the efficiency of alert management.

This feature allows to advertise routes learnt via BGP into IS IS network or IS IS routes into BGP network. It also

The regex-session action enables matching of Regular Expression patterns against packet content. When a packet matches the specified pattern, its session is tracked based on configured timeouts and other parameters including, anchor, offset, and ip-proto.

With the 18.0 release, you can prevent clients using locally-administered MAC addresses from accessing your network. Network administrators can ensure that only clients using their device’s globally unique MAC addresses are able to connect to the network. By making sure that only devices with globally unique MAC addresses connect to the network, you can mitigate potential security threats associated with spoofing or unauthorized access by having control over device identification.

In the BGP Update message’s AS_PATH, routers have the capability to perform route aggregation and combine the ASes an update has traversed, merging the discrete entries into an  AS_SET. Routers can also do this within the local confederation with member AS numbers, using an AS_CONFED_SET. Route aggregation can be problematic as it blurs the semantics of what it means to originate a route. RFC 6472 recommends not using AS_SET or AS_CONFED_SET in BGP, and further justifies reasoning as to why, as well as provides a recommended way to handle updates with these messages.

Similar to reconfiguring the traffic-class to transmit-queue map, the traffic-class to priority-group mapping can also be changed using the CLI. This enables configuration capability to the user who can adjust the mapping based on the nature of the traffic. This configuration change doesn’t inhibit the flow of traffic.

This feature removes an ARP entry when the physical port, on which the ARP entry's MAC address is learned, goes down. This feature applies only to dynamic ARP entries, not static ARP entries. In addition, if the physical port, which is down,

This document describes the workflow for renaming a Group Name in DMF. Navigate to Security → Groups and select Groups.

When this feature is disabled, the dst_vlan field in the switch extension always equals to the src_vlan field for L2 traffic. When this feature is enabled, the dst_vlan field will be the 802.1Q VLAN ID of the outgoing frame for L2 traffic.

In the 14.0 release, CloudVision Cognitive Unified Edge (CV-CUE) introduces a new Report, WiFi-Radios Instantaneous.

Arista WM gathers a wealth of data about the wireless deployment. The data gathered includes Wireless Intrusion

Even if the LEM table is exhausted and the routes are being added to LPM due to LEM overflow, the reserved amount of entries in LEM should persist.

Equal Cost Multi-path (ECMP) provides the ability to load-share traffic across multiple next-hops. When a next-hop fails or is deleted all flows are affected. This is due to the nature of the load-balancing algorithm which re-calculates a new hash for the flows based on the remaining active next-hops.

Routes covered by a resilient equal-cost multi-path (RECMP) prefix are types of routes that make use of hardware tables dedicated for equal-cost multi-path (ECMP) routing. Resilient ECMP deduping is a new feature wherein the switch will reactively attempt to reduce the number of ECMP hardware table entries allocated by forcing routes that share the same set of next hops but point to different hardware table entries to point to the same hardware table entry when hardware resource utilization is high. Forcing RECMP routes to change the hardware table entry that they point to may potentially cause a traffic flow disruption for any existing flows going over that route. The deduping process will attempt to minimize the amount of potential traffic loss caused.

When this feature is enabled, responses to gNMI get requests as well as NETCONF get-config responses will contain the default values for YANG leafs if those leafs do not have any other value. This means that where a leaf value would normally be returned in a response, its default value (as defined in the YANG model) will be returned if the leaf does not have any other value assigned to it. Before this change, leafs that had a default value would not have been included in gNMI get responses.

When this feature is enabled, responses to gNMI subscribe requests contain the default values for YANG leafs if those leafs do not have any other value.

The transmit power configured on UI is now treated as EIRP (Equivalent Isotropically Radiated Power) instead of

The BGP labeled unicast (LU) RFC is used to advertise BGP routes with a stack of MPLS labels, thereby allowing

This feature provides support for advertising IPv4 unicast Network Layer Reachability Information (NLRI) with

EOS 4.17.0F adds support for IPv4 address family in OSPFv3 (multiple address family support) based on RFC5838.

Multi Agent, Platform independent. This feature supports RFC 7606, which  provides improved security and

This feature provides support for advertising VPN-IPv4 Network Layer Reachability Information (NLRI) with IPv6 next-hops over IPv6 peering sessions described as the Extended Next Hop Encoding capability in RFC8950. Extended Next Hop Encoding capability can be supported for IPv4 unicast, IPv4 Labeled Unicast, and IPv4 VPN address and sub-address families (1/1, 1/4, 1/128 respectively) per RFC. The Extended Next Hop support for IPv4 unicast is described in RFC 5549 .

RIB Route Control is a collection of mechanisms for controlling how IP routing table entries get used. Next hop resolution policy adds support for preventing recursive resolution of next hops based on route map evaluation of resolving routes.

With the 16.0 release, CloudVision Cognitive Unified Edge (CV-CUE) introduces the Client Roaming Explorer. It provides a graphical and tabular view of a client’s roaming events from one access point (AP) to another AP.

RDMA over converged ethernet version 2 (RoCEv2) is a UDP protocol for transferring memory blocks between compute nodes. It is used for AI applications. RoCEv2 aware sampled flow tracking with IPFIX export is an enhancement that allows customers access to RoCEv2 flow information, for the purposes of analyzing and monitoring traffic associated with AI workloads.

Link Aggregation Group (LAG) or port channel interfaces comprise multiple member interfaces. Network devices typically distribute packets across the member interfaces using a hash computed from packet header fields. The Round-Robin LAG Distribution feature introduces a new packet distribution method: the round-robin method. A round-robin LAG configuration balances packets evenly across all member interfaces in a sequential, round-robin fashion.

This feature adds support for ‘match interface’ clause under route map config for Bgp policy application in

EOS 4.35.2F introduces support to configure tag at interface level configuration to add a route tag attribute for connected routes. These tags are optionally configured per address.This feature adds the ability to define tags for local/directly connected prefixes as part of ‘ip address’ command. These tags can then be used in a RCF function or route-map for policy decision and route filtering as opposed to maintaining prefix-list when redistributing routes between protocols.

Beginning with DMF version 8.9, the action keyword is required to add or modify actions within a managed service. This keyword is a mandatory token across all managed service submodes, providing a consistent way to define service behaviors.

The broadcast queue towards the CPU is shared among all interfaces of the forwarding chip. So broadcast storm on a

This feature allows routing traffic across two Vrf domains on the same switch using an external loopback cable

Routing control functions (RCF) is a language that can be used to express route filtering and attribute modification logic in a powerful and programmatic fashion. This document serves as a reference guide for: Routing protocol attributes , Operators for comparing and modifying attributes

Routing control functions (RCF) is a language that can be used to express route filtering and attribute modification logic in a powerful and programmatic fashion. This document serves as a reference guide for Bgp agent points of application:

Routing control functions (RCF) is a language that can be used to express route filtering and attribute modification logic in a powerful and programmatic fashion. This document serves as a reference guide for IpRib agent points of application Configuration of RCF

Routing control functions (RCF) is a language that can be used to express route filtering and attribute modification logic in a powerful and programmatic fashion. This document serves as a reference guide for Isis agent points of application Configuration of RCF.

Routing control functions (RCF) is a language that can be used to express route filtering and attribute modification logic in a powerful and programmatic fashion.This document serves as a reference guide for KernelFib agent points of application:

Routing control functions (RCF) is a language that can be used to express route filtering and attribute modification logic in a powerful and programmatic fashion. 

Routing control functions (RCF) is a language that can be used to express route filtering and attribute modification logic in a powerful and programmatic fashion.

Routing control functions (RCF) is a language that can be used to express route filtering and attribute modification logic in a powerful and programmatic fashion.

In an MLAG setup, routing on a switch (MLAG peer) is possible using its own bridge/system MAC, VARP MAC or VRRP MAC.

RSVP-TE, the Resource Reservation Protocol (RSVP) for Traffic Engineering (TE), is used to distribute MPLS labels for steering traffic and reserving bandwidth. The Label Edge Router (LER) feature implements the headend functionality, i.e., RSVP-TE tunnels can originate at an LER which can steer traffic into the tunnel.

RSVP-TE applies the Resource Reservation Protocol (RSVP) for Traffic Engineering (TE), i.e., to distribute MPLS labels for steering traffic and reserving bandwidth.

RSVP-TE P2MP LER adds ingress and egress support for Point-to-Multipoint (P2MP) LSPs to be used in Multicast Virtual Private Network (MVPN) as an extension to the LSR support which adds transit support.

RSVP-TE P2MP LSR adds transit support for Point-to-Multipoint (P2MP) LSPs. Specifically the feature adds protocol support for the transit role as described in RFC 4875.

The Rule Groups Dashboard aligns with modern DMF User Interface (UI) standards. This view maintains full functional parity with the previous version while delivering a consistent and unified user experience.

With the 13.0 release, you can integrate SAML SSO with a captive portal for authentication. The SAML integration functionality is only available for captive portals hosted on the Arista Cloud. It is not available if the captive portal is hosted on third-party servers or on the access point.

Network administrators require access to flow information that passes through various network elements, for the purpose of analyzing and monitoring their networks. This feature provides access to IP flow information by sampling traffic flows in ingress and/or egress directions on the interfaces on which it is configured. The samples are then used to create flow records, which are exported to the configured collectors in the IPFIX format. Egress Flow tracking is supported from EOS-4.29.0F on the DCS-7170B-64C series and supported on 7280, 7500 and 7800 series platforms from EOS-4.31.1"

Sampled Mirroring is an extension of the Mirroring feature and sampling is a property of the individual mirroring session: when the session's sample rate N is specified, a packet eligible for mirroring will have a 1/N chance of being mirrored, that is, 1 packet is mirrored for every N packets.