[e-nsp] Problem with vMAN and QinQ

[Roger Wiklund]

That was my original post.

Unfortunately the vMAN implementation in BD6800/EW is very limited. 
All you do to enable vMAN is to change the ethertype from 8100 to 88a8, 
and enable jumbo frames.

But all Cisco switching devices use the default Ethertype field value 
of 0x8100, even when using QinQ (not entirley sure about this). This means 
that you can´t have a regular Q-trunk between a Cisco-device and the 
BD6800, because of the ethertype mismatch.

The solution at least to my knowledge is to use the standard 8100 
ethertype on the BD, and use Cisco devices at the edges with QinQ enabled. 
Or you can use newer Extreme switches, like the x450, that has much better 
vMAN support. And set the vMAN ethertype to 8100. And you can even use 
vMAN and VLAN och the same switch, just specify witch ports belong to 
either vMAN och VLAN.

/Roger


On Tue, 26 Feb 2008, Andraz Sraka wrote:

> Hello,
>
> I came across this post
> <http://puck.nether.net/pipermail/extreme-nsp/2007-April/000159.html>
> when tying to actually put several Cisco 3550 edge switches to work with
> Extreme BD switches - running QinQ.
>
>> Is it possible to run both VLAN and vMAN at the same time on the
>> BD6808?
>> Can you use several Cisco & Extreme switches and have them co-exist with
>> regular L2 Q-trunk between them and use QinQ/vMan at the edges for
>> customers?
>
> Any suggesting how to make this two vendors working together in a way
> double vlan tagging would be possible?
>
> Thanks in advance,
> Andraz
>
> -- 
> Humppa all the way!!
>