Re: MPLS ping not working

Hi,

I'd like to learn some more about this command "ping mpls ipv4 ....".
Anyway I played around with it and it seems like it might work if you
try "ping mpls ipv4 20.20.20.0 255.255.255.0". Even if that works I'm
not sure what it tells us.

I then captured via Wireshark with a normal ping from R1 to see that
mpls encapsulation was occurring.

-Rich

On Sat, Jun 18, 2011 at 2:39 PM, Naufal Jamal <naufalccie_at_yahoo.in> wrote:
> Hi,
>
> I have a 3 router scenario, R1 in the middle R2 in the left and R3 in the
> right. All the interfaces of routers are advertised through eigrp 100. We have
> a full ipv4 reachability. I have configured loopbacks on all the routers like
> R1 has 1.1.1.1 and etc.
>
> From R2 i am trying to ping one interface in R3 (20.20.20.2) via MPLS but
> unable to do so.
>
> R2#ping mpls ipv4 20.20.20.2 255.255.255.0
> Sending 5, 100-byte MPLS Echos to 20.20.20.2/24,
> timeout is 2 seconds, send interval is 0 msec:
> Codes: '!' - success, 'Q' - request not sent, '.' - timeout,
> 'L' - labeled output interface, 'B' - unlabeled output interface,
> 'D' - DS Map mismatch, 'F' - no FEC mapping, 'f' - FEC mismatch,
> 'M' - malformed request, 'm' - unsupported tlvs, 'N' - no label entry,
> 'P' - no rx intf label prot, 'p' - premature termination of LSP,
> 'R' - transit router, 'I' - unknown upstream index,
> 'X' - unknown return code, 'x' - return code 0
> Type escape sequence to abort.
> QQQQQ
> Success rate is 0 percent (0/5)
>
> Below are the ouputs of ldp neigbors and ldp bindings from R2. Any guess why
> the mpls ping is not working here??
>
> R2#sh mpls ldp nei
> Peer LDP Ident: 20.20.20.2:0; Local LDP Ident 2.2.2.2:0
> TCP connection: 20.20.20.2.14310 - 2.2.2.2.646
> State: Oper; Msgs sent/rcvd: 62/61; Downstream
> Up time: 00:47:00
> LDP discovery sources:
> Targeted Hello 10.10.10.2 -> 20.20.20.2, passive
> Addresses bound to peer LDP Ident:
> 20.20.20.2 3.3.3.3
> Peer LDP Ident: 1.1.1.1:0; Local LDP Ident 2.2.2.2:0
> TCP connection: 1.1.1.1.646 - 2.2.2.2.58751
> State: Oper; Msgs sent/rcvd: 56/59; Downstream
> Up time: 00:43:04
> LDP discovery sources:
> FastEthernet0/0, Src IP addr: 10.10.10.1
> Addresses bound to peer LDP Ident:
> 10.10.10.1 1.1.1.1 20.20.20.1
>
> R2#sh mpls ldp binding
> tib entry: 1.1.1.0/24, rev 21
> local binding: tag: 17
> remote binding: tsr: 20.20.20.2:0, tag: 17
> remote binding: tsr: 1.1.1.1:0, tag: imp-null
> tib entry: 2.2.2.0/24, rev 9
> local binding: tag: imp-null
> remote binding: tsr: 20.20.20.2:0, tag: 18
> remote binding: tsr: 1.1.1.1:0, tag: 16
> tib entry: 3.3.3.0/24, rev 23
> local binding: tag: 18
> remote binding: tsr: 20.20.20.2:0, tag: imp-null
> remote binding: tsr: 1.1.1.1:0, tag: 17
> tib entry: 10.10.10.0/24, rev 17
> local binding: tag: imp-null
> remote binding: tsr: 20.20.20.2:0, tag: 16
> remote binding: tsr: 1.1.1.1:0, tag: imp-null
> tib entry: 20.20.20.0/24, rev 19
> local binding: tag: 16
> remote binding: tsr: 20.20.20.2:0, tag: imp-null
> remote binding: tsr: 1.1.1.1:0, tag: imp-null
>
>
>
>
>
>
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Sat Jun 18 2011 - 18:26:37 ART