Chris,
Thanks, I just tried it and this works...guess I was making it more
difficult that it needed to be. I haven't tested spanning tree through
it or other layer2 control protocols but you are thinking they should
pass through just like and l2vpn?
Thanks again,
Kevin
On 03/08/2015 05:52 PM, Chris Kawchuk wrote:
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.vitkov...@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)
}
}
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
