Unsolved
This post is more than 5 years old
30 Posts
0
4417
June 6th, 2016 05:00
OME and iDRAC Service Module, issues with Device Name
For my Gen 13 PowerEdge servers, I want to move away from installing OMSA agent, and doing OME discovery on both iDRAC and OMSA.
I understand that by installing the iDRAC Service Module 2.3 for ESXi or Windows, and running discovery on only the iDRAC, I should get more or less the same functionality as I had with OMSA.
However, after removing OMSA, installing iSM, rebooting, removing the device from OME, removing the discovery of OMSA, and re-running discovery and inventory on the iDRAC IP, the device is indeed added back into OMSA, but the Device Name is that of the iDRAC, and not the actual hostname of the server.
When i log on to the iDRAC I can see that it displays the actual hostname under System Host Name.
So my question is then, why doesn't OME pickup the correct hostname and rather displays the iDRAC name?
OME 2.1.2635
rogers78
30 Posts
0
June 6th, 2016 05:00
Thanks for the quick reply, but I'm still a bit confused.
One of the purposes of the iSM is to get the OS hostname to the iDRAC, right? And this is working. When I log into the iDRAC, it displays the OS hostame in System Host Name.
My problem is, why doesn't OME use this value?
Who wants to have the iDRAC names in OME and not the actual OS host name?
DELL-Martijn G
291 Posts
0
June 6th, 2016 05:00
The reason for this is because OME does the aggregation of the inventoried iDRAC and OS. When both are inventoried it aggregate the data of both and uses the sytem hostname to list it in OME.
When only the iDRAC is inventoried it will use the FQDN if it exist and otherwise just the iDRAC hostname.
DELL-Martijn G
291 Posts
0
June 6th, 2016 06:00
Yes you are correct, iSM will get the hostname inside the iDRAC but this will just be inventory data that resides in the iDRAC.
The actual iDRAC name will stay the same as it was because from a network view the iDRAC and OS are two completely different entities with different IP addresses.
OME will aggregate the iDRAC name with the Hostname because it was programmed to do so if an inventory for an iDRAC as well as an OS is present. So this is something that OME does internally and not something it directly gets from the OS or iDRAC.
I hope it is a bit more clear now?
To summarize OME will try to name an iDRAC in this order if present.
DELL-Martijn G
291 Posts
0
June 6th, 2016 06:00
The first one will only happen when OME it self inventories the iDRAC and the OS.
You can still inventory the OS without OMSA.
rogers78
30 Posts
1
June 6th, 2016 06:00
I tried you suggestion and it works, the device name in OME is now the OS hostname.
But I guess I then in the future still have to make sure to install/configure SNMP on Windows servers and WSMAN for ESXi etc...
Might as well stick with OMSA as well I guess.
I was hoping to go out-of-band only. Oh well, I hope a future version of OME honors any OS host name picked up from iSM.
Thanks for you help Martijn!
rogers78
30 Posts
0
June 6th, 2016 06:00
It's getting clearer :-) But I still struggle to see why OME showed the correct hostname when OMSA was installed, but not with iSM.
As you say:
"OME will try to name an iDRAC in this order if present.
And I would argue that server OS is indeed inventoried because I have the iSM, don't you agree?
If this indeed is by design I'm very surprised and I would probably go back to OMSA, which has other issues, but that's another post.
DELL-Rob C
3 Apprentice
•
2.8K Posts
0
June 6th, 2016 07:00
Martijn is spot on.
One other bit of info that might be useful. You might also try an experiment on a box that does not have iSM and try to discover out-of-band WSMan plus in-band WMI (without an agent). We should correlate IB/OOB and prefer the IB name.
Regards,
Rob