Sun Microsystems
Products & Services
 
Support & Training
 
 

Previous Previous     Contents     Index     Next Next

ProcedureTo Configure External IP Addresses

To configure external IP addresses for a master-eligible node, the node must have an extra physical network interface or logical network interface. An extra physical network interface is an unused interface on an existing Ethernet card or a supplemental HME Ethernet card or QFE Ethernet card, for example, hme2. A logical network interface is an interface that is configured on an existing Ethernet card, for example, hme1:101.

  1. Configure an external IP address for the extra network interface based on your public network policy.

Configuring the Foundation Services on the Master-Eligible Nodes

Configure the services that are installed on the master-eligible nodes by modifying the nhfs.conf and the cluster_nodes_table files on each master-eligible node in the cluster. Master-eligible nodes have read-write access to these files. Diskless nodes or dataless nodes in the cluster have read-only access to these files.

  • nhfs.conf

    This file contains configurable parameters for each node and for the Foundation Services. This file must be configured on each node in the cluster.

  • cluster_nodes_table

    This file contains information about nodes in the cluster, such as nodeid and domainid. This file is used to elect the master node in the cluster. Therefore, this file must contain the most recent information about the nodes in the cluster.

    There is one line in the table for each peer node. When the cluster is running, the table is updated by the nhcmmd daemon on the master node. The file is copied to the vice-master node every time the file is updated. The cluster_nodes_table must be located on a local partition that is not exported. For information about the nhcmmd daemon, see the nhcmmd(1M) man page.

Configuring the nhfs.conf File

The following procedures describe how to configure the nhfs.conf file.

ProcedureTo Configure the nhfs.conf File Properties

The nhfs.conf file enables you to configure the node after you have installed the Foundation Services on the node. This file provides parameters for configuring the node, CMM, Reliable NFS, the direct link between the master-eligible nodes, the Node State Manager, the Watchdog Timer, and daemon scheduling.

  1. As superuser, copy the template /etc/opt/SUNWcgha/nhfs.conf.template file:

    # cp /etc/opt/SUNWcgha/nhfs.conf.template /etc/opt/SUNWcgha/nhfs.conf

  2. For each property that you want to change, uncomment the associated parameter, that is, delete the comment mark at the beginning of the line.

  3. 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.

ProcedureTo Create Floating Address Triplet Assigned to the Master Role

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.

  1. 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.

ProcedureTo Configure a Direct Link Between the Master-Eligible Nodes

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.

  1. 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.

  2. Configure the direct link parameters as described in the nhfs.conf(4) man page.

Creating the cluster_nodes_table File

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.

ProcedureTo Create the cluster_nodes_table File

  1. Log in to a master-eligible node as superuser.

  2. 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.

  3. 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.

  4. 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.

  5. Log in to the other master-eligible node as superuser.

  6. 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.

  7. 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.

Previous Previous     Contents     Index     Next Next