Guidelines and Limitations for VM Tracker
VM Tracker has the following guidelines and limitations:
-
VM Tracker supports up to four vCenter connections.
-
VM Tracker supports high availability and the fault tolerance features of vCenter.
-
VM Tracker supports up to 64 VMs per host.
-
VM Tracker supports up to 350 hosts across all vCenters.
-
VM Tracker supports up to 600 VLANs.
-
VM Tracker supports only 507 VLANs in Per VLAN Rapid Spanning Tree (PVRST) mode due to hardware limitations. To enable more than 507 VLANs, use Multiple Spanning Tree (MST).
-
The current version of VM Tracker is supported only on ESXi 5.1 and ESXi 5.5 on Windows and Linux.
-
The current version of VM Tracker supports only VMware orchestration. It does not support orchestration with other hypervisors.
-
For all ports on which VM Tracker is enabled, you must not perform any Layer 2 or Layer 3 configuration that is related to switchports and VLANs. However, you can update the native VLAN.
-
VM Tracker does not support VLAN 4095.
-
VM Tracker is not supported on the virtual port channel (vPC) switch although it can be configured on the downstream switch on the vPC setup.
-
You must connect the host directly to the Cisco Nexus 3000 Series ports. Host connectivity through the IOM, fabric extender (FEX), or chassis is not supported.
-
If you do not specify the virtual routing and forwarding (VRF) while configuring the remote IP address, the management VRF is used.
-
If you do not configure a VLAN as a native VLAN on the interface, VM Tracker cannot remove this VLAN and disable VM Tracker.
-
For vCenter version 5.1 and 5.5, the CDP information can contain a maximum of 32 characters for the name of the switch. If the name of the switch exceeds 32 characters, VM Tracker will not work.