EOS 4.15.0F TOI

802.1X port security controls who can send traffic through and receive traffic from the individual switch ports. A

Ingress policing provides the ability to monitor the data rates for a particular class of traffic and perform action

Starting EOS 4.15.0F, users can configure NAT at IP address level with dynamically assigned one to one mapping

The "set as path prepend" clause in the config route map mode is enhanced to accept the "auto" keyword. The "auto"

AVB technology allows transporting time sensitive professional grade audio and video streams over a switched

At the beginning of 2014 the the Number Resource Organization announced that the pool of 2 byte BGP AS numbers had

EOS BGP implementation normally considers only active routes in RIB for advertisement to its peers. In certain

IPv6 BGP peers and IPv6 prefixes for non default VRFs are supported starting EOS 4.15.0F. All CLI commands available

EOS by default selects the prefix for ECMP if the two paths have the same AS PATH length regardless of the ASN values in

BGP Prefix Independent Convergence (PIC Edge) refers to fast re convergence of traffic destined for BGP prefixes on a

BGP sFlow export is to add BGP route information including source and destination AS path information, local

In order to use the BST(Binary Search Tree) resources more efficiently for multicast, we are introducing a new CLI

Command API's authentication can now be accomplished via X.509 public key certificates. Public key

Command API requests for "show" commands return structured outputs which are based on some internal models in EOS. In

In EOS 4.15.0F release, we have introduced the configuration sessions feature. Configuration sessions allow the

An IPv6 link local address for an interface is generated automatically using the modified EUI 64 scheme. All IPv6

This feature adds support for securing out of band connection between CVX server and CVX clients by SSL/TLS

Stream Control Transmission Protocol (132) is a transport layer protocol, much like TCP. After the IP header, a

The EOS DHCP relay agent now supports forwarding of DHCP requests to DHCP servers located in a different VRF to the DHCP

The following new enhancements to DirectFlow and/or OpenFlow are added in EOS 4.15.0F:. DirectFlow

IEEE802.1D 2004, Section 7.12.6 specifies destination MAC addresses that are normally trapped (not forwarded) by

Starting with EOS4.15.0F, dynamic and symmetric LAG hashing policies are supported on the 7500E platform. Dynamic

Egress ACL deny logging on Arista DCS 7280E, DCS 7500 and DCS 7500E series switches allows the logging of the

IPv4/IPv6 over MPLS packets are now eligible for ACLs at egress stage by default. The feature is applicable only to

Starting EOS 4.15.0F, EOS can monitor (for long durations) low error rate errors on all fabric links. It

The 7280E and 7500E series are Virtual Output Queues (VOQs) based multi chip systems where there is a VOQ for all the

The Hardware Switch Controller (HSC) provides an integration point between the SDN controllers (NSX or Nuage) and

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

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

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

As of EOS 4.15.0F, VRRP is supported in a VRF context. Virtual IP addresses can be reused in different VRF contexts,

IPv6 access lists can be used to filter IPv6 network traffic. Starting EOS 4.15.0F release, we have added support

IPv6 egress ACLs applied to routed interfaces across the same chip on the DCS 7500E and the DCS 7280E series can be

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

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

LANZ is the EOS Latency and congestion ANalyZer. On DCS-7280, DCS-7020, DCS-7500 and DCS-7800 series, it allows monitoring congestion and transmit latencies on both front panel and CPU ports.

Loop protection is a loop detection and prevention method which is independent of Spanning Tree Protocol (STP) and is not disabled when the switch is in switchport backup mode or port is in discarding state. The LoopProtect agent has a method to detect loops and take action based on the configuration by the user. In order to find loops in the system, a loop detection frame is sent out periodically on each interface that loop protection is enabled on. The frame carries broadcast destination MAC address, bridge MAC source address, OUI Extended EtherType 0x88b7 as well as information to specify the origins of the packet.

EOS 4.15.0F adds support for MPLS encapsulation of IP packets in EOS. The functionality is exposed through two

Multiprotocol Label Switching (MPLS) is a networking process that replaces complete network addresses with short

While migrating from PVST to MSTP, or vice verse, the network engineer may choose not to run MSTP throughout the

In Tap Aggregation mode, an interface can be configured as tap or tool port. Tap ports are used to 'tap' the traffic and

Nexthop selection using GRE key allows for nexthop routing selection based on the GRE key of a GRE encapsulated IP

Vmware NSX Controllers expect Hardware VTEPs to monitor the liveness of the Replication Service Node via BFD.  In

OpenFlow 1.3 protocol is supported in EOS 4.15.0F on DCS 7050 and DCS 7050X series of switches. The switch and the

A new forwarding pipeline is being introduced in EOS 4.15.0F which allows the traffic entering the switch to be

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

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

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