cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
147
Views
10
Helpful
3
Replies
Highlighted
Beginner

MPLS Ping between ASR920 and Juniper MX204

Hello,

My setup looks like this:

|                   |           |                |           |                    |           |                      |           |                     |

|MX204 R1   |------|MX204 R2|------|ASR920        |------|NCS5501-SE |------|   7206VXR    |

|10.10.10.23|           |10.10.10.2|          | 10.10.10.27 |          |  10.10.10.24  |           |  10.10.10.21|

 

IGP (IS-IS) and LDP adjacencies are all up, and from the Junipers (R2 for this case) I can do LSP pings to every other device.

# run ping mpls ldp 10.10.10.23/32
!!!!!
--- lsping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss

[edit]
# run ping mpls ldp 10.10.10.27/32
!!!!!
--- lsping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss

[edit]
# run ping mpls ldp 10.10.10.24/32
!!!!!
--- lsping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss

[edit]
# run ping mpls ldp 10.10.10.21/32
!!!!!
--- lsping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss

 

Classic IOS and IOS -XR:

Can also ping the Junipers.

 

ping mpls ipv4 10.10.10.2/32
Sending 5, 100-byte MPLS Echos to 10.10.10.2/32,
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.
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms

ping mpls ipv4 10.10.10.2/32

Sending 5, 100-byte MPLS Echos to 10.10.10.2/32,
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 rx label,
'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.

!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 2/2/3 ms

 

However on the ASR920 I'm getting unsupported tlv error as below:

 

ping mpls ipv4 10.10.10.2/32
Sending 5, 72-byte MPLS Echos to 10.10.10.2/32,
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,
'l' - Label switched with FEC change, 'd' - see DDMAP for return code,
'X' - unknown return code, 'x' - return code 0

Type escape sequence to abort.
mmmmm
Success rate is 0 percent (0/5)
Total Time Elapsed 86 ms

 

ping mpls ipv4 10.10.10.2/32 source 10.10.10.27 verbose
Sending 5, 72-byte MPLS Echos to 10.10.10.2/32,
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,
'l' - Label switched with FEC change, 'd' - see DDMAP for return code,
'X' - unknown return code, 'x' - return code 0

Type escape sequence to abort.
m size 72, reply addr 10.10.10.2, return code 2
m size 72, reply addr 10.10.10.2, return code 2 ---[ Code meaning: One Or More of the TLVs was not Understood]
m size 72, reply addr 10.10.10.2, return code 2
m size 72, reply addr 10.10.10.2, return code 2
m size 72, reply addr 10.10.10.2, return code 2

Success rate is 0 percent (0/5)
Total Time Elapsed 38 ms

 

Debugs and other troubleshooting information

Running debug from the MX204 and ASR920 while the ping is running shows below:

Junos

lsping sent echo reply for seq 3 to 10.10.10.27 from 10.10.10.2 return code Unknown TLV
lsping echo request, from 10.10.10.27, port 44813, src_ifl_idx 79, dest 127.0.0.1, version no 1, seq no 4, tlv type 64512 flags 0x0
lsping echo request with optional tlv type: 64512, skipping over it
lsping sent echo reply for seq 4 to 10.10.10.27 from 10.10.10.2 return code Unknown TLV
lsping echo request, from 10.10.10.27, port 44813, src_ifl_idx 79, dest 127.0.0.1, version no 1, seq no 5, tlv type 64512 flags 0x0

 

IOS-XE

#debug mpls lspv tlv
tlv debugging is on

LSPV: Echo Hdr encode: version 1, msg type 1, reply mode 2, return_code 0, return_subcode 0, sender handle 0x8ED910D1, sequence number 4, flags 0x0, timestamp sent Sun Feb 21 15:50:47.510, timestamp rcvd Mon Jan 01 03:00:00.000
LSPV: Cisco ext subTLV encode: type 1, length 4, tlv revision 0x4
LSPV: Generic IPv4 prefix encode: destaddr 10.10.10.2/32
LSPV: Echo Hdr decode: version 1, msg type 2, reply mode 2, return_code 2, return_subcode 1, sender handle 0x8ED910D1, sequence number 4, flags 0x0, timestamp sent Sun Feb 21 15:50:47.510, timestamp rcvd Sun Feb 21 15:50:47.496
LSPV: Echo packet decoded assuming tlv version 4

 

Working MPLS ping debugs on the Juniper are as below:

lsping echo request, from 10.10.10.21, port 44813, src_ifl_idx 79, dest 127.0.0.1, version no 1, seq no 4, tlv type 64512 flags 0x0
lsping echo request with optional tlv type: 64512, skipping over it
lsping sent echo reply for seq 4 to 10.10.10.21 from 10.10.10.2 return code Egress-ok
lsping echo request, from 10.10.10.21, port 44813, src_ifl_idx 79, dest 127.0.0.1, version no 1, seq no 5, tlv type 64512 flags 0x0
lsping echo request with optional tlv type: 64512, skipping over it
lsping sent echo reply for seq 5 to 10.10.10.21 from 10.10.10.2 return code Egress-ok

 

Something that I noticed is if i run the mpls ping with fec-type ldp on the ASR920 it works, fec-type generic gives the unsupported tlv error.

 

#ping mpls ipv4 10.10.10.2/32 fec-type generic
Sending 5, 72-byte MPLS Echos to Generic FEC 10.10.10.2/32,
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,
'l' - Label switched with FEC change, 'd' - see DDMAP for return code,
'X' - unknown return code, 'x' - return code 0

Type escape sequence to abort.
mmmmm
Success rate is 0 percent (0/5)
Total Time Elapsed 42 ms


#ping mpls ipv4 10.10.10.2/32 fec-type ldp
Sending 5, 72-byte MPLS Echos to LDP IP FEC 10.10.10.2/32,
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,
'l' - Label switched with FEC change, 'd' - see DDMAP for return code,
'X' - unknown return code, 'x' - return code 0

Type escape sequence to abort.
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 2/14/46 ms
Total Time Elapsed 89 ms

 

Questions

  1. Is there a way to influence the TLVs sent by the ASR?
  2. Is there a knob to tell the 920 to use ldp fec-type by default? As an aside we are not running SR on either the Cisco or Juniper boxes. MPLS OAM configuration options didn't seem to have anything useful in this regard.
  3. Is this a (known) bug on the ASR920? OS version is provided below
  4. Anything else that I can try to get it working? 

IOS XE Version

sh ver | i image|License
licensed under the GNU General Public License ("GPL") Version 2.0. The
documentation or "License Notice" file accompanying the IOS-XE software,
System image file is "bootflash:/asr920igp-universalk9.16.09.04.SPA.bin"
License Level: advancedmetroipaccess
License Type: Permanent

 

Junos Version

Model: mx204
Junos: 18.2R3-S5.3

 

Thank you for any assistance that you may provide.

 

Regards,

 

 

 

 

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Cisco Employee

Hi Wandal,

 

> Is there a way to influence the TLVs sent by the ASR?

You can disable the vendor specific TLVs with the following config:

mpls oam
no echo vendor-extension

> Is there a knob to tell the 920 to use ldp fec-type by default? As an aside we are not running SR on either the Cisco or Juniper boxes.

> MPLS OAM configuration options didn't seem to have anything useful in this regard.

The only way to change the default behavior is by specifying the fec-type on the CLI

> Is this a (known) bug on the ASR920? OS version is provided below

I have seen a few TAC cases referring to an issue on the JUNOS side to cope with the feb-type generic coming from the Cisco side.

> Anything else that I can try to get it working? 

You could continue using fec-type ldp. Alternatively, you could open a case with JTAC to find out if there is an upgrade that would fix the issue on their side.

 

Regards,

Harold Ritter
Sr Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México

View solution in original post

3 REPLIES 3
Highlighted
Cisco Employee

Hi Wandal,

 

> Is there a way to influence the TLVs sent by the ASR?

You can disable the vendor specific TLVs with the following config:

mpls oam
no echo vendor-extension

> Is there a knob to tell the 920 to use ldp fec-type by default? As an aside we are not running SR on either the Cisco or Juniper boxes.

> MPLS OAM configuration options didn't seem to have anything useful in this regard.

The only way to change the default behavior is by specifying the fec-type on the CLI

> Is this a (known) bug on the ASR920? OS version is provided below

I have seen a few TAC cases referring to an issue on the JUNOS side to cope with the feb-type generic coming from the Cisco side.

> Anything else that I can try to get it working? 

You could continue using fec-type ldp. Alternatively, you could open a case with JTAC to find out if there is an upgrade that would fix the issue on their side.

 

Regards,

Harold Ritter
Sr Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México

View solution in original post

Highlighted

Hello Harold,

Thanks for the response. It does seem that the behavior might be more cosmetic than I thought. I've had discussions with other operators who run networks with both 920s and the 204s and they see the same thing but no MPLS services are affected (at least up-to IOS-XE version 16.11.1a). We have lab tested with a few EoMPLS and L3VPN circuits and traffic seems to flow OK.

 

We'll follow up with JTAC to see how to get it fixed, otherwise troubleshooting broken LSPs might be tricky.

 

NB: Disabling echo vendor-extension doesn't change the ping response.

mpls oam
no echo vendor-extension

ping mpls ipv4 10.10.10.2/32 so 10.10.10.27
Sending 5, 72-byte MPLS Echos to 10.10.10.2/32,
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,
'l' - Label switched with FEC change, 'd' - see DDMAP for return code,
'X' - unknown return code, 'x' - return code 0

Type escape sequence to abort.
mmmmm
Success rate is 0 percent (0/5)
Total Time Elapsed 16 ms

 

Thank you again for the response.

Regards,

wandal

Highlighted

Hi Wandal,

 

Yes, it is indeed purely cosmetic. This is just an interop issue between Cisco and Juniper implementation of MPLS OAM.

 

Regards,

Harold Ritter
Sr Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México
Content for Community-Ad