Adding VMANs to an Existing VLAN network

[Chris1]

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.

[Chris1]

Anyone around 🙂

[Chris1]

Quick question, if we're passing off the vman to them via our core switches which are a MLAG group...

Do i need to run spanning tree or something on the untagged port facing them that's delivering all the vlans? to prevent a loop between our MLAG1 and MLAG2 and their 2 switches, that they run stpd on? I know stp works via vlan, not vman so ... sorta lost, do i just not add the vman to the ISC port and send it to their port on each unit untagged

[EtherMAN]

Stephane can't say everyone uses 0x8100 but I have 5 carriers where we have a ten gig NNI established and 4 of the 5 requested 0x8100... The one exception has 2 NNI's and we map specific cvids to our svids when we bundle the services over an NNI. I like Chris have a few older switches that in order to do vlans and vmans on the same common trunk link you have to use 0x8100. I have tested triple tags and am doing one triple tag service using 0x8100 I am not sure if we were using 88a8 triple tagging would work. None of the switches support reusing one tag id for vlans and vmans... If you want to discuss this further look me up and call or email direct... I sure don't want to confuse Chris. Chris just out of curiosity take time to ask the other carrier you are doing business with if they have a preferred ethertype for their QnQ service if they ever wanted to hand you a tagged vman.... Still good luck with your efforts...

[Chris1]

Wait so technically, all we need to do if we're 100% extreme, and we're untagging the traffic to return it to standard vlans on the way out to the customer network, is leave it at 88a8? so basically all i'm doing is enabling jumbo frames, and typing "enable/config vman" instead of enable/config vlan" for this qinq vman? Seems ... too simple lol

crap just saw in the 15.3 manual that with x450's with PNP+tagged on same port i have to use 0x8100, from x450-x450 if i'm reading it right.

BTW best recommendation for figuring out of our switch types + version of fw supports vman+vlan on same ports?

Now just got to figure if my various wireless radios, have anywhere i need to enable jumbo support, or if its on by default for the backhauls 