Cisco Nexus 9000 Series User manual

Cisco Nexus 9000 Series NX-OS Virtual Machine Tracker
Configuration Guide, Release 6.x
First Published: 2014-07-23
Last Modified: 2015-05-06
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: [phone]
800 553-NETS (6387)
Fax: [phone]

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 ([email protected]).
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)
This product includes software written by Tim Hudson ([email protected]).
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: http://
www.cisco.com/go/trademarks. 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)
©2014 Cisco Systems, Inc. All rights reserved.

CONTENTS
Preface Preface v
Audience v
Document Conventions v
Related Documentation for Cisco Nexus 9000 Series Switches vi
Documentation Feedback vi
Obtaining Documentation and Submitting a Service Request vii
CHAPTER 1 New and Changed Information 1
New and Changed Information 1
CHAPTER 2 Overview 3
Information About Virtual Machine Tracker 3
Virtual Machine Tracker and VMware vCenter 3
CHAPTER 3 Configuring Virtual Machine Tracker 5
Information About Virtual Machine Tracker 5
Guidelines and Limitations for VM Tracker 5
Enabling Virtual Machine Tracker 6
Creating a New Connection to vCenter 6
Synchronizing Information with VMware vCenter 7
Compatibility Checking on a VPC Topology 8
Verifying the Virtual Machine Tracker Configuration 9
Enabling Virtual Machine Tracker on Specific Interfaces 10
Configuring Dynamic VLAN Creation 10
Enabling Dynamic VLAN Creation 10
Configuring an Allowed VLAN List 11
Example of VM Tracker Information 11
Cisco Nexus 9000 Series NX-OS Virtual Machine Tracker Configuration Guide, Release 6.x
iii

Example Configuration for Virtual Machine Tracker 18
Cisco Nexus 9000 Series NX-OS Virtual Machine Tracker Configuration Guide, Release 6.x
iv
Contents

Preface
This preface includes the following sections:
•Audience, page v
•Document Conventions, page v
•Related Documentation for Cisco Nexus 9000 Series Switches, page vi
•Documentation Feedback, page vi
•Obtaining Documentation and Submitting a Service Request, page vii
Audience
This publication is for network administrators who install, configure, and maintain Cisco Nexus switches.
Document Conventions
Command descriptions use the following conventions:
DescriptionConvention
Bold text indicates the commands and keywords that you enter literally
as shown.
bold
Italic text indicates arguments for which the user supplies the values.
Italic
Square brackets enclose an optional element (keyword or argument).[x]
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}
Cisco Nexus 9000 Series NX-OS Virtual Machine Tracker Configuration Guide, Release 6.x
v

DescriptionConvention
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.
[x {y | z}]
Indicates a variable for which you supply values, in context where italics
cannot be used.
variable
A nonquoted set of characters. Do not use quotation marks around the
string or the string will include the quotation marks.
string
Examples use the following conventions:
DescriptionConvention
Terminal sessions and information the switch displays are in screen font.screen font
Information you must enter is in boldface screen font.boldface screen font
Arguments for which you supply values are in italic screen font.
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:
http://www.cisco.com/en/US/products/ps13386/tsd_products_support_series_home.html
Documentation Feedback
To provide technical feedback on this document, or to report an error or omission, please send your comments
to [email protected]. We appreciate your feedback.
Cisco Nexus 9000 Series NX-OS Virtual Machine Tracker Configuration Guide, Release 6.x
vi
Preface
Related Documentation for Cisco Nexus 9000 Series Switches

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: http://
www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html.
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.
Cisco Nexus 9000 Series NX-OS Virtual Machine Tracker Configuration Guide, Release 6.x
vii
Preface
Obtaining Documentation and Submitting a Service Request

Cisco Nexus 9000 Series NX-OS Virtual Machine Tracker Configuration Guide, Release 6.x
viii
Preface
Obtaining Documentation and Submitting a Service Request

CHAPTER 1
New and Changed Information
•New and Changed Information, page 1
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.
Where DocumentedAdded or Changed in
Release
DescriptionFeature
This document.6.1(2)I3(1)Initial Virtual Machine Tracker
support.
Virtual Machine
Tracker
Cisco Nexus 9000 Series NX-OS Virtual Machine Tracker Configuration Guide, Release 6.x
1

Cisco Nexus 9000 Series NX-OS Virtual Machine Tracker Configuration Guide, Release 6.x
2
New and Changed Information
New and Changed Information

CHAPTER 2
Overview
This chapter contains the following sections:
•Information About Virtual Machine Tracker, page 3
•Virtual Machine Tracker and VMware vCenter, page 3
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.
Cisco Nexus 9000 Series NX-OS Virtual Machine Tracker Configuration Guide, Release 6.x
3

•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.
Cisco Nexus 9000 Series NX-OS Virtual Machine Tracker Configuration Guide, Release 6.x
4
Overview
Virtual Machine Tracker and VMware vCenter

CHAPTER 3
Configuring Virtual Machine Tracker
This chapter contains the following sections:
•Information About Virtual Machine Tracker, page 5
•Enabling Virtual Machine Tracker, page 6
•Creating a New Connection to vCenter, page 6
•Synchronizing Information with VMware vCenter, page 7
•Compatibility Checking on a VPC Topology, page 8
•Verifying the Virtual Machine Tracker Configuration, page 9
•Enabling Virtual Machine Tracker on Specific Interfaces, page 10
•Configuring Dynamic VLAN Creation, page 10
•Example of VM Tracker Information, page 11
•Example Configuration for Virtual Machine Tracker, page 18
Information About 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.0, 5.1, and 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.
Cisco Nexus 9000 Series NX-OS Virtual Machine Tracker Configuration Guide, Release 6.x
5

Connecting a host through a fabric extender (FEX) is supported by a Cisco Nexus 9000
Series switch.
Note
Enabling Virtual Machine Tracker
By default, the VM Tracker feature is enabled on all interfaces.
Procedure
PurposeCommand or Action
Enters global configuration mode.switch# configure terminal
Step 1
Enables the VM Tracker feature on all interfaces.switch(config)# [no] feature
vmtracker
Step 2
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
Procedure
PurposeCommand or Action
Enters global configuration mode.switch# configure terminal
Step 1
Enters VM Tracker connection configuration
mode for the connection name specified.
switch(config)# [no] vmtracker connection
connection-name
Step 2
The no form of the command disables the
connection.
Configures remote IP parameters.switch(config-vmt-conn)# [no] remote {ip
address ip_address |port port_number |
vrf}
Step 3
Verifies the username and password to connect
to vCenter.
switch(config-vmt-conn)# username
username password password
Step 4
Connects to vCenter.switch(config-vmt-conn)# [no] connect
Step 5
Cisco Nexus 9000 Series NX-OS Virtual Machine Tracker Configuration Guide, Release 6.x
6
Configuring Virtual Machine Tracker
Enabling Virtual Machine Tracker

PurposeCommand or Action
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.
PurposeCommand
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 find-new-host 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.
[no] set interval sync-full-info val
Synchronizes all host, VM, and port group related
information with vCenter immediately for the
specified connection.
vmtracker connection connection-name refresh
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
Cisco Nexus 9000 Series NX-OS Virtual Machine Tracker Configuration Guide, Release 6.x
7
Configuring Virtual Machine Tracker
Synchronizing Information with VMware vCenter

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.
To ensure that the VM Tracker compatibility checking was successful, use the show system internal vmtracker
info vpc-sync-config command. This command provides information about consistency parameter checking.
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#
The following is an example of VM Tracker compatibility:
switch# show system internal vmtracker info vpc-sync-config
------------------------------------------------------------------------------
Conn Name Conn IP Conn Port Allowed Vlan-Range
------------------------------------------------------------------------------
conn1 10.193.174.215 80 1-4094
switch#
Cisco Nexus 9000 Series NX-OS Virtual Machine Tracker Configuration Guide, Release 6.x
8
Configuring Virtual Machine Tracker
Compatibility Checking on a VPC Topology

Verifying the Virtual Machine Tracker Configuration
Use the following commands to display and verify VM Tracker configuration information:
PurposeCommand
Displays the VM Tracker configuration.show running-config vmtracker [all]
Displays the VM Tracker configuration based on the
following:
•Connection
•Interface
•Event history
show vmtracker [connection conn_name] {{info
[interface intf_id ]{summary |detail |host |vm |
port-group}} | event-history}
Displays the IP address and connection status of the
vCenter connection specified.
show vmtracker [connection conn_name]status
Displays the logging level of the syslog messages for
VM Tracker.
show logging level vmtracker
Displays the configuration information of VM Tracker
based on the following:
•All configuration information.
•Counter information.
•DVS information.
•Event history information.
•Host CDP information.
•Host DVS portgroup information.
•Host DVS Switch information.
•Host LLDP information.
•Host portgroup information.
•Host which are not connected.
•Host Virtual Machine information.
•Host vSwitch information.
•Switch information.
•Switch device IDs.
•Information related to the duration of various
events.
•vPC related connection information.
show system internal vmtracker info all show
system internal vmtracker {info [all |counters |
dvs-info |event-history |host-cdp |
host-dvs-portgroup |host-dvs-switch |host-lldp |
host-portgroup |host-unconnected |host-vm |
host-vswitch |switch |switch-device-id |time-info
|vpc-sync-config]
Cisco Nexus 9000 Series NX-OS Virtual Machine Tracker Configuration Guide, Release 6.x
9
Configuring Virtual Machine Tracker
Verifying the Virtual Machine Tracker Configuration

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.
Procedure
PurposeCommand or Action
Enters global configuration mode.switch# configure terminal
Step 1
Enters the interface configuration mode for the
specified interface.
switch(config)# interface type
slot/port
Step 2
Enables the VM Tracker feature on the specified
interface.
switch(config-if)# [no] vmtracker
enable
Step 3
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
Configuring Dynamic VLAN Creation
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.
Procedure
PurposeCommand or Action
Enters global configuration mode.switch# configure terminal
Step 1
Cisco Nexus 9000 Series NX-OS Virtual Machine Tracker Configuration Guide, Release 6.x
10
Configuring Virtual Machine Tracker
Enabling Virtual Machine Tracker on Specific Interfaces

PurposeCommand or Action
Enters VM Tracker connection configuration mode
for the connection name specified.
switch(config)# vmtracker connection
connection-name
Step 2
Enables dynamic VLAN creation and deletion.switch(config-vmt-conn)# [no] autovlan
enable
Step 3
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.
Procedure
PurposeCommand or Action
Enters global configuration mode.switch# configure terminal
Step 1
Enters VM Tracker connection configuration
mode for the connection name specified.
switch(config)# vmtracker connection
connection-name
Step 2
Configures a list of VLANs that can be
dynamically configured on interfaces.
switch(config-vmt-conn)# allowed-vlans
{allow-vlans |add add-vlans |except
except-vlans |remove remove-vlans |all}
Step 3
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 of VM Tracker Information
This example uses the show system internal vmtracker info detail command to display VM Tracker
information.
switch# show system internal vmtracker info all
Cisco Nexus 9000 Series NX-OS Virtual Machine Tracker Configuration Guide, Release 6.x
11
Configuring Virtual Machine Tracker
Configuring an Allowed VLAN List

VM-Interface Mapping (Device:50:87:89:a1:f0:de)
------------------------------------------------------------------------------
Interface Host VMNIC VM State PortGroup VLAN-Range
------------------------------------------------------------------------------
port-channel2 10.193.174.213 vmnic7 Site-1-Hos on dvPortGrou 1-100
port-channel2 10.193.174.213 vmnic7 Site-1-Hos on dvPortGrou 1-100
VM-Interface Mapping (Device:50:87:89:a1:f0:df)
------------------------------------------------------------------------------
Interface Host VMNIC VM State PortGroup VLAN-Range
------------------------------------------------------------------------------
port-channel3 10.193.174.214 vmnic7 Site-1-Hos on dvPortGrou 1-100
port-channel3 10.193.174.214 vmnic7 Site-1-Hos on dvPortGrou 1-100
VM-Interface Mapping (Device:50:87:89:a1:f0:e1)
------------------------------------------------------------------------------
Interface Host VMNIC VM State PortGroup VLAN-Range
------------------------------------------------------------------------------
------------------------------------------------------------------------------
Host VM Info (Conn:conn1 IP:10.193.174.215)
------------------------------------------------------------------------------
Host VM State PortGroup
------------------------------------------------------------------------------
10.193.174.213 Site-1-Host-1-VM-1-Ubuntu on VM Network
10.193.174.213 Site-1-Host-1-VM-1-Ubuntu on dvPortGroup
10.193.174.213 Site-1-Host-1-VM-10-Ubunt on VM Network
10.193.174.213 Site-1-Host-1-VM-2-Ubuntu on VM Network
10.193.174.213 Site-1-Host-1-VM-2-Ubuntu on dvPortGroup
10.193.174.213 Site-1-Host-1-VM-3-Ubuntu on VM Network
10.193.174.213 Site-1-Host-1-VM-4-Ubuntu on VM Network
10.193.174.213 Site-1-Host-1-VM-5-Ubuntu on VM Network
10.193.174.213 Site-1-Host-1-VM-6-Ubuntu on VM Network
10.193.174.213 Site-1-Host-1-VM-7-Ubuntu on VM Network
10.193.174.213 Site-1-Host-1-VM-8-Ubuntu on VM Network
10.193.174.213 Site-1-Host-1-VM-9-Ubuntu on VM Network
10.193.174.213 Site-1-vCenter-Server on VM Network
10.193.174.214 Site-1-Host-2-VM-1-Ubuntu on VM Network
10.193.174.214 Site-1-Host-2-VM-1-Ubuntu on dvPortGroup
10.193.174.214 Site-1-Host-2-VM-2-Ubuntu on VM Network
10.193.174.214 Site-1-Host-2-VM-2-Ubuntu on dvPortGroup
10.193.174.214 Site-1-Host-2-VM-3-Ubuntu on VM Network
10.193.174.214 Site-1-Host-2-VM-4-Ubuntu on VM Network
10.193.174.214 Site-1-Host-2-VM-5-Ubuntu on VM Network
10.193.174.214 Site-1-Host-2-VM-6-Ubuntu on VM Network
10.193.174.214 Site-1-Host-2-VM-7-Ubuntu on VM Network
10.193.174.214 Site-1-Host-2-VM-8-Ubuntu on VM Network
------------------------------------------------------------------------------
Host CDP Info (Conn:conn1 IP:10.193.174.215)
------------------------------------------------------------------------------
Host Switch Port VMNIC Status
------------------------------------------------------------------------------
------------------------------------------------------------------------------
Host LLDP Info (Conn:conn1 IP:10.193.174.215)
------------------------------------------------------------------------------
Host Switch Port VMNIC Status
------------------------------------------------------------------------------
10.193.174.213 50:87:89:a1:f0:df Ethernet1/2 vmnic5 connected
10.193.174.213 50:87:89:a1:f0:de Ethernet1/1 vmnic7 connected
10.193.174.214 50:87:89:a1:f0:e1 Ethernet1/4 vmnic5 connected
10.193.174.214 50:87:89:a1:f0:e0 Ethernet1/3 vmnic7 connected
------------------------------------------------------------------------------
Host vSwitch Port Group Info (Conn:conn1 IP:10.193.174.215)
------------------------------------------------------------------------------
Host vSwitch PortGroup
------------------------------------------------------------------------------
10.193.174.213 vSwitch0 Management Network
10.193.174.213 vSwitch0 VM Network
10.193.174.214 vSwitch0 Management Network
10.193.174.214 vSwitch0 VM Network
Cisco Nexus 9000 Series NX-OS Virtual Machine Tracker Configuration Guide, Release 6.x
12
Configuring Virtual Machine Tracker
Example of VM Tracker Information