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.
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.
There are no specific requirements for this document.
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.
Refer to Cisco Technical Tips Conventions for more information on document conventions.
The VSM was accidentally deleted before the DVS was removed. The DVS must be gracefully removed from vCenter before the VSM is deleted.
Use this solution to solve the problem.
Deploy a temporary VSM.
Restore the startup configuration (or at least restore the previous switch name).
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:
In vCenter, navigate to the networking view.
In the right pane, choose the DVS.
Click the Summary tab. The extension key is listed under Annotations.
To go to the vCenter's mob, browse to https://<VC_IP_ADDR>/mob.
Go to the rootFolder "group-d1".
Find your datacenter from "childEntity" which contains Datacenter-IDs. (When you click on a datacenter, you will find a name associated with it.)
From your datacenter, go to the network folder (for example, "group-n6").
From the network folder, choose the child entity (for example, "group-n373").
In childEntity, click your DVS (for example, "dvs-7"). The extension key is listed under the DVS config attribute.
Enter the vmware vc extension-key <extension-id> command to assign the extension-id to the VSM.
Enter the show vmware vc extension-key command to verify the new extension key on the CP.
Save and reboot the VSM.
Delete the extension key present on the VC with MOB (unregister extension API) with these steps:
To go to the extension manager, browse to https://<VC_IP_ADDR>/mob/?moid=ExtensionManager.
Click Unregister extension (https://<VC_IP_ADDR>/mob/?moid=ExtensionManager&method=unregisterExtension).
Enter Cisco_Nexus_1000V_ <Key for DVS to recover> (your extension key attached to the DVS).
Click Invoke Method.
Reregister the extension key. If you obtain the XML file through the browser, refresh the browser before you download the XML file.
Reregister the extension plug-in.
Set up the Server Virtualization Switch (SVS) connection properties (for example; VC IP, Port, Datacenter name).
Connect to your SVS connection.
From the SVS context on the VSM, enter the no vmware dvs command to gracefully remove the DVS.
Verify the DVS is removed from vCenter.
Delete the temporary VSM.