Using RRs with MPLS - Can't ping between two CEs

[ryanpst88]

OSPF for IGP and all devices know about each other and can ping. The RR is learning routes off both CEs and both CEs are learning the routes from the RR (see "show ip route vrf" section in image) but I just can't ping from R1 to R3 in the VRF.

https://imgur.com/1WiqwTc

Any advice?

[Julio E. Moisa]

Hi

10.255.255.1 & 3 are part of the VRF on the specific router, right? have you tried using source? also have you verified the forwarding table to verify if there are tags?

Show mpls forwarding-table

[ryanpst88]

This is the output of that command, not sure what I'm looking at here?:

7200-1#show mpls forwarding-table
Local  Outgoing      Prefix            Bytes Label   Outgoing   Next Hop
Label  Label or VC   or Tunnel Id      Switched      interface
16     Pop Label     172.31.255.4/32   0             Fa3/0      10.0.0.6
17     No Label      172.31.255.3/32   9940          Gi2/0      10.0.0.3
18     No Label      10.0.0.4/31       0             Gi2/0      10.0.0.3
19     Pop Label     10.255.255.1/32[V]   \
                                       0             aggregate/V1000:RYAN       
20     Pop Label     192.168.0.0/26[V] 0             aggregate/V1000:RYAN       
21     No Label      10.255.255.3/32[V]   \
                                       0             drop
22     No Label      192.168.0.64/26[V]   \
                                       0             drop

[Julio E. Moisa · Accepted solution]

Hi

Please verify the results of this command on each router:

show mpls ldp neighbor 

[ryanpst88]

Thanks for the help Julio. I was missing some standard lines off R2, so R1 and R3 were updating the RR with routes for their VRFs but they couldn't route between one another. This was the output of the command:

7200-RR2#show mpls ldp neighbor
    Peer LDP Ident: 172.31.255.1:0; Local LDP Ident 172.31.255.4:0
        TCP connection: 172.31.255.1.646 - 172.31.255.4.30973
        State: Oper; Msgs sent/rcvd: 103/104; Downstream
        Up time: 01:21:48
        LDP discovery sources:
          GigabitEthernet1/0, Src IP addr: 10.0.0.7
        Addresses bound to peer LDP Ident:
          10.0.0.1        185.72.92.0     172.31.255.1    10.0.0.2
          10.0.0.7
7200-RR2#

#############################

7200-1#show mpls ldp neighbor
    Peer LDP Ident: 172.31.255.4:0; Local LDP Ident 172.31.255.1:0
        TCP connection: 172.31.255.4.30973 - 172.31.255.1.646
        State: Oper; Msgs sent/rcvd: 103/102; Downstream
        Up time: 01:21:17
        LDP discovery sources:
          FastEthernet3/0, Src IP addr: 10.0.0.6
        Addresses bound to peer LDP Ident:
          10.0.0.6        172.31.255.4
7200-1#

#############################

7200-2#show mpls ldp neighbor

7200-2#

#############################

7200-3#show mpls ldp neighbor

7200-3#

Thanks again!

[Julio E. Moisa]

Hi

Really appreciated, now understanding correctly, R2 and R3 are part of the MPLS? Is possible to share the configuration into a notepad?

[ryanpst88]

 Hi sorry just realised I'm missing 10.255.255.1-3 from the diagram, this is the IP I set for the loopback in the VRF.

10.255.255.1 = 7200-1 in V1000

10.255.255.3 = 7200-3 in V1000

[Harold Ritter · Accepted solution]

Hi Ryan,

There are currently no LDP session on R2 and R3. You need to enable LDP ("mpls ip") on all core interfaces.

Regards,