The purpose of connectivity to vCenter is to allow a network administrator visibility into physical and/or virtual VMware entities that are behind each port of the Pluribus fabric for operational simplification. The properties of the entities are categorized into three classes:
Server, hypervisor,and one or more physical NICs
Virtual Machine including guest OS, virtual NIC properties such as MAC address, IP address, and VLAN.
VM Kernel ports and the associated services like vMotion and vSAN.
Netvisor OS now provides vCenter Connection Service that allows you to connect to VMware vCenter and allows you to do the following tasks:
Identify the switch port used for each Virtual Machine (VM).
Track the movement of VMs from one host (ESXi) to another host.
Identify the VLAN requirements of each VM on the network.
Track network statistics at a granular level for troubleshooting purposes.
Track VM configuration changes such as additions, deletions, or modifications of VLANs, and configure VLANs on Netvisor OS switch ports.
Track the additions or deletions of VMs and hosts, and configure VLANs on Netvisor OS switches.
Track the state of VMs and dynamically provisions VLANs on the servers facing physical ports.
vCenter Connection Service also synchronizes with VMware vCenter to obtain the following information:
The host where the VMs exist.
The Netvisor OS switch ports connected to the VM.
The virtual network interface card (vNIC) that connects the VM to a virtual switch.
The Power status of the VM as on or off.
VLAN information of port groups.
The port groups required for the VM.
This information is associated with MAC addresses and VLANs on the network.
vCenter Connection Service currently has the following limitations for this Netvisor OS release:
Support for only 1 VMware vCenter connections
Supported on ESXi 5.x and 6.x versions of VMware vCenter.
It is recommended check the status of the connection. To check the status of the connection, use the connection-show command. If the connection status shows an error message with the state as "enabled”, then you should first disable the connection and then enable it to restart the connection service.
Figure 1: Example LAN and VLAG Topology for vCenter
Example output with a list of VMs running on the two VMware ESXi servers along with visibility into the associated VLANs, attached port group, vswitches:
CLI network-admin@switch > vport-show format ip,entity,status vnic-type
owner ip hostname entity power os portgroup vswitch
----- --------- -------- ------- ------- --------- --------- ------
SW-2 10.9.8.13 esx-1 MyTestVM powered-on Ubuntu Linux VM Network vSwitch0
vs-type vnic-type.. status
------- --------- ------
host-vs tagged vm