mpls xconnect will not pass data after upgrade to ES+20s

Answered Question
Dec 15th, 2009

on our MPLS network, we are in the process up upgrading to ES+20 cards.  After putting the last batch in, we're finding that syntax has changed.

I have moved the config from the unsupported sub-ints to service instances, but it's still not passing traffic.

A mpls pseudo-wire ping works fine from both directions, but data won't transfer.

If I move the termination point back to an OSM or sip600+10x1ge card it also works fine.

basic design is

end station -> switch (vlan 104) -> trunk-> PE (7600) -> GSR -> PE(7600) -> trunk -> switch -> end station

new service config is:

interface GigabitEthernet1/2

no ip address

service instance 104 ethernet

  encapsulation dot1q 104

  xconnect 10.166.8.30 104 encapsulation mpls

!

end

far side is:

interface GigabitEthernet4/1.104

encapsulation dot1Q 104

xconnect 10.166.8.29 104 encapsulation mpls

end

I don't completely get the rewrite config option, is that what I'm missing here?  (both 7600s are on 12.2.33 SRD3 and the ps-wire ping works perfect)

Anyone have any thoughts?

-frank

I have this problem too.
0 votes
Correct Answer by Laurent Aubert about 4 years 3 months ago

Hi Frank,

As you felt it, ES-20 LC have a different implementation and so different behavior than the classical LC. Actually they are ethernet services oriented

Focussing on L2PVN, the classical LC will always pop up the outer tag (and PW will add another one with vc-type 4) but the EFP interface will do nothing by default. It means in your case you need to add the following command on the ES-20 LC interface:

interface GigabitEthernet1/2

service instance 104 ethernet

rewrite ingress tag pop 1 sym

You may also find the following discussion interesting: https://supportforums.cisco.com/message/973210#973210

HTH

Laurent.

  • 1
  • 2
  • 3
  • 4
  • 5
Average Rating: 5 (1 ratings)
Correct Answer
Laurent Aubert Fri, 12/18/2009 - 07:12

Hi Frank,

As you felt it, ES-20 LC have a different implementation and so different behavior than the classical LC. Actually they are ethernet services oriented

Focussing on L2PVN, the classical LC will always pop up the outer tag (and PW will add another one with vc-type 4) but the EFP interface will do nothing by default. It means in your case you need to add the following command on the ES-20 LC interface:

interface GigabitEthernet1/2

service instance 104 ethernet

rewrite ingress tag pop 1 sym

You may also find the following discussion interesting: https://supportforums.cisco.com/message/973210#973210

HTH

Laurent.

fwalters Fri, 12/18/2009 - 07:47

Laurent,

This makes total sense and works perfectly in the lab.  It's confounded our SE, NSA and Tac handler, your help is much appreciated!

-frank

Actions

Login or Register to take actions

This Discussion

Posted December 15, 2009 at 12:49 PM
Stats:
Replies:2 Avg. Rating:5
Views:1454 Votes:0
Shares:0
Tags: mpls, xconnect
+

Related Content

Discussions Leaderboard