<div dir="ltr"><div><div><div>Dear Martijn,<br><br></div>Thank you for your feedback but I'm trying to achieve the other way around ie strip Provider's outer VLAN.<br><br>We do agree on the fact that provider-facing port has to be declared as expecting QinQ frames :<br><br>tag-type 9100 ethe X/Y.<br><br></div>Then, I have to "strip out" outer-VLAN and declare my end clients 802.1Q VLANs in their VPLS instances :<br><br><div><a name="148cb2da0b402206_1084050">Brocade(config-mpls)#vpls test 10</a></div>
<div><a name="148cb2da0b402206_1084054">Brocade(config-mpls-vpls-test10)#vlan X inner-vlan Y</a></div>
<div><a name="148cb2da0b402206_1084058">Brocade(config-mpls-vpls-test_10-vlan-X-inner-vlan-Y)#tagged Ethernet 2/1</a></div><br>X being SP transport VLAN (outer VLAN) and Y being clustomer VLAN (inner VLAN).<br><br></div>I am correct ?<br><br>Thanks.<br><div><div><br><br><div class="gmail_extra"><br><div class="gmail_quote">2014-10-02 18:32 GMT+02:00 i3D.net - Martijn Schmidt <span dir="ltr"><<a href="mailto:martijnschmidt@i3d.net" target="_blank">martijnschmidt@i3d.net</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Hello Youssef,<br>
<br>
It looks something like the below for MPLS VLL, I haven't
experimented with VPLS yet but suspect you'd have to terminate as
untagged as well:<br>
<br>
tag-type 9100 ethe 7/2<br>
<br>
vll MODERATED 3003<br>
vll-peer A.B.C.D<br>
untag e 7/2<br>
<br>
SSH@MODERATED#show vlan e 7/2<br>
VLL name MODERATED, VLL ID:
3003, VLAN: 1 Untagged<br>
<br>
Best regards,<br>
Martijn<div><div class="h5"><br>
<br>
<div>On 10/02/2014 05:37 PM, Youssef
Bengelloun-Zahr wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>
<div>Hello Martijn,<br>
<br>
</div>
Would care to share some configuration example please ?<br>
<br>
</div>
Best regards.<br>
<br>
<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2014-10-02 17:25 GMT+02:00 i3D.net -
Martijn Schmidt <span dir="ltr"><<a href="mailto:martijnschmidt@i3d.net" target="_blank">martijnschmidt@i3d.net</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> Youssef,<br>
<br>
In our experience with QinQ over MPLS VLL, not VPLS,
you'll want to make the customer-facing MPLS port
untagged.<br>
<br>
QinQ will then encapsulate the whole thing, dump it into
the VLL as a single "instance/VLAN", and <random
device> on the other side of the line can unpack it
again.<br>
<br>
Best regards,<br>
Martijn
<div>
<div><br>
<br>
<div>On 10/02/2014 05:15 PM, Youssef Bengelloun-Zahr
wrote:<br>
</div>
</div>
</div>
<blockquote type="cite">
<div>
<div>
<div dir="ltr">
<div>Hello,<br>
<br>
Anyone ?<br>
<br>
</div>
Y.<br>
<div class="gmail_extra"><br>
<br>
<br>
<div class="gmail_quote">2014-10-01 12:07
GMT+02:00 Youssef Bengelloun-Zahr <span dir="ltr"><<a href="mailto:youssef@720.fr" target="_blank">youssef@720.fr</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>Dear Community,<br>
<br>
</div>
A provider of ours is handing off
clients VLANs over a fiber interco
using QinQ (outer VLAN is for
transport on their network and
inner VLAN is our end client).<br>
<br>
</div>
We actually terminate this on a
Cisco ME but would like to move that
to an MLXe action as MPLS PE and map
VLANs into different MPLS instances.<br>
<br>
</div>
I wanted to confirm the exact stanza
based on what I found in NI5.4 config
guide :<br>
<br>
</div>
1/ Activate QinQ on the provider facing
port :<br>
<br>
tag-type 9100 ethe X/Y.<br>
<br>
</div>
<div>I found this section in the guide
related to this :<br>
<br>
<div><a name="148d1b487366bf18_148d17677fb5b28d_148cb2da0b402206_1084042">"<i>Special
considerations for dual-tagged
endpoints</i></a></div>
<i> </i>
<div><i><a name="148d1b487366bf18_148d17677fb5b28d_148cb2da0b402206_1084043">Before
configuring a dual-tagged VPLS
endpoint, consider the following:</a></i></div>
<i> </i>
<div style="margin-left:0pt">
<table summary="" border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr style="vertical-align:baseline">
<td>
<div style="width:18pt;white-space:nowrap">
<i><span>• </span></i> </div>
</td>
<td width="100%">
<div><i><a name="148d1b487366bf18_148d17677fb5b28d_148cb2da0b402206_1084044">The
tag protocol identifier
(TPID) of the inner VLAN
tag must be 0x8100 be
classified as
dual-tagged and
recognized by
dual-tagged endpoints.
If the TPID is not
0x8100, the packet will
be classified as a
single-tagged packet.</a></i></div>
</td>
</tr>
</tbody>
</table>
</div>
<i> </i><i> </i>
<table summary="" border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr style="vertical-align:baseline">
<td>
<div style="width:18pt;white-space:nowrap">
<i><span>• </span></i> </div>
</td>
<td width="100%"><i> </i>
<div><a name="148d1b487366bf18_148d17677fb5b28d_148cb2da0b402206_1084045"><i>The
TPI</i>D of the outer VLAN
tag must be the port’s
configured tag type (the
default tag type is
0x8100)."</a></div>
</td>
</tr>
</tbody>
</table>
<br>
<br>
</div>
2/ Map client VLAN into the different VPLS
instances :<br>
<br>
<div><a name="148d1b487366bf18_148d17677fb5b28d_148cb2da0b402206_1084050">Brocade(config-mpls)#vpls
test 10</a></div>
<div><a name="148d1b487366bf18_148d17677fb5b28d_148cb2da0b402206_1084054">Brocade(config-mpls-vpls-test10)#vlan
X inner-vlan Y</a></div>
<div><a name="148d1b487366bf18_148d17677fb5b28d_148cb2da0b402206_1084058">Brocade(config-mpls-vpls-test_10-vlan-X-inner-vlan-Y)#tagged
Ethernet 2/1</a></div>
<br>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>X being SP transport
VLAN (outer VLAN) and Y
being clustomer VLAN
(inner VLAN).<br>
<br>
<br>
</div>
<div>Does that sound about
right to you ?<br>
<br>
</div>
<div>Thanks for the
feedbacks.<br>
<br>
</div>
<div>Best regards.<span><font color="#888888"><br clear="all">
</font></span></div>
<span><font color="#888888">
<div>
<div>
<div>
<div><br>
<br>
<br>
-- <br>
Youssef
BENGELLOUN-ZAHR<br>
</div>
</div>
</div>
</div>
</font></span></div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
Youssef BENGELLOUN-ZAHR<br>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div>
</div>
<pre>_______________________________________________
foundry-nsp mailing list
<a href="mailto:foundry-nsp@puck.nether.net" target="_blank">foundry-nsp@puck.nether.net</a>
<a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a></pre>
</blockquote>
<br>
<br>
<br>
<font face="arial">Best regards,<br>
<br>
Martijn Schmidt<br>
<font color="000000"><a href="http://www.i3D.net" target="_blank">http://www.i3D.net</a></font>
<br>
<br>
<img src="cid:part13.08020201.04040401@i3d.net" width="100" align="left" height="59">i3D.net is a
private company registered in The Netherlands at Meent
93b, Rotterdam. Registration #: 14074337 - VAT # NL
8202.63.886.B01. i3D.net is CDSA certified on Content
Protection and Security and provides hosting from 16
global ISO-certified datacenters. We are ranked in the
Deloitte Technology Fast 500 EMEA as one of the fastest
growing technology companies. <br>
</font><br>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
Youssef BENGELLOUN-ZAHR<br>
</div>
</blockquote>
<br>
<br>
<br>
<font face="arial">Best regards,<br><br>Martijn Schmidt<br><font color="000000"><a href="http://www.i3D.net" target="_blank">http://www.i3D.net</a></font> <br><br><img src="cid:5b9cf835.8e7c0883.jpg.1038440e" width="100" align="left" height="59">i3D.net is a private company registered in The Netherlands at Meent 93b, Rotterdam. Registration #: 14074337 - VAT # NL 8202.63.886.B01. i3D.net is CDSA certified on Content Protection and Security and provides hosting from 16 global ISO-certified datacenters. We are ranked in the Deloitte Technology Fast 500 EMEA as one of the fastest growing technology companies. <br></font><br>
</div></div></div>
</blockquote></div><br><br clear="all"><br>-- <br>Youssef BENGELLOUN-ZAHR<br>
</div></div></div></div>