Comments on: Removing orphaned Nexus DVS

By: Øystein F

Øystein F — Tue, 15 Mar 2011 13:31:56 +0000

Frank, thank you for this article, it has just saved my day
Just to mention it, I found the old extension keys by running a query directly on the database: “Select Name, Extension_key from VPX_DVS”

By: Ilya Meylikhov

Ilya Meylikhov — Tue, 28 Dec 2010 11:50:17 +0000

Frank, thx u 4 article, but it seems to me that it is either not worikng for version 4.0.4.SV1.3b or I am doing something wrong: on the last step on issuining “connect” command, I got this error:
“A vDS Nexus_1kv-primary with spec.name as Nexus_1kv-primary already exists, cannot create vDS Nexus_1kv-primary”
But I recheck all twice: I ‘ve removed new key, changed the extension key of VSM to the old one, downloaded plugin, registered it, and try to reconnect and everytime I get this error message,
any suggestions?…

By: Lee Luu

Lee Luu — Fri, 26 Nov 2010 01:02:37 +0000

Theres an easier method to find the extension key. Just create the 1000v with the same hostname as that of the orphaned DVS, and connect to the SVS. The resultant error will give you the required extension key to be voided.

By: 5 days to vote | frankdenneman.nl

5 days to vote | frankdenneman.nl — Sun, 19 Sep 2010 05:46:08 +0000

[...] Removing an orphaned Nexus DVS [...]

By: Ben S

Ben S — Wed, 25 Aug 2010 16:40:16 +0000

Frank,

I cannot thank you enough for this article!

One part that seemed a bit confusing was when I initially entered the:

no vmware dvs

command it removed the extension key for the “new” DVS from the vCenter DB.

So, effectively there was only (1) extension key for me in the DB.

I then took that key, disconnected the VSM, changed the hostname, set the key, and unregistered the key using the MOB.

After this I was able to register the VSM and remove the old DVS.

Thank you
Ben

By: virtuel

virtuel — Thu, 24 Jun 2010 06:36:43 +0000

Frank,
you always have great articles. I have a question related to the Nexus VSM not directly related to the points you bring up in this article.

We have a vSphere4 enterprise configuration with dVs and were looking to use the nexus 1000v. I was wondering if you can give me some of the downside to using the Nexus enterprise wide. What are the risks? what happens when vCenter is unavailable or there is a SAN Issue or datastore issue that somehow corrupts the database?

I guess you can rightfully pose the same questions of every single component of vCenter but I want the customer to rightfully understand what the pros and cons are of going this way. I know there is redundancy with the VSM – at least 2 VSM appliances on pinned on seperate ESX Hosts and datastores? Is there a best practices confguration for redundancy? a Real-world solution or situation?

Thanks for any feedback
Virtuel

By: Virtualization Short Take #37 | Free Techie Blog

Virtualization Short Take #37 | Free Techie Blog — Thu, 01 Apr 2010 03:54:21 +0000

[...] Denneman has published a couple of really great articles recently. The first discussed how to remove an orphaned Nexus 1000V distributed virtual switch; the second discusses a complex interaction between HP Continuous Access and LUN balancing scripts. [...]

By: Virtualization Short Take #37 - blog.scottlowe.org - The weblog of an IT pro specializing in virtualization, storage, and servers

Wed, 24 Mar 2010 13:49:10 +0000

By: INTERNETWORK EXPERT .ORG » links for 2010-03-14

INTERNETWORK EXPERT .ORG » links for 2010-03-14 — Mon, 15 Mar 2010 01:01:23 +0000

[...] Removing an orphaned Nexus 1000v from vCenter Did you delete your Nexus 1000v VSM before removing it from vCenter? This article will help. (tags: n1k) [...]

By: Top 5 Planet V12n blog posts week 10 | VMvisor

Top 5 Planet V12n blog posts week 10 | VMvisor — Sun, 14 Mar 2010 10:55:17 +0000

[...] Denneman – Removing an orphaned Nexus DVSWhen installing the Cisco Nexus 1000V VSM, the VSM uses an extension-key for identification. During [...]