Scribd
Upload
287 views2 pages

BGP PIC Implementation Considerations

The document discusses configuring BGP Prefix Independent Convergence (PIC) on Cisco routers. It describes BGP PIC implementation considerations and provides configuration steps to enable hardware-assisted BGP PIC and calculate backup paths using additional paths selection and route policies.

Uploaded by

sezam102
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
287 views2 pages

BGP PIC Implementation Considerations

The document discusses configuring BGP Prefix Independent Convergence (PIC) on Cisco routers. It describes BGP PIC implementation considerations and provides configuration steps to enable hardware-assisted BGP PIC and calculate backup paths using additional paths selection and route policies.

Uploaded by

sezam102
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

BGP PIC

Restrictions:
• Ensure that the Border Gateway Protocol (BGP) and the IP or Multiprotocol Label Switching (MPLS)
network is up and running at the customer site that is connected to the provider site by more than one
path (multihomed).
• Ensure that the backup or alternate path has a unique next hop that is not the same as the next hop of the
best path.

• BGP PIC Implementation Considerations, on page 1


• Configure BGP PIC, on page 1

BGP PIC Implementation Considerations


• BGP PIC over BVI (core or edge) is not supported.
• For labelled BGP loopback peering, the system supports only one primary and one backup path. No
support for BGP PIC multipath protect.
• PIC EDGE is supported for all services, such as IPv4, IPv6, VPNv4, VPNv6, 6PE, 6VPE, VPWS, VPLS,
and EVPN.over labelled unicast address-family.

Configure BGP PIC


Step 1 cef encap-sharing disable
Example:
RP/0/RP0/CPU0:router(config)# cef encap-sharing disable

By default, without primary and backup path installation in the hardware, IPv4, IPv6, 6PE (per-vrf), 6VPE (per-vrf/per-ce),
L3VPN (per-vrf/per-ce) has good convergence.
When the mode is a per-prefix by default, BGP-PIC does not give good convergence, hence you must do hardware-assisted
PIC. For this, configure the cef encap-sharing disable command in XR Config mode.

BGP PIC
1
BGP PIC
Configure BGP PIC

With hardware-assisted BGP PIC that is configured using the cef encap-sharing disable command, separate hardware
resources (FEC/EEDB) are allocated for every prefix. Cisco recommends you to make sure that the router has sufficient
hardware resources for the resource allocation.
Caution This CLI reprograms the CEF completely and impacts traffic. We recommend that you do it in the maintenance
window.

Step 2 router bgp as-number


Example:

RP/0/RP0/CPU0:router(config)# router bgp 100

Specifies the autonomous system number and enters the BGP configuration mode, allowing you to configure the BGP
routing process.

Step 3 address-family {vpnv4 unicast | vpnv6 unicast | ipv4 unicast | ipv6 unicast}
Example:

RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicast


address-family ipv4 unicast
additional-paths receive
additional-paths selection route-policy backup 1
allocate-label all
!

Step 4 additional-paths selection route-policy route-policy-name


Example:
RP/0/RP0/CPU0:router(config-bgp-af)# additional-paths selection route-policy ap1

Configures extra paths selection mode for a prefix.


Note Use the additional-paths selection command with an appropriate route-policy to calculate backup paths and
to enable Prefix-Independent Convergence (PIC) functionality.
The route-policy configuration is a prerequisite for configuring the additional-paths selection mode for a prefix. This is
an example route-policy configuration to use with additional-selection command:
route-policy ap1
set path-selection backup 1 install
end-policy

BGP PIC
2

You might also like