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


363 New Members signed up the last 30 days!


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

Tags: , ,

Forum Replies

  1. Hi Sai,

    I think you refer to MPLS L2 and L3 VPN?

    This is about what protocols we transport over the MPLS VPN network. For example with L3, we can transport prefixes from the customer over our MPLS VPN network. Here’s an example with RIP:

    With MPLS L2 VPN, we can transport Ethernet, frame-relay or any other L2 protocol over the MPLS VPN network:


  2. Hi Rene

    Thank you for the article.

    I could get hold of everything other than why we need vpn label and what are its contents? Why wouldn’t only transport label be enough ?

    Thank you

  3. Hi Rene, Andrew
    I am afraid I still don’t understand one thing- why do we need vpn label if we have both RD and RT’s ?
    It was said the router wouldn’t know what VRF the route belongs to… well:
    When PE1 advertises the route to PE2 , this route is unique for BGP because of RD and PE2 also knows in what VRF to install it thanks to Route Target value.
    So the MPLS VPN label seems to be redundant as the BGP can figure the VRF out based solely on the Route Targets …
    What am I missing in this puzzle :slight_smile:
    Thank you
    Edit- ok, I think I mix up the control and data plane again , found nice explanation here :

  4. Deep says:

    Awesome simplified lessons here! I did not know forum has such in depth explanations too! Any plans for half duplex VRF explanation?

  5. Hello Maodo

    Hmmm, that is strange. I’ll get @ReneMolenaar to take a look…



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