Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
653
Views
0
Helpful
4
Replies

Limit IN MTU Tunel pseudowire, Why?

FedeSaraullo
Level 1
Level 1

‎01-22-2016 06:01 AM - edited ‎03-05-2019 03:11 AM

Hello to all! I Have a question about the limit of the pw between two cisco 7600.

In direction to RBRPB01 router, the ping mpls pseudowire trunk in 1577 mtu (The tunel is configurated in MTU 9216 aprox)
In direction to RBCRD01 router, the same ping reaches 9000 MTU (working ok).

Here you have the configurations and de pings test. In the middle of both routers there are two CRS-x. 


RBCRD01:

interface GigabitEthernet8/11
description Conexion con CORE-RES6 - (Gi5/2)
mtu 9216
no ip address
logging event link-status
load-interval 30
no cdp enable

interface GigabitEthernet8/11.3017
description Conexion con CORE-RES6 - (Gi6/1) ** Republica ** [tunel a RBRPB01 Te4/2.3017]
encapsulation dot1Q 3017
xconnect 200.63.137.1 3017 encapsulation mpls
service-policy input TDATA-AToM
!

policy-map TDATA-AToM
class BEST-EFFORT
set mpls experimental imposition 0
class DATOS-NO-CRITICOS
set mpls experimental imposition 1
class DATOS-CRITICOS
set mpls experimental imposition 3
class VIDEO
set mpls experimental imposition 4
class VOZ
set mpls experimental imposition 5
class CONTROL-RED
set mpls experimental imposition 6

PING TEST


ping mpls pseudowire 200.63.137.1 2942 verbose sweep 1550 9000 1

RBCRD01#ping mpls pseudowire 200.63.137.1 3017 verbose sweep 1550 9000 1
%Total number of MS-PW segments is less than segment number; Adjusting the segment number to 1
Sending 5, [1550..9000]-byte MPLS Echos to 200.63.137.1,
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.
! size 1550, reply addr 200.51.240.169, return code 3[Labels: 127 Exp: 0]
Rx Interface: 200.51.240.169
local 200.51.240.37 remote 200.63.137.1 vc id 3017
! size 1551, reply addr 200.51.240.169, return code 3[Labels: 127 Exp: 0]
Rx Interface: 200.51.240.169
local 200.51.240.37 remote 200.63.137.1 vc id 3017
! size 1552, reply addr 200.51.240.169, return code 3[Labels: 127 Exp: 0]
Rx Interface: 200.51.240.169
local 200.51.240.37 remote 200.63.137.1 vc id 3017
! size 1553, reply addr 200.51.240.169, return code 3[Labels: 127 Exp: 0]
Rx Interface: 200.51.240.169
local 200.51.240.37 remote 200.63.137.1 vc id 3017
! size 1554, reply addr 200.51.240.169, return code 3[Labels: 127 Exp: 0]
Rx Interface: 200.51.240.169
local 200.51.240.37 remote 200.63.137.1 vc id 3017
! size 1555, reply addr 200.51.240.169, return code 3[Labels: 127 Exp: 0]
Rx Interface: 200.51.240.169
local 200.51.240.37 remote 200.63.137.1 vc id 3017
! size 1556, reply addr 200.51.240.169, return code 3[Labels: 127 Exp: 0]
Rx Interface: 200.51.240.169
local 200.51.240.37 remote 200.63.137.1 vc id 3017
! size 1557, reply addr 200.51.240.169, return code 3[Labels: 127 Exp: 0]
Rx Interface: 200.51.240.169
local 200.51.240.37 remote 200.63.137.1 vc id 3017
! size 1558, reply addr 200.51.240.169, return code 3[Labels: 127 Exp: 0]
Rx Interface: 200.51.240.169
local 200.51.240.37 remote 200.63.137.1 vc id 3017
! size 1559, reply addr 200.51.240.169, return code 3[Labels: 127 Exp: 0]
Rx Interface: 200.51.240.169
local 200.51.240.37 remote 200.63.137.1 vc id 3017
! size 1560, reply addr 200.51.240.169, return code 3[Labels: 127 Exp: 0]
Rx Interface: 200.51.240.169
local 200.51.240.37 remote 200.63.137.1 vc id 3017
! size 1561, reply addr 200.51.240.169, return code 3[Labels: 127 Exp: 0]
Rx Interface: 200.51.240.169
local 200.51.240.37 remote 200.63.137.1 vc id 3017
! size 1562, reply addr 200.51.240.169, return code 3[Labels: 127 Exp: 0]
Rx Interface: 200.51.240.169
local 200.51.240.37 remote 200.63.137.1 vc id 3017
! size 1563, reply addr 200.51.240.169, return code 3[Labels: 127 Exp: 0]
Rx Interface: 200.51.240.169
local 200.51.240.37 remote 200.63.137.1 vc id 3017
! size 1564, reply addr 200.51.240.169, return code 3[Labels: 127 Exp: 0]
Rx Interface: 200.51.240.169
local 200.51.240.37 remote 200.63.137.1 vc id 3017
! size 1565, reply addr 200.51.240.169, return code 3[Labels: 127 Exp: 0]
Rx Interface: 200.51.240.169
local 200.51.240.37 remote 200.63.137.1 vc id 3017
! size 1566, reply addr 200.51.240.169, return code 3[Labels: 127 Exp: 0]
Rx Interface: 200.51.240.169
local 200.51.240.37 remote 200.63.137.1 vc id 3017
! size 1567, reply addr 200.51.240.169, return code 3[Labels: 127 Exp: 0]
Rx Interface: 200.51.240.169
local 200.51.240.37 remote 200.63.137.1 vc id 3017
! size 1568, reply addr 200.51.240.169, return code 3[Labels: 127 Exp: 0]
Rx Interface: 200.51.240.169
local 200.51.240.37 remote 200.63.137.1 vc id 3017
! size 1569, reply addr 200.51.240.169, return code 3[Labels: 127 Exp: 0]
Rx Interface: 200.51.240.169
local 200.51.240.37 remote 200.63.137.1 vc id 3017
! size 1570, reply addr 200.51.240.169, return code 3[Labels: 127 Exp: 0]
Rx Interface: 200.51.240.169
local 200.51.240.37 remote 200.63.137.1 vc id 3017
. size 1571
. size 1572
. size 1573
. size 1574



RBRPB01:

interface TenGigabitEthernet4/2.3017
description Conexion con BB-ASR-REP1 - (Te0/0/0/3) ** Resistencia ** [tunel a RBCRD01 Gi8/11.3017]
encapsulation dot1Q 3017
xconnect 200.51.240.37 3017 encapsulation mpls
service-policy input TDATA-AToM

policy-map TDATA-AToM
class BEST-EFFORT
set mpls experimental imposition 0
class DATOS-NO-CRITICOS
set mpls experimental imposition 1
class DATOS-CRITICOS
set mpls experimental imposition 3
class VIDEO
set mpls experimental imposition 4
class VOZ
set mpls experimental imposition 5
class CONTROL-RED
set mpls experimental imposition 6


interface TenGigabitEthernet4/2
description Conexion con BB-ASR-REP1 - (Te0/0/0/3) ** AToM TDATA **
mtu 9216
no ip address
logging event link-status
load-interval 30
wrr-queue bandwidth 0 0 13 20 20 15 2
wrr-queue queue-limit 0 0 10 18 18 13 2
wrr-queue threshold 3 100 1 1 1 1 1 1 1
wrr-queue threshold 4 100 1 1 1 1 1 1 1
wrr-queue threshold 5 100 1 1 1 1 1 1 1
wrr-queue random-detect min-threshold 3 40 1 1 1 1 1 1 1
wrr-queue random-detect min-threshold 4 60 1 1 1 1 1 1 1
wrr-queue random-detect min-threshold 5 70 80 1 1 1 1 1 1
wrr-queue random-detect max-threshold 3 70 1 1 1 1 1 1 1
wrr-queue random-detect max-threshold 4 80 1 1 1 1 1 1 1
wrr-queue random-detect max-threshold 5 80 90 1 1 1 1 1 1
wrr-queue random-detect 4
wrr-queue random-detect 5
wrr-queue cos-map 3 1 0
wrr-queue cos-map 4 1 1
wrr-queue cos-map 5 1 2
wrr-queue cos-map 5 2 3
wrr-queue cos-map 6 1 4
wrr-queue cos-map 7 1 6 7

Thanks for your attention!

Labels:
0 Helpful
4 Replies 4

Philip D'Ath
VIP Alumni
VIP Alumni

‎01-22-2016 02:27 PM

I'm not sure.  Does the CRS have a consistent MTU applied on the related ports?

0 Helpful

Philip D'Ath
VIP Alumni
VIP Alumni
In response to Philip D'Ath

‎01-22-2016 02:28 PM

Does all the device connect using the same layer 1 cable, or does it pass though some other active device first (weather it me a media converter, switch, etc)?

0 Helpful

FedeSaraullo
Level 1
Level 1
In response to Philip D'Ath

‎01-25-2016 05:06 AM

No, it doesn´t pass trough some other device.

We do ping on other pw tunel on the same interface and  it had the same result.

Sorry for my english..

0 Helpful

FedeSaraullo
Level 1
Level 1
In response to Philip D'Ath

‎01-25-2016 05:02 AM

Yes, the CRS have applied a consistent MTU on the related ports. 

In a CRS:

 interface Bundle-Ether7
description Conexion con RBCRD01 - (Po7)
mtu 9100
service-policy output QOS_BACKBONE
ipv4 address 200.51.240.166 255.255.255.254
load-interval 30
flow mpls monitor FNF_MONITOR_MAP-2 sampler FNF_SAMPLER_MAP ingress
logging events link-status

In the other CRS:

interface TenGigE0/5/0/0
description Conexion con RBRPB01 - (Te3/1)
mtu 9216
service-policy output QOS_BACKBONE
ipv4 mtu 9086
ipv4 address 200.51.240.168 255.255.255.254
load-interval 30
flow mpls monitor FNF_MONITOR_MAP-2 sampler FNF_SAMPLER_MAP ingress

0 Helpful
Customers Also Viewed These Support Documents
Review Cisco Networking products for a $25 gift card