# BGP PIC (Prefix Independent Convergence) Core & Edge **URL:** \ **Category:** Lessons Discussion\ **Created:** [March 29, 2018, 11:31am UTC](https://forum.networklessons.com/t/bgp-pic-prefix-independent-convergence-core-edge/3367 "2018-03-29T11:31:29Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![chrisnewnham17](https://cdn-forum.networklessons.com/letter_avatar_proxy/v4/letter/c/f9ae1b/32.png) [@chrisnewnham17](https://forum.networklessons.com/u/chrisnewnham17)\ **Post date:** [November 10, 2018, 3:02pm UTC](https://forum.networklessons.com/t/bgp-pic-prefix-independent-convergence-core-edge/3367/2 "2018-11-10T15:02:08Z")
Great lesson, Rene! I studied this from the Cisco documentation but they never explained in clear terms what was going on, but you managed it! Small typo (should be 88.88.88.88/32?): > 88.88.88.88/43 via 192.168.24.4 interface GigabitEthernet0/1 Also could you provide the configs for PIC edge, at the end? === Just came across this quote from Cisco: > PIC core ensures fast convergence for BGP routes when there is a link or node failure in the core that causes a change in the IGP reachability to a remote BGP next-hop address. > > PIC edge ensures fast convergence to a BGP backup path when an external (eBGP) edge link or an external neighbor node fails. In your example you use iBGP between PE’s for obvious reasons, so I’m a bit surprised they say PIC edge is for “external neighbours”? > **[Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 6.x...](https://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/6_x/nx-os/unicast/configuration/guide/b-7k-Cisco-Nexus-7000-Series-NX-OS-Unicast-Routing-Configuration-Guide-Release-6x/n7k_unicast_config_basic_bgp.html)** > > Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 6.x > -Configuring Basic BGP --- _[View the full topic](https://forum.networklessons.com/t/bgp-pic-prefix-independent-convergence-core-edge/3367)._