cancel
Showing results for 
Search instead for 
Did you mean: 

Adding VMANs to an Existing VLAN network

Adding VMANs to an Existing VLAN network

Chris1
New Contributor
We're running a network with a good deal of switches, we're L2/L3 pretty much all over the place, using basic vlans. But now we need to provide service to another provider and we're trying to figure out how to make it work, i've probably read through the vman docs 4-5 times but still keep getting lost maybe its the abreviations not sticking or something but i just keep getting lost.

We have

Sites - Other Sites - Core via L2 vlans currently some sites have customers hooked up on the switches on untagged vlan ports, from site to site we're always tagging...

So now what we want to do is be able to dump a give a port on our core to the other provider, and a port at each of our sites, that way we only have to truck 1 vman/vlan across our network of 60+ switches instead of lugging hundreds of their vlans across 1 at a time which will be a logistical nightmare.

Can we do this easily if so how, to operate vlan and vman on same network of switches and transit these vlans between our sites+core to their hardware+core transparently to us.
10 REPLIES 10

Hi,

just to clarify this sentence:

"Need to change vman ethertype to 0x8100 on any switches before you create a vman on it. This ethertype seems to be more universal than the default Extreme uses of 0x88a8. "

0x8100 is the ethertype for 802.1Q VLAN.
0x88a8 is the ethertype for 802.1ad Provider Bridge (aka VMAN, aka Q-in-Q)

These are IEEE standards.
Changing the 802.1ad ethertype to 0x8100 is a trick to transport a VMAN across switches not aware of this standard encapsulation. Extreme EXOS allows you to do it, fortunately.
GTM-P2G8KFN