22-2
Cisco Nexus 1000V Troubleshooting Guide, Release 5.2(1)SV3(1.1)
OL-31593-01
Chapter 22 System
General Restrictions for vCenter Server
See the
Cisco Nexus 1000V Getting Started Guide
for a detailed overview of how the Nexus 1000V
works with VMware ESX software.
General Restrictions for vCenter Server
When you are troubleshooting issues related to vCenter Server, make sure that you observe the following
restrictions:
•
The name of a distributed virtual switch (DVS) name must be unique across Datacenters
•
You create a DVS in a network folder
•
A Datacenter cannot be removed unless the DVS folder or the underlying DVS is deleted.
•
A DVS can be deleted only with the help of VSM using the
no vmware dvs
command in
config-svs-conn mode.
•
The no vmware dvs command can succeed only if there are no VMs using the DVS port-groups.
•
A port group on vCenter Server can be deleted only if there are no interfaces associated with it.
•
A sync operation performed in conjunction with the
connect
command helps VSM keep in sync with
vCenter Server.
•
Each VSM uses a unique extension key to communicate with vCenter Server and perform operations
on a DVS.
Extension Key
The VSM uses the extension key when communicating with the vCenter Server. Each VSM has its own
unique extension key, such as Cisco_Nexus_1000V_32943215
Use the
show vmware vc extension-key
command to find the extension key of the VSM. It is also listed
in the .xml file.
The extension key registered on the vCenter Server can be found through the MOB. For more
information, see the
“Finding the Extension Key Tied to a Specific DVS” procedure on page 3-8
The same extension key cannot be used to create more than one DVS on the vCenter Server.
Recovering a DVS
You can use this procedure to recover a DVS if the VSM VM that was used to create it is lost or needs
to be replaced. This section includes the following procedures:
•
Recovering a DVS With a Saved Copy of the VSM, page 22-3
•