Some zone types need an external controller to manage the VNet control-plane.
Currently this is only required for the bgp-evpn
zone plugin.
For BGP-EVPN
, we need a controller to manage the control plane.
The currently supported software controller is the "frr" router.
You may need to install it on each node where you want to deploy EVPN zones.
apt install frr frr-pythontools
Configuration options:
-
asn
-
A unique BGP ASN number. It’s highly recommended to use private ASN
number (64512 – 65534, 4200000000 – 4294967294), as else you could end up
breaking, or get broken, by global routing by mistake.
-
peers
-
An ip list of all nodes where you want to communicate for the EVPN (could be also
external nodes or route reflectors servers)
The bgp controller is not used directly by a zone.
You can used it to configure frr to manage bgp peers.
For BGP-evpn, it can be use to define a different ASN by node, so doing EBGP.
Configuration options:
-
node
-
The node of this BGP controller
-
asn
-
A unique BGP ASN number. It’s highly recommended to use private ASN
number from the range (64512 - 65534) or (4200000000 - 4294967294), as else
you could end up breaking, or get broken, by global routing by mistake.
-
peers
-
An IP list of peers you want to communicate with for the underlying
BGP network.
-
ebgp
-
If your peer’s remote-AS is different, it’s enabling EBGP.
-
loopback
-
If you want to use a loopback or dummy interface as source for the
evpn network. (for multipath)
-
ebgp-mutltihop
-
if the peers are not directly connected or use loopback, you can increase the
number of hops to reach them.