Virtual Machine Tracker auto-config is a feature that automatically configures a tenant for provisioning.

The Virtual Machine Tracker auto-config feature retrieves information about a tenant from the database (LDAP) and issues the necessary configuration commands for the provisioning.

The commands required for provisioning the tenant are stored in the form of a configuration profile. A configuration profile is a set of commands that will be required for provisioning a particular tenant, except the required parameters are written as variables instead of actual values in a command.

The information about the tenant includes:

• The values for the variables of a configuration profile.

• The actual configuration profile that a tenant uses.

Orchestrators, such as the Cisco Virtual Topology System (VTS) or the Cisco UCS Director (UCSD), are used to populate the tenant information.

Note	Virtual Machine Tracker auto-config is only supported on Cisco Nexus 9300 Series switches.

Note	Virtual Machine Tracker auto-config supports Cisco Nexus 9300 Series switches in FEX configurations.

VM Tracker has the following guidelines and limitations:

• show commands with the internal keyword are not supported.

• Enabling the VM Tracker auto-config feature is disruptive. A best practice is to disconnect all VM Tracker connections before enabling VM Tracker auto-config.

• When VM Tracker auto-config is enabled after VM Tracker is already connected to VMware vCenter and has configured the switch, the existing VM Tracker configuration is removed and then VM Tracker auto-config is triggered.

• When VM Tracker auto-config is disabled, the auto-config triggered configuration is removed and the VM Tracker reverts back to the configured VLAN that was initially created by VM Tracker.

• switchport trunk allowed vlan vlan-list are configured on the host facing interface for both auto-config triggered configurations and initial VM Tracker configurations.

• The VLAN is always created when the VM Tracker auto-config triggers the configuration. The autovlan enable command is ineffective and is not supported when VM Tracker auto-config is enabled.

• allowed-vlan takes effect when VM Tracker auto-config is enabled.

• VM Tracker and a vPC Configuration

  • VM Tracker should be configured on both switches of the vPC pair so that the host facing trunk port is configured.

  • In a vPC configuration when both the vPC primary and the vPC secondary are configured to connect to the VMware vCenter, VM Tracker on the vPC secondary will not trigger auto-config. The auto-config profile is synced from primary to standby by HMM. The purpose of this is not to overwhelm HMM with downloading and sync profiles from the vPC primary to the vPC secondary and from the vPC secondary to the vPC primary at the same time.

  • If the primary vPC interface is down, when vCenter detects the link being down, VM Tracker is updated, VM Tracker triggers the profile unapply request to HMM, and the host facing “trunk allowed vlan” configuration is removed. When the VM Tracker retry timer expires on the secondary, the “skipped” profile is inspected and VM Tracker triggers the auto-config from the standby side if it detects the primary vPC interface is down.

  • When the primary vPC interface is up again, VM Tracker on the primary triggers auto-config. At this time both switches trigger auto-config.

• When migrating from VM Tracker to VM Tracker auto-config in a vPC setup, the following procedure is a best practice:

  • Disconnect all VM Tracker connections on the vPC primary and the vPC secondary switches.

  • Enable VM Tracker auto-config using the vmtracker fabric auto-config command on the vPC primary and the vPC secondary switches.

  • Connect the VM Tracker connection on the vPC primary switch.

  • Connect the VM Tracker connection on the vPC secondary switch.

Caution

Enabling the VM Tracker auto-config feature is disruptive. A best practice is to disconnect all VMTracker connections before enabling VM Tracker auto-config.

1.    switch# configure terminal

2.    switch(config)# [no] vmtracker fabric auto-config


3.    switch(config)# [no] vmtracker connection connection-name


4.    switch(config-vmt-conn)# [no] remote {ip address ip_address | port port_number | vrf}


5.    switch(config-vmt-conn)# username username password password


6.    switch(config-vmt-conn)# [no] connect

switch# configure terminal
switch(config)# vmtracker fabric auto-config
switch(config)# vmtracker connection v229
switch(config-vmt-conn)# remote ip address  172.29.21.29 port 80 vrf management
switch(config-vmt-conn)# username user1 password abc1234
switch(config-vmt-conn)# connect