<div dir="ltr">Yes that is one way to do it.<div><br></div><div>I would suggesting using a Local-VPLS for this myself. That way, if you ever need to extend out to another router/switch you would be able to do so with the flexibility of changing tags, double tagging, etc.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jan 31, 2014 at 10:36 AM, Todd Adamson <span dir="ltr"><<a href="mailto:tadamson@routers.com" target="_blank">tadamson@routers.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello all. This is my first foray into 802.1q-in-q and I want to make sure that I am doing this correctly. I have a MLXe, version 5.5.0c running that has a client utilizing 5 fiber ports for their own routed backbone network. I currently have them running on their own VLAN and all is good.<br>
<br>
But they now want to change their setup and utilize their own VLANs between locations. To prevent any customer vlan leakage or overlapping of VLAN numbers, I'm planning to incorporate q-in-q on their ports. After reading the docs, it appears that all I have to do is add the following command to the MLXe:<br>
<br>
tag-type 9150 eth 3/11 to 3/15<br>
<br>
Is this all I have to do? Am I missing something?<br>
<br>
Any help/suggestions are appreciated.<span class="HOEnZb"><font color="#888888"><br>
<br>
Todd<br>
<br>
-- <br>
Todd Adamson<br>
<a href="mailto:tadamson@routers.com" target="_blank">tadamson@routers.com</a><br>
<br>
______________________________<u></u>_________________<br>
foundry-nsp mailing list<br>
<a href="mailto:foundry-nsp@puck.nether.net" target="_blank">foundry-nsp@puck.nether.net</a><br>
<a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/<u></u>mailman/listinfo/foundry-nsp</a><br>
</font></span></blockquote></div><br></div>