Now that Cisco is giving away the Nexus 1000v, I am guessing we will see less people removing 1000v’s and going back to the standard vDS. If you do need to remove a 1000v instance however, there is a possibility that certain port profiles will remain in vCenter after the removal.
Here’s how to fix this issue.
First off, this post assumes basic familiarity with SQL Management Studio. If you’re not comfortable running queries and deleting data from your vCenter database, call VMware support, and they’ll help you out.
This is what you’ll see in vCenter when you have this issue. Note the 1kv instance is gone. You won’t see the switches, but you will see a folder with the name of the missing 1kv instance. Below that will be your orphaned port profile.
As with any scenario where you will be editing a database, start by doing a full backup of that database.
Next, start a new query.
In the query window, type the following:
SELECT * FROM VPX_ENTITY WHERE NAME =‘<name of profile>’;
Click the Execute button.
You will see the query results show the name of the orphaned port profile.
You should only see one row of results. That’s our orphan. If you do see more than one row, you’ll need to match up the correct vDS with the correct ID.
Do that by running the following:
SELECT * FROM VPX_ENTITY WHERE NAME =‘<name of DVS>’;
In this example, we can see the Parent ID is 70. If you had more than one, you’ll need to make sure you delete the right one, or you’ll be restoring that backup you just made.
Now, start another new query and type the following:
DELETE FROM VPX_ENTITY WHERE ID= ‘<name of profile>’;
Execute this one, and then restart vCenter.
Once you get back into vCenter, you will no longer see the orphan.
Hat tip to Ben Perove on this one. The guy is a 1000v genius!