Hi, You can use a single service instance and configure "encapsulation default". It will match all ingress frames just like the ME3400 dot1q-tunnel.
On Tue, Nov 4, 2014 at 7:35 PM, Tony Bunce <[email protected]> wrote: > Does anyone have tips on how to get the equivalent of a dot1q-tunnel > between a ME3400 and a ME3600 working? I'm trying to provide a pretty > basic Metro-E type service for a customer and have a ME-3400 at one site > and a ME-3600 at the other site. A ME-3400 sits at the head end to connect > the two sites. > ME-3400 --> ME-3400E <-- ME3600 > > The 3600 doesn't support dot1q-tunnel so I have to use a EVC on that > side. I'm trying to get all traffic (some tagged, some untagged) from port > 1 of the ME-3400 at one site to port 1 of the ME-3600. > > If I replace the ME-3600 with a 3400 and do a basic dot1q-tunnel > everything works fine and the customer is able to pass vlans between the > two sites. When I try to use the 3600 the customer can't ping between the > two sites. I see mac address from Site 1 in Site 2's mac table but pings > don't seem to work > > ME-3400 (Site 1) > ! > interface GigabitEthernet0/1 > description P-t-P MetroE > switchport access vlan 400 > switchport mode dot1q-tunnel > > ME-3600 (Site 2): > interface GigabitEthernet0/1 > description P-t-P MetroE > switchport trunk allowed vlan none > switchport mode trunk > mtu 9000 > service instance 1 ethernet > encapsulation untagged !untagged traffic > l2protocol tunnel cdp stp vtp dtp lacp > bridge-domain 400 > ! > service instance 2 ethernet > encapsulation dot1q 1-4094 !all tagged vlans > bridge-domain 400 > ! > end > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
