- Written by Keon Vafai
- Posted on 9月 30, 2019
- Updated on 9月 30, 2019
- 3889 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 4月 25, 2022
- Updated on 6月 19, 2023
- 3464 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 11月 9, 2020
- Updated on 12月 23, 2021
- 3962 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 11月 11, 2021
- Updated on 12月 28, 2021
- 3827 Views
Egress Peer Engineering (EPE) using BGP LU enables traffic engineering of the links between Autonomous Systems
- Written by Pedro Coutinho
- Posted on 4月 16, 2021
- Updated on 4月 16, 2021
- 3136 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 9月 11, 2023
- Updated on 9月 14, 2023
- 168 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.