Guest

Cisco Nexus 1000V Switch for VMware vSphere

Orphaned Distributed Virtual Switch in Nexus 1000V vCenter

Document ID: 115759

Updated: Jan 18, 2013

Contributed by Robert Burns, Cisco TAC Engineer.

   Print

Introduction

This document describes the solution when the Virtual Supervisor Module (VSM) is deleted accidentally and the Distributed Virtual Switch (DVS) continues to display in Cisco Nexus 1000V vCenter.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

This document is not restricted to specific software and hardware versions.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.

Problem

The VSM was accidentally deleted before the DVS was removed. The DVS must be gracefully removed from vCenter before the VSM is deleted.

Solution

Use this solution to solve the problem.

  1. Deploy a temporary VSM.

  2. Restore the startup configuration (or at least restore the previous switch name).

  3. Enter the vmware vc extension-key <extension-id> command to have a new control processor (CP) connect to the current DVS. The extension- id in this command should be the same one that is tied down to the DVS. You can find the extension-id with one of these two methods:

    Method 1

    1. In vCenter, navigate to the networking view.

    2. In the right pane, choose the DVS.

    3. Click the Summary tab. The extension key is listed under Annotations.

    Method 2

    1. To go to the vCenter's mob, browse to https://<VC_IP_ADDR>/mob.

    2. Go to the rootFolder "group-d1".

    3. Find your datacenter from "childEntity" which contains Datacenter-IDs. (When you click on a datacenter, you will find a name associated with it.)

    4. From your datacenter, go to the network folder (for example, "group-n6").

    5. From the network folder, choose the child entity (for example, "group-n373").

    6. In childEntity, click your DVS (for example, "dvs-7"). The extension key is listed under the DVS config attribute.

  4. Enter the vmware vc extension-key <extension-id> command to assign the extension-id to the VSM.

  5. Enter the show vmware vc extension-key command to verify the new extension key on the CP.

  6. Save and reboot the VSM.

  7. Delete the extension key present on the VC with MOB (unregister extension API) with these steps:

    1. To go to the extension manager, browse to https://<VC_IP_ADDR>/mob/?moid=ExtensionManager.

    2. Click Unregister extension (https://<VC_IP_ADDR>/mob/?moid=ExtensionManager&method=unregisterExtension).

    3. Enter Cisco_Nexus_1000V_ <Key for DVS to recover> (your extension key attached to the DVS).

    4. Click Invoke Method.

  8. Reregister the extension key. If you obtain the XML file through the browser, refresh the browser before you download the XML file.

  9. Reregister the extension plug-in.

  10. Set up the Server Virtualization Switch (SVS) connection properties (for example; VC IP, Port, Datacenter name).

  11. Connect to your SVS connection.

  12. From the SVS context on the VSM, enter the no vmware dvs command to gracefully remove the DVS.

  13. Verify the DVS is removed from vCenter.

  14. Delete the temporary VSM.

Related Information

Updated: Jan 18, 2013
Document ID: 115759