Chapter 1. New and Changed Information

New and Changed Information

Chapter 2. Overview

Information About Virtual Machine Tracker

Virtual Machine Tracker and VMware vCenter

Chapter 3. Configuring Virtual Machine Tracker

Guidelines and Limitations for VM Tracker

Enabling Virtual Machine Tracker

Creating a New Connection to vCenter

Synchronizing Information with VMware vCenter

Compatibility Checking on a VPC Topology

Verifying the Virtual Machine Tracker Configuration

Enabling Virtual Machine Tracker on Specific Interfaces

Enabling Dynamic VLAN Creation

Configuring an Allowed VLAN List

Example Configuration for Virtual Machine Tracker

Chapter 4. Using Virtual Machine Tracker Auto-Config

Virtual Machine Tracker Auto-Config

Configuration Profile

Configuration Profile Refresh

Network Database

Network Table

Partition Table

ProfileTable

Configuration Profile Example

Using auto-pull

Virtual Machine Tracker Auto-Config Workflow

Guidelines and Limitations for Virtual Machine Tracker Auto-Config

Enabling Virtual Machine Tracker Auto-Config

Triggering Auto-Config

Verifying Virtual Machine Tracker Auto-Config Configuration

Example Configuration for Virtual Machine Tracker Auto-Config

Preface

Audience

Document Conventions

Related Documentation for Cisco Nexus 9000 Series Switches

Documentation Feedback

Obtaining Documentation and Submitting a Service Request

Copyright Page

Chapter 1. New and Changed Information

- New and Changed Information

New and Changed Information

The following table provides an overview of the significant changes made to this configuration guide. The table does not provide an exhaustive list of all changes made to this guide or all new features in a particular release.

Feature

Description

Added or Changed in Release

Where Documented

Virtual Machine Tracker auto-config feature

Enables automatic configuration of a tenant for provisioning.

7.0(3)I2(1)

Virtual Machine Tracker Auto-Config

No updates since release 6.x

7.0(3)I1(1)

Chapter 2. Overview

This chapter contains the following sections:

- Information About Virtual Machine Tracker

- Virtual Machine Tracker and VMware vCenter

Information About Virtual Machine Tracker

Virtual Machine Tracker (VM Tracker) works together with VMware vCenter and enables you to do the following:

- Identify the Cisco Nexus 9000 Series port that is used for each VM

- Identify the VLAN requirements of each VM

- Track the movement of VMs from one host (ESXi) to another

- Track VM configuration changes such as additions, deletions, or modifications of VLANs, and configure VLANs on Cisco Nexus 9000 Series ports accordingly

- Track the additions or deletions of VMs and hosts, and configure VLANs on Cisco Nexus 9000 Series ports accordingly

- Track the state of VMs and dynamically provisions VLANs on the Cisco Nexus 9000 server facing physical ports.

Virtual Machine Tracker and VMware vCenter

VM Tracker synchronizes with VMware vCenter to retrieve the following information:

- The host on which the VMs exist.

- The Cisco Nexus 9000 Series ports through which the VM traffic flows.

- The virtual network interface card (vNIC) that connects the VM to a virtual switch.

- The power state of the VM.

- The VLAN information of port groups or distributed virtual switch (DVS) port groups.

- The port groups or DVS port groups that are required for the VM.

Chapter 3. Configuring Virtual Machine Tracker

This chapter contains the following sections:

- Enabling Virtual Machine Tracker

- Creating a New Connection to vCenter

- Synchronizing Information with VMware vCenter

- Compatibility Checking on a VPC Topology

- Verifying the Virtual Machine Tracker Configuration

- Enabling Virtual Machine Tracker on Specific Interfaces

- Example Configuration for Virtual Machine Tracker

Guidelines and Limitations for VM Tracker

VM Tracker has the following guidelines and limitations:

- show commands with the internal keyword are not supported.

- VM Tracker supports up to four vCenter connections.

- VM Tracker supports high availability and the fault tolerance features of vCenter.

- VM Tracker is only supported on ESXi 5.1 and ESXi 5.5 versions of VMware vCenter.

- You must connect a host directly to the port of a Cisco Nexus 9000 Series switch. Host connectivity through fabric interconnect, another switch, or chassis is not supported.

Note

Connecting a host through a fabric extender (FEX) is supported by a Cisco Nexus 9000 Series switch.

Enabling Virtual Machine Tracker

By default, the VM Tracker feature is enabled on all interfaces.

SUMMARY STEPS

1.    switch# configure terminal

2.    switch(config)# [no] feature vmtracker

DETAILED STEPS

Command or Action

Purpose

Step 1

switch# configure terminal

Enters global configuration mode.

Step 2

switch(config)# [no] feature vmtracker

Enables the VM Tracker feature on all interfaces.

The no form of the command disables the VM Tracker feature on all interfaces.

This example shows how to enable VM Tracker:

switch# configure terminal
switch(config)# feature vmtracker
switch(config)#

Creating a New Connection to vCenter

SUMMARY STEPS

1.    switch# configure terminal

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

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

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

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

DETAILED STEPS

Command or Action

Purpose

Step 1

switch# configure terminal

Enters global configuration mode.

Step 2

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

Enters VM Tracker connection configuration mode for the connection name specified.

The no form of the command disables the connection.

Step 3

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

Configures remote IP parameters.

Step 4

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

Verifies the username and password to connect to vCenter.

Step 5

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

Connects to vCenter.

The no form of the command disconnects VM Tracker from vCenter.

This example shows how to create a new connection to VMware vCenter:

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

Synchronizing Information with VMware vCenter

By default, VM Tracker tracks all asynchronous events from VMware vCenter and updates the switchport configuration immediately. Optionally, you can also configure a synchronizing mechanism that synchronizes all host, VM, and port group information automatically with VMware vCenter at a specified interval.

Command

Purpose

[no] set interval find-new-host val

Sets the interval, in seconds, for finding hosts that are newly connected to vCenter. The no form of the command disables the previously configured interval.

The default duration is 3600 seconds.

[no] set interval sync-full-info val

Sets the interval, in seconds, for synchronizing all host, VM, and port group related information with vCenter. The no form of the command disables the previously configured interval.

The default duration is 3600 seconds.

vmtracker connection connection-name refresh

Synchronizes all host, VM, and port group related information with vCenter immediately for the specified connection.

This example shows how to set an interval for finding hosts that are newly connected to vCenter:

switch(config-vmt-conn)# set interval find-new-host 300

This example shows how to set an interval for synchronizing all host, VM, and port group information with vCenter:

switch(config-vmt-conn)# set interval sync-full-info 120

This example shows how to immediately synchronize all host, VM, and port group information with vCenter:

switch(config-vmt-conn)# vmtracker connection conn1 refresh

Compatibility Checking on a VPC Topology

On a VPC topology, VM Tracker performs a Type 2 compatibility checking. The checking ensures that for a particular connection name, the following fields match across the VPC peers:

- The vCenter IP address that VM Tracker should connect to.

- The vCenter port number that VM Tracker should connect on.

- The allowed VLAN range for that particular connection.

- The username/password combination that VM Tracker should use to connect to the vCenter Server.

To determine if the VPC checking was successful, use the show vpc consistency-parameters global command.

The following is an example of VPC checking:

switch# show vpc  consistency-parameters global

Legend:
Type 1 : vPC will be suspended in case of mismatch

Name                        Type  Local Value            Peer Value
-------------               ----  ---------------------- -----------------------
Vlan to Vn-segment Map      1     No Relevant Maps       No Relevant Maps
STP Mode                    1     Rapid-PVST             Rapid-PVST
STP Disabled                1     None                   None
STP MST Region Name         1     ""                     ""
STP MST Region Revision     1     0                      0
STP MST Region Instance to  1
VLAN Mapping
STP Loopguard               1     Disabled               Disabled
STP Bridge Assurance        1     Enabled                Enabled
STP Port Type, Edge         1     Normal, Disabled,      Normal, Disabled,
BPDUFilter, Edge BPDUGuard        Disabled               Disabled
STP MST Simulate PVST       1     Enabled                Enabled
Interface-vlan admin up     2     1-8                    1-8
Interface-vlan routing      2     1-8                    1-8
capability
vmtracker connection        2     conn1, 10.193.174.215, conn1, 10.193.174.215,
params                             80, 1-4094             80, 1-4094
Allowed VLANs               -     1-100                  1-100
Local suspended VLANs       -     -                      -
switch#

Verifying the Virtual Machine Tracker Configuration

Use the following commands to display and verify VM Tracker configuration information:

Command

Purpose

show running-config vmtracker [all]

Displays the VM Tracker configuration.

show vmtracker [connection conn_name] {{info [interface intf_id ]{summary | detail | host | vm | port-group}} | event-history}

Displays the VM Tracker configuration based on the following:

- Connection

- Interface

- Event history

show vmtracker [connection conn_name] status

Displays the IP address and connection status of the vCenter connection specified.

show logging level vmtracker

Displays the logging level of the syslog messages for VM Tracker.

Enabling Virtual Machine Tracker on Specific Interfaces

When VM Tracker is enabled by using the [no] feature vmtracker command, it is enabled on all interfaces by default. You can optionally disable and enable it on specific interfaces by using the [no] vmtracker enable command.

SUMMARY STEPS

1.    switch# configure terminal

2.    switch(config)# interface type slot/port

3.    switch(config-if)# [no] vmtracker enable

DETAILED STEPS

Command or Action

Purpose

Step 1

switch# configure terminal

Enters global configuration mode.

Step 2

switch(config)# interface type slot/port

Enters the interface configuration mode for the specified interface.

Step 3

switch(config-if)# [no] vmtracker enable

Enables the VM Tracker feature on the specified interface.

The no form of the command disables the VM Tracker feature on the specified interface.

This example shows how to enable VM Tracker on a specified interface:

switch# configure terminal
switch(config)# interface ethernet 1/3/1
switch(config-if)# vmtracker enable

Enabling Dynamic VLAN Creation

Dynamic creation and deletion of VLANs globally is enabled by default. When dynamic VLAN creation is enabled, if a VM is moved from one host to another and the VLAN required for this VM does not exist on the switch, the required VLAN is automatically created on the switch. You can also disable this capability. However, if you disable dynamic VLAN creation, you must manually create all the required VLANs.

Before You Begin

Ensure that the VM Tracker feature is enabled.

SUMMARY STEPS

1.    switch# configure terminal

2.    switch(config)# vmtracker connection connection-name

3.    switch(config-vmt-conn)# [no] autovlan enable

DETAILED STEPS

Command or Action

Purpose

Step 1

switch# configure terminal

Enters global configuration mode.

Step 2

switch(config)# vmtracker connection connection-name

Enters VM Tracker connection configuration mode for the connection name specified.

Step 3

switch(config-vmt-conn)# [no] autovlan enable

Enables dynamic VLAN creation and deletion.

The no form of the command disables dynamic VLAN creation and deletion.

This example shows how to enable dynamic VLAN creation:

switch# configure terminal
switch(config)# vmtracker connection conn1
switch(config-vmt-conn)# autovlan enable

Configuring an Allowed VLAN List

By default, all VLANs can be configured dynamically on interfaces. You can also define a restricted list of such VLANs.

Before You Begin

Ensure that the VM Tracker feature is enabled.

SUMMARY STEPS

1.    switch# configure terminal

2.    switch(config)# vmtracker connection connection-name

3.    switch(config-vmt-conn)# allowed-vlans {allow-vlans | add add-vlans | except except-vlans | remove remove-vlans | all}

DETAILED STEPS

Command or Action

Purpose

Step 1

switch# configure terminal

Enters global configuration mode.

Step 2

switch(config)# vmtracker connection connection-name

Enters VM Tracker connection configuration mode for the connection name specified.

Step 3

switch(config-vmt-conn)# allowed-vlans {allow-vlans | add add-vlans | except except-vlans | remove remove-vlans | all}

Configures a list of VLANs that can be dynamically configured on interfaces.

This example shows how to configure a list of allowed VLANs:

switch# configure terminal
switch(config)# vmtracker connection test
switch(config-vmt-conn)# allowed-vlans 100-101

Example Configuration for Virtual Machine Tracker

This example shows how to create a connection with vCenter:

switch# configure terminal
switch(config)# feature vmtracker
switch(config)# vmtracker connection test
switch(config-vmt-conn)# remote ip address 20.1.1.1 port 80 vrf management
switch(config-vmt-conn)# username user1 password abc@123
switch(config-vmt-conn)# connect
switch(config-vmt-conn)# show vmtracker status

Connection           Host/IP                             status
-----------------------------------------------------------------------------
test                 20.1.1.1                                              Connected

switch(config-vmt-conn)# show vmtracker info detail
------------------------------------------------------------------------------
Interface       Host            VMNIC   VM         State PortGroup  VLAN-Range
------------------------------------------------------------------------------
Ethernet1/3/1   20.2.2.2                          vmnic4  No-OS1     on    PGroup100  100

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

switch(config-vmt-conn)# show running-config vmtracker
!Command: show running-config vmtracker
!Time: Mon Mar 10 09:07:47 2014
version 6.0(2)U3(1)
feature vmtracker
vmtracker connection test
remote ip address 20.1.1.1 port 80
username user1 password abc@123
connect

switch(config-vmt-conn)# show running-config interface ethernet 1/3/1
!Command: show running-config interface Ethernet1/3/1
!Time: Mon Mar 10 09:09:13 2014
version 6.0(2)U3(1)
interface Ethernet1/3/1
switchport mode trunk
switchport trunk allowed vlan 1,100

Note

VLAN 1 is the native VLAN on interface Ethernet1/3/1.

This example shows how to verify VM Tracker information after you power off the VM on vCenter:

switch(config-vmt-conn)# show vmtracker info detail
------------------------------------------------------------------------------
Interface       Host            VMNIC   VM         State PortGroup  VLAN-Range
------------------------------------------------------------------------------
Ethernet1/3/1   20.2.2.2                          vmnic4  No-OS1     off   PGroup100  100

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

switch(config-vmt-conn)# show running-config interface ethernet 1/3/1
!Command: show running-config interface Ethernet1/3/1
!Time: Mon Mar 10 09:09:13 2014
version 6.0(2)U3(1)
interface Ethernet1/3/1
switchport mode trunk
switchport trunk allowed vlan 1, 100

This example shows how to verify VM Tracker information after you add a new VLAN through vCenter:

switch(config-vmt-conn)# show vmtracker info detail
------------------------------------------------------------------------------
Interface       Host            VMNIC   VM         State PortGroup  VLAN-Range
------------------------------------------------------------------------------
Ethernet1/3/1   20.2.2.2                          vmnic4  No-OS1     on    PGroup100  100
Ethernet1/3/1   20.2.2.2                          vmnic4  No-OS1     on    PGroup103  103

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

switch(config-vmt-conn)# show running-config interface ethernet 1/3/1
!Command: show running-config interface Ethernet1/3/1
!Time: Mon Mar 10 09:11:06 2014
version 6.0(2)U3(1)
interface Ethernet1/3/1
switchport mode trunk
switchport trunk allowed vlan 1,100,103

This example shows how verify VM Tracker event-history information:

switch(config-vmt-conn)# show vmtracker event-history
------------------------------------------------------------------------------
Event History (Connection:test NumEv:6 IP:20.1.1.1)
------------------------------------------------------------------------------
EventId    Event Msg
------------------------------------------------------------------------------
77870      Reconfigured No-OS1 on 20.2.2.2 in N3K-VM
77867      No-OS1 on  20.2.2.2 in N3K-VM is powered on
77863      Reconfigured No-OS1 on 20.2.2.2 in N3K-VM
77858      No-OS1 on  20.2.2.2 in N3K-VM is powered off

This example shows how to disconnect from vCenter:

switch(config)# vmtracker connection test
switch(config-vmt-conn)# no connect
switch(config-vmt-conn)# show vmtracker status
Connection           Host/IP                             status
-----------------------------------------------------------------------------
test                 20.1.1.1                                             No Connect

switch(config-vmt-conn)# sh running-config interface ethernet 1/3/1
!Command: show running-config interface Ethernet1/3/1
!Time: Mon Mar 10 09:15:43 2014
version 6.0(2)U3(1)
interface Ethernet1/3/1
switchport mode trunk
switchport trunk allowed vlan 1

switch(config-vmt-conn)# show vmtracker info detail
------------------------------------------------------------------------------
Interface       Host            VMNIC   VM         State PortGroup  VLAN-Range
------------------------------------------------------------------------------

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

Chapter 4. Using Virtual Machine Tracker Auto-Config

- Virtual Machine Tracker Auto-Config

- Guidelines and Limitations for Virtual Machine Tracker Auto-Config

- Enabling Virtual Machine Tracker Auto-Config

- Verifying Virtual Machine Tracker Auto-Config Configuration

- Example Configuration for Virtual Machine Tracker Auto-Config

Virtual Machine Tracker Auto-Config

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.

- Configuration Profile

- Using auto-pull

- Virtual Machine Tracker Auto-Config Workflow

Configuration Profile

A configuration profile for auto-config is a collection of commands used to instantiate a specific configuration. Based on appropriate end-host triggers (VM Tracker trigger), configuration profiles are grouped to allow flexible and extensible options to instantiate tenant-related configurations on a leaf node.

The commands are entered using variables for certain parameters instead of entering the actual value. The switch fills in the actual values to derive the completed command. When the required parameters for a particular configuration profile are available, the profile can be instantiated to create a configuration set. The switch applies this configuration set to complete the command execution belonging to the configuration set.

The commands that are supported in a configuration profile are called config-profile-aware commands. Most of the commands for a switch can be used in the configuration profile.

Various sets of configuration profiles can be created and stored in the network database using LDAP, and each network can use a different configuration profile. The configuration profiles from the network are used to configure the leaf whenever required. Configuration profiles can also be designed with VRFs. An "include profile any" in the configuration profile can indicate that a particular profile needs to be instantiated for the VRF. The network database for the VRF carries the name to be used for the included profile.

- Configuration Profile Refresh

- Network Database

- Configuration Profile Example

Configuration Profile Refresh

A configuration profile refresh involves updating and/or removing profile parameters (arguments or variables) without disrupting network traffic. When the network database is modified for parameters of a network profile, the changes are pulled down to the switch by issuing a refresh command. When using Cisco DCNM for auto-config, Cisco Prime DCNM executes the fabric database refresh vni/dot1q/vrf command on the fabric switches when network parameters are modified for a particular entry in the network database.

Network Database

A network database is stored in an external LDAP server as multiple tables. There are three different tables:

- Network Table

- Partition Table

- Profile Table

- Network Table

- Partition Table

- ProfileTable

Network Table

All the parameters for a host network are stored in this table in the LDAP. This includes, segment ID, VLAN, Gateway, and VRF information.

fabric database type network
server protocol ldap host dcnm721_39.cisco.com vrf management
db-table ou=networks,dc=cisco,dc=com key-type 1
db-security user cn=reader,dc=cisco,dc=com password cisco123

Partition Table

All parameters that are required to provision a VRF on the switch are stored in the partition table. A network table entry specifies which VRF it uses. The VRF partition table specifies the parameters that are required for this VRF, including the profile that the VRF partition uses.

fabric database type partition
server protocol ldap host dcnm721_39.cisco.com vrf management
db-table ou=partitions,dc=cisco,dc=com
db-security user cn=reader,dc=cisco,dc=com password cisco123

ProfileTable

The profile table stores the configuration profiles that are required to instantiate a particular network. Each network/partition table specifies which profile it uses. The profile table holds the configuration profile itself.

fabric database type profile
server protocol ldap host dcnm721_39.cisco.com vrf management
db-table ou=profilesIPFabric,dc=cisco,dc=com
db-security user cn=reader,dc=cisco,dc=com password cisco123

Configuration Profile Example

The following are examples of configuration profiles that can be used for network host and VRF provisioning.

- The defaultNetworkEVPNProfile profile can be attached to a network table entry to provision VLAN, segment, gateway IP, and VTEP related information for workloads attached to a switch.

config profile defaultNetworkEVPNProfile
vlan $vlanId
vn-segment $segmentId
interface vlan $vlanId
vrf member $vrfName
ip address $gatewayIpAddress/$netMaskLength tag 12345
ipv6 address $gatewayIpv6Address/$prefixLength tag 12345
fabric forwarding mode anycast-gateway
no shutdown
interface nve $nveId
member vni $segmentId
mcast-group $mcastGroupIpAddress
evpn
vni $segmentId l2
rd auto
route-target import auto
route-target export auto
include profile any
end

- The vrf-common-evpn profile can be used to provision corresponding Layer 3 VRF information.

configure profile vrf-common-evpn
vrf context $vrfName
vni $include_vrfSegmentId
rd auto
address-family ipv4 unicast
route-target both auto
route-target both auto evpn
router bgp $asn
vrf $vrfName
address-family ipv4 unicast
advertise l2vpn evpn
redistribute direct route-map FABRIC-RMAP-REDIST-SUBNET
address-family ipv6 unicast
advertise l2vpn evpn
redistribute direct route-map FABRIC-RMAP-REDIST-SUBNET
interface nve $nveId
member vni $include_vrfSegmentId associate-vrf
End

Using auto-pull

In certain scenarios, you might be required to manually provision a network based on the LDAP database. You can perform this from DCNM using the deploy option or directly from a switch.

You can use one of the following to manually provision a network from a switch:

switch# fabric database auto-pull dot1q interface ethernet <id>
switch# fabric database auto-pull vni interface ethernet <id> overwrite-vlan <vlan-id>

Virtual Machine Tracker Auto-Config Workflow

The following is a typical workflow to provision a tenant and provide an EVPN capable fabric connection to the tenant's workloads.

Note

All leaf switches in the network fabric are provisioned with the VM Tracker connections based on the set of hosts that are connected to the switch.

- Identify the VLAN that a tenant’s virtual machine needs to utilize.

- Provision the required port-groups on the VMware vSphere Distributed Virtual Switch (DVS) or virtual switch.

(You can use an orchestrator such as Cisco UCS Director (UCSD) or provision directly on the VMware vCenter.)

- Determine the configuration profile that needs to be associated with the tenant for provisioning the VRF. For example, associating the vrf-common-universal-evpn profile.

- Collect the tenant's network information and provision the network database with an application that uses the documented DCNM REST APIs.

The network information includes:

- Required configuration profile associated with the server-facing network that is being created.

- All the network parameters required to provision the required configuration profile.

- The mobility domain that is associated with the network.

Note

Only one mobility domain can be supported.

At this point, the fabric is ready for auto provisioning the workloads at any switch which is configured with the suitable mobility domain and the VM Tracker connection.

- When the workloads are powered on, VM Tracker detects the workload and pulls the appropriate network information from the LDAP database and provisions the network on the switch where the workload is connected.

- When a workload is no longer necessary, powering the workload off ensures that the previously configured provisioning is removed.

Guidelines and Limitations for Virtual Machine Tracker Auto-Config

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.

Enabling Virtual Machine Tracker Auto-Config

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.

Before You Begin

VM Tracker feature is enabled.

SUMMARY STEPS

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

DETAILED STEPS

Command or Action

Purpose

Step 1

switch# configure terminal

Enters global configuration mode.

Step 2

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

Enables VM Tracker auto-config trigger.

The no form of the command disables the auto-config trigger.

Step 3

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

Enters VM Tracker connection configuration mode for the connection name specified.

The no form of the command disables the connection.

Step 4

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

Configures remote IP parameters.

Step 5

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

Verifies the username and password to connect to vCenter.

Step 6

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

Connects to vCenter.

The no form of the command disconnects VM Tracker from vCenter.

This example shows how to enable the VM Tracker auto-config trigger:

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

- Triggering Auto-Config

Triggering Auto-Config

You can use the fabric database auto-pull dot1q interface ethernet id command or the fabric database auto-pull vni interface ethernet id overwrite-vlan vlan-id command to trigger VM Tracker auto-config to automatically configure a switch.

Note

When triggering an automatic configuration with auto-pull, subsequent VM Tracker auto-config requests are not supported and are rejected.

Note

An auto-pull automatic configuration is not supported when the VM Tracker auto-vlan feature is enabled.

Verifying Virtual Machine Tracker Auto-Config Configuration

Use the following command to display and verify VM Tracker auto-config configuration information:

Command

Purpose

show vmtracker fabric auto-config

Displays the VM Tracker auto-config information.

Example Configuration for Virtual Machine Tracker Auto-Config

switch# configure terminal
switch(config)# feature vmtracker
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 root password Nbv!23
switch(config-vmt-conn)# connect

switch(config-vmt-conn)# show vmtracker fabric auto-config

Fabric Auto Configuration is enabled
Auto Configure Retry Time left: 107 seconds
Switch Device: SAL1833YM0V
------------------------------------------------------------------------------
Port                          Port-Channel                  Vlan     Status
------------------------------------------------------------------------------
Ethernet1/3                   port-channel13                50       Pending
Ethernet1/3                   port-channel13                56       Pending

On Standalone or VPC Pair Primary:

switch(config-vmt-conn)# show vmtracker fabric auto-config

Fabric Auto Configuration is enabled
Auto Configure Retry Time left: 100 seconds
Switch Device: SAL1833YM0V
------------------------------------------------------------------------------
Port                          Port-Channel                  Vlan     Status
------------------------------------------------------------------------------
Ethernet1/3                   port-channel13                50       Success
Ethernet1/3                   port-channel13                56       Success

On VPC Pair Secondary:

switch(config-vmt-conn)# show vmtracker fabric auto-config

Fabric Auto Configuration is enabled
Auto Configure Retry Time left: 82 seconds
Switch Device: SAL1833YM64
------------------------------------------------------------------------------
Port                          Port-Channel                  Vlan     Status
------------------------------------------------------------------------------
Ethernet1/3                   port-channel13                50       Skipped
Ethernet1/3                   port-channel13                56       Skipped

Switch downloaded profile:

switch(config-vmt-conn)# show fabric database host

Active Host Entries
flags: L - Locally inserted, V - vPC+ inserted, R - Recovered, X - xlated Vlan
VLAN  VNI      STATE           FLAGS PROFILE(INSTANCE)
50    30001    Profile Active  L     defaultNetworkUniversalEvpnProfile-edcs(instance_def_50_1)
56    30056    Profile Active  L     defaultNetworkUniversalEVPNProfileNew(instance_def_56_1)

Switch was profiled synced from VPC peer:

switch(config-vmt-conn)# show fabric  database host

Active Host Entries
flags: L - Locally inserted, V - vPC+ inserted, R - Recovered, X - xlated Vlan
VLAN  VNI      STATE           FLAGS PROFILE(INSTANCE)
50    30001    Profile Active  V     defaultNetworkUniversalEvpnProfile-edcs(instance_def_50_1)
56    30056    Profile Active  V     defaultNetworkUniversalEVPNProfileNew(instance_def_56_1)

switch(config-vmt-conn)# show run vlan 50 expand-port-profile

!Command: show running-config vlan 50 expand-port-profile
!Time: Sat Aug  8 05:25:09 2015version 7.0(3)I2(1)
vlan 50
vn-segment 30001

switch(config-vmt-conn)# show run interface vlan 50 expand-port-profile

!Command: show running-config interface Vlan50 expand-port-profile
!Time: Sat Aug  8 05:29:49 2015
version 7.0(3)I2(1)
interface Vlan50
no shutdown
vrf member Org1:vrfedcs
ip address 50.50.50.15/24 tag 12345
fabric forwarding mode anycast-gateway

Preface

This preface includes the following sections:

- Audience

- Document Conventions

- Related Documentation for Cisco Nexus 9000 Series Switches

- Documentation Feedback

- Obtaining Documentation and Submitting a Service Request

Audience

This publication is for network administrators who install, configure, and maintain Cisco Nexus switches.

Document Conventions

Command descriptions use the following conventions:

Convention

Description

bold

Bold text indicates the commands and keywords that you enter literally as shown.

Italic

Italic text indicates arguments for which the user supplies the values.

[x]

Square brackets enclose an optional element (keyword or argument).

[x | y]

Square brackets enclosing keywords or arguments separated by a vertical bar indicate an optional choice.

{x | y}

Braces enclosing keywords or arguments separated by a vertical bar indicate a required choice.

[x {y | z}]

Nested set of square brackets or braces indicate optional or required choices within optional or required elements. Braces and a vertical bar within square brackets indicate a required choice within an optional element.

variable

Indicates a variable for which you supply values, in context where italics cannot be used.

string

A nonquoted set of characters. Do not use quotation marks around the string or the string will include the quotation marks.

Examples use the following conventions:

Convention

Description

screen font

Terminal sessions and information the switch displays are in screen font.

boldface screen font

Information you must enter is in boldface screen font.

italic screen font

Arguments for which you supply values are in italic screen font.

< >

Nonprinting characters, such as passwords, are in angle brackets.

[ ]

Default responses to system prompts are in square brackets.

!, #

An exclamation point (!) or a pound sign (#) at the beginning of a line of code indicates a comment line.

Related Documentation for Cisco Nexus 9000 Series Switches

The entire Cisco Nexus 9000 Series switch documentation set is available at the following URL:

Click Here

Documentation Feedback

To provide technical feedback on this document, or to report an error or omission, please send your comments to nexus9k-docfeedback@cisco.com. We appreciate your feedback.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What's New in Cisco Product Documentation at: Click Here .

Subscribe to What's New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation as an RSS feed and delivers content directly to your desktop using a reader application. The RSS feeds are a free service.

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. ( Click Here )

This product includes software written by Tim Hudson (tjh@cryptsoft.com).

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: Click Here . Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)