03-10-2011 04:44 AM
Hi
I am trying to setup EoMPLS Vlan mode between an ASR9K and a 3825 that is connected as back to back PE's.
Although I managed to get the PW Tunnel up no data passed between the edge devices.
(7200Edge1)-----(ASR9K-PE1)----------(3800-PE2)-------(3800Edge2)
Please advise me on how to fix this.
These are the PE1 and PE2 configs
PE1
hostname ASR9K-PE1
interface GigabitEthernet0/0/0/17
cdp
mtu 1514
!
interface GigabitEthernet0/0/0/17.10 l2transport
encapsulation dot1q 10
!
!
l2vpn
pw-class test
encapsulation mpls
transport-mode vlan
!
!
xconnect group TEST
p2p test
interface GigabitEthernet0/0/0/17.10
neighbor 10.30.0.21 pw-id 7
pw-class test
----------------------------------------------------------------------------
PE2
hostname 3800-PE2
pseudowire-class test
encapsulation mpls
!
interface GigabitEthernet0/1
mtu 1504
no ip address
duplex auto
speed auto
media-type rj45
!
interface GigabitEthernet0/1.10
encapsulation dot1Q 10
xconnect 10.30.0.16 7 pw-class test
!
-------------------------------------------------------------------------------
PE1
sh l2vpn xconnect group TEST det
Thu Mar 10 12:37:41.910 UTC
Group TEST, XC test, state is up; Interworking none
AC: GigabitEthernet0/0/0/17.10, state is up
Type VLAN; Num Ranges: 1
VLAN ranges: [10, 10]
MTU 1504; XC ID 0x840002; interworking none
Statistics:
packets: received 1125, sent 1081
bytes: received 101040, sent 95790
drops: illegal VLAN 0, illegal length 0
PW: neighbor 10.30.0.21, PW ID 7, state is up ( established )
PW class test, XC ID 0x840002
Encapsulation MPLS, protocol LDP
PW type Ethernet VLAN, control word disabled, interworking none
PW backup disable delay 0 sec
Sequencing not set
MPLS Local Remote
------------ ------------------------------ -----------------------------
Label 16003 16
Group ID 0x4000540 0x0
Interface GigabitEthernet0/0/0/17.10 unknown
MTU 1504 1504
Control word disabled disabled
PW type Ethernet VLAN Ethernet VLAN
VCCV CV type 0x2 0x2
(LSP ping verification) (LSP ping verification)
VCCV CC type 0x6 0x2
(router alert label) (router alert label)
(TTL expiry)
------------ ------------------------------ -----------------------------
MIB cpwVcIndex: 0
Create time: 10/03/2011 08:49:09 (03:48:31 ago)
Last time status changed: 10/03/2011 10:15:38 (02:22:02 ago)
Statistics:
packets: received 1081, sent 1125
bytes: received 95790, sent 101040
--------------------------------------------------------------------------------------------------------------------------------------------------------
PE2
sh mpls l2transport vc detail
Local interface: Gi0/1.10 up, line protocol up, Eth VLAN 10 up
Destination address: 10.30.0.16, VC ID: 7, VC status: up
Output interface: Gi0/0, imposed label stack {16003}
Preferred path: not configured
Default path: active
Next hop: 10.0.6.2
Create time: 02:46:12, last status change time: 02:23:06
Signaling protocol: LDP, peer 10.30.0.16:0 up
MPLS VC labels: local 16, remote 16003
Group ID: local 0, remote 67110208
MTU: local 1504, remote 1504
Remote interface description: GigabitEthernet0_0_0_17.10
Sequencing: receive disabled, send disabled
VC statistics:
packet totals: receive 1047, send 1069
byte totals: receive 99846, send 118228
packet drops: receive 0, seq error 0, send 0
Solved! Go to Solution.
03-13-2011 04:09 PM
Hi,
ASR9k will negotiate VC Type 4 with the 3825. By default the AC on the 3825 will pop tag 10 and the PW will add a fake one (could be the same though) to respect VC Type 4.
On the ASR9k, the AC will do nothing by default so you will end with a packet with a double tag. You need to apply the rewrite ingress pop 1 symmetric command on the ASR9k sub-interface so you will have the same behavior than the 3825.
HTH
Laurent.
03-13-2011 10:47 AM
Hi
Looks like your control plane is ok. Can you perform a pseudowire ping to make sure your forwarding plane is ok
Sent from Cisco Technical Support iPhone App
03-13-2011 04:09 PM
Hi,
ASR9k will negotiate VC Type 4 with the 3825. By default the AC on the 3825 will pop tag 10 and the PW will add a fake one (could be the same though) to respect VC Type 4.
On the ASR9k, the AC will do nothing by default so you will end with a packet with a double tag. You need to apply the rewrite ingress pop 1 symmetric command on the ASR9k sub-interface so you will have the same behavior than the 3825.
HTH
Laurent.
03-14-2011 12:33 PM
Thanks Laurent it works......
03-14-2011 02:17 PM
Glad to read that
Laurent.
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