This procedure describes how to use the scrgadm command to register and configure Sun Cluster HA for Sun ONE Directory Server.
Other options also enable you to register and configure the data service. See “Tools for Data Service Resource Administration” in Sun Cluster 3.1 Data Service Planning and Administration Guide for details about these options.
To perform this procedure, you need the following information about your configuration.
The name of the resource type for Sun Cluster HA for Sun ONE Directory Server. This name is SUNW.nsldap.
The names of the cluster nodes that can master the data service.
The network resource that clients use to access Sun Cluster HA for Sun ONE Directory Server. Normally, you set up this network resource when you install the cluster. See the Sun Cluster 3.1 Concepts Guide document for details on network resources.
The path to the Sun ONE Directory Server application binaries that are the resources for Sun Cluster HA for Sun ONE Directory Server. You can install the binaries on the local disks or the cluster file system. See “Planning for Sun Cluster Data Services” in Sun Cluster 3.1 Data Service Planning and Administration Guide for a discussion of the advantages and disadvantages of each location.
The port where Sun ONE Directory Server listens. For non-secure instances, the Port_list standard resource property for the Sun ONE Directory Server resource defaults to 389/tcp, and the value for the secure port is 636/tcp. If you set the port to a number other than 389, you must specify that value when you configure the Port_list property. See “Administering Data Service Resources” in Sun Cluster 3.1 Data Service Planning and Administration Guide for instructions on how to set resource properties.
Perform this procedure on any cluster member.
The fault monitor determines whether the Sun Cluster HA for Sun ONE Directory Server instance is secure or non-secure. The monitor probes secure and non-secure directory servers differently. If you have created a password file, the instance is determined to be secure. If you have not created a password file, the instance is determined to be non-secure. The password file is named keypass and is in a different format than iPlanet's password file. The keypass file contains only the password for which a secure instance of directory server prompts when started manually. This password file is located in the same directory as the start-slapd program that is used to start this instance of the directory server.
If Sun ONE Directory Server is in secure mode, then the path name must also contain a file named keypass, which contains the secure key password that is needed to start this instance. If a keypass file exists, then Sun Cluster HA for Sun ONE Directory Server assumes that the keypass instance is secure.
Perform the following steps to complete your configuration.
Become superuser on a cluster member.
Register the resource type for the data service.
# scrgadm -a -t SUNW.nsldap |
Adds the data service resource type.
Specifies the predefined resource type name.
Add the Sun ONE Directory Server application resource to the failover resource group that you created for your network resources.
The resource group that contains the application resources is the same resource group that you created for your network resources in How to Configure and Activate Network Resources.
# scrgadm -a -j resource -g resource-group \ -t SUNW.nsldap [-y Network_resources_used=network-resource, …] \ -y Port_list=port-number/protocol -x Confdir_list=pathname |
Specifies the Sun ONE Directory Server application resource name.
Specifies a comma-separated list of network resources (logical hostnames or shared addresses) in resource-group, which the Sun ONE Directory Server application resource must use.
Specifies the type of resource to add.
Specifies a port number and the protocol to be used, for example, 389/tcp. The Port_list property must have one or two entries.
Specifies a path for your Sun ONE Directory Server configuration directory. The Confdir_list extension property is required. The Confdir_list property must have exactly one entry.
Enable the resource and its monitor.
# scswitch -e -j resource |
Enables the resource and its monitor.
Specifies the name of the application resource that is being enabled.
This example shows how to register Sun Cluster HA for Sun ONE Directory Server.
Cluster Information Node names: phys-schost-1, phys-schost-2 Logical hostname: schost-1 Resource group: resource-group-1 (for all resources) Resources: schost-1 (logical hostname), nsldap-1 (Sun ONE Directory Server application resource) (Create a failover resource group.) # scrgadm -a -g resource-group-1 -h phys-schost-1,phys-schost-2 (Add a logical hostname resource to the resource group.) # scrgadm -a -L -g resource-group-1 -l schost-1 (Bring the resource group online.) # scswitch -Z -g resource-group-1 (Install and configure Sun ONE Directory Server.) (To install and configure the iPlanet Directory Server, run the “setup” program from the node that is currently hosting the logical hostname.” (Stop the Sun ONE Directory Server server.) (Register the SUNW.nsldap resource type.) # scrgadm -a -t SUNW.nsldap (Create an Sun ONE Directory Server resource and add it to the resource group.) # scrgadm -a -j nsldap-1 -g resource-group-1 \ -t SUNW.nsldap -y Network_resources_used=schost-1 \ -y Port_list=389/tcp \ -x Confdir_list=/global/nsldap/slapd-schost-1 (Enable the application resources.) # scswitch -e -j nsldap-1 |
The SUNW.HAStoragePlus resource type was introduced in Sun Cluster 3.0 5/02. This new resource type performs the same functions as SUNW.HAStorage, and synchronizes actions between HA storage and the data service.
SUNW.HAStoragePlus also has an additional feature to make a local file system highly available. Sun Cluster HA for Sun ONE Directory Server is not disk-intensive and not scalable, and therefore setting up the SUNW.HAStoragePlus resource type is optional.
See the SUNW.HAStoragePlus(5) man page and “Relationship Between Resource Groups and Disk Device Groups” in Sun Cluster 3.1 Data Service Planning and Administration Guide for background information. See “Synchronizing the Startups Between Resource Groups and Disk Device Groups” in Sun Cluster 3.1 Data Service Planning and Administration Guide for the procedure. (If you are using a Sun Cluster 3.0 version prior to 5/02, you must set up SUNW.HAStorage instead of SUNW.HAStoragePlus. See “Synchronizing the Startups Between Resource Groups and Disk Device Groups” in Sun Cluster 3.1 Data Service Planning and Administration Guide for the procedure.)