Haven't y'all had to use this command often ? I have. Doesn't seem to work without it in many scenarios...
"rewrite ingress tag pop 1 symmetric" ...seems that for basic, single dot1q tag trunking, I've found that this command is required. Lemme know what you think. However, in scenarios where I've plumed that service instance into an eompls pw (vpws) and not a bridge domain, I have NOT had to use the rewrite ingress tag pop trick.... ...me3600x... interface GigabitEthernet0/6 switchport trunk allowed vlan none switchport mode trunk service instance 491 ethernet encapsulation dot1q 491 rewrite ingress tag pop 1 symmetric bridge-domain 491 interface Vlan491 ip vrf forwarding two ip address 10.80.2.2 255.255.255.0 standby 1 ip 10.80.2.1 standby 1 priority 120 standby 1 preempt delay minimum 60 ...asr901... interface GigabitEthernet0/5 load-interval 30 media-type sfp negotiation auto service-policy input pm service instance 1 ethernet encapsulation dot1q 3290 xconnect 10.101.0.13 17 encapsulation mpls mtu 9206 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Pete Lumbis Sent: Saturday, October 27, 2012 3:47 PM To: Eric A Louie Cc: Cisco NSP Subject: Re: [c-nsp] ME3600x sub-interfaces Eric, To provide routing on a service instance, Jason is correct, you need to tie it to a bridge-domain. service instance 1 ethernet encapsulation dot1q 101 bridge-domain 100 service instance 2 ethernet encapsulation dot1q 201 bridge-domain 100 int vlan 100 ip add 192.168.1.1 255.255.255.0 If you are new to service instances take a look at a doc I wrote on Cisco's support forums to help explain how they work. https://supportforums.cisco.com/docs/DOC-21299 -Pete On Fri, Oct 26, 2012 at 2:04 PM, Eric A Louie <[email protected]> wrote: > Thanks Thomas. That's definitely an option - it was my 2nd one. The > plain old subinterfaces, like on a router, don't work on this platform, apparently. > > Much appreciated, Eric > > > > > ________________________________ > From: "[email protected]" <[email protected]> > To: Eric A Louie <[email protected]>; Cisco NSP > <[email protected]> > Sent: Fri, October 26, 2012 10:53:09 AM > Subject: Re: [c-nsp] ME3600x sub-interfaces > > Hi Eric, > > this is a switch. > > You have to configure a SVI Interface. > > conf t > vlan 55 > int vlan 55 > ip add X.X.x.X > > > if you want to use more vlans on a port you have to use switchport > mode trunk and you should remobe the comannd switchport access vlan 55. > > Regards > Thomas > >> Are sub-interfaces supported on the ME3600x? Or is there some >> special formula > >> that I need to enable them? >> >> Cisco IOS Software, ME360x Software (ME360x-UNIVERSALK9-M), Version >> 15.2(4)S, RELEASE SOFTWARE (fc1) License Level: AdvancedMetroIPAccess >> License Type: Permanent >> >> interface GigabitEthernet0/1 >> no switchport >> ip address 192.168.111.2 255.255.255.0 ! >> interface GigabitEthernet0/2 >> description test interface >> switchport access vlan 55 >> switchport mode trunk >> >> me3600-2(config)#int g0/1.1 >> ^ >> % Invalid input detected at '^' marker. >> >> me3600-2(config)#int g0/2.1 >> ^ >> % Invalid input detected at '^' marker. >> >> >> >> >> Much appreciated, Eric >> _______________________________________________ >> 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/ _______________________________________________ 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/
