hostname and nodename in Serviceguard

[Basheer_2]

Hello

Is this TRUE

Service Guard the HA Clustering software uses both hostnames and nodenames and they have to be consistent.

Any links which confirms this.

[Jaime Bolanos Rojas.]

Basheer,

This two documents might give you and idea of what you are trying to accomplish and its limitations.

http://docs.hp.com/en/B3935-90015/B3935-90015.pdf

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1027417&admit=-682735245+1152641076153+28353475

Regards,

Jaime.

[Greg Vaidman]

hostname and nodename are mostly generic terms which are used to refer to the same thing. an HP-UX host does have an official setting for the "hostname" but none for "nodename". There are settings in the ServiceGuard configuration files which refer to "nodename", but these reference the exact same thing as the "hostname"

in other words, the statement is true, but not very useful. 8-)

[Bill Hassell · Accepted solution]

Actually, there is a (poorly documented) NODENAME variable. It is mentioned in the script /sbin/init.d/hostname and refers to the NODENAME variable. If NODENAME is undefined, then uname's value is set to HOSTNAME minus any FQDN extensions like host.company.com. But if NODEMAME is defined, then uname is assigned the value of NODENAME.

Since hostnames are Internet names, they are not limited to the 8 characters found in uname (aka, UUCP names). So for a sysadmin that wants to set a longer hostname, set NODENAME=8charsmax and HOSTNAME=longName in the /etc/rc.config.d/netconf file. Note that netconf does not have a line for NODENAME so you'll have to add that.

However, using different names can introduce a possible compatibility issue where the software uses both uname and hostname. So after all that, it's best to leave NODENAME unset and keep the assigned HOSTNAME in netconf to 8 chars. You can always have longer aliases in /etc/hosts or DNS.