How to Configure the Name-Service Switch
Perform this task on each node in the cluster.
Become superuser on the cluster node.
Edit the /etc/nsswitch.conf file.
Verify that cluster is the first source look-up for the hosts and netmasks database entries.
This order is necessary for Sun Cluster software to function properly. The scinstall(1 M) command adds cluster to these entries during installation.
(Optional) To increase availability to data services if the naming service becomes unavailable, change the look-up order of the following entries.
For the hosts and netmasks database entries, follow cluster with files.
For Sun Cluster HA for NFS, also insert [SUCCESS=return] after cluster files and before name services.
hosts: cluster files [SUCCESS=return] nis
This look-up order ensures that, if the node resolves a name locally, the node does not contact the listed name service(s). Instead, the node returns success immediately.
For all other database entries, place files first in the look-up order.
If the [NOTFOUND=return] criterion becomes the last item of an entry after you modify the lookup order, the criterion is no longer necessary. You can either delete the [NOTFOUND=return] criterion from the entry or leave the criterion in the entry. A [NOTFOUND=return] criterion at the end of an entry is ignored.
The following example shows partial contents of an /etc/nsswitch.conf file. The look-up order for the hosts and netmasks database entries is first cluster, then files. The look-up order for other entries begins with files. The [NOTFOUND=return] criterion is removed from the entries.
# vi /etc/nsswitch.conf ... passwd: files nis group: files nis ... hosts: cluster files nis ... netmasks: cluster files nis ...
See the nsswitch.conf(4) man page for more information about nsswitch.conf file entries.
Set up your root user's environment.
How to Set Up the Root Environment
Perform these tasks on each node in the cluster.
Note - In a Sun Cluster configuration, user initialization files for the various shells must verify that they are run from an interactive shell before they attempt to output to the terminal. Otherwise, unexpected behavior or interference with data services might occur. See "Customizing a User's Work Environment" in System Administration Guide, Volume 1 (Solaris 8) or "Customizing a User's Work Environment" in System Administration Guide: Basic Administration (Solaris 9) for more information.
Become superuser on a cluster node.
Modify PATH and MANPATH entries in the .cshrc or .profile file.
Set the PATH to include /usr/sbin and /usr/cluster/bin. Also include the following volume-manager-specific paths that apply to your configuration:
Software Product
PATH
VERITAS Volume Manager (VxVM)
/etc/vx/bin
VxVM 3.2 GUI
/opt/VRTSvmsa/bin
VxVM 3.5 GUI
/opt/VRTSob/bin
VERITAS File System (VxFS)
/opt/VRTSvxfs/sbin, /usr/lib/fs/vxfs/bin, and /etc/fs/vxfs
Set the MANPATH to include /usr/cluster/man. Also include the following volume-manager-specific paths that apply to your configuration:
Software Product
MANPATH
Solstice DiskSuite/Solaris Volume Manager
/usr/share/man
VxVM
/opt/VRTS/man
VxVM GUI
/opt/VRTSvmsa/man
VxFS
/opt/VRTS/man
(Optional) For ease of administration, set the same root password on each node, if you have not already done so.
Repeat Step 1 through Step 3 on each remaining cluster node.
Install data-service software packages.
To use the scinstall utility, go to How to Install Data-Service Software Packages (scinstall).
To use the Web Start program to install data services from the Sun Cluster 3.1 10/03 Data Services release, go to How to Install Data-Service Software Packages (Web Start).
How to Install Data-Service Software Packages (Web Start)
If you install data services from the Sun Cluster 3.1 10/03 Data Services release, you can use the Web Start program to install the packages. To install data services from a an earlier release, follow the procedures in How to Install Data-Service Software Packages (scinstall).
You can run the Web Start program with a command-line interface (CLI) or with a graphical user interface (GUI). The content and sequence of instructions in the CLI and the GUI are similar. For more information about the Web Start program, see the installer(1M) man page.
Become superuser on a cluster node.
(Optional) If you intend to use the Web Start program with a GUI, ensure that the DISPLAY environment variable is set.
Load the Sun Cluster 3.1 Agents CD-ROM into the CD-ROM drive.
If the Volume Management daemon vold(1M) is running and is configured to manage CD-ROM devices, the daemon automatically mounts the CD-ROM on the /cdrom/suncluster_3_1_u1 directory.
Change to the directory where the CD-ROM is mounted.
# cd cdrom-mount-point
Start the Web Start program.
# ./installer
Follow instructions on the screen to install the data-service packages on the node.
After the installation is finished, the Web Start program provides an installation summary. This summary enables you to view logs that the program created during the installation. These logs are located in the /var/sadm/install/logs directory.
Exit the Web Start program.
Unload the Sun Cluster 3.1 Agents CD-ROM from the CD-ROM drive.
To ensure that the CD-ROM is not being used, change to a directory that does not reside on the CD-ROM.
Eject the CD-ROM.
# eject cdrom
Repeat Step 1 through Step 10 on each remaining cluster node.
Install any Sun Cluster data-service patches.
See "Patches and Required Firmware Levels" in Sun Cluster 3.1 Release Notes for the location of patches and installation instructions.
You do not have to reboot after you install Sun Cluster data-service patches unless a reboot is specified by the patch special instructions. If a patch instruction requires that you reboot, perform the following steps:
Shut down the cluster by using the scshutdown(1M) command.
Reboot each node in the cluster.
Note - Until cluster installation mode is disabled, only the first-installed node, which established the cluster, has a quorum vote. In an established cluster which is still in installation mode, if the cluster is not shut down before the first-installed node is rebooted, the remaining cluster nodes cannot obtain quorum. The entire cluster then shuts down. Cluster nodes remain in installation mode until the first time you run the scsetup(1M) command, during the procedure How to Perform Postinstallation Setup.
Perform postinstallation setup and assign quorum votes.