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 651 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

470 Sign Ups in the last 30 days

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

Tags: ,

Forum Replies

  1. Great as always. Just one minor issue. On the first topology picture, shouldnt the provider AS number be 123 as you stated in text instead of AS 234 or vice versa?

  2. @Zaman.rubd @lagapides

    The output is correct, keep in mind that MPLS traceroute works a bit different than regular IP traceroute:


    I think they show the IP address of the remote PE router in the VRF on purpose, instead of the interface that connects to the P router. The IP address of the PE router in the VRF is reachable from the CE1 router, making it useful for troubleshooting.

  3. Hi. Thanks for the lesson. It helped me learn something about MPLS.
    One question though. What if I want to connect another 2 CE routers, and wants to add more VRF? I’ve tried adding new address-family ipv4 vrf to existing BGP process in PE1 and PE2, and redistribute the new routing protocol by adding it to address-family ipv4 vrf and all just like in the lesson, but to no success. The new router still can’t ping successfully.

    What’s needed to add new networks to the MPLS VPN? I maybe haven’t understood it all completely.

  4. Hello Ivan,

    You could use a topology like this:


    In that example, I have redundant P and PE routers but I didn’t use MPLS there. What you need for MPLS VPN is:

    • The P routers only run an IGP and MPLS on the interfaces so that’s straight-forward.
    • The PE routers require a full mesh of iBGP for the VPN routes but you could also use a route-reflector instead. Both interfaces that connect to the customer are in the same VRF.

    If you can configure a MPLS VPN topology without redundancy t

    ... Continue reading in our forum

  5. Hello Ivan.

    According to Cisco:

    VRRP is supported on Ethernet, Fast Ethernet, Bridge Group Virtual Interface (BVI), and Gigabit Ethernet interfaces, and on Multiprotocol Label Switching (MPLS) Virtual Private Networks (VPNs), VRF-aware MPLS VPNs, and VLANs.

    Similarly, GLBP can also be used for MPLS implementations as well.

    HSRP, FRRP and GLBP are all protocols that fall into the category of First Hop Redundancy Protocols (FHRP).

    I hope this has been helpful!


79 more replies! Ask a question or join the discussion by visiting our Community Forum