G.2 Associating Resources to a Cluster Service Instance

PRIMECLUSTER Installation and Administration Guide 4.1 (for Solaris(TM) Operating System)

Appendix G Registering SynfinityCluster-compatible Resources

G.2 Associating Resources to a Cluster Service Instance

The SynfinityCluster-compatible cluster service instance needs to be associated with the following product:

Interstage Traffic Director

For products other than the above, the procedure for associating the product to a cluster service instance is unnecessary.

The procedure for associating the above product with a SynfinityCluster-compatible cluster service instance is described below.

Operation Procedure:

Log in with the system administrator authority.
Log in with the system administrator authority to one of the nodes of the cluster system.

Perform Step 2 only if userApplication was set up with the CUI and IP address takeover was set during userApplication setup. If userApplication was set up with the GUI or if IP address takeover was not set during userApplication setup, Step 2 is unnecessary.

Execute the "clgettree(1)" command in the format shown below, and check the resource IDs of the PublicLAN resources in all nodes that execute IP address takeover. The resource class of PublicLAN resources is "Ethernet."

# /etc/opt/FJSVcluster/bin/clgettree

Example) In the following case, the resource ID of the PublicLAN resource in the narcissus node is "25" and the resource ID of the PublicLAN resource in the sweetpea node is "26."

# /etc/opt/FJSVcluster/bin/clgettree

Cluster 1 /

           Domain 2 RC9

           Shared 7 SHD_RC9

           Node 3 narcissus ON

                    Psd 21 hme1 ON

                    Psd 22 hme2 ON

                    Ethernet 25 hme0 ON

                    DISK 19 c0t0d0 UNKNOWN

                    SytemState2 40 FJSVndbs UNKNOWN

           Node 5 sweetpea ON

                    Psd 23 hme1 ON

                    Psd 24 hme2 ON

                    Ethernet 26 hme0 ON

                    DISK 20 c0t0d0 UNKNOWN

                    SytemState2 41 FJSVndbs UNKNOWN

Execute the "clcreate-iprsc(1M)" command in the format shown below, and register the IP address takeover resources.
```
# /etc/opt/FJSVcluster/sys/clcreate-iprsc -p resource-ID-of-PublicLAN-resource...(*1) takeover-IP-address(*2)
```
*1For "resource-ID-of-PublicLAN-resource...," specify the resource IDs of the PublicLAN resources of all nodes that were confirmed with the previous "clgettree(1)" command.

*2For "takeover-IP-address," specify the takeover IP address that was specified during userApplication setup.

Example) If the resource IDs of the PublicLAN resources are "25," "26" and the takeover IP address is "192.168.246.1"
```
# /etc/opt/FJSVcluster/sys/clcreate-iprsc -p 25,26 192.168.246.1
```

Associate the resources to cluster service instances.
Associate the following resources to cluster service instances:
- IP address takeover resources (*1)
*1If IP address takeover resources were registered in Step 2, associated them to cluster service instances.
- "Interstage Traffic Director" resources
1. Execute the clgettree(1) command in the format shown below, and check the resource IDs of the resources to be associated to cluster service instances. The resource class of IP address takeover resources is "IP_Address." The resource name of the Interstage Traffic Director resource is "FJSVndbs."
```
# /etc/opt/FJSVcluster/bin/clgettree
```
  Example) For the "clgettree(1) command execution example" described below, the resource IDs for the IP address takeover and Interstage Traffic Director resources are as follows:
  
  Node
  
  Resource ID of IP address takeover resource
  
  Resource ID of Interstage Traffic Director resource
  
  narcissus
  
  27
  
  40
  
  sweetpea
  
  28
  
  41
  
  [Execution example of clgettree(1) command]
```
# /etc/opt/FJSVcluster/bin/clgettree
```
```
Cluster 1 /
```
```
             Domain 2 RC9
```
```
             Shared 7 SHD_RC9
```
```
                      SHD_Host 29 192.168.246.1 UNKNOWN
```
```
                              IP_Address 27 hme0:1 UNKNOWN narcissus
```
```
                              IP_Address 28 hme0:1 UNKNOWN sweetpea
```
```
             Node 3 narcissus ON
```
```
                      Psd 21 hme1 ON
```
```
                      Psd 22 hme2 ON
```
```
                      Ethernet 25 hme0 ON
```
```
                              IP_Address 27 hme0:1 UNKNOWN
```
```
                      DISK 19 c0t0d0 UNKNOWN
```
```
                      SytemState2 40 FJSVndbs UNKNOWN
```
```
             Node 5 sweetpea ON
```
```
                      Psd 23 hme1 ON
```
```
                      Psd 24 hme2 ON
```
```
                      Ethernet 26 hme0 ON
```
```
                              IP_Address 28 hme0:1 UNKNOWN
```
```
                      DISK 20 c0t0d0 UNKNOWN
```
```
                      SytemState2 41 FJSVndbs UNKNOWN
```
2. Using the format shown below, execute the "clrepparent(1M)" command for each node in the userApplication configuration, and associate the IP address takeover and Interstage Traffic Director resource to cluster service instances.
  # /etc/opt/FJSVcluster/sys/clrepparent -s resource-IDs-of-IP-address-takeover-and-Interstage-Traffic Director-resources(*1) -t resource-ID-of-cluster-service-instance(*2)
*1Specify the resource IDs of the IP address takeover and Interstage Traffic Director resources that were obtained with the clgettree(1) command in each node.
*2
If userApplication was set up with the CUI

Specify the resource ID of the cluster service instance that was registered in each node according to Step 5 "Register the cluster service instance" in "Registering a Cluster Service."

If userApplication was set up with the GUI
Execute the "clgettree(1)" command in the format shown below, and check the resource ID of the cluster service instance in each node. The resource class for cluster service instances is "AndBinding." The node name to which the cluster service instance belongs is displayed at the end of the line for the "AndBinding" resource class.
```
  # /etc/opt/FJSVcluster/bin/clgettree -s
```
In the following example, the resource ID of the cluster service instance in the narcissus node is "101," and the resource ID of the cluster service instance in the sweetpea node is "102."
```
  # /etc/opt/FJSVcluster/bin/clgettree -s
```
```
  Standby 68 Service1 STOP AVAILABLE
```
```
     AndBinding 101 Instance1_Of _narcissus STOP STOP(RUN) narcissus
```
```
     AndBinding 102 Instance1_Of _sweetpea STOP STOP(RUN) sweetpea
```
Example) When the resource ID of the cluster service instance in the narcissus node is "101" and the resource ID of the cluster service instance in the sweetpea node is "102" and the following resources are registered in each node:
Node

Resource ID of IP address takeover resource

Resource ID of Interstage Traffic Director resource

narcissus

27

40

sweetpea

28

41
```
# /etc/opt/FJSVcluster/sys/clrepparent -s 27,40 -t 101
```
```
# /etc/opt/FJSVcluster/sys/clrepparent -s 28,41 -t 102
```

Contents Index

Node	Resource ID of IP address takeover resource	Resource ID of Interstage Traffic Director resource
narcissus	27	40
sweetpea	28	41