Hi Guys, Worst case (slightly temporary) solution would be to carefully configure an exit for the QinQ domain into the 802.1q domain and put a crossover cable from one port to another.
Unless of course you have a big overlap of regular vlan's. cheers /rolf On Monday 21 May 2007 10:31:17 David Freedman wrote: > Bridging was also suggested, but I dont think this would be suitable > since we are talking about a couple of 100 Megs of traffic with lots of > multicast :) > > Does anybody know what kind of performance gain provided by using l2 > local switching over bridging? > > I can't find much documentation on this, I'm assuming that because > l2 local switching was developed with CEF in mind it should have bad > things about it, but I could be wrong... > > Dave. > > David Freedman wrote: > > Anybody know when this will be available? > > > > Currently does not work in 12.2(28)SB6 on 72xx > > > > ! > > int g0/3.28100 > > encaps dot1q 28 second-dot1q 100 > > ! > > int g0/3.28150 > > encaps dot1q 28 second-dot1q 150 > > ! > > > > (config)#connect foo Gi0/3.28100 Gi0/3.28150 > > QinQ not supported on GigabitEthernet0/3.28100 > > %CONN: invalid segment 1 > > %CONN: Invalid Command > > > > Many thanks > > > > David Freedman > > > > _______________________________________________ > > 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/
