Cisco Virtual Switch Update Manager Troubleshooting Guide, Release 2.x

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Book Contents
Find Matches in This Book
Available Languages
Download Options

Book Title

Cisco Virtual Switch Update Manager Troubleshooting Guide, Release 2.x

Chapter Title

Migrating Cisco Nexus 1000V

Results

Updated:
February 22, 2016

Chapter: Migrating Cisco Nexus 1000V

Migrating Cisco Nexus 1000V

This chapter contains the following sections:

Problems with Migrating Hosts to the Cisco Nexus 1000V

This section includes symptoms, possible causes, and solutions for the following problems while you migrate hosts to the Cisco Nexus 1000V.

Symptom

Possible Causes

Verification and Solution

Hosts do not appear under the supported host list.

The host could be one of the following:

  • Disconnected or not responding state

  • Already added to the Cisco Nexus 1000V switch.

  • Running an unsupported ESXi version by the switch.

Resolve the host issues and refresh the page.

Cisco Virtual Switch Update Manager displays the following error message:

"The port profile does not have its native VLAN configured correctly."

If Cisco Discovery Protocol (CDP) is enabled on the upstream for the VMNIC, the Cisco Virtual Switch Update Manager automatically suggests a port profile with the native VLAN. If CDP is disabled, the native VLAN does not appear for the port profile associated with the VMNIC.

Enter the native VLAN manually in the Native VLAN field and click Finish to migrate the host to the Cisco Nexus1000V switch.

The connectivity to some of the VMs is lost.

All the physical adapters are moved to the Cisco Nexus 1000V, while some VMs are not migrated.

Do not move all the physical adapters. You must retain at least one active physical adapter that can be used for any of the VMs that are not migrated.

The VLANs are not backed up by the uplink port profiles.

The VLANs that belong to the VMkernels and the VMs are not configured in the Ethernet port profile.

Ensure that all the VMkernel and the VM VLANs are configured in the uplink Ethernet port profile.

Add the VLANs manually to the uplink Ethernet port profiles that are not backed by the Ethernet port profile.

The VEM module goes missing.

The VSM to VEM communication is incomplete.

Ensure that the IP address and the VLAN that is selected for the VMkernel for the Layer 3 control traffic is correct.

An internal error occurs.

  1. Log into a terminal session.

  2. Navigate to etc/ciscoapp_install

    and run the $ ./bundleLogs.sh command.

  3. In the root directory, retrieve the ajaxLogsfolder, compress the folder, and send it to the Cisco Technical Assistance Center.

    Note   

    For a first-time VSUM 2.0 installation, the folder name will be vsumLogs instead of ajaxLogs.

If a problem persists after you try one of the first five solutions in the preceding table, follow instructions in the section Collecting VSUM Bundle Logs for the Cisco Technical Assistance Center.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco