- Written by Keon Vafai
- Posted on September 30, 2019
- Updated on September 30, 2019
- 12014 Views
This feature implements RFC3107 that allows carrying a label stack with BGP route updates, using multi protocol BGP.
- Written by Shamit Kapadia
- Posted on April 25, 2022
- Updated on June 19, 2023
- 11742 Views
To understand why BGP-LU tunnels are required to be redistributed into LDP and vice versa, let’s consider the following basic topology for InterAS Option C. It uses IS-IS as IGP where indicated along with LDP:
- Written by Andrew Li
- Posted on November 9, 2020
- Updated on December 23, 2021
- 10801 Views
Normally the ingress router in the following diagram has no control over an autonomous system border router’s
- Written by Andrew Li
- Posted on November 11, 2021
- Updated on December 28, 2021
- 10076 Views
Egress Peer Engineering (EPE) using BGP LU enables traffic engineering of the links between Autonomous Systems
- Written by Pedro Coutinho
- Posted on April 16, 2021
- Updated on April 16, 2021
- 9544 Views
The MPLS ping/traceroute utilities were extended in EOS version 4.26.0F to support connectivity checking of BGP
- Written by Yaonan Liang
- Posted on September 11, 2023
- Updated on September 14, 2023
- 5710 Views
Normally BGP allocates local labels and installs LFIB entries for all received IPv4/IPv6 Labeled Unicast (LU) routes in anticipation of readvertising them with nexthop-self. However, some deployments don’t require nexthop-self with LU routes, so LFIB hardware resources are needlessly allocated, which can present an issue in large scale LU deployments.