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

[Doug Hanks]

The MX probably has the best support for QinQ I've seen.

-----Original Message-----
From: Matthew S. Crocker [mailto:matthew at corp.crocker.com] 
Sent: Sunday, July 17, 2011 12:02 PM
To: Doug Hanks
Cc: Matthew S. Crocker; juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] dot1q CCC/MPLS on EX4200 series switches


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
> 
> 
>