...
Additional configuration is necessary to enable ARP/ND suppression, provision inter-subnet routing, and so on. The configuration depends on the deployment scenario. You can also configure various other BGP parameters depending on your network requirements.
Enable EVPN Between BGP Peers
The very basic steps needed to enable BGP EVPN between a BGP neighbor is as under.
| Code Block |
|---|
admin@router1# set protocols bgp local-as 65101 admin@router1# set protocolprotocols bgp router-id 10.10.10.1 admin@router1# set protocolprotocols bgp neighbor swp51 interface>100.1.1.134 remote-as external650101 setadmin@router1# protocolcommit bgpCommit l2vpnOK. evpn neighbor swp51 activate commitSave done! |
The configuration below adds the evpn address family to the BGP neighbor address-family so that BGP peers activate exchanging EVPN routes with each other. After this configuration, the BGP still does not know about the local VNI's.
Advertise All VNIs Through BGP
To allow BGP know about all VNIs or hosts associated with those local VNIs, enable the BGP control plane for all VNIs using the configuration shown below.
| Code Block |
|---|
admin@router# set protocol bgp l2vpn evpn advertise-all-vni admin@router# commit Commit OK. Save Done! |
| Note | ||
|---|---|---|
| ||
Only leaf switches that are VTEPs need this configuration. EVPN routes are still accepted from BGP peers as they reside in the global EVPN routing table, but are only made effective when the VNI corresponding to the received route is locally known. |
Sample Configuration Topology with EVPN Symmetric Routing
Figure 1 shows our sample topology for EVPN symmetric routing. We have two routers with two servers connected to each router.
The configuration for router 1 is show below.
EVPN with MLAG
To be completed...
EVPN with NAC
To be completed...