Planning the Installation and Configuration

Use this section in conjunction with the worksheets in the Sun Cluster 3.0 U1 Release Notes as a checklist before installation and configuration.

Consider the following points prior to starting 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 NDS instances on a node, you must set the listenhost directive in the slapd.conf file with the appropriate network resource as the IP address (a logical hostname). This setting is necessary because the default NDS 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 logical hostname nds-1, add the following entry to the instance's slapd.conf file: listenhost nds-1. This setting causes the instance to bind to the logical hostname nds-1 only, rather than to all the IP addresses on the node.

• The LDAP administrative server is case-sensitive in its consideration of hostnames. Therefore, all hostnames specified in the LDAP configuration for the administrative server must match their case with the LDAP specification in the name service in use on the cluster node. If DNS is the name service in use, this case-matching is particularly important because the DNS domain name must also match the host-name specification in the LDAP configuration.

  Be sure that the case of the fully qualified domain name of the machine for LDAP 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 spell that name exactly the same way when you configure the LDAP administrative server.