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

[Keegan Holley]

You can create a ccc based on port and just everything that comes in the
port to the other end regardless of vlan or encapsulation.  There is also no
mac learning to worry about.  This in my experience is easier to manage than
q-in-q which requires mac learning and spanning-tree.  The down side is that
each port requires a dedicated LSP, so 48 ports would create 48 new LSP's
between the two devices.  I'm not sure what the LSP limitations are but I
would assume it's pretty high.

2011/7/17 Matthew S. Crocker <matthew at crocker.com>

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