Sub-secondĬonvergence is not supported for BGP PIC Edge for prefixes beyond 4000. The maximum number of bridge domain interfaces (BDI) that can act as protected or protecting interfaces via BGP PIC is 24.īGP PIC Core is enabled only if a minimum of 15 BGP prefixes are received from the peer.īGP PIC edge works only when BGP PIC core is enabled.Įach of the 2 BGP peers must send the same set of 15 BGP prefixes to the DUT.īGP PIC edge provides sub-second convergence for Global prefixes, EoMPLS over BGP LU, VPLS, and 6PE.īGP PIC edge provides sub-second convergence for VPNv4/VPNv6 prefixes with a maximum of 4000 (including global). The BGP Best External feature, you receive an error.īGP PIC over bridge domain interface (BDI) core interfaces can have only one Ethernet Flow Point (EFP) associated with each If you try to configure the BGP PIC feature after configuring The BGP PIC feature does not work with the BGP Best External feature. The BGP PIC feature solves the traffic forwarding only for a single network failure at both the edge and the core. Neither router will reach the CE router, and traffic will continue to be forwarded between the PE routers until the time-to-live When two PE routers become each other’s backup/alternate path to a CE router, traffic might loop if the CE router fails. If the route reflector is only in the control plane, then you do not need BGP PIC, because BGP PIC addresses data plane convergence. ![]() The BGP PIC feature cannot be configured with Multicast or L2VPN Virtual Routing and Forwarding (VRF) address families. The BGP PIC feature supports prefixes only for IPv4, IPv6, VPNv4, and VPNv6 address families. In MPLS VPNs, the BGP PIC feature is not supported with MPLS VPN Inter-Autonomous Systems Option B. With BGP Multipath, the BGP Prefix-Independent Convergence (PIC) feature is already supported. Provider site by more than one path (multihomed).īackup/alternate path has a unique next hop that is not the same as the nextīidirectional Forwarding Detection (BFD) protocol to quickly detect linkįailures of directly connected neighbors. (MPLS) network is up and running with the customer site connected to the An account on is not required.īorder Gateway Protocol (BGP) and the IP or Multiprotocol Label Switching Use Cisco Feature Navigator to find information about platform support and Cisco software image support. This module, and to see a list of the releases in which each feature is supported, see the feature information table at the To find information about the features documented in For the latest feature information andĬaveats, see the release notes for your platform and software release. Your software release may not support all the features documented in this module. In this document, the BGP PIC Edge for IP and MPLS-VPN feature is called by the short name BGP PIC. When a failure is detected, the backup or alternate path immediately Information base (FIB), and Cisco Express Forwarding. ![]() The BGP PIC Edgeįor IP and MPLS-VPN feature creates and stores a backup or alternate path in the routing information base (RIB), forwarding This convergence is applicable to both core and edge failures and can be used in both IP and MPLS networks. The BGP PIC (Prefix Independent Convergence) Edge for IP and MPLS-VPN feature improves BGP convergence after a network failure.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |