[j-nsp] VPLS pass tagged/untagged traffic

Chris Kawchuk juniperdude at gmail.com
Sun Mar 8 18:52:09 EDT 2015


Err, why not just something like:

        interfaces {
             ge-1/1/0 {
                 mtu 9192;
                 encapsulation ethernet-vpls;
                 unit 0;
             }

That will accept untagged, tagged, double tagged, etc... It makes the VPLS "not care" whats going on in that port. Doesnt even care about TPIDs. Even takes spanning tree and such.

Ensure not to declare any vlan-id in the routing-instance VPLS {} stanza. No translations ingress/egress.

- Ck.



On 09/03/2015, at 9:19 AM, Adam Vitkovsky <Adam.Vitkovsky at gamma.co.uk> wrote:

> on the PE1 logical system:
>          interfaces {
>              ge-1/1/0 {
>                  native-vlan-id 4096
>                  unit 0 {
>                      encapsulation vlan-vpls
>                      vlan-id-range 1-4096
>                      family vpls; (have tried with and without this)
>                  }
>              }



More information about the juniper-nsp mailing list