[j-nsp] SRX VPLS learning domains

[Tom Storey]

Ive been through this myself. The short of it is that you will need a
VPLS instance for each VLAN you wish to carry on SRX.

I dont remember the exact details, but the MX do some "magic" to
automatically carry multiple VLANs through a single VPLS instance,
whereas the SRX do not.

Try as you might, you probably wont get it to work and will waste
countless hours on it (unless theyve changed something in more recent
JunOS versions...) :-)

On 24 December 2015 at 23:26, Dan Rimal <dan at danrimal.net> wrote:
> Hi,
>
> I am trying to pass multiple VLAN via single VPLS routing instance and
> assume separate learning domain for every single VLAN. I tried knob
> "vlan-id all" under routing instance without success. O MX series it
> works, it create multiple learning domain, on SRX 240 (second site) nope
> and same MAC from different VLANs collide. Is it some SRX limitation or
> something like this?
>
> Junos 12.1X46-D35 on SRX240B
>
> My config:
>
> ge-0/0/3 {
>     vlan-tagging;
>     mtu 1590;
>     encapsulation flexible-ethernet-services;
>     unit 512 {
>         description CE-facing-1;
>         encapsulation vlan-vpls;
>         vlan-id 512;
>         family vpls {
>             policer {
>                 input vpls-10m;
>                 output vpls-10m;
>             }
>         }
>     }
>
>    unit 513 {
>         description CE-facing-1;
>         encapsulation vlan-vpls;
>         vlan-id 513;
>         family vpls {
>             policer {
>                 input vpls-10m;
>                 output vpls-10m;
>             }
>         }
>     }
>
>
>    VPLS-ALGO-V512 {
>         instance-type vpls;
>         interface lt-0/0/0.0;
>         interface ge-0/0/3.512;
>         interface ge-0/0/3.513;
>         vlan-id all;
>         route-distinguisher 31.41.176.64:512;
>         vrf-target target:36736:512;
>         protocols {
>             vpls {
>                 site-range 4;
>                 mac-table-size {
>                     128;
>                     packet-action drop;
>                 }
>                 no-tunnel-services;
>                 site j3r-512 {
>                     site-identifier 2;
>                     interface ge-0/0/3.512;
>                     interface ge-0/0/3.513;
>                     interface lt-0/0/0.0;
>                 }
>                 connectivity-type ce;
>             }
>         }
>     }
>
>
> Thanks,
>
> Dan
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp