EVPN
-
Inline BFD with EVPN-VXLAN for Type 2 and Type 5 tunnel repair (QFX5130-32CD, QFX5130E-32CD, QFX5130-48C, QFX5700, and QFX5700E)—We support inline BFD with EVPN-VXLAN for faster recovery of PE to PE network failures.
-
Override global AS number for auto-derived route targets in EVPN instances (QFX5130-32CD)—By default, EVPN provider edge devices use the global autonomous system (AS) number to auto-derive route targets and configure the related route target import and export policies in EVPN instances (EVIs). If required, you can override this default behavior to instead specify a common AS number to use for auto-derived route targets across EVPN peer devices. With this feature, you can ensure consistent route advertisements and import policies in EVPN fabrics that use external BGP (eBGP) underlay and overlay peering.
Use the
import-asandexport-asoptions to assign an AS number on all EVPN peer devices for auto-derived route target import and export policies. Alternatively, you can use theas-numoption to assign the same AS number for both import and export policies.-
For
default-switchinstances:set switch-options vrf-target auto import-as asnum vni-list <all | [vni-1 vni-2 …]> set switch-options vrf-target auto export-as asnum vni-list <all | [vni-1 vni-2 …]> set switch-options vrf-target auto as-num asnum vni-list <all | [vni-1 vni-2 …]>
-
For
mac-vrfinstances:set routing-instances name vrf-target auto import-as asnum vni-list <all | [vni-1 vni-2 …]> set routing-instances name vrf-target auto export-as asnum vni-list <all | [vni-1 vni-2 …]> set routing-instances name vrf-target auto as-num asnum vni-list <all | [vni-1 vni-2 …]>
[See Auto-derived Route Targets and vrf-target.]
-