Provide a list of border-leaf IPs on which the centralized router (VRF) needs to be instantiated. If a given fabric has only one BL pair and you have not provided any BL pair as centralized router, then the only available BL pair is used as centralized router by default.
Provide only one BL pair on which the centralized router (VRF) needs to be instantiated.
VRF instantiation happens on the border-leaf devices during the EPG (endpoint group) create or update operations.
You can't provide leaf, spine, or super-spine IPs as the target device for centralized routing.
VRF (with centralized routing enabled) and its dependent L3 configuration (anycast-ip, local-ip, VRF static route, VRF static route bfd, router bgp static or dynamic peer, and router bgp peer-group) are instantiated only on the border-leaf(s) on which the parent VRF exists.
The VRF instantiation happens only on those border-leaf devices and not on any other leaf or border-leaf devices.
The anycast-ip configuration happens automatically on the border-leaf devices on which the VRF is instantiated.
efa tenant vrf create --name <vrf-name> --tenant <tenant-name> --routing-type {centralized | distributed} --centralized-router <list-of-border-leaf-routers>
Example
efa tenant vrf create –-name VRF1 --tenant tenant1 --routing-type centralized --centralized-router BL1-IP,BL2-IP
Instantiate VRFs on the border-leaf devices based on the L3 scale requirements.
Suppose the fabric has 100 VRFs with 4K anycast-ip, then you can instantiate all 100 VRFs on a single border-leaf pair. If the L3 scale requirements are higher than the scale supported by a single border-leaf pair, then add additional border-leaf pair.