How to Configure and Activate Network Resources for a Failover Configuration

If you configure Sun Java System Application Server as a failover service, you must set up the network resources before you install and configure the Sun Java System Application Server. The failover service uses these network resources after installation and configuration in order to run in a cluster.

To perform this procedure, you need the following information about your configuration.

• The names of the cluster nodes that can master the data service.

• The hostnames that are used for configuring the network resource that clients use to access the Sun Java System Application Server. Normally, you set up this hostname when you install the cluster. See the Sun Cluster Concepts Guide for Solaris OS for details on network resources.

Perform this procedure on any cluster member.

Steps

1. Become superuser on a cluster member.

2. Verify that all of the network addresses that you use have been added to your name service database.

   You should have performed this verification during the Sun Cluster installation. See the planning chapter in the Sun Cluster Software Installation Guide for Solaris OS.

   ---

   Note –

   To avoid name service look-up failures, ensure that all of the logical hostnames are present in the /etc/inet/hosts file on all of the cluster nodes. Configure name service mapping in the /etc/nsswitch.conf file on the servers to check the local files before trying to access NIS, NIS+, or DNS.

   ---

3. Create a failover resource group to contain the network and application resources.

   # scrgadm -a -g resource-group [-h nodelist]

   -g resource-group

   Specifies the name of the resource group. This name can be your choice.

   [-h nodelist]

   Specifies an optional comma-separated list of physical node names that identify potential masters. The order here determines the order in which the nodes are considered primary during failover.

   ---

   Note –

   Use the -h option to specify the order of the node list. If all of the nodes in the cluster are potential masters, you do not need to use the -h option.

   ---

4. Add network resources to the resource group.

   Use the following command to add a logical hostname to a resource group.

   # scrgadm -a -L -g resource-group -l hostname, …[-n netiflist]

   -L

   Specifies that a network resource is being added.

   -g resource-group

   Specifies the name of the resource group.

   -l hostname, …

   Specifies a comma-separated list of network resources.

   -n netiflist

   Specifies an optional, comma-separated list that identifies the IP Networking Multipathing groups that are on each node.

   ---

   Note –

   Each element in netiflist must be in the form of netif@node, where netif can be given as an IP Networking Multipathing group name, such as sc_ipmp0. The node can be identified by the node name or node ID, such as sc_ipmp0@1 or sc_ipmp@phys-schost-1. Sun Cluster does not currently support the use of the adapter name for netif.

   ---

5. Bring the resource group online.

   # scswitch -Z -g resource-group

   -Z

   Moves the resource group to the MANAGED state, and brings the resource group online

   -g resource-group

   Specifies the name of the resource group