Tag :: TOI

IFA Latency Analyzer feature measures round trip time(RTT) and per-hop latency( residence time) between source and destination switches by sending IFA(Inband Flow Analyzer) probes. On Switch A, in this version of script, packet is first redirected to an internal loopback interface and latency is measured as time duration between the time the packet ingresses internal loopback port to time it egresses out of the interface connected Switch B in the chip pipeline.

IFA Latency Analyzer feature measures round trip time(RTT) and per-hop latency( residence time) between source and destination switches by sending IFA(Inband Flow Analyzer) probes.

IGMP Snooping Proxy feature is an optimization over IGMP snooping. When IGMP Snooping Proxy is enabled, the switch

This feature enables the user to configure a list or range of BGP attributes to be ignored by the router on receipt of a BGP update message. The BGP attributes are discarded from the BGP update message, and unless the action of discarding an attribute causes the update message to trigger error handling, then the update message is parsed as normal.

You can import Ekahau floor plans to CloudVision Cognitive Unified Edge (CV-CUE) and then manage the access points (AP) from CV-CUE. Once you import the floor plan to CV-CUE, you can map the AP to CV-CUE and start managing the AP.

DMF 8.5 introduced a newly designed Create Policy configuration workflow, replacing the former workflow page.

Each ARP/ND packet into a switch may generate an update for the switch ARP/Neighbor table and this update may need to be synchronized with the MLAG peer when VXLAN is configured. Prior to this feature, these updates (on a VXLAN setup) are synchronized by sending an UDP packet (one packet per update) containing the IP/MAC/VLAN information from the MLAG peer where the ARP/ND packet is received to the other MLAG peer. 

For network monitoring and troubleshooting flow related issues, it is desirable to know the path, latency, queue and congestion information for flows at different times. The inband telemetry feature(INT), based on Inband Flow Analyzer RFC draft -IFA 2.0 and IFA 1.0(on some platforms) , is used to gather per flow telemetry information like path, per hop latency and congestion. INT is supported for both IPv4 and IPv6 traffic.

Incoming LACPDU Rate Limit on Arista switches allows for errdisabling of ports experiencing a sustained rate of

With the 20.0 release, network administrators can enable 14 unique SSIDs per Access Point (AP). If your network includes APs that are not on the 20.0 release or do not support more than 8 SSIDs, then such APs broadcast only 8 SSIDs. Only those APs that support 14 SSIDs will broadcast all SSIDs.

The Infrastructure Dashboard provides an overview of the health of all managed Access Points (APs). This dashboard provides a real-time health snapshot of your access points, covering connectivity status, performance metrics, link speed, power delivery, RF noise, channel usage, and distribution.

With the 14.0 release, CV-CUE introduces an Infrastructure Dashboard that provides an overview of the health of all managed access points (APs).You can view the Infrastructure Dashboard by navigating to

Implementing these identifier fields ensures compatibility with IPFIX record collector tools that require both ingress and egress data for flow record processing.

This feature optimizes the utilization of hardware resources by sharing the hardware resources between different VLAN interfaces when they have the same ACL attached in the ingress direction. This is particularly useful for larger deployments where the ACL is applied to multiple VLANs and with the RACL sharing capability, lesser hardware resources are used irrespective of the number of VLANs.

On DCS 7048, DCS 7280E, DCS 7500 and DCS 7500E, prior to EOS 4.14.5, multicast traffic using ingress replication would

The feature enables support for displaying per traffic class counters on ingress interfaces. The feature is

This feature provides support for per-interface ingress/egress packet/byte counters for both IPv4 and IPv6.

The Inner IP hashing for MPLSoGRE feature enabled hashing of inner IP source/destination address. With this

This feature when configured enables users to rewrite the DSCP of the GUE encapsulated header on IP-over-UDP tunnels while preserving the TOS value of the inner IP ( IPv4 / IPv6 ) payload. Starting from software version 4.34.1F, the CLI configuration to enable or disable DSCP preserve globally on the egress interface introduces a clear distinction in the behavior of GUE encapsulation on the core facing interface of the IP-over-UDP tunnels. ( The user can configure DSCP to be rewritten using a set DSCP action via QoS Policy-Map or Traffic-Policy )

The DCS 7280E and DCS 7500E platforms are virtual output queue (VOQ) based architectures where there is a VOQ for all

Arista access points (APs) support the integration of SESimagotag’s Electronic Shelf Labels (ESLs), which dynamically display prices and offers in retail environments. The SES-Imagotag Retail IoT Connector (USB dongle) connects automatically to the ESLs through a proprietary protocol based on the IEEE 802.15.4 standard. This dongle plugs into the USB port of Arista APs and is managed by SESimagotag’s Serial Communication Daemon (SCD). The SCD ensures seamless AP and USB dongle connectivity to VusionCloud.

To address these challenges, AristaAppForSplunk is integrated directly into EOS. The application now ships with the SWI image and will automatically enable once the Splunk Universal Forwarder is installed on the switch. Not only does it reduce potential compatibility breakages to a large extent, but also eliminate the installation step of the AristaAppForSplunk extension.

This feature, when enabled, allows NAT to function on traffic traversing between VRFs, over inter-VRF static routes or routes leaked to VRFs other than where they were configured.

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.

The Interface Diagnostics quick action provides you with a fast and efficient way to run interface cycles and cable diagnostics on your campus devices from the Campus Health Overview Dashboard. The devices available are those with a Campus tag, which is automatically assigned to devices configured with the Campus Fabric Studio (L2/L3/EVPN).

The document describes the support for dedicated and group ingress policing on interfaces without using QoS policy-maps to match on the traffic and apply policing.

This document describes the support for interface policing counters on interfaces where interface policing feature is configured. Counters for this feature provide information on how many packets are being allowed or dropped on a given interface via the policers configured. The counters are only supported on interfaces where dedicated policers are configured.

You can use the Access Interface Configuration quick action to assign configuration profiles to devices. The guided workflow will display an illustration of device front panels, which you can use to select interfaces from.

You can use the Access Interface Configuration quick action to assign configuration profiles to devices. The guided workflow will display an illustration of device front panels, which you can use to select interfaces from.

In a typical switch deployment, multiple ports can have the same configuration, such as description and access VLAN. With the interface profile feature, a user can define a set of Ethernet configurations in an “interface profile.” Then, the profile can be applied to one or more Ethernet interfaces, so that all the commands defined in the profile will be configured on the interface. Any changes made in the profile will automatically update the configurations of the interfaces using the profile.

One of the reasons why Wi-Fi clients encounter RF issues is non-Wi-Fi interference. All Wi-Fi 6 and above APs can perform interference classification. CloudVision Cognitive Unified Edge (CV-CUE) classifies interference into four categories — Wi-Fi, Microwave Oven (MWO), Frequency Hopping Spread Spectrum (FHSS), and Continuous Wave (CW).

VLAN COS and IP DSCP values in a packet may be inconsistent. Without this feature, regardless of the interface's QoS trust mode, VLAN tagged packets always use the VLAN COS value as the input priority for PFC PG selection. This can lead to unpredictable PFC behavior. This feature allows tagged packets to use the QoS trust mode as the source for PG selection, instead of always using VLAN COS. This unifies the behavior for tagged and untagged packets, ensuring consistent PFC operation.

The internet exit feature enables hosts attached to a VRF in an edge router to reach prefixes that may be reachable over the internet. Since the addresses assigned within a VRF may be non-routable private addresses which cannot be directly used when going to the Internet, the NAT feature is used as a part of the Internet exit solution to provide internet connectivity.

IPv6 multicast routing protocols are used to distribute IPv6 datagrams to one or more recipients. IPv6 PIM builds and maintains multicast routing using reverse path forwarding (RPF) based on the unicast routing table. IPv6 PIM is protocol-independent and can use routing tables consisting of OSPFv3, IPv6 BGP or static routes, for RPF lookup. MLD is used to discover multicast hosts and maintain group membership on a directly attached link.

With this feature, Arista 7050 and 7050X series of switches can now decapsulate IP in IP tunneled packets. When IP in IP decapsulation is configured, incoming packets with an outer IP header having IpProto=4 (IP in IP) and IpDest matching the one configured will be decapsulated, meaning that the outer IP header will be removed from the packet and all subsequent forwarding decisions will be based on the inner IP header.

With this feature, Arista 7050 and 7050X series of switches can now decapsulate IP in IP tunneled packets.

IP Locking is an EOS feature configured on an Ethernet Layer 2 port or on a VLAN. When enabled, it ensures that a configured port or all member ports of a configured VLAN will only permit IP and ARP packets with IP source addresses that have been authorized. IP Locking prevents another host on a different IP Locking enabled interface from claiming ownership of an IP address through either IP or ARP spoofing. Additionally, IP Locking prevents hosts from masquerading as a DHCP server by blocking DHCP (server-to-client) packets.

Current behavior for IPv4 Options packets is to let Kernel do the forwarding. Strata Platforms do this by setting the action of drop=1 and CPU=1 in the IP_OPTION_CONTROL_PROFILE_TABLE Hardware table so that all IPv4 options packets reach the CPU for forwarding in the Kernel.

Similar to L4 ports, ACL rules can be configured to filter ingress packets based on their IP length (present in the IPv4

IP Source Guard (IPSG) is a security feature that can help prevent IP spoofing attacks. It filters inbound IP packets

With this feature, IPv4 or IPv6 packets matching a static nexthop-group route can be encapsulated within an IP-in-IP tunnel and forwarded

With this feature, IPv4 or IPv6 packets matching a static nexthop-group route can be encapsulated within an IP-in-IP tunnel and forwarded

When the next hop of an IP route (hereafter referred to as the dependent route) resolves over another IP route (hereafter referred to as the resolving route), the adjacency information of the resolving route’s FEC is typically duplicated into the dependent route’s FEC. With this feature, we prevent the duplication of the adjacency information. Instead, the dependent route’s FEC points to the resolving route’s FEC, forming a hierarchical FEC for the dependent route.

This feature addresses a restriction on the combination of IKE and IPSec algorithms that can be used in a security configuration. The National Information Assurance Partnership (NIAP) Common Criteria certification requires that:

Support for IPSec connections in a full-cone Network/Port Address Translation (NAT) environment has been added to the Dynamic Path Selection (DPS) setup. DPS optimizes application performance by selecting different paths for various types of traffic. In this configuration, STUN is used to discover the translated IP address of WAN interfaces and export it to BGP.

PKI (Public Key Infrastructure) is a certificate based authentication solution for IPsec protocol.

IPSec tunnel mode support allows the customer to encrypt traffic transiting between two tunnel endpoints.

This feature enables dataplane forwarding of IPv4 traffic on interfaces that are not IPv4 address enabled, but only

IPv4 routes of certain prefix lengths can be optimized for enhanced route scale on 7500E, 7280E, 7500R and 7280R

IPv4 routes of certain prefix lengths can be optimized for enhanced route scale. This document describes the enhancements done to IPv4 route scale in subsequent EOS releases.