Hi I have not verified but the more specific one should be before the general rule. So you should switch them around.
interface TenGigabitEthernet0/1 service instance 10 ethernet encapsulation dot1q 10 second-dot1q 555 rewrite ingress tag pop 1 symmetric bridge-domain 10555 service instance 20 ethernet encapsulation dot1q 10 second-dot1q any rewrite ingress tag pop 1 symmetric bridge-domain 10000 service instance 30 ethernet encapsulation dot1q 10 rewrite ingress tag pop 1 symmetric bridge-domain 10 In this case, though not tested, a packet tagged 10+555 would be sent too bd10555 and 10+any to bd10000 and then 10+non to bd10. //Mattias Gyllenvarg Obduro Network AB On Wed, Dec 11, 2013 at 3:51 PM, Arash Alizadeh <aras...@hotmail.se> wrote: > Hi, > > I wonder if anyone knows if you in two seperate EFP's could match the same > outermost tag where one matches a single-tagged frame and the other one > matches it when it's stacked . > > I.e: > > interface TenGigabitEthernet0/1 > service instance 1 ethernet > encapsulation dot1q 10 > rewrite ingress tag pop 1 symmetric > bridge-domain 10 > ! > service instance 2 ethernet > encapsulation dot1q 10 second-dot1q any > rewrite ingress tag pop 1 symmetric > bridge-domain 20 > ! > > Unfortunately I'm not able to try this myself and I havn't found anything > on the web covering this scenario. > > Thanks in advance. > > Arash > > _______________________________________________ > cisco-nsp mailing list cisco-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > -- *Med Vänliga Hälsningar* *Mattias Gyllenvarg* _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/