The OSPF Non Stop Forwarding (NSF) feature adds support for Graceful OSPF Restart (IETF RFC 3623) and Graceful OSPFv3

EOS 4.15.3F adds support for configuring auto cost in OSPFv3 for routed ethernet interfaces and LAG interfaces.

An OSPF router can attract all traffic towards itself from within the OSPF network, by advertising a default route. Often it is desirable to advertise this default route conditionally, for instance, only when there is a connection to an upstream router or when a default route is learnt through other protocols like BGP. OSPF conditional default-originate provides the above functionality.

OSPF distribute list is a policy construct to filter out routes received from OSPF LSAs so that they will not be

The OSPF Max LSA Retransmission Threshold feature adds a configurable limit to the number of LSA update

OSPF Non Stop Forwarding (NSF) adds support for Graceful OSPF Restart, IETF RFC 3623 .  With OSPF Graceful Restart

An OSPF router can attract all traffic towards itself from within the OSPF network, by advertising a default route. Often it is desirable to set a route tag in this default route. This feature will add a CLI parameter to default-information originate that allows an external route tag to be set on the default route for both unconditional and conditional modes.

This feature adds authentication support for OSPFv3. Unlike OSPFv2, OSPFv3 does not have authentication fields

EOS 4.17.0F adds support for BFD in OSPFv3. BFD provides a faster convergence in scaled deployments where using

OSPFv3 distribute-list is a policy construct to filter out routes received from OSPFv3 LSAs so that they will not be installed on the router even though the routes are resolved and are installable. The filtering is performed after SPF calculation and only on routes from received LSAs, not on self-originated LSAs. This feature does not affect the OSPFv3 protocol behavior of the router. LSAs are exchanged, e.g. flooded, even if the routes are not installed locally on the router.

EOS release 4.20.1F adds OSPFv3 flood pacing support that allows configuring the minimum interval between the

TOI 4.20.1F

In previous releases of EOS, Stub area and NSSA area types were supported for OSPFv3, but without support of the "no

Today in any WAN deployment, customers are required to configure path metrics in load balance policy to program a set of best paths in dataplane. Path metrics are multi-dimensional, it include loss, latency, jitter, and load of path. It is not very intuitive to come up with exact values for these metrics as they are highly dependent on the type of application and geographical locations of routers. Also these path metrics keep changing and except for a few apps that require strict max characteristics on latency, jitter or loss, the other apps are able to tolerate variances in metrics.

Overlay IPv6 routing over VXLAN Tunnel is simply routing IPv6 packets in and out of VXLAN Tunnels, similar to

This document describes a few enhancements done in Wireless Manager (WM) release 8.8 in respect of  AP firmware

By default, the scheduling between parent interfaces and the attached shaped subinterfaces is done in strict priority mode where the parent interface has higher priority than shaped subinterfaces. Subinterfaces that are not shaped use the same queues as the parent so the traffic on these subinterfaces will also have strict priority over shaped subinterfaces.

With the 14.0 release, you can add device passwords and AP-Server Key passphrase as defined in the password policy. The passwords are based on the password policy and password settings that you configure in CV-CUE.

This feature provides the capability to mirror special L2 control frames, called the Pause or Priority Flow Control

Policy Based Routing (PBR) provides the flexibility of routing according to custom defined policies in a way that

Prior to EOS 14.15.0F, if a single packet hit both a PBR and an ACL rule, then only the hardware counters corresponding

The per port per VLAN feature allows application of QoS policies for IP, IPv6 and non IP traffic on a per port per VLAN

TOI 4.17.0F

DCS 7010T. DCS 7050X. DCS 7250X. DCS 7260X. DCS 7280E, DCS 7280R. DCS 7300X. DCS 7320X. DCS 7500E,

This feature enables per port TC-To-COS mapping, where TC represents Traffic-Class and COS represents Vlan tag PCP bits. While at present there is a global TC-To-COS mapping, we can use the TC-To-COS feature to create custom profiles which can be applied to the required interfaces. 

Per VLAN MAC Learning is a feature to enable/disable mac learning per vlan instead of per port. Using this feature with

TOI 4.17.0F

Policy-map counters can be configured to display per-interface counters for all class-maps attached to all successfully programmed policy-maps. The feature is not enabled by default and has to be configured through the command line interface. When enabled, the output of the show command will display both per-interface and aggregate counters.

The Per-MAC ACL feature provides the functionality to apply an IPv4/IPv6 ACL to a 802.1x supplicant instead of applying them on the port that the supplicant is behind. This allows for more flexible and specific traffic policies to be defined for supplicants trying to access certain resources on the network.

The software for Syslog, NTP and SNMP used in EOS resolves hostnames at service start-up. It’s possible that during service operation, the configured host becomes unavailable and the configuration needs to be set to a different host to continue the service. The problem is that such change requires manual restart of the service. Even if the hostname doesn’t change and only the underlying address is updated at the DNS server, the administrator has to manually reset service configuration.

Permitting traffic during ACL updates has been available for traffic steering in tap aggregation mode since EOS

Hosts in a branch need to access internet bound services. In traditional deployments, edge routers in branches are connected to the internet via WAN port. To secure the internal network from the internet we have ACLs( Access Control Lists ) to filter the traffic in/out from the WAN port. If we want to filter the traffic into the port we have ingress ACL, egress ACL filters the traffic out of the port. By default, without any ACL configuration present on the WAN port, we accept every traffic coming to the WAN port.

PFC (Priority based Flow Control) is a flow control mechanism used in RDMA environments. PFC provides a link level

This feature enables detection of egress queues that are unable to transmit packets for prolonged periods of time

DCS 7050X/X2/X3 series. DCS 7060X/X2/X3 series. In previous releases, PFC Watchdog supported only queues

This article is intended to discuss how to configure the Phone VLAN on an Arista switch.

The PHY test pattern CLI can be used to check the quality of the physical layer for an Ethernet interface. This is done by

PIM External Gateways (PEGs) allow an EVPN overlay multicast network to interface with an external PIM domain. They can be used to interconnect two data centers using an external PIM domain in between them.

PIM VRF feature adds VRF support to these existing multicast protocols: PIM SM, PIM BSR, IGMP and MSDP.

PIM Static Source Discovery (SSD) is a feature implemented as part of PIM-SM. Familiarity with setting up and configuring PIM-SM (Sparse Mode) and PIM-SSM (Source-Specific Multicast) is assumed.

Ingress policing on front panel ports is supported on DCS 7010X and DCS 7050X since EOS4.14.0F. When ingress policing

TOI 4.17.0F

Traffic is managed through policy maps that apply data shaping methods to specific data streams. A policy map is a data

TOI 4.20.1F

EOS provides support for the use of IPsec to establish and maintain IPsec tunnels. This feature adds support for redirecting traffic matching on traffic policy rules to an IPSec tunnel.

QoS profiles have been applicable on fabric and front panel ports across all platforms from EOS 4.17.0F release

Policy Based Routing (PBR) is a feature that is applied on routable ports, to preferentially route packets.  This is

In previous versions, the DMF Controller had a hidden CLI command to change the log level from INFO to WARN for a particular port down log in the DMF Controller. This hidden command has been removed in DMF 8.7.0. The following is an example of the hidden command:

Port mirroring is used to send a copy of packets seen on one port to a network monitoring connection on another switch port. Port mirroring is commonly used with network probes or other monitoring devices; examples include intrusion detection devices, latency analyzers, or packet capture and protocol analysis tools.

Port Security: Protect mode (PortSec Protect) is newly added to the Port Security feature and is designed to restrict

Introduced in the 4.34.0F release, the maximum links feature allows users to specify the number of active members in both LACP and static port-channels. If active members become inactive due to configuration changes or link failure, previously restricted members can become active. This ensures the port-channel remains operational, preventing disruptions even if all initial active members fail.

Port Channel member status logging on Arista switches allows logging of Ethernet interfaces joining or leaving a

TOI Chicago

The postcard telemetry (GreenT - GRE Encapsulated Telemetry) feature is used to gather per flow telemetry information like path and per hop latency. For network monitoring and troubleshooting flow related issues, it is desirable to know the path, latency and congestion information for flows at different times.

View PTP counters to identify the types of messages being sent and received by PTP-enabled devices. Use this to troubleshoot issues with your network PTP configuration and connectivity. When announce and sync messages are present but delay request messages are missing, for instance, it may suggest that a host is having trouble locking to the boundary clock.

Precoding is used to help reduce the burst error length of DFE (Decision Feedback Equalizer) error events with PAM-4 modulation