https://danhearty.wordpress.com/2019/10/12/evpn-vxlan-layer-3-gateway-irb-junos/
extended-vni-list | set protocols evpn extended-vni-list <VNI> Establishes which VXLAN Network Identifiers (VNI) will be part of the Virtual Switch (VS) instance. |
no-gateway-community | set protocols evpn default-gateway no-gateway-community when virtual-gateway-address ( VGA) is used, a VRRP based MAC “00:00:5e:00:01:01” is used on both the spines, so MAC synch is not needed To stop the CLI knob, |
bgp group xxx vpn-apply-export | When you apply a VRF export policy for the VRF Table on PE Routers in VPNs, routes from VPN routing instances are advertised to other PE routers based on this policy, whereas the BGP export policy is ignored. Apply both the VRF export and BGP group or neighbor export policies (VRF first, then BGP) before routes from the vrf or l2vpn routing tables are advertised to other PE routers. |
bgp group xxx multipath | All paths with the same neighboring AS, learned by a multipath-enabled BGP neighbor, are considered. |
routing-option resolution | Use bgp.rtarget.0 table to filter ( access only the local route target ) |
routing-option resolution xxx resolution-ribs | https://www.juniper.net/documentation/en_US/junos/topics/reference/configuration-statement/resolution-ribs-edit-routing-options.html |
switch-options | Configure Layer 2 learning and forwarding properties for a set of bridge domains. |
interfaces irb unit xx proxy-macip-advertisement | nterfaces irb unit xx proxy-macip-advertisement In case of CRB: SPINE=L3 and Leaf= L2 Spine will adv Mac+IP to all L2 gw ( Leaf) and L3 gw ( Spine) |
set interfaces irb unit 40 virtual-gateway-accept-data | set interfaces irb unit 40 virtual-gateway-accept-data To support pinging on the virtual gateway IP address, you must include both the virtual-gateway-accept-data statement and the preferred statement at the [edit interfaces irb unit] hierarchy of the preferred virtual gateway. |
set interfaces irb unit 40 virtual-gateway-esi all-active | set interfaces irb unit 40 virtual-gateway-esi all-active ????? To disable automatic ESI generation, include the no-auto-virtual-gateway-esi statement |
interface-routes & rib-group | set routing-instances NETWORKB routing-options interface-routes rib-group inet NETWORKB-RIB Will import the interface routes ( "direct" in rt) into other routing table ( like VRF, vrouter, . . . ) |
load-balance per-packet | [edit policy-options policy-statement <policy-name> term <term-name> from] route-filter destination-prefix <match-type> load-balance per-packet; |