ON THIS PAGE
How to Protect and Reroute Traffic Using BGP Labeled Unicast
Summary
Learn how to protect and reroute traffic to the destination network if a border node fails in a multi-domain network.
BGP PIC Edge Using BGP Labeled Unicast Overview
Summary
This section talks about the benefits and overview of BGP PIC Edge using BGP labeled unicast as the transport protocol.
Benefits of BGP PIC Edge Using BGP Labeled Unicast
Provides traffic protection in case of border (ABR and ASBR) node failures in multi-domain networks.
Provides faster restoration of network connectivity and reduces traffic loss if the primary path becomes unavailable.
How does BGP Prefix Independent Convergence Work?
BGP Prefix Independent Convergence (PIC) improves BGP convergence on network node failures. BGP PIC creates and stores primary and backup paths for the indirect next hop on the Routing Engine and also provides the indirect next hop route information to the Packet Forwarding Engine. When a network node failure occurs, the Routing Engine signals the Packet Forwarding Engine that an indirect next hop has failed, and that the traffic is rerouted to a pre-calculated equal-cost or backup path without modifying BGP prefixes. Routing the traffic to the destination prefix continues by using the backup path to reduce traffic loss until the global convergence through BGP is resolved.
BGP convergence is applicable to both core and edge network node failures. In the case of BGP PIC Core, adjustments to the forwarding chains are made as a result of node or core link failures. In the case of BGP PIC Edge, adjustments to the forwarding chains are made as a result of edge node or edge link failures.
BGP PIC Edge Using BGP Labeled Unicast as the Transport Protocol Overview
BGP PIC Edge using the BGP labeled unicast transport protocol helps to protect and reroute traffic when border nodes (ABR and ASBR) failures happen in multi-domain networks. Multi-domain networks are typically used in Metro Ethernet aggregation and mobile backhaul network designs.
On Juniper Networks MX Series and PTX Series routers, BGP PIC Edge supports IPv4, IPv6, BGP labeled unicast, and Layer 3 VPN services. These BGP services are multipath (learnt from multiple PEs) and resolved through BGP labeled unicast routes, which could again be a multipath learnt from other ABRs. Transport protocols supported over BGP PIC Edge are RSVP, LDP, OSPF, and ISIS.
The following BGP service routes are supported:
IPv6 Layer 3 VPN services over IPv4 BGP labeled unicast
IPv4 services over IPv4 BGP labeled unicast
IPv4 Layer 3 VPN services over IPv4 BGP labeled unicast
IPv6 BGP labeled unicast service over IPv4 BGP labeled unicast
Starting with Junos OS Release 19.4R1, MX Series and PTX Series routers support BGP PIC Edge with BGP labeled unicast as the transport protocol.
WHAT'S NEXT
For an example on configuring BGP PIC Edge using BGP labeled unicast, see Example: Protecting IPv4 Traffic over Layer 3 VPN Running BGP Labeled Unicast.
For more information on configuring BGP PIC and load balancing, see Load Balancing for a BGP Session.