This is a very interesting question. Have you received any feedback on it ? One very stupid way of doing it would be to untagg towards the XMR or Loop a XMR interface. I know Redback and Ericsson equipment can do this as well.
Curious if you received any feedback on this matter. Regards Andreas On Tue, Apr 22, 2008 at 4:31 PM, David Ball <davidtball at gmail.com> wrote: > I have a non-Foundry switch connected to an XMR Gig port (running > 3.6.0cT163). I'm expecting QinQ'd traffic (tag-types will both be > 8100) coming from that switch. I'm trying to determine how I can > strip off the outer tag, then assign the traffic to different VLLs, > VPLSs, etc. based on the 'inner' tag. I've read the VLANs section of > the config guide a few times over and either it's not mentioning it, > or I don't 'get' it. I'm more familiar with Juniper's way of doing > this, which lets you inspect both inner and outer tags, and do > pop/push/swap with the tags, but am struggling to understand how the > XMRs handle things. Any insight would be appreciated. > Some (possibly irrelevant) config snippets are below. > > interface ethernet 2/1 > enable > no spanning-tree > no flow-control > gig-default neg-off > ! > <snip> > vll vll-tagged 500 raw-mode > vll-peer 172.16.0.1 > vlan 500 > tagged e 2/11 > <snip> > _______________________________________________ > foundry-nsp mailing list > foundry-nsp at puck.nether.net > http://puck.nether.net/mailman/listinfo/foundry-nsp > -------------- next part -------------- An HTML attachment was scrubbed... URL: https://puck.nether.net/pipermail/foundry-nsp/attachments/20080422/b51b8ff4/attachment.html
