
22-5
Cisco Nexus 1000V Troubleshooting Guide, Release 5.2(1)SV3(1.1)
OL-31593-01
Chapter 22 System
Problems Related to VSM and vCenter Server Connectivity
For more information see the following procedure in the
Cisco Nexus 1000V Getting Started Guide
.
•
Creating a Cisco Nexus 1000V Plug-In on the vCenter Server
Step 5
Manually recreate the old port profiles from your previous configuration.
For more information, see the following procedures in the
Cisco Nexus 1000V Getting Started Guide
.
•
Configuring the system port profile for VSM-VEM Communication
•
Configuring the uplink port profile for VM Traffic
•
Configuring the data port profile for VM Traffic
Note
If you do not manually recreate the port profiles, then all port groups on the vCenter Server
are removed when the VSM connects.
Step 6
On the VSM, restore the configuration for the vCenter server connection.
Example
:
switch#
config t
switch (config)#
svs connection VC
switch(config-svs-conn#)
protocol vmware-vim
switch(config-svs-conn#)
remote ip address 192.168.0.1
switch(config-svs-conn#)
vmware dvs datacenter-name Hamilton-DC
Step 7
Connect to vCenter Server.
Example
:
switch(config-svs-conn#)
connect
You can now use the old DVS or remove it.
Problems Related to VSM and vCenter Server Connectivity
Symptom
Solution
Connections are not
supported between Release
4.0(4)SV1(3a) VSMs and
VMware vCenter Server 5.0
Upgrade to a compatible version of the Cisco Nexus 1000V software.
The vCenter Server
connection seems to succeed,
but does not.
Make sure that the domain ID is configured correctly.
The
svs connection
command
fails.
Make sure you have configured all parameters for the
svs connection
command.
Make sure you can ping the vCenter Server IP address.
Make sure that the proxy.xml file is correct for both the IP address and
length.
Restart the vCenter Server