1 Rookie
•
3 Posts
0
21
September 12th, 2025 08:07
OME devices names as human readable
What are people using to be able to refer to human readable device names?
OME Version 4.3.2
I've tried everything and there really seems to be no way to set the device name during discovery for device records or change it once the device is discovered. Including using CSV files for import.
Also, nothing in the GUI to do it manually.
API endpoints don't support renaming (despite what some of the AI's say). I can see the DeviceService/Devices/{device_id} and the DeviceName field and I've tried to set it and it fails. Anyone have an example of it working?
Device discovery DNS options that are mentioned on the net don't exist.
Discovery by hostname is not working unless you use a FQDN despite having set the domain name in both the gui and the tui console.
If you do discover with a FQDN, it still populates the device and uses the IP address as the device name.
There also doesn't seem to be a way to select the columns in the UI. The device record does have the FQDN (when you click on the device) but you can't use it as a column in the UI.
Basically, I can't get a device name as anything other than an IP address.
Any ideas?
DELL-Chris H
Moderator
•
9.5K Posts
0
September 12th, 2025 12:16
Peter Kerney,
You’re encountering a situation where devices discovered in OME 4.3.2 are named by IP address, and attempts to override this behavior—via CSV import, GUI, or API—have failed. This is a known limitation in OME 4.3.x, and unfortunately, there is no supported method to manually rename devices or force hostname usage during or after discovery. The reason is that OME uses WSMan for discovery and typically resolves device names via reverse DNS lookup, and if reverse DNS fails or is incomplete, the device name defaults to the IP address.
What you can try is the following:
Reverse DNS Configuration
Ensure that:
Each device has a valid PTR record in DNS.
The OME appliance can resolve hostnames via ping -a <IP>.
DNS suffix is correctly set in the OME console and TUI.
iDRAC Customization
On the iDRAC:
Navigate to System Settings > User Interface.
Set Title Bar Information to use the hostname instead of IP
Discovery Settings
In OME:
Go to Application Settings > Console Preferences > Discovery Settings.
Set Name Resolution to NetBIOS or DNS, depending on your environment
Let me know if this helps.
Peter Kerney
1 Rookie
•
3 Posts
0
September 12th, 2025 22:35
Thanks for the response, Chris.
Both forward and reverse DNS lookup's work from other hosts. You can't login to the OME console to check from OME, but the discovery job can show in the status if you're watching it when you use FQDN. It's like the OME discovery ignores the domain name setting or the internal resolver is not searching the domain properly. So there still seems to be something wrong there. Ping definitely works from other hosts by IP or name.
The other issue is that the name of the iDRAC is NOT the name of the host. The name of the host is something different and it also has a different IP. So, the IP of the iDRAC, which is on a management subnet, does not necessarily have any relationship to the actual host IP or host name. We've created DNS records for "host.domain" and "host-idrac.domain" which are completely different IP's. The admin wants to manage the "host" machine, not the iDRAC so the device name should be "host" and the device record should have a pointer to the iDRAC IP.
We've had to "set idrac.webserver.HostHeaderCheck 0" in the iDRAC to allow managing by name different to the name of the iDRAC which is "idrac-servicetag". Are you saying that if I had a DNS record for "idrac-servicetag" that something different would happen? Would setting the iDRAC name to "host-idrac" do something different?
It seems like a big miss that you can't rename the devices either manually or through batch/API. This would make OME so much more usable. We have a large network with multiple subnets and hosts including clusters and finding the right host using IP is very tedious.
Just some feedback on the product.
(edited)
Peter Kerney
1 Rookie
•
3 Posts
0
September 14th, 2025 06:03
@DELL-Chris H - Your recommendation of
Discovery Settings
In OME:
Go to Application Settings > Console Preferences > Discovery Settings.
Set Name Resolution to NetBIOS or DNS, depending on your environment
Did produce a much better result and did not require a full device re-discovery either.
Unfortunately, it displays the FQDN (which I guess is probably required if you have multiple domains), which is not required in our environment but this is significantly better than an IP.
Thanks for the response.
I still have difficulty discovering by "hostname" rather than "hostname.domainname", but that's for another day.
(edited)