OMSA Configuration failed: Could not contact the given vCenter server due to wrong credentials.

Hi Niesbeest,

My apologies in advance for all the questions.  I’d like to get a better understanding on how you are adding the hosts.  You mentioned that the connection profiles are working.  Were you able to add all of the hosts to a connection profile and have test connection work?  Was an inventory able to complete successfully for the hosts?  Did you see this error when running inventory or when running host compliance?   What versions of the appliance, Dell Servers, vCenter, esxi and OMSA are involved?

I’ve used the integration with multiple datacenters and clusters and am not aware of any field issues.  With some additional info maybe we can narrow down the problem some.

Thanks,

Michael H.

Hi Michael,

Per ESXi host we use a different host profile, the connection test(s) are working, both credentials Pass.

A inventory is run for this esxi host without error, the error appears when trying to run the host compliance option.

Appliance version: 2.0.0.1262 (got the update link from this forum) Dell Servers: R710 - BIOS version 6.3.0 - iDRAC6 1.95.00 (Build 5) Hypervisor: VMware ESXi 5.1.0 Update 1 Patch 16 (build-1157734) Kernel 5.1.0 (x86_64)

VMware vCenter Server Version 5.1.0 Build 1364037 Vsphere Client Version 5.1.0 Build 1364039 ESXi: Vmware ESXi 5.1.0 1312873 OMSA: Openmange 7.3.0.2 for ESXi510

Please double check the credentials you entered in the connection profiles. 

I’m guessing on this, but one thing that does come to mind is a bug in the test connection profile where the host credentials can give a false success due to some code implemented to work around host authentication in lockdown mode. The host doesn’t need be in lockdown mode to give the false positive, and hopefully we can get this bug addressed so the test connection profile can be a definitive answer or more information.

When inventory runs and you have invalid host credentials in a connection profile, I have seen it still succeed due to the authentication in lockdown mode workaround mentioned above, but should have and written the same error message you reported for compliance in the log… “Could not contact the given vCenter server due to wrong credentials. Check the username and password.”'

Could go into the Job Queue and kick off an inventory? Give it some time after kicking it off, and then click on the Log tab in the management center and let me know if you see the credentials message? When I saw this before the inventory did eventually succeed even though I had changed the credentials to invalid ones (using esxi 5.x), but the same message you mention was in the Log. 

Also, the configuring host compliance being write action perhaps, may be handling the fallback authentication for lockdown mode differently and failing right away with invalid credentials, and that might explain why everything else is working except for configuring host compliance. 

Other than that I’m kind of stumped, and we may need to have you call into support to dig into the troubleshooting logs.

Hello Michael,

Thank you for pointing out the possible issue with the credentials going to check this because I think this is the issue here.

Just wondering what the phone number is for support in the EU?

 You can start at support.euro.dell.com to get the phone number.  You will need to select the country at the top left, then enter details for your PowerEdge server with ProSupport.  Once you get to the call director the help you need is in the advanced virtualization queue.

I don't have the support number, and it varies by country and product.   If you go to the support.dell.com website (make sure you are on the correct language) and input details for a server with pro support, the site should give you a number to call.

If you try the website and still have dificulty getting a support number, reply back and I'll get someone from the support team to reach out to you somehow.

Hello Niesbeest,

Here you can find the Dell Support Phone numbers by Region and Entitlement.

http://www.dell.com/content/topics/global.aspx/services/prosupport/regional_contacts

Hope it helps.

Regards,

Gustavo