Cisco Nexus 1000V Troubleshooting Manual page 46

Problems with the Nexus 1000V Installation Management Center
S e n d d o c u m e n t c o m m e n t s t o n e x u s 1 k - d o c f e e d b a c k @ c i s c o . c o m .
Symptom
Port migration fails.
The VEM is missing on the VSM after
the migration.
Configuration file issue.
Cisco Nexus 1000V Troubleshooting Guide, Release 4.2(1)SV2(2.1)
3-14
Problem
VSM to VEM migration fails in Layer
2 / Layer 3 mode installation.
The installer application finishes
•
successfully with port migration in
Layer 3 mode.
The VEM is added to the vCenter
•
but does not display when the show
module command is entered on the
VSM.
After loading the previously saved
configuration file, the installation
application does not complete.
Chapter 3
Recommended Action
Check if there is any VM running on
•
the vSwitch. You need to power off
all such VMs before migration.
Check if the vCenter is VUM
•
enabled. Before migration, the host
is added to the DVS by using VUM.
Verify that the native VLAN in the
•
upstream switch configuration is
correct.
Ensure that the VUM repositories
•
are up to date and accurate.
Verify that the Layer 3 control
•
profile VLAN is configured as a
system VLAN.
Verify that the uplink profile is
•
allowing the Layer 3 control vmknic
VLAN and that it is a system
VLAN.
From the ESX host (VEM), issue a
•
vmkping to the mgmt0/control0 IP
address. It should be successful. If
not, check the intermediate switches
for proper routes between the
subnets.
• The vmknic should be pingable
from the VSM.
• Check the vCenter mob for opaque
data propagation.
• Check the configuration file for
appropriate contents.
You might need to change a few
Note
of the fields before reusing the
previously saved files.
Check if a VM with the same name
•
already exists in the DC.
This can be identified by reviewing
the Virtual Machine field in the
configuration file.
Installation
OL-28795-01