This file contains entries for all of the network interfaces that are to be used as resources in the configuration. Typically, each entry associates a logical interface name, or IP alias, with a physical interface on a specified node. The IP alias always presents the same IP address, even though it is switched from node to node, and even if the underlying physical interface has different characteristics on each node.
Note
Each IP alias with its IP address must be entered in the /etc/hosts file. The IP address does not appear in the hvipalias file.
Each entry in hvipalias must contain the following fields:
<Uname> <IfName> <IfDevice> <Netmask/Prefix>
The fields are defined as follows:
Uname - Name of the machine to host the logical interface. This is usually the value returned by the 'uname -n' command.
Alternatively, you can use the Cluster Foundation (CF) node name, which is returned by the 'cftool -ql' command. This can be used to differentiate two machines which are configured with the same 'uname -n' setting, provided they were assigned different names when CF was configured.
IfName - Logical interface name, or IP alias. This name must appear with its associated IP address in the node's /etc/hosts file, and the associated IP address must be the same on every node.
IfDevice - Physical device name to be associated with the logical interface when it is switched to the specified machine.
Netmask/Prefix - The netmask (IPv4) or the prefix length (IPv6) to use with the IP address associated with the interface name.
The netmask (IPv4) must be set as the 8-digit hexadecimal number string. The prefix length (IPv6) must be set as the decimal number string between 0 and 128.
Note
To avoid network conflicts, a network hostname or address monitored by the IpAddress subapplication can be active on only one node in the cluster at any time.
When the configuration is activated, the hvipalias file in the local node is copied in all the nodes. If a file with the same name or path exists in the remote nodes, the file is overwritten with new contents. Therefore, a line in which all interfaces and their switch destination node combinations are described must be included in the file.
For instance, if the interface named dbhost can be switched between two nodes, then hvipalias on each node should contain lines for both the local and remote interfaces:
Example
Linux
#Uname IfName IfDevice Netmask shasta1 dbhost eth1 0xffffff00 shasta2 dbhost eth1 0xffffff00
Solaris
#Uname IfName IfDevice Netmask fuji2 dbhost hme0 0xffffff00 fuji3 dbhost hme0 0xffffff00
