Unsolved

969

March 2nd, 2020 09:00

SAE - Manage Devices from OME

Hi,

I am seeing an issue (idrac connection failed in SAE) for the Windows servers idrac connection from SAE. SAE integrated to OME and found the device details are taken from OME. During the process the windows servers in OME uses hostname in the OME --> All Devices --> Name column instead of idrac IP address and hence SAE uses hostname instead of IP address to connect the device.

On the Linux servers, we see Idrac IP address in the OME --> All deviecs --> due issue with the idrac service module package.

Just wondering if any come across this issue?

Thank you

Regards,Moorthi

Moderator

 • 

790 Posts

March 6th, 2020 06:00

Hi Moorthi,

which version of SAE are you running, Windows or Linux?

For me, it sounds like Linux, but this one is not able to discover Windows devices, only Linux and iDRAC.

Regards,
Stefan

March 6th, 2020 08:00

Hi Stefan,

I am using SupportAssist version: 4.00.05.30 as VMware appliance.

Windows iDRAC cannot discover due to hostname (as OS hostname  instead of iDRAC IP address) in the OME.

Regards,

Moorthi

 
 
 

 

2 Posts

July 27th, 2020 08:00

Same issue here.  Upgraded OM Essentials to OM Enterprise and pulled the devices over just fine.  When I installed SupportAssist Enterprise and connected to OMEnt, everythhing shows up, but cannot validate.  I noticed the same issue where is appears it is using the Host name and not the iDrac address.

Anyone figure out how to make it work yet?

No Events found!

Top