The specified key, name, or identifier already exists problem

[pie8ter]

We bought a new Dell R720 with ESXi5.5.  I logged into the server with the vSphere client 5.5.  Created few vmknics for the iSCSI SAN but later deleted them for reasons I can't remember why.  Now I am recreating the vmknics with the same name, network, etc. However, when I change the MTU to 9000 in the GUI for jumbo frame, I get the "The specified key, name, or identifier already exists" error. If I change the vmknic's name to say "blah" and then change the MTU from 1500 to 9000, no problem.  I can even now change the "blah" to the old name without any issue.  Please note this is a standalone host for now and not part of any vcenter server. So:

1) Create a vmk nic VMK1.  Change the MTU from 1500 to 9000.  No issue.  Now delete it.

2) Create a vmk nic VMK1.  Change the MTU from 1500 to 9000 in GUI.  The error "The specified key, name, or identifier already exists" comes up.

3) Change the name VMK1 to "blah".  Change the MTU from 1500 to 9000 in GUI.  No problem.

4) Now change the name from "blah" to VMK1. No problem. (keep in mind now the MTU is 9000)

I have no problem doing any of the steps above in CLI.

I thought OEM's ESXi installation must've been hosed. So I completely wiped their install and reinstalled the latest build. Repeated steps 1 through 4 and got the same results.  So I am guessing the vmkernel properties are cached/stored locally somewhere.

This error is keeping us from moving forward with our migration plan.  We have an open ticket with vmware.  Any help is greatly appreciated.

Thanks

[Prateek Jain]

After step 2 restart management agents on the host using the command services.sh restart from cli and also do a backup of the host configuration to /sbin/auto-backup.sh

Let me know if this helps.

[pie8ter]

Sorry it didn't help.  I even rebooted the host and still get the error.

Here is more information.

Current setup:

We have a cluster of 4 hosts (vwhost1, vwhost2, vwhost3, vwhost4)  with Esxi4.1 and managed by a standard vcenter 4.1 server. 

The vwhost4 host is a old Dell and will be replaced with the new server.

Ongoing activities:

-Installed the VCenter 5.5 on a new VM with the Windows 2008R2 (This VM is on the 4.1 cluster above).  We decided to migrate instead of upgrade our entire vmware infrastructure.

-Removed vmhost4 from the 4.1 cluster.  Bought a new Dell server with ESXi5.5 and named it "vmhost4" (not joined to the new 5.5 VC).  New server's iSCSI NICs are now on the same iscsi switch as the 4.1 hosts.

-Later we also plan to remove each 4.1 vmhosts one by one and perform a fresh install of the 5.5 before joining them to the new 5.5 vcenter server.

So I am not sure the fact that the new server has the same name as the old decommissioned server means anything.  New server's vmkernel nics also have the same name as the old server. 

[Vikas Shitole]

"The specified key, name, or identifier already exists"

This error usually pops up when same entity is already available but as you said, all such objects are deleted and created again, it should allow you to create.

Plz make sure you have deleted that object from all the hosts.

You are correct that earlier object is cached and it causing this issue. If you are sure you have deleted object (NIC etc..)in question & if it is reoccurring,  I suggest you to raise VMware support request.  

[pie8ter]

I just got a call back from vmware and was told they also see the same behavior in their lab.  So it seems like the issue with the product itself (vpshere5.5 client or esxi 5.5).

[Vikas Shitole]

This is great, plz let us know more updates on this from Vmware

[pie8ter]

They found the issue is with the vSphere 5.5 client and will fix the bug in the next update.  We are moving on with our project since we can do everything we want using the CLI.