Tag :: BGP

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

Adds the ability to revert to previous behavior where BGP and static routes could resolve over BGP aggregates (when

This feature is provided on all platforms. The BGP listen range command has been modified to optionally allow

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

It is often useful to know on a per AFI/SAFI basis, the number of paths that have been selected from a peer as best paths.

ACL based traffic management often requires matching packets’ destination addresses against one or more sets of

BGP Conditional route inject provides the capability to control BGP advertisements based on certain conditions in

This feature adds support for “Enhanced Route Refresh” capability (RFC7313). An enhanced route refresh is,

The goal of IAR operation is to minimize the CPU processing and churn in hardware by identifying a set of nexthop adjacencies such that updating those adjacencies in-place is sufficient to correctly forward the traffic quickly for all the affected routes.

This feature adds support for sending and receiving BGP IPv6 labeled-unicast routes with IPv4-mapped IPv6 next hops. With this feature enabled, when a BGP speaker receives a next hop with IPv4-mapped IPv6 address,

This feature adds support for BGP peering over IPv6 link local addresses. This feature is available with the with the

The BGP-LS extension to be obsoleted allows IGP (OSPF/IS-IS) link state database information to be injected into BGP. This is typically used in deployments where some external component, (like a controller or Path Computation Engine) can do centralized path computations by learning the entire IGP topology through BGP-LS. The controller can then communicate the computed paths based on the BGP-LS updates to the head end device in the network. 

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

The BGP graceful restart mechanism has a limitation that the graceful restart time cannot exceed 4095 seconds per the

BGP Monitoring Protocol (BMP) allows a monitoring station to connect to a router and collect all of the BGP

BGP Monitoring Protocol (BMP) allows a monitoring station to connect to a router and collect all of the BGP

The route reflector, as described in RFC 4456, is a router allowed to advertise (reflect) iBGP learned routes to other

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

BGP Non Stop Forwarding (NSF) aims to minimize the traffic loss when the the following scenarios occur:

Route reflectors are commonly used to distribute routes between BGP peers belonging to the same autonomous system. However, this can lead to non-optimal path selection. The reason for this is that the route reflector chooses the optimal route based on IGP cost from its perspective. This may not be optimal from the perspective of the client as its location may be different from the RR

The BGP graceful restart mechanism has a limitation that the graceful restart time cannot exceed 4095 seconds as per

BGP update wait for convergence feature prevents BGP from programming routes into hardware and advertising routes

The sub route map configuration simplifies routing policies by sharing common policy across route maps. Common

RPKI provides a mechanism to validate the originating AS of an advertised prefix. EOS support

Remove Private AS Ingress is a feature used for removing and replacing private AS numbers from inbound AS paths, so

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 adds support for BGP peering with multiple peers using the same IP address. The router id of those peers is

This change adds a global toggle to BGP communities that allow for community sharing to be enabled/disabled for all

When a Provider Edge (PE) device loses BGP connectivity to the core (uplink) devices, it may be unable to forward any traffic from its downlink devices, typically CE (Customer Edge) devices. It is beneficial to indicate this connectivity loss to these CE devices so that they may find alternative paths to forward traffic.

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.

BGP Monitoring Protocol (BMP) allows a monitoring station to connect to a router and collect all of the BGP announcements received from the router’s BGP peers.

Class Based Forwarding (CBF) is a means for steering IP traffic into colored tunnels based on the ingress DSCP values.  CBF may be used with SR-TE Policy or RSVP-TE colored tunnels.

This feature provides the ability to track the reason why a BGP path is excluded from the BGP best path selection

The “maximum-paths <m>” (default m=1) configuration that controls BGP’s multipath behavior, is available as a global knob, and not as a peer/peer-group knob today in EOS. When “maximum-paths” CLI is configured with m > 1, BGP starts forming ECMP groups for paths with similar attributes received from all configured neighbors.

In a Service Provider network, a Provider Edge (PE) device learns VPN paths from remote PEs and uses the Route Target

The eBgp "ip next hop unchanged" feature allows a router to send routes to its eBgp peers without changing their next

As described in the Multi VTEP MLAG TOI, singly connected hosts can lead to suboptimal peer link utilisation. By

EVPN MPLS VPWS (RFC 8214) provides the ability to forward customer traffic to / from a given attachment circuit (AC)

Multihoming in EVPN allows a single customer edge (CE) to connect to multiple provider edges (PE or tunnel endpoint).

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

The General Router ID configuration provides the ability to configure a common Router ID for all routing protocols

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

This feature introduces the ability to match on 1) any BGP aggregate contributor or 2) a specific BGP aggregate’s

Currently, the 'maximum routes' knob allows one to set an upper bound on the number of routes that can be received from a