![]() |
|||
![]() |
![]() ![]() |
![]() |
![]() ![]() |
![]() |
![]() ![]() |
![]() |
| ||
|
# cp /etc/opt/SUNWcgha/nhfs.conf.template /etc/opt/SUNWcgha/nhfs.conf |
For each property that you want to change, uncomment the associated parameter, that is, delete the comment mark at the beginning of the line.
Modify the value of each parameter that you want to change.
For descriptions of each parameter, see the nhfs.conf(4) man page.
If you have not installed the CGTP patches and packages, do the following:
Disable the Node.NIC1 and Node.NICCGTP parameters.
To disable these parameters, add a comment mark (#) at the beginning of the line containing the parameter if this mark is not already present.
Configure the Node.UseCGTP and the Node.NIC0 parameters:
Node.UseCGTP=False
Node.NIC0=interface-name
where interface-name is the name of the NIC0 interface, for example, hme0, qfe0, or eri0.
The floating address triplet is a triplet of three logical addresses active on the node holding the master role. When the cluster is started, the floating address triplet is activated on the master node. In the event of a switchover or a failover, these addresses are activated on the new master node. Simultaneously, the floating address triplet is deactivated automatically on the old master node, that is, the new vice-master node.
To create the floating address triplet, you must define the master ID in the nhfs.conf file.
The floating address triplet is calculated from the master ID, the netmask, and the network interface addresses.
For more information about the floating address triplet of the master node, see "Cluster Addressing and Networking" in Netra High Availability Suite Foundation Services 2.1 6/03 Overview.
You can configure a direct link between the master-eligible nodes to prevent a split brain cluster. A split brain cluster is a cluster that has two master nodes because the network between the master node and the vice-master node has failed.
Connect the serial ports of the master-eligible nodes.
For an illustration of the connection between the master-eligible nodes, see the Netra High Availability Suite Foundation Services 2.1 6/03 Hardware Guide.
Configure the direct link parameters as described in the nhfs.conf(4) man page.
The cluster_nodes_table file contains the configuration data for each node in the cluster. Create this file on each master-eligible node. Once the cluster is running, this file is accessed by all nodes in the cluster. Therefore, the cluster_nodes_table on both master-eligible nodes must be exactly the same.
Log in to a master-eligible node as superuser.
Copy the template file from /etc/opt/SUNWcgha/cluster_nodes_table.template to /etc/opt/SUNWcgha/cluster_nodes_table.
You can save the cluster_nodes_table file in a directory other than the /etc/opt/SUNWcgha directory. By default, the cluster_nodes_table file is located in the /etc/opt/SUNWcgha directory.
Edit the cluster_nodes_table file to add a line for each node in the cluster.
For more information, see the cluster_nodes_table(4) man page.
Edit the nhfs.conf file to specify the directory that contains the cluster_nodes_table file:
CMM.LocalConfig.Dir=/etc/opt/SUNWcgha |
For more information, see the nhfs.conf(4) man page.
Log in to the other master-eligible node as superuser.
Copy the /etc/opt/SUNWcgha/cluster_nodes_table file from the first master-eligible node to the same directory on the second master-eligible node.
If you saved the cluster_nodes_table file in a directory other than /etc/opt/SUNWcgha, copy the file to that other directory on the second master-eligible node. The cluster_nodes_table file must be available in the same directory on both master-eligible nodes.
Repeat Step 4 on the second master-eligible node.
When there is a change in the attribute of a node, the cluster_nodes_table file is updated by the nhcmmd daemon on each master-eligible node. If a switchover or failover occurs, the diskless nodes or dataless nodes in the cluster access the cluster_nodes_table file on the new master node. Only master-eligible nodes can write information to the cluster_nodes_table file.
![]() ![]() |