04-08-2013 03:28 AM
Hello
We are trying to set up a pseudowire connection between a Cisco 7609-S and ME3600.
When xconnect is applied on physical interface or service instance there is no problem.
When we are moving to interface vlan xconnect is up but ac is down.
Cisco 7609 is using a 7600-ES+20G3CXL gigabit port NOT RSP720 and IOS version c7600rsp72043-advipservicesk9-mz.153-1.S.bin
ME3600 is using IOS version me360x-universalk9-mz.153-1.S1.bin
We have successfully set up the same scenario with 2 ME3600.
Please check attached files for sample configurations and show - debugs commands.
Regards
Antonis.
04-08-2013 04:42 AM
I forgot to mention that in 7609-S show mpls forwarding-table Outgoing interface is none.
Network Topology
7609----------ME3600---------ME3600
| |
| |
interface interface
vlan20 vlan20
04-08-2013 05:18 AM
Hi Antonis
Could you try with any other encapsulation rather than the "default" on 7600 because it looks like that 7600 AC is not showing up probably because of this.
Regards
04-08-2013 05:41 AM
Hi
I have change the configuration in both with the same results
ME3600
interface GigabitEthernet0/23
switchport trunk allowed vlan none
switchport mode trunk
service instance 20 ethernet
encapsulation dot1q 20
rewrite ingress tag pop 1 symmetric
bridge-domain 20
interface Vlan20
no ip address
xconnect 172.16.0.1 20 encapsulation mpls
Cisco 7609-S
interface GigabitEthernet1/18
description TEST_MPLS_PSEUDOWIRE
no ip address
load-interval 30
speed 1000
no cdp enable
service instance 20 ethernet
encapsulation dot1q 20
rewrite ingress tag pop 1 symmetric
bridge-domain 20
interface Vlan20
no ip address
xconnect 172.18.0.17 20 encapsulation mpls
Antonis.
04-08-2013 10:09 PM
Hello Antonis,
Please look in to this area.
I think you already have done with the above problem here
http://www.gossamer-threads.com/lists/cisco/nsp/169757
Regards
Thanveer
"Everybody is genius. But if you judge a fish by its ability to climb a tree, it will live its whole life believing that it is a stupid."
04-10-2013 02:31 AM
Cisco 7906 have 2 mpls enabled interfaces one L3 and one L2+SVI. The label-switched path was through L2 interface. When we route the path through L3 core facing mpls interface the pseudowire was came up.
Our initial thought for bringing up the pseudowire through an SVI was to replace the following scenario
7609 <---------- ME3600-B <--------- ME3600-A <------- BGP SESSION
We have a BGP session with a carrier delivered on ME3600-A. Because ME3600 is not able to carry bgp table we have create vlan 100 and we and made the gigabit port access to vlan 100.
ME3600-A
vlan 100
name BGP_PEERING
interface GigabitEthernet0/1
description BGP_PEERING
switchport access vlan 100
ME3600-A and ME3600-B are interconnected with a trunk port.
ME3600-B
vlan 100
name BGP_PEERING
ME3600-B and 7609 are also interconnected with a trunk port
CISCO 7609-S
vlan 100
name BGP_PEERING
interface Vlan128
description BGP_PEERING
ip address XXX.XXX.XXX.XXX 255.255.255.248
So the vlan 100 travels all the way from ME3600-A to 7609 and the bgp session is running on 7609.
I am trying to say is possible to replace the vlan with EoMPLS ?
Best Regards
Antonis.
04-10-2013 02:42 AM
Yes you can do that by enabling MPLS on the 3600's and on 7600 using routed PW concept.
So, your config on 7609 will look like:
interface Vlan128
description BGP_PEERING
ip address XXX.XXX.XXX.XXX 255.255.255.248
xconnect
!
On the ME3600-A simply use EVC and run a EoMPLS.
04-10-2013 07:06 AM
For some reason ME3600 is sending packets but is not receiving
3600#show mpls l2transport vc 250 detail
VC statistics:
transit packet totals: receive 0, send 593
transit byte totals: receive 0, send 45388
transit packet drops: receive 0, seq error 0, send 0
7609#show mpls l2transport vc 250 detail
VC statistics
transit packet totals: receive 1030, send 0
transit byte totals: receive 63730, send 0
transit packet drops: receive 0, seq error 0, send 0
7609 configuration
interface Vlan250
ip address 192.168.33.2 255.255.255.0
xconnect 172.18.0.17 250 encapsulation mpls
3600 configuration
interface GigabitEthernet0/23
switchport trunk allowed vlan none
switchport mode trunk
service instance 250 ethernet
encapsulation untagged
bridge-domain 250
interface Vlan250
no ip address
xconnect 172.16.0.0 250 encapsulation mpls
I have tried several ways on 3600 xconnect under L3 physical interface, xconnect under L2 service instance physical interface but same behavior in all cases.
Any ideas ?
04-10-2013 07:33 AM
On ME 3600 use xconnect under the service instance and also if possible try a tagged encapsulation.
Also on 7600 what is the mpls enabled interface. Is it a Vlan ?
04-10-2013 07:36 AM
With tagged encap you muat also use "rewrite ingress tag pop 1 symmetric"
04-12-2013 12:59 AM
I cannot add tagget encapsulation since traffic from carrier will be untagget.
Regards
Antonis.
04-15-2013 12:53 AM
Any suggestions?
04-15-2013 05:40 AM
Lets make a recap
HOST(192.168.33.2/24)----->ME3600------>7609(SVI:192.168.33.1/24)
ME3600
vlan 250
name RPW
interface GigabitEthernet0/23
switchport trunk allowed vlan none
switchport mode trunk
service instance 250 ethernet
encapsulation untagged
bridge-domain 250
interface Vlan250
no ip address
xconnect 172.16.0.0 250 encapsulation mpls
7609
vlan 250
name RPW
interface Vlan250
ip address 192.168.33.2 255.255.255.0
xconnect 172.18.0.17 250 encapsulation mpls
Keep in mind 7609 has only one core facing L3 interface.
From mpls l2 detailed
7609
VC statistics:
transit packet totals: receive 29, send 0
transit byte totals: receive 4252, send 0
transit packet drops: receive 0, seq error 0, send 0
3600
VC statistics:
transit packet totals: receive 0, send 31
transit byte totals: receive 0, send 4496
transit packet drops: receive 0, seq error 0, send 0
Packet recieved from 3600 no packets send from 7609.
Any ideas? I have read that this is a working scenario.
04-28-2013 10:14 PM
Hi
On ME3600, instead of the configuration you have could you try the below:
interface GigabitEthernet0/23
switchport trunk allowed vlan none
switchport mode trunk
!
service instance 250 ethernet
encapsulation untagged
xconnect 172.16.0.0 250 encapsulation mpls
!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide