Sun Cluster 3.1 10/03 Software Installation Guide

Example - Installing Sun Cluster Software on an Additional Node

The following example shows the scinstall command executed and the messages that the utility logs as scinstall completes installation tasks on the node phys-schost-3. The sponsoring node is phys-schost-1.
>>> Confirmation <<< Your responses indicate the following options to scinstall: scinstall -ik \ -C sc-cluster \ -N phys-schost-1 \ -A trtype=dlpi,name=hme1 -A trtype=dlpi,name=hme3 \ -m endpoint=:hme1,endpoint=switch1 \ -m endpoint=:hme3,endpoint=switch2 Are these the options you want to use (yes/no) [yes]? Do you want to continue with the install (yes/no) [yes]? Checking device to use for global devices file system ... done Adding node "phys-schost-3" to the cluster configuration ... done Adding adapter "hme1" to the cluster configuration ... done Adding adapter "hme3" to the cluster configuration ... done Adding cable to the cluster configuration ... done Adding cable to the cluster configuration ... done Copying the config from "phys-schost-1" ... done Setting the node ID for "phys-schost-3" ... done (id=3) Verifying the major number for the "did" driver with "phys-schost-1" ...done Checking for global devices global file system ... done Updating vfstab ... done Verifying that NTP is configured ... done Installing a default NTP configuration ... done Please complete the NTP configuration after scinstall has finished. Verifying that "cluster" is set for "hosts" in nsswitch.conf ... done Adding the "cluster" switch to "hosts" in nsswitch.conf ... done Verifying that "cluster" is set for "netmasks" in nsswitch.conf ... done Adding the "cluster" switch to "netmasks" in nsswitch.conf ... done Verifying that power management is NOT configured ... done Unconfiguring power management ... done /etc/power.conf has been renamed to /etc/power.conf.61501001054 Power management is incompatible with the HA goals of the cluster. Please do not attempt to re-configure power management. Ensure that the EEPROM parameter "local-mac-address?" is set to "true" ...done Ensure network routing is disabled ... done Network routing has been disabled on this node by creating /etc/notrouter. Having a cluster node act as a router is not supported by Sun Cluster. Please do not re-enable network routing. Log file - /var/cluster/logs/install/scinstall.log.9853 Rebooting ...

Using SunPlex Manager to Install Sun Cluster Software

Note - To add a new node to an existing cluster, do not use SunPlex Manager. Instead, use the procedure How to Install Sun Cluster Software on Additional Cluster Nodes (scinstall).

This section describes how to install SunPlex Manager. This section also describes how to use SunPlex Manager to install Sun Cluster software and to establish new cluster nodes. You can also use SunPlex Manager to install or configure one or more of the following additional software products:

(On Solaris 8 only) Solstice DiskSuite software - After installing Solstice DiskSuite software, SunPlex Manager configures up to three metasets and associated metadevices. SunPlex Manager also creates and mounts cluster file systems for each metaset.
(On Solaris 9 only) Solaris Volume Manager software - SunPlex Manager configures up to three Solaris Volume Manager volumes. SunPlex Manager also creates and mounts cluster file systems for each volume. Solaris Volume Manager software is already installed as part of Solaris software installation.
Sun Cluster HA for NFS data service.
Sun Cluster HA for Apache scalable data service.

The following table lists SunPlex Manager installation requirements for these additional software products.

Table 2-2 Requirements to Use SunPlex Manager to Install Software

Software Package	Installation Requirements
Solstice DiskSuite/Solaris Volume Manager	A partition that uses `/sds` as the mount-point name. The partition must be at least 20 Mbytes in size.
Sun Cluster HA for NFS data service	At least two shared disks, of the same size, that are connected to the same set of nodes. Solstice DiskSuite software installed, or Solaris Volume Manager software configured, by SunPlex Manager. A logical hostname for use by Sun Cluster HA for NFS. The logical hostname must have a valid IP address that is accessible by all cluster nodes. The IP address must be on the same subnet as the base hostnames of the cluster nodes. A test IP address for each node of the cluster. SunPlex Manager uses these test IP addresses to create Internet Protocol (IP) Network Multipathing (IP Network Multipathing) groups for use by Sun Cluster HA for NFS.
Sun Cluster HA for Apache scalable data service	At least two shared disks of the same size that are connected to the same set of nodes. Solstice DiskSuite software installed, or Solaris Volume Manager software configured, by SunPlex Manager. A shared address for use by Sun Cluster HA for Apache. The shared address must have a valid IP address that is accessible by all cluster nodes. The IP address must be on the same subnet as the base hostnames of the cluster nodes. A test IP address for each node of the cluster. SunPlex Manager uses these test IP addresses to create Internet Protocol (IP) Network Multipathing (IP Network Multipathing) groups for use by Sun Cluster HA for Apache.

The test IP addresses that you supply must meet the following requirements:

Test IP addresses for all adapters in the same multipathing group must belong to a single IP subnet.
Test IP addresses must not be used by normal applications because the test IP addresses are not highly available.

The following table lists each metaset name and cluster-file-system mount point that is created by SunPlex Manager. The number of metasets and mount points that SunPlex Manager creates depends on the number of shared disks that are connected to the node. For example, if a node has four shared disks connected, SunPlex Manager creates the mirror-1 and mirror-2 metasets. However, SunPlex Manager does not create the mirror-3 metaset, because the node does not have enough shared disks to create a third metaset.

Table 2-3 Metasets Installed by SunPlex Manager

Shared Disks	Metaset Name	Cluster File System Mount Point	Purpose
First pair of shared disks	`mirror-1`	`/global/mirror-1`	Sun Cluster HA for NFS or Sun Cluster HA for Apache scalable data service, or both
Second pair of shared disks	`mirror-2`	`/global/mirror-2`	Unused
Third pair of shared disks	`mirror-3`	`/global/mirror-3`	Unused

Note - If the cluster does not meet the minimum shared-disk requirement, SunPlex Manager still installs the Solstice DiskSuite packages. However, without sufficient shared disks, SunPlex Manager cannot configure the metasets, metadevices, or volumes. SunPlex Manager then cannot configure the cluster file systems that are needed to create instances of the data service.

SunPlex Manager recognizes a limited character set to increase security. Characters that are not a part of the set are silently filtered out when HTML forms are submitted to the SunPlex Manager server. The following characters are accepted by SunPlex Manager:
()+,-./0-9:=@A-Z^_a-z{|}~

This filter can cause problems in the following two areas:

Password entry for Sun Open Net Environment (Sun ONE) services - If the password contains unusual characters, these characters are stripped out, resulting in one of the following problems:
- The resulting password has less than eight characters and therefore fails.
- The application is configured with a different password than the user expects.
Localization - Alternative character sets, for example, accented characters or Asian characters, do not work for input.


2. Installing and Configuring Sun Cluster Software Installing the Software How to Install Sun Cluster Software on Additional Cluster Nodes (`scinstall`)