HP Serviceguard manual Configuration file see Configuring Packages, Sitepreferred or

NODE_NAME	The hostname of each system that will be a node in the
	cluster.
	CAUTION: Make sure that the node name is unique within
	the subnets configured on the cluster nodes; under some
	circumstances Serviceguard may not be able to detect a
	duplicate name and unexpected problems may result.
	Do not use the full domain name. For example, enter
	ftsys9, not ftsys9.cup.hp.com. A Serviceguard cluster
	can contain up to 16 nodes (though not in all third-party
	configurations; see “Veritas Cluster Volume Manager (CVM)”
	(page 85), and the latest Release Notes for your version of
	Serviceguard).
	IMPORTANT: Node names must be 39 characters (bytes)
	or less, and are case-sensitive; for each node, the
	NODE_NAME in the cluster configuration file must exactly
	match the corresponding node_name in the package
	configuration file (see Chapter 6: “Configuring Packages
	and Their Services ” (page 227)) and these in turn must
	exactly match the hostname portion of the name specified
	in the node’s networking configuration. (Using the above
	example, ftsys9 must appear in exactly that form in the
	cluster configuration and package configuration files, and
	as ftsys9.cup.hp.com in the DNS database).
	The parameters immediately following NODE_NAME in this
	list (SITE, NETWORK_INTERFACE, HEARTBEAT_IP,
	STATIONARY_IP, CLUSTER_LOCK_LUN,
	FIRST_CLUSTER_LOCK_PV,
	SECOND_CLUSTER_LOCK_PV, CAPACITY_NAME, and
	CAPACITY_VALUE) apply specifically to the node identified
	by the preceding NODE_NAME entry.
SITE	The name of a site (defined by SITE_NAME) to which the
	node identified by the preceding NODE_NAME entry belongs.
	Can be used only in a site-aware disaster-tolerant cluster,
	which requires Metrocluster (additional HP software); see
	the documents listed under “Cross-Subnet Configurations”
	(page 30) for more information.
	If SITE is used, it must be used for each node in the cluster
	(that is, all the nodes must be associated with some defined
	site, though not necessarily the same one).
	If you are using SITEs, you can restrict the output of
	cmviewcl (1m) to a given site by means of the -S
	<sitename> option. In addition, you can configure a
	site_preferred or
	site_preferred_manualfailover_policy (page 237)
	for a package.
NETWORK_INTERFACE	The name of each LAN that will be used for heartbeats or
	for user data on the node identified by the preceding
	NODE_NAME. An example is lan0. See also
	HEARTBEAT_IP, STATIONARY_IP, and “About Hostname

Cluster Configuration Planning 113