We're Sorry, Full Content Access is for Members Only...

If you like to keep on reading, Become a Member Now! Here is Why:

  • Learn any CCNA, CCNP and CCIE R&S Topic. Explained As Simple As Possible.
  • Try for Just $1. The Best Dollar You've Ever Spent on Your Cisco Career!
  • Full Access to our 629 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

 

409 New Members signed up the last 30 days!

satisfaction-guaranteed

100% Satisfaction Guaranteed!
You may cancel your monthly membership at any time.
No Questions Asked!

Tags:


Forum Replies

  1. 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

    ... Continue reading in our forum

  2. Hello Chris

    Thanks for pointing that out, I’ll let Rene know…

    I’ll also let him know about the request for the configurations for PIC edge.

    The Cisco comment is indeed correct. Even though iBGP is run between PE

    ... Continue reading in our forum

  3. Thanks Laz.

    Still don’t really agree though - PIC edge is clearly addressing data plane convergence for IBGP neighbours in a service provider environment.

    I just can’t see how that can be possible be called “external neighbours”, which implies the BGP neighbour operates in a different AS when in fact it doesn’t. The external customer may not even be running BGP!

    Oh well!

Ask a question or join the discussion by visiting our Community Forum