This feature increases the number of routes that can be forwarded using hardware on platforms based on ASIC that

This feature allows a user to configure Autonomous System Number (ASN) in Asdot notation and get the ASN in output of

BGP 4.22.0F 4 Byte ASDOT

ASU, or Accelerated Software Upgrade, is a feature to minimize traffic loss when upgrading from one ASU supported EOS

SSU ASU 4.22.0F

ASU (or Accelerated Software Upgrade) is a feature that will minimize traffic loss when upgrading from one ASU

SSU ASU 4.22.0F 4.23.0F

A common way of configuring a switch is with config session or with config replace. In a config session, if the

ACL Rollback 4.22.0F

ACL counters can be displayed on a per chip basis by passing an additional option in the ACL show command. The output of

ACL Counters 4.22.0F

BFD (Bidirectional Forwarding Detection) authentication is used to validate the identity of BFD peers.

This feature implements RFC3107 that allows carrying a label stack with BGP route updates, using multi protocol BGP.

This feature adds support for user configured BGP Nexthop Resolution RIB profiles for various BGP based services

The replace remote AS feature allows a provider edge (PE) router to change the autonomous system (AS) number used by a

The “set as path prepend” clause in route map configuration mode has been enhanced with the addition of

This feature extends the BGP Layer 3 VPN Import/Export and VRF Route Leaking functionality to “default” VRF.

Coherent systems connect data centers over distances of hundreds, even thousands of miles. In some cases, the fiber


This feature allows the user to reset the forward error correction (FEC) statistics counters shown in the output of

PHY 4.22.0F

The feature allows a simulated transceiver removal, without physically touching the module. This can be used for

This article describes the support for IP ACLs on the egress ports for filtering Bridged IPv4 traffic. The users will

ACL 4.22.0F

The base kernel for EOS was upgraded to use newer maintenance version 4.9.122 from version 4.9.108, bringing many


This feature extends the capabilities of event monitor to include IPv6 Route and IPv6 Neighbor event logging.

This feature provides a mechanism to export default VRF routes into EVPN and advertise them as EVPN type 5 IP Prefix


Ethernet VPN (EVPN) networks normally require some measure of redundancy to reduce or eliminate the impact of outages and maintenance. RFC7432 describes four types of route to be exchanged through EVPN, with a built-in multihoming mechanism for redundancy. Prior to EOS 4.22.0F, MLAG was available as a redundancy option for EVPN with VXLAN, but not multihoming. EVPN multihoming is a multi-vendor standards-based redundancy solution that does not require a dedicated peer link and allows for more flexible configurations than MLAG, supporting peering on a per interface level rather than a per device level. It also supports a mass withdrawal mechanism to minimize traffic loss when a link goes down.

Starting with EOS release 4.22.0F, the EVPN VXLAN L3 Gateway using EVPN IRB supports routing traffic from one IPV6

Starting with EOS release 4.22.0F, the EVPN VXLAN L3 Gateway using EVPN IRB supports routing traffic from IPV6 host to

Starting with EOS release 4.22.0F, the EVPN VXLAN L3 Gateway using EVPN IRB supports routing traffic from one IPV6

Fair Adaptive Dynamic Thresholds (FADT) provides efficient allocation of shared packet buffer resources amongst

Buffering 4.22.0F VoQ FADT

This feature involves the use of packet’s Time to Live (TTL) (IPv4) or Hop Limit (IPv6) attributes to protect

This feature involves the use of packet’s Time to Live (TTL) (IPv4) or Hop Limit (IPv6) attributes to protect

Hardware counter feature allows enabling counters for features using programmable hardware counter resources.

Counters 4.22.0F

In a typical switch deployment, multiple ports can have the same configuration, such as description and access VLAN.

Many a times it helps to make sure the service, that is going to be provided to a customer, is really going to work as

4.22.0F RFC 2544

IPv4 traffic can be encrypted and carried over IPSec tunnels originating or terminating on EOS dut. 

4.22.0F IPSec

This feature makes a switch act as a neighbor discovery proxy for an IPv6 subnets. It can be used in conjunction with BUM

This configuration command features an IPv6 Neighbor Discovery (ND) option (called Boot File URL (BFURL) option)

This feature adds support for PIM SSM (Source Specific Multicast) for IPv6 Multicast Routing on platforms listed

Multicast Ipv6 4.22.0F PIM6

This feature implements RFC6119, which allows the extension of IS IS protocol to carry IPv6 Traffic Engineering

This feature allows a user to configure multiple static adjacency SIDs for an IS IS adjacency. This feature is an

This feature allows customers to run Label Distribution Protocol (LDP) on a subset of the interfaces that run Multi

LDP MPLS 4.22.0F

The main motivation for the feature is to provide high availability to the ManagementActive interface (Management0) via multiple redundant paths in the modular system. The ManagementActive interface(Management0) is a virtual interface pointing to the active supervisor.

Enhancement of QOS class maps to match on nexthop groups along with dscp (dscp being optional) to set any QOS actions

QoS Nexthop Group 4.22.0F

The objective of Maintenance Mode on MLAG is to gracefully drain away the traffic (L2 and BGP) flowing through a switch

A new configuration model for the BFD (Bidirectional Forwarding Detection) agent was added in order to more

CLI BFD 4.22.0F

The "set metric" clause in a route map sequence has been enhanced with the addition of the "igp nexthop cost" keyword.

Add support for dynamic prefix list based matching in multi agent model. Please refer the TOI for rib

BGP Multi Agent 4.22.0F

The PIM routing protocol builds multicast routing state based on control packets and multicast data events. In our

BGP Multicast 4.22.0F MFA

The OSPFv2 Secure Hash Algorithms (SHA) Authentication support as defined in RFC 5709 supports the configuration of

OSPF supports all of RFC3630 and parts of RFC4203. When configured, OSPF generates the following information in

This feature supports generation of non host routes for the IPv6 neighbor entries learnt on an SVI interface. These

BGP Ipv6 4.22.0F

This feature is an extension of Qos Policy. It allows the user to configure Qos Policy Map counters. If a class map is

RIB Route Control is a method of controlling how IP routing table entries get used. Route resolution policy adds

RIB 4.22.0F Route Control

Secure boot is an anti tamper mechanism. It verifies the cryptographic signature embedded in an EOS SWI image to

Aboot 4.22.0F Secure Boot

Segment Routing Traffic Engineering Policy (SR-TE) aka SR Policy makes use of Segment Routing (SR) to allow a headend to steer traffic along any path without maintaining per flow state in every node. A headend steers traffic into an SR Policy.