Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

R

rogers78

30 Posts

2129

October 19th, 2017 03:00

SAE 1.1 and VMware ESXi Servers issues

-Clean install of OME 2.3 on Windows Server 2016.
-OMSA Agent installed on VMware ESXi 6.0 Servers
-OME configured to Discover both the iDRAC and ESXi Server
-SAE 1.1 installed
-Account Credentials and Credential Profile created
-OME adapter added to SAE.

For ESXi servers discovered in OME using iDRAC only, status in SAE is OK

For ESXi servers discovered in OME using iDRAC and ESXi/OMSA, status is either:

Unable to add device: 

SupportAssist Enterprise is unable to add the device vitesxd399.vismait.no because a required file has either been deleted or moved.

Error Code : SA-0060

or:

Credentials not correct: 

SupportAssist Enterprise is unable to connect to the device by using the provided credentials. To update the device credentials, select the device and click Edit Credentials.

Error Code : SA-20060

It seems to me like SAE is trying to authenticate to the iDRAC using the ESXi credentials

dave_lal

4 Operator

 • 

39 Posts

October 20th, 2017 09:00

Hello Rogers78,

Can you share with us on how the devices that are throwing the exception categorized as in SAE UI?  Are they showing up as iDRAC or some other value?

Thank You.

rogers78

30 Posts

October 22nd, 2017 01:00

Hi Dave,

The device is categorized as iDRAC in the SAE UI. But I think I see the root cause of this problem now. As I said I have OMSA agents installed on most of my servers. It's only the servers with OMSA installed that are throwing exceptions in SAE.

If I go back to OME: First I have forward and reverse DNS configured for both iDRAC and ESXi managment. And OME Discovery is set to use DNS resolution. If I compare a server with OMSA and one without in OME, there is a clear difference in the RAC name column.

For a server without OMSA, discovered only using iDRAC, the RAC name is the FQDN of the iDRAC. This server is working fine in SAE.

For a server with OMSA, discovered using both iDRAC and ESXi, the RAC name is not a FQDN, simply "idrac- ".

I'm guessing SAE tries to use this RAC value. Since it's not an IP or an FQDN, it then tries the ESXi FQDN, which will of course not work since it's not an iDRAC address..

So, if I could only get OME to display the FQDN of the iDRAC in the RAC name column, I think this would solve the problem.

Was this post helpful?

View All

No Events found!

Top