topic RILOE II & Server Name in Server Management - Remote Server Management

RILOE II & Server Name

TStinnett — Tue, 03 Feb 2004 18:10:35 GMT

RILOE displays a server name that is different than what is in "Computer Name". I don't see anywhere in RILOE configuration to change this. Do I need to reset the RILOE? Is the server name RILOE reports somewhere in the ROM configuration on the server?

Re: RILOE II & Server Name

David Claypool — Wed, 04 Feb 2004 09:55:45 GMT

RILOE/iLO get the name of the host from the drivers in the host OS. Once set, if the host name subsequently changes and the drivers aren't running, RILOE isn't communicated the change.

Make sure you have the most recent ProLiant Support Pack loaded and running on your system.

Re: RILOE II & Server Name

TStinnett — Wed, 04 Feb 2004 10:17:46 GMT

What about uninstalling and re-installing the driver with the SmartStart CD?

Re: RILOE II & Server Name

barnett chan — Wed, 04 Feb 2004 11:20:30 GMT

Make sure the management agents are loaded, too.

Re: RILOE II & Server Name

Daniel Thrun — Mon, 29 Mar 2004 03:51:43 GMT

Greetings. Our same problem as you have was fixed by running the Management Agents install again. Once done the issues went away.. Here is the link for Windows 2000/2003

http://h18007.www1.hp.com/support/files/server/us/download/18538.html

Re: RILOE II & Server Name

N Vivegananthan — Thu, 22 Apr 2004 01:36:35 GMT

Have tested and confirmed that the HP Insight Management Agents for Windows 2000/Server 2003 re-installation does solve this issue but the server requires a reboot after installation to take effect

Re: RILOE II & Server Name

Energen Unix Admin — Mon, 26 Apr 2004 15:45:30 GMT

Is this procedure diffent for non-Windows installations? I am using Red Hat Enterprise Linux 3, and re-installing the ProLiant Support Pack does not change the name of the server as reported from the iLO web interface.

--Karl

Re: RILOE II & Server Name

Energen Unix Admin — Fri, 14 May 2004 16:07:29 GMT

Removing and re-installing the hprsm corrected my problem on Red Hat Enterprise Linux 3. Apparently, hprsm isn't installed in the correct order in Proliant Support Pack 7.0 for RHEL3, so not all of the hprsm is functional without first removing it and re-installing.