Use this section in conjunction with the worksheets in the Sun Cluster 3.1 Release Notes as a checklist before installation and configuration.
Consider the following points before you start your installation.
Where will the server root reside?
You can store files and data that do not change on the local file system of each cluster node. However, place dynamic data on the cluster file system so that you can view or update the data from any cluster node.
If you plan to use multiple Sun ONE Directory Server instances on a node, you must set the nsslapd-listenhost directive with the appropriate network resource as the IP address. This setting is necessary because the default Sun ONE Directory Server behavior is for the instance to bind to all IP addresses on the node.
For example, to set up a particular instance to use the network resource nds-1, use the following entry.
This setting causes the instance to bind to the network resource nds-1 only, rather than to all of the IP addresses on the node.
The Sun ONE Directory Server administrative server is case-sensitive in its consideration of hostnames. Therefore, all hostnames specified in the Sun ONE Directory Server configuration for the administrative server must match their case with the Sun ONE Directory Server specification in the name service in use on the cluster node. This case-matching is particularly important because the DNS domain name must also match the host-name specification in the Sun ONE Directory Server configuration.
Be sure that the case of the fully qualified domain name of the machine for Sun ONE Directory Server matches the case of the domain name that the resolver returns. For example, if the DNS resolver returns Eng.Sun.COM as the domain name (note the mixed case), you must identically spell that name when you configure the Sun ONE Directory Server administrative server.