Tag :: 4.25.0F

This feature adds a configuration option which provides a CLI error if a reference is made to an unconfigured policy

To use IPv6 addresses for VXLAN underlay, there are two different approaches.  The first approach is to make use of

This feature provides the capability to count the number of packets hitting rules associated with egress ACLs

This feature provides the capability to count the number of packets hitting rules associated with egress ACLs

Normally the ingress router in the following diagram has no control over an autonomous system border router’s

This feature adds control plane support for inter subnet forwarding between EVPN networks. This support is achieved

In a traditional EVPN VXLAN centralized anycast gateway deployment, multiple L3 VTEPs serve the role of the

Logical ports are hardware resources that are required to activate interfaces.

BFD sessions are only established for OSPFv2 and OSPFv3 adjacencies that are in the FULL state.  In a LAN environment

This feature adds support to match against nexthop address for VPNV4/V6 routes. This support allows

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 NTP service in EOS may be configured to act as an NTP server for other devices as clients.  Previously, all clients

The feature allows modification of the egress TTL of packets routed via PBR, and  to modify the TTL of naked IP/IPv6

This feature extends link bandwidth extended community deletion mechanism, which previously always required

A Management VRF instance allows network operators to separate their management traffic from the rest of the

This document describes the OSPFv2 and OSPFv3 feature that allows enabling or disabling the inclusion of LSAs having

4.25.0F adds support to use large community lists in the ‘set large community’ route map set clause.

Sub-interfaces can be grouped into logical units called scheduling groups, which are shaped as a single unit. Each scheduling group may be assigned a scheduling policy which defines a shape rate in kbps and optionally a guaranteed bandwidth, also in kbps.

This document details how to use the Zero Touch Provisioning (ZTP) USB configuration feature. Arista’s Zero Touch