vCenter showing Nimble IP as source for Active Directory user account lockout

[rbrussell8239]

Our previous Network Admin setup most of our vCenter and Nimble configs and he used his AD account somewhere.  We are setup with Windows Servers.

In Active Directory, the workstation causing the lockout is our vCenter Server.  When I log into the vSphere Web Client as admin, it shows the account lockout and gives me the IP address, which is one of our Nimble arrays.

I've gone through all of the Volume Collections and everything I can find and it is all setup with a service account.

When we unlock the account, it will get locked again.  The logs on the vSphere Web Client show an attempt every hour, 3 times, 10 minutes apart, but no other information is given.

In VMWare, it shows the SSO Identity Manager, but not much other information.

Any ideas?

[alex_goltz]

Did you check to see what account is being used for the vCenter Plug-in account?
Nimble GUI --> Administration --> vCenter PlugIn

[rbrussell8239]

I'm having a similar issue on our DR setup.  I have checked the vCenter Plugin on that site and have verified that it is using the service account we want it to.  The Nimble is trying to login to this user every 10 minutes.  9:01am, 9:11am, 9:21am, etc.

I have checked all of the volume collections that are configured with vCenter Synchronization and they're configured with the service account as well.

[melcher8395]

Was a solution ever found? I am having a similar issue.

[minorthr127]

Same thing here IP shows as Nimble I've unregistered the plugin and registered it again with service account and its still hammering away at the AD account.

[rvvliet78110]

Could it maybe be a volume collection with VSS or vcenter credentials?

[sesol70]

Hi, also having the same issue, tried to register and unregister plugin, but the Nimble array is still sending login requests to the vcenter.

[mblumberg16]

Hi Staffan, it could be that you have a stale entry on the Nimble array, I would suggest to user the CLI with vcenter --list, the output should be all the vcenters registered with the array, you can after remove with the vcenter --remove command.

If this doesn't work, you might want to call support to check out if there are any stale hidden entries.

[sesol70]

Hi,

we have tried that and it says "no plugin found".

Will try and and call support an look for hidden entries.

Br,

Staffan

[jmp16578]

Any update on this? We are getting the exact same issue.

We are using a separate domain account for the collections and it works fine with no errors.

Just like the OP I was not the original person that set this up. I believe the account that is constantly getting locked was used to setup the plugin. However, there are no credentials listed in the vCenter Plugin settings on either nimble box.

I'm not sure if I should attempt to put the know credentials in and Unregister or if I should just Register.