How the EFA vCenter Service Works
Use the Extreme Fabric Automation (EFA) application to automate the configuration of the data center's physical network hardware once you have finished configuring your VMware vCenter Server and the associated virtual machines. EFA then imports VMware's infrastructure and topology information and then applies this to the fabric managed by it.
EFA requires that the physical connection between the VMware ESXi servers and Extreme Fabric devices is working and is configured properly. You should also ensure that the EFA server can access the vCenter Server. The EFA server need not be connected to the individual ESXi servers for this service to work.
Once properly configured, the EFA vCenter service queries the VMware vCenter server to:
Discover network assets and configurations for the specific VMware vCenter server that will be used.
Discover the ESXi servers that the specific VMware vCenter server manages. It also discovers the virtual machines and virtual network adapters that are configured on each physical ESXi server.
Discover the physical network adapters that are associated with the virtual machines discovered as mentioned above. All the above information are saved in a local database for use. This stored information is used to verify if there are any changes in the networking assets/configurations for the specified VMware vCenter server.
Interact with EFA's Inventory service to inquire and find the connections between the physical network adapters and the ESXi servers. It also constantly interacts with the Inventory service to find the port information for any new connections with the ESXi servers.
Interact with EFA's Tenant Service to create the required tenants and End Point Groups. It also uses the Tenant Service to periodically update the tenants and EPG information to ensure that the information stored locally is in-sync with the actual network topology.