[j-nsp] dot1q CCC/MPLS on EX4200 series switches

[David Ball]

  We've used EX4200s as 10Gig customer demarc in a few situations and
do just that.  Q-in-Q on the EX4200 customer port so you don't care
what VLANs the cust is sending, trunk port out to your MX80, and use
'input-vlan-map pop' with something like 'encapsulation vlan-ccc' on
the MX80 to remove the outer tag.  Not sure what you're planning to do
on the MX80, but we dump ours into customer-specific L2VPNs.  I don't
have EX4200 configs handy, but your MX80 interface side might
resemble:

[edit interfaces xe-y/y/y]
<snip MTU, autoneg, etc stuff>
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
unit <QinQtag> {       # Unit number is arbitrary, but keep it simple
and match the VLAN ID if you can.
  vlan-id <QinQtag>;
  encapsulation vlan-ccc;
  input-vlan-map pop;
  output-vlan-map push;
}

HTH,

David


On 17 July 2011 13:02, Matthew S. Crocker <matthew at corp.crocker.com> wrote:
>
> Can the MX80 handle QinQ?
>
> Can I run QinQ for this customer and MPLS in my 10GigE core?  I don't think the EX 4200 can do that.
>
> If I wanted to stay MPLS would I need to configure each vlan on the customer interface and map it to a unqiue CCC to the other end (EX4200->MX80 & MX80->EX4200)?
>
>
> ----- Original Message -----
>> From: "Doug Hanks" <dhanks at juniper.net>
>> To: "Matthew S. Crocker" <matthew at crocker.com>, juniper-nsp at puck.nether.net
>> Sent: Sunday, July 17, 2011 2:42:17 PM
>> Subject: RE: [j-nsp] dot1q CCC/MPLS on EX4200 series switches
>>
>> It's probably easier to use QinQ.
>>
>> Doug
>>
>> -----Original Message-----
>> From: juniper-nsp-bounces at puck.nether.net
>> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Matthew S.
>> Crocker
>> Sent: Sunday, July 17, 2011 7:08 AM
>> To: juniper-nsp at puck.nether.net
>> Subject: [j-nsp] dot1q CCC/MPLS on EX4200 series switches
>>
>>
>> Hello,
>>
>>  I have a customer handing me a GigE with dot1q tags to my EX4200
>>  switch.  I need to carry the GigE/dot1q over a couple other EX4200s
>>  and terminate on a GigE port of my MX80.   I've read through the
>>  docs for building MPLS/ccc circuits between the two devices. It
>>  isn't clear to me if I need to establish a ccc for each vlan (i.e.
>>  I will need to know the VLANs the customer is sending me).  Or, can
>>  I create one CCC that will catch all tags and transport them across
>>  my MPLS and dump them out the MX80.   I would prefer not having to
>>  know the VLANs my customer is sending me.
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>
>>
>>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>