Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Removing a Cisco Nexus 1000V from vCenter Server (1020542)

Symptoms

  • Removing a Cisco Nexus 1000V from vCenter Server fails
  • You see the error:
Cannot remove the object, since it has active related objects.

Or
Failed to delete dvs from VC. 'VC' is Disconnected. Removing config locally

Purpose

This article provides steps to remove a Cisco Nexus 1000V Virtual Supervisor Module (VSM) from vCenter Server.

Resolution

Note: The links in this article were correct as of February 5, 2013. If you find a broken link, please provide feedback and a VMware employee will update the link.
 
Run the command no vmware dvs from an svs connection to remove a Cisco Nexus 1000V VSM from vCenter Server. You cannot remove the VSM from within vCenter Server. For more information, see Removing the Cisco Nexus 1000V from the vCenter Server  in the Cisco Nexus 1000V Troubleshooting Guide.
 
If you have removed the VSM without running the no vmware dvs command, the old VSM remains in vCenter Server. You have to manually delete the VSM entries.
 
To delete the remaining VSM:
  1. Reconnect the VSM to vCenter Server, or create a new VSM with the same extension key (either from ISO or OVF).

  2. Ensure the hostname of the VSM matches with the name of the N1KV vDS as seen in vCenter Server. To modify hostname, log in to VSM and run these commands:

    n1000v # conf t
    n1000v(config)# hostname Oldhostname
    n1000v(config)# exit
    n1000v # copy run start


  3. Find the extension key tied to the old VSM.

    To find the extension key tied to a VSM:

    • Log in to vCenter Server using the vSphere Client.
    • Go to Home > Networking.
    • Click N1KV DVS.
    • Click the Summary tab. The extension key string is listed in the Notes field.

    For more information, see the Finding the Extension Key on the Cisco Nexus 1000V section in the Cisco Nexus 1000V Troubleshooting Guide

  4. Configure the extension key on the new VSM with the command:

    n1000v(config)# vmware vc extension-key key

  5. Unregister the related extension key on vCenter Server. For more information, see the Unregistering the Extension Key in the vCenter Server section in the Cisco Nexus 1000V Troubleshooting Guide.

  6. Open a browser, browse to the VSM, and download the extension.xml file. Refresh the browser page to get the current extension key.

  7. Register the new extension.xml file in vCenter Server:

    1. In vCenter Client, click the Plug-ins menu.
    2. Click Manage Plug-ins.
    3. Right-click the white space within the dialog and click New Plug-In.
    4. Click Browse and choose the cisco_nexus1000v_extension.xml file that you downloaded from the VSM home page.
    5. Click Register Plug-In.
    For more information, see Creating a Cisco Nexus 1000V Plug-In on the vCenter Server in the Cisco Nexus 1000V Software Installation Guide.

    Note: Ensure that the switch name of the VSM is the same as one you are trying to delete.

  8. Reconnect the VSM to vCenter Server using these commands:

    n1000v# conf t
    n1000v(config)# svs conn VC
    n1000v(config-svs-conn)# protocol vmware-vim
    n1000v(config-svs-conn)# remote ip address [IP_address of VC]
    n1000v(config-svs-conn)# vmware dvs datacenter-name [DC_name]
    n1000v(config-svs-conn)# connect


    Note: You must be connected to vCenter Server before you remove the DVS.

  9. When it connects to vCenter Server, delete the VSM using the no vmware dvs command under an svs connection.
THE CONTENT OF THIS ARTICLE IS PROVIDED "AS-IS," AND TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, VMWARE DISCLAIMS ALL OTHER REPRESENTATIONS AND WARRANTIES, EXPRESS OR IMPLIED, REGARDING THIS CONTENT, INCLUDING THEIR FITNESS FOR A PARTICULAR PURPOSE, THEIR MERCHANTABILITY, OR THEIR NONINFRINGEMENT. VMWARE SHALL NOT BE LIABLE FOR ANY DAMAGES ARISING OUT OF OR IN CONNECTION WITH THE USE OF THIS CONTENT, INCLUDING DIRECT, INDIRECT, CONSEQUENTIAL DAMAGES, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF VMWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Additional Information

For details on more commands, see Managing Server Connections in the Cisco Nexus 1000V System Management Configuration Guide.
 

Tags

removing-nexus-1000v-vds

See Also

Update History

2/5/2013 - Replaced Cisco documentation links with a more current release 4.2(1)SV2(1.1) and added ESXi 5.x to the list of products. 11/22/2013 - Added steps to register the new extension.xml file in vCenter Server

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 17 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 17 Ratings
Actions
KB: