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

 

299 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: ,


Notable Replies

  1. milan9 says:

    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. Marek,
    This topic can become less confusing if you think about what is going on in the control plane vs the data plane. The RTs are used in the control plane to associate ROUTES with VRFs. The VPN label is used in the data plane to associate PACKETS with VRFs.

    Check out this great article that talks about why RDs, RTs, and VPN Labels are all needed:
    https://mellowd.co.uk/ccie/?p=2923

  3. Dear Rene,,
    I have encountered following log message when setting this up. Can you confirm if we need to make the Loopback Interfaces as /32 s across the MPLS core ?

    *Jan 15 01:49:04.853: %BGP-4-VPNV4NH_MASK: Nexthop 1.1.1.1 may not be reachable from neigbor 2.2.2.2 - not /32 mask

  4. This error occurs if you have a loopback interface with a subnet mask that is not /32 and that is advertised in OSPF.

    OSPF will always advertise a loopback as a /32 (network type LOOPBACK). LDP however, looks at the actual subnet mask of the interface so there will be a mismatch between LDP and your routing table.

    To fix this, you have two options:

    • Change the network type of your loopback interface to ip ospf network-point-to-point so that OSPF advertises the actual subnet mask of the interface.

    OR

    • Change the subnet mask of the loopback interface to /32.

    Rene

  5. Hi Rene,
    When we give a trace from a Non-MPLS device and its travel thru a MPLS network.So, how Device know about the MPLS path IP and label from output ..

    CE1#traceroute 5.5.5.5 source loopback 0
    Type escape sequence to abort.
    Tracing the route to 5.5.5.5
    VRF info: (vrf in name/id, vrf out name/id)
      1 192.168.12.2 0 msec 0 msec 4 msec
      **2 192.168.23.3 [MPLS: Labels 17/19 Exp 0] 0 msec 0 msec 4 msec**
      **3 192.168.45.4 [MPLS: Label 19 Exp 0] 0 msec 0 msec 4 msec**
      4 192.168.45.5 0 msec 0 msec *

    So from the output how CE1 informed the IP 192.168.23.3 and 192.168.45.4 with the label value 17 , 19 respectively.I want to know the discovering process deeply. please assist me in your clear text .Thx

    I know how Traceroute works normally but In MPLS domain I cant understand .

    br//zaman

Continue the discussion forum.networklessons.com

41 more replies

Participants