Support for VLAN Alarms in vCenter

Netvisor One can be configured with a vCenter Connection Service to read metadata from a vCenter server and updates to the vPort table when learned from an inventory scan. A remote plugin for vCenter is now capable of auto provisioning a VLAN range for a DvPortgroup associated with uplinks going to the Netvisor One fabric.

vCenter Alarm integration allows you to see the vCenter connection service running with supported VLAN ranges configured on DVPortgroup.

If a DVPortgroup associated with a VM is configured for VLAN trunking using VLANs unsupported by auto provisioning, then you receive alarms on the vSphere Web Client Server. When you receive an alarm, you can modify the VLAN range or request additional VLANs from the Netvisor One switch administrator.

To configure the vCenter Connection Service with VLANs, use the following syntax:

CLI (network-admin@switch) > vcenter-connection-create name svc12 host user administrator@lab.pluribus vlans 10-15

CLI (network-admin@switch) > vcenter-connection-show

switch             name        host          user                       enable state

------------------ ----------- ------------  ------------------------- ------- -----

switch-1           svc15  administrator@lab.pluribus yes    ok

switch-2           svc15   administrator@lab.pluribus yes    ok


connected-time                   vlans

-------------------------------- -----

connected at 2017-03-02 20:14:55 10-15

connected at 2017-03-02 20:14:57 10-15


If you configure a VM with a VLAN that is not in the 10-15 VLAN range, then an alarm is triggered.

Figure - vCenter Alarms