How to Configure Sun Cluster Software on All Nodes (scinstall)

Perform this procedure from one node of the global cluster to configure Sun Cluster software on all nodes of the cluster.

This procedure uses the interactive form of the scinstall command. To use the noninteractive forms of the scinstall command, such as when developing installation scripts, see the scinstall(1M) man page.

Ensure that Sun Cluster software packages are installed on the node, either manually or by using the silent-mode form of the Java ES installer program, before you run the scinstall command. For information about running the Java ES installer program from an installation script, see Chapter 5, Installing in Silent Mode, in Sun Java Enterprise System 5 Update 1 Installation Guide for UNIX.

Before You Begin

Perform the following tasks:

• Ensure that the Solaris OS is installed to support Sun Cluster software.

  If Solaris software is already installed on the node, you must ensure that the Solaris installation meets the requirements for Sun Cluster software and any other software that you intend to install on the cluster. See How to Install Solaris Software for more information about installing Solaris software to meet Sun Cluster software requirements.

• SPARC: If you are configuring Sun Logical Domains (LDoms) I/O domains or guest domains as cluster nodes, ensure that Sun LDoms software is installed on each physical machine and that the domains meet Sun Cluster requirements. See SPARC: How to Install Sun Logical Domains Software and Create Domains.

• Ensure that Sun Cluster software packages and patches are installed on each node. See How to Install Sun Cluster Framework and Data-Service Software Packages.

• Determine which mode of the scinstall utility you will use, Typical or Custom.

  For the Typical installation of Sun Cluster software, scinstall automatically specifies the following configuration defaults.

  Component	Default Value
  Private-network address	172.16.0.0
  Private-network netmask	Solaris 9: 255.255.248.0Solaris 10: 255.255.240.0
  Cluster-transport adapters	Exactly two adapters
  Cluster-transport switches	switch1 and switch2
  Global fencing	Enabled
  Global-devices file-system name	/globaldevicesIf scinstall does not find a mounted /globaldevices file system in /etc/vfstab on a node, it prompts you to instead configure a lofi device or specify another file-system name
  Installation security (DES)	Limited

• Complete one of the following cluster configuration worksheets, depending on whether you run the scinstall utility in Typical mode or Custom mode.

  • Typical Mode Worksheet – If you will use Typical mode and accept all defaults, complete the following worksheet.

    Component	Description/Example	Answer
    Cluster Name	What is the name of the cluster that you want to establish?
    Cluster Nodes	List the names of the other cluster nodes planned for the initial cluster configuration.(For a single-node cluster, press Control-D alone.)
    Cluster Transport Adapters and Cables	What are the names of the two cluster-transport adapters that attach the node to the private interconnect?	First	Second
    	Will this be a dedicated cluster transport adapter? (Answer No if using tagged VLAN adapters.)	Yes | No	Yes | No
    	If no, what is the VLAN ID for this adapter?
    Quorum Configuration  (two-node cluster only)	Do you want to disable automatic quorum device selection? (Answer Yes if any shared storage is not qualified to be a quorum device or if you want to configure a quorum server or a Network Appliance NAS device as a quorum device.)	Yes  |  No
    Check	Do you want to interrupt cluster creation for cluster check errors?	Yes  |  No
    Global-Devices File System	(Prompted if no mounted /globaldevices file system is found on a node)Do you want to use the default name of the global-devices file system (/globaldevices)?	Yes  |  No
    	(Solaris 10 only) If no, do you want to use a lofi device instead and continue the installation?	Yes  |  No
    	If no, do you want to use an already-existing file system?	Yes  |  No
    	What is the name of the file system that you want to use?

  • Custom Mode Worksheet – If you will use Custom mode and customize the configuration data, complete the following worksheet.

    ---

    Note –

    If you are installing a single-node cluster, the scinstall utility automatically assigns the default private network address and netmask, even though the cluster does not use a private network.

    ---

    Component	Description/Example	Answer
    Cluster Name	What is the name of the cluster that you want to establish?
    Cluster Nodes	List the names of the other cluster nodes planned for the initial cluster configuration.(For a single-node cluster, press Control-D alone.)
    Authenticating Requests to Add Nodes  (multiple-node cluster only)	Do you need to use DES authentication?	No  |  Yes
    Minimum Number of Private Networks  (multiple-node cluster only)	Should this cluster use at least two private networks?	Yes  |  No
    Point-to-Point Cables  (multiple-node cluster only)	If this is a two-node cluster, does this cluster use switches?	Yes  |  No
    Cluster Switches  (multiple-node cluster only)	Transport switch name:  Defaults: switch1 and switch2	First	Second
    Cluster Transport Adapters and Cables  (multiple-node cluster only)	Node name (the node from which you run scinstall):
    	Transport adapter name:	First	Second
    	Will this be a dedicated cluster transport adapter? (Answer No if using tagged VLAN adapters.)	Yes | No	Yes | No
    	If no, what is the VLAN ID for this adapter?
    	Where does each transport adapter connect to (a switch or another adapter)? Switch defaults: switch1 and switch2	First	Second
    	If a transport switch, do you want to use the default port name?	Yes | No	Yes | No
    	If no, what is the name of the port that you want to use?
    	Do you want to use autodiscovery to list the available adapters for the other nodes?  If no, supply the following information for each additional node:	Yes  |  No
    Specify for each additional node (multiple-node cluster only)	Node name:
    	Transport adapter name:	First	Second
    	Will this be a dedicated cluster transport adapter? (Answer No if using tagged VLAN adapters.)	Yes | No	Yes | No
    	If no, what is the VLAN ID for this adapter?
    	Where does each transport adapter connect to (a switch or another adapter)? Defaults: switch1 and switch2	First	Second
    	If a transport switch, do you want to use the default port name?	Yes | No	Yes | No
    	If no, what is the name of the port that you want to use?
    Network Address for the Cluster Transport  (multiple-node cluster only)	Do you want to accept the default network address (172.16.0.0)?	Yes   |  No
    	If no, which private network address do you want to use?	___.___.___.___
    	Do you want to accept the default netmask?	Yes   |  No
    	If no, what are the maximum numbers of nodes, private networks, and zone clusters that you expect to configure in the cluster?	_____ nodes  _____ networks  _____ zone clusters
    	Which netmask do you want to use? (Choose from the values calculated by scinstall or supply your own.)	___.___.___.___
    Global Fencing	Do you want to disable global fencing? (Answer No unless the shared storage does not support SCSI reservations or unless you want systems that are outside the cluster to access the shared storage.)	Yes | No	Yes | No
    Quorum Configuration  (two-node cluster only)	Do you want to disable automatic quorum device selection? (Answer Yes if any shared storage is not qualified to be a quorum device or if you want to configure a quorum server or a Network Appliance NAS device as a quorum device.)	Yes | No	Yes | No
    Global Devices File System  (specify for each node)	Do you want to use the default name of the global-devices file system (/globaldevices)?	Yes  |  No
    	If no, is it okay to use the lofi method?	Yes  |  No
    	If no, do you want to use an already-existing file system?	Yes  |  No
    	What is the name of the file system that you want to use?
    Check  (multiple-node cluster only)	Do you want to interrupt cluster creation for cluster check errors?	Yes  |  No
    (single-node cluster only)	Do you want to run the cluster check utility to validate the cluster?	Yes  |  No
    Automatic Reboot  (single-node cluster only)	Do you want scinstall to automatically reboot the node after installation?	Yes  |  No

Follow these guidelines to use the interactive scinstall utility in this procedure:

• Interactive scinstall enables you to type ahead. Therefore, do not press the Return key more than once if the next menu screen does not appear immediately.

• Unless otherwise noted, you can press Control-D to return to either the start of a series of related questions or to the Main Menu.

• Default answers or answers to previous sessions are displayed in brackets ([ ]) at the end of a question. Press Return to enter the response that is in brackets without typing it.

1. If you disabled remote configuration during Sun Cluster software installation, re-enable remote configuration.

   Enable remote shell (rsh(1M)) or secure shell (ssh(1)) access for superuser to all cluster nodes.

2. If you are using switches in the private interconnect of your new cluster, ensure that Neighbor Discovery Protocol (NDP) is disabled.

   Follow the procedures in the documentation for your switches to determine whether NDP is enabled and to disable NDP.

   During cluster configuration, the software checks that there is no traffic on the private interconnect. If NDP sends any packages to a private adapter when the private interconnect is being checked for traffic, the software will assume that the interconnect is not private and cluster configuration will be interrupted. NDP must therefore be disabled during cluster creation.

   After the cluster is established, you can re-enable NDP on the private-interconnect switches if you want to use that feature.

3. From one cluster node, start the scinstall utility.

   phys-schost# /usr/cluster/bin/scinstall

4. Type the option number for Create a New Cluster or Add a Cluster Node and press the Return key.

   *** Main Menu *** Please select from one of the following (*) options: * 1) Create a new cluster or add a cluster node * 2) Configure a cluster to be JumpStarted from this install server 3) Manage a dual-partition upgrade 4) Upgrade this cluster node * 5) Print release information for this cluster node * ?) Help with menu options * q) Quit Option: 1

   The New Cluster and Cluster Node Menu is displayed.

5. Type the option number for Create a New Cluster and press the Return key.

   The Typical or Custom Mode menu is displayed.

6. Type the option number for either Typical or Custom and press the Return key.

   The Create a New Cluster screen is displayed. Read the requirements, then press Control-D to continue.

7. Follow the menu prompts to supply your answers from the configuration planning worksheet.

   The scinstall utility installs and configures all cluster nodes and reboots the cluster. The cluster is established when all nodes have successfully booted into the cluster. Sun Cluster installation output is logged in a /var/cluster/logs/install/scinstall.log.N file.

8. For the Solaris 10 OS, verify on each node that multiuser services for the Service Management Facility (SMF) are online.

   If services are not yet online for a node, wait until the state changes to online before you proceed to the next step.

   phys-schost# svcs multi-user-server node STATE STIME FMRI online 17:52:55 svc:/milestone/multi-user-server:default

9. From one node, verify that all nodes have joined the cluster.

   phys-schost# clnode status

   Output resembles the following.

   === Cluster Nodes === --- Node Status --- Node Name Status --------- ------ phys-schost-1 Online phys-schost-2 Online phys-schost-3 Online

   For more information, see the clnode(1CL) man page.

10. (Optional) Enable the automatic node reboot feature.

    This feature automatically reboots a node if all monitored shared-disk paths fail, provided that at least one of the disks is accessible from a different node in the cluster.

    1. Enable automatic reboot.

       phys-schost# clnode set -p reboot_on_path_failure=enabled

       -p

       Specifies the property to set

       reboot_on_path_failure=enable

       Enables automatic node reboot if failure of all monitored shared-disk paths occurs.

    2. Verify that automatic reboot on disk-path failure is enabled.

       phys-schost# clnode show === Cluster Nodes === Node Name: node … reboot_on_path_failure: enabled …

11. If you intend to use Sun Cluster HA for NFS on a highly available local file system, ensure that the loopback file system (LOFS) is disabled.

    To disable LOFS, add the following entry to the /etc/system file on each node of the cluster.

    exclude:lofs

    The change to the /etc/system file becomes effective after the next system reboot.

    ---

    Note –

    You cannot have LOFS enabled if you use Sun Cluster HA for NFS on a highly available local file system and have automountd running. LOFS can cause switchover problems for Sun Cluster HA for NFS. If you choose to add Sun Cluster HA for NFS on a highly available local file system, you must make one of the following configuration changes.

    However, if you configure non-global zones in your cluster, you must enable LOFS on all cluster nodes. If Sun Cluster HA for NFS on a highly available local file system must coexist with LOFS, use one of the other solutions instead of disabling LOFS.

    • Disable LOFS.

    • Disable the automountd daemon.

    • Exclude from the automounter map all files that are part of the highly available local file system that is exported by Sun Cluster HA for NFS. This choice enables you to keep both LOFS and the automountd daemon enabled.

    ---

    See The Loopback File System in System Administration Guide: Devices and File Systems (Solaris 9 or Solaris 10) for more information about loopback file systems.

Example 3–1 Configuring Sun Cluster Software on All Nodes

The following example shows the scinstall progress messages that are logged as scinstall completes configuration tasks on the two-node cluster, schost. The cluster is installed from phys-schost-1 by using the scinstall utility in Typical Mode. The other cluster node is phys-schost-2. The adapter names are qfe2 and qfe3. The automatic selection of a quorum device is enabled. Both nodes use the partition /globaldevices for the global-devices namespace.

  Installation and Configuration

    Log file - /var/cluster/logs/install/scinstall.log.24747

    Testing for "/globaldevices" on "phys-schost-1" … done
    Testing for "/globaldevices" on "phys-schost-2" … done
    Checking installation status … done

    The Sun Cluster software is already installed on "phys-schost-1".
    The Sun Cluster software is already installed on "phys-schost-2".
    Starting discovery of the cluster transport configuration.

    The following connections were discovered:

        phys-schost-1:qfe2  switch1  phys-schost-2:qfe2
        phys-schost-1:qfe3  switch2  phys-schost-2:qfe3

    Completed discovery of the cluster transport configuration.

    Started cluster check on "phys-schost-1".
    Started cluster check on "phys-schost-2".

    cluster check completed with no errors or warnings for "phys-schost-1".
    cluster check completed with no errors or warnings for "phys-schost-2".

    Removing the downloaded files … done

    Configuring "phys-schost-2" … done
    Rebooting "phys-schost-2" … done

    Configuring "phys-schost-1" … done
    Rebooting "phys-schost-1" …

Log file - /var/cluster/logs/install/scinstall.log.24747

Rebooting …

Troubleshooting

Unsuccessful configuration – If one or more nodes cannot join the cluster, or if the wrong configuration information was specified, first attempt to rerun this procedure. If that does not correct the problem, perform the procedure How to Unconfigure Sun Cluster Software to Correct Installation Problems on each misconfigured node to remove it from the cluster configuration. You do not need to uninstall the Sun Cluster software packages. Then rerun this procedure.

Next Steps

• If you installed a single-node cluster, cluster establishment is complete. Go to Creating Cluster File Systems to install volume management software and configure the cluster.

• If you installed a multiple-node cluster and chose automatic quorum configuration, postinstallation setup is complete. Go to How to Verify the Quorum Configuration and Installation Mode.

• If you installed a multiple-node cluster and declined automatic quorum configuration, perform postinstallation setup. Go to How to Configure Quorum Devices.

If you intend to configure any quorum devices in your cluster, go to How to Configure Quorum Devices.

Otherwise, go to How to Verify the Quorum Configuration and Installation Mode.