Unsolved
This post is more than 5 years old
2 Intern
•
743 Posts
0
31693
October 30th, 2012 16:00
Server Hostname incorrect
Hi,
When viewing from an M1000e chassis the following:
Server Overview/Setup/Slot Names
.......we find that sometimes the host name is OMSALIVE, even though the server may have an O/S on it (Windows or Linux).
The box marked "Use HostName for the Slot" is ticked.
How do we get rid of the OMSALIVE name being used for the HostName??
thx,
John Bradshaw
(PS 99% of the blades show the correct HostName, just the occasional one has OMSALIVE).
No Events found!


Daniel My
12 Elder
•
6.2K Posts
0
October 30th, 2012 16:00
Hello John
Most likely Openmanage was used at some point to boot to on the server. The hostname was updated to the slot name and it hasn't updated since. Check to see if it thinks the hostname is OMSALIVE or if it is not correctly using the hostname. Run racadm getslotname to find out what the CMC is detecting.
<ADMIN NOTE: Broken link has been removed from this post by Dell>
If the CMC is detecting the hostname correctly then try unchecking and rechecking the use hostname for the slot option. If it is not detected correctly then try restarting the server. If that does not resolve the issue then let me know the results.
Thanks
bradje1
2 Intern
•
743 Posts
0
October 30th, 2012 17:00
Hey Daniel,
Thx very much.
The following are returned even though one of the hosts is off and the other is definitely running a live Linux O/S (Redhat) with a very diferent host name.
But let's just focus on the running, Linux box, if that's OK.
9 omsalive omsalive
1 omsalive omsalive
I have tried unticking the Use Hostname box , applying that, then ticking and applying again, but it comes back to the same as above. For this Linux box it will not pick up the actual Hostmane.
I do not understand still how it could get the OMSALIVE hostname at all. Would you kindly explain that again?
Unfortunately, restarting the Linux server is a big deal and i won't be able to do that for quite a while.
Cheers,
John Bradshaw
bradje1
2 Intern
•
743 Posts
0
October 30th, 2012 18:00
Thx very much daniel.
It will take me a while to get to the groups involved with this where I am, but the advice is very helpful.
JB
Daniel My
12 Elder
•
6.2K Posts
0
October 30th, 2012 18:00
It is reported by OMSA. If you booted the server to any of our utility discs I believe the default hostname is OMSA live. That is likely how that host name got there. The SMTD, SBUU, OMSALive, and any other OMSA based CD/DVDs would probably have that host name. If you booted to one of those and then exited without a full server restart and allowed it to boot to the current OS then the host name may not have updated. That is my guess as to what happened.
Check inside OMSA on the server. If the host name is reported correctly from OMSA within the server then a restart would likely resolve. I'm pretty sure that the host name is only updated once on boot and is not actively updated. I would have to check with someone in escalations to be sure on that though.
If OMSA is not reporting the host name correctly then I would suggest uninstalling/reinstalling OMSA and making sure you have a compatible version installed.
The other possibility I can think of is a communication issue with OMSA. Having an old BIOS version and a new OMSA version or vice versa may cause the host name to not report correctly.
If none of those ideas help you out then let me know and I'll ask our escalation group for ideas tomorrow.
Thanks