Tag :: Multi Agent

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

In the multi agent routing protocol model, the Bgp agent now supports matching community lists with a logical OR via

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

Sflow samples can be augmented with additional Extended gateway data by getting data from BGP in addition to

This feature implements support for RFC8203/BIS so that users can attach the reason of BGP instance or peer session

This feature adds support for BGP UCMP in the multi agent routing protocol model. The TOI for BGP UCMP in the ribd

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

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

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

The Multicast Source Discovery Protocol (MSDP) provides a mechanism to connect together multiple PIM Sparse Mode

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

When there are multiple VRFs on the device and there is a need to share routes between them, typically for shared

VRF Route leaking can be used when routes from one VRF are required in another VRF (e.g. in case of shared services). If

This feature adds support for ‘match interface’ clause under route map config for Bgp policy application in

This feature adds support for ‘match ip(v6) resolved next hop’ clause under route map config for BGP policy

Routing control functions (RCF) is a new language that can be used to express BGP route filtering and attribute

Routing Control Functions (RCF) is a language that can be used to express route filtering and attribute modification logic in a powerful and programmatic fashion. This document covers Configurations of a RCF function for BGP points of application, CLI show commands to provide visibility into operational status, and the protocol attributes supported for BGP points of application.

Routing Control Functions (RCF) is a language that can be used to express route filtering and attribute modification logic in a powerful and programmatic fashion.

Routing Control Functions (RCF) is a language that can be used to express route filtering and attribute modification logic in a powerful and programmatic fashion.

Traffic steering enables traffic for a specified set of prefixes to get forwarded along traffic engineered paths

This feature introduces a metric for static routes so that the user can configure both administrative distance and

Sflow samples can be augmented with additional Extended gateway data by getting data from BGP in addition to

Support for negotiating and receiving IPv6 unicast and IPv6 labeled unicast (6PE) updates from a BGP peer.

This feature adds support for static inter VRF routes. This enables configuration of routes to destinations in one

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

Currently EOS supports redistribution into BGP at the global (instance) level. Also EOS supports redistribution in

The CLI command “show rib route ip[ipv6]” and its sub commands (e.g. “show rib route ip

Unequal cost multi path (UCMP) for BGP is a mechanism for forwarding ECMP route traffic using weights, with which the

In the ribd routing protocol model, the “maximum paths … ecmp …” command allows restricting the number of BGP