[j-nsp] evpn trouble

[Baldur Norddahl]

Hello Roger

Thank you for the comment. I will research mac-vrf which is new to me. We
are using MPLS and are migrating from VPLS. The ACX5448 / ACX710 do not
have virtual-switch support (but mac-vrf appears to be available). Aside
from mac-vrf my choices are evpn and evpn-vpws. Apparently subscriber
management, which we use, only supports evpn-vpws at this time.

This thread was about our server / vm hosting setup however. We only have
four server vlans and so I created one evpn instance per vlan.

Customer traffic is q-in-q. Not a problem for evpn-vpws but that has
limitations which may be a problem for me. I wish Juniper had made support
for more than just evpn-vpws as transport interface for "ps" interfaces. I
may be forced to stay with VPLS for the time being.

Thanks,

Baldur

Den tir. 11. maj 2021 kl. 15.45 skrev Roger Wiklund <roger.wiklund at gmail.com
>:

> Hi
>
> What data plane are you using, MPLS or VXLAN?
>
> Instance-type evpn is VLAN-Based Service. I.E one VLAN per EVPN instance,
> is this what you want?
> Configuring EVPN with VLAN-Based Service | EVPN User Guide | Juniper
> Networks TechLibrary
> <https://www.juniper.net/documentation/us/en/software/junos/evpn-vxlan/topics/task/evpn-routing-instance-vlan-based-configuring.html>
>
> If you want to run multiple VLANs in one EVPN instance you can use
> VLAN-Aware Service (instance-type virtual-switch or in default
> virtual-switch) where each VLAN/VNI will have a unique RT.
> Understanding VLAN-Aware Bundle and VLAN-Based Service for EVPN | EVPN
> User Guide | Juniper Networks TechLibrary
> <https://www.juniper.net/documentation/us/en/software/junos/evpn-vxlan/topics/concept/evpn-vlan-services-overview-qfx-series.html>
>
> With that said from Junos 20.4R1 there's a new mac-vrf instance-type where
> you can more clearly define the different services
> instance-type mac-vrf
> service-type vlan-aware / vlan-based / vlan-bundle
> Microsoft Word - EVPN_VxLAN_MAC-VRF_NCE.docx (juniper.net)
> <https://www.juniper.net/documentation/en_US/release-independent/nce/information-products/pathway-pages/nce/EVPN_VxLAN_MAC-VRF.pdf>
>
> Not sure when MX/ACX will gain this feature though.
>
> Regards
> Roger
>
>
>
> On Sat, May 8, 2021 at 12:12 AM Baldur Norddahl <baldur at gigabit.dk> wrote:
>
>> Hello
>>
>> I found the answer to this one. On ACX5448 and ACX710 the
>> routing-interface
>> statement does absolutely nothing. Instead you need to use the
>> undocumented
>> l3-interface statement at the same place. On the MX204 platform the
>> l3-interface statement does not exist. I will list the two configs below
>> for those that might need to know.
>>
>> Compare mx204 config:
>>
>> baldur at formervangen-edge1# show routing-instances evpntest
>> instance-type evpn;
>> protocols {
>>     evpn {
>>         default-gateway advertise;
>>     }
>> }
>> vlan-id 20;
>> routing-interface irb.20;
>> interface xe-0/1/7.21;
>> vrf-target target:60876:20;
>>
>> And acx710 / acx5448:
>>
>> baldur at formervangen-core4# show routing-instances evpntest
>> instance-type evpn;
>> protocols {
>>     evpn {
>>         default-gateway advertise;
>>     }
>> }
>> vlan-id 20;
>> l3-interface irb.20;
>> interface xe-0/0/0.20;
>> vrf-target target:60876:20;
>>
>> Regards,
>>
>> Baldur
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>
>