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

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

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.

• Ensure that Sun Cluster software packages are installed on the node. See How to Install Sun Cluster Framework and Data-Service Software Packages (Java ES installer).

• 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	255.255.0.0
  Cluster-transport junctions	switch1 and switch2
  Global-devices file-system name	/globaldevices
  Installation security (DES)	Limited
  Solaris and Sun Cluster patch directory	/var/cluster/patches/

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

  • Typical Mode - 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	What are the names of the other cluster nodes planned for the initial cluster configuration?
    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?	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 Network Appliance NAS device as a quorum device.)	Yes  |  No
    Check	Do you want to interrupt installation for sccheck errors? (sccheck verifies that preconfiguration requirements are met)	Yes  |  No

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

    Component	Description/Example	Answer
    Cluster Name	What is the name of the cluster that you want to establish?
    Cluster Nodes	What are the names of the other cluster nodes planned for the initial cluster configuration?
    DES Authentication  (multiple-node cluster only)	Do you need to use DES authentication?	No  |  Yes
    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, supply your own network address:	_____ . _____.0.0
    	Do you want to accept the default netmask (255.255.0.0)?	Yes   |  No
    	If no, supply your own netmask:	255.255. ___ . ___
    Point-to-Point Cables  (multiple-node cluster only)	If this is a two-node cluster, does this cluster use transport junctions?	Yes  |  No
    Cluster-Transport Junctions  (multiple-node cluster only)	If used, what are the names of the two transport junctions?  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 adapters:	First	Second
    	Will this be a dedicated cluster transport adapter?	Yes | No	Yes | No
    	If no, what is the VLAN ID for this adapter?
    	Where does each transport adapter connect to (a transport junction or another adapter)? Junction defaults: switch1 and switch2
    	For transport junctions, 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 adapters:	First	Second
    	Will this be a dedicated cluster transport adapter?	Yes | No	Yes | No
    	If no, what is the VLAN ID for this adapter?
    	Where does each transport adapter connect to (a transport junction or another adapter)? Defaults: switch1 and switch2
    	For transport junctions, 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?
    Software Patch Installation	Do you want scinstall to install patches for you?	Yes  |  No
    	If yes, what is the name of the patch directory?
    	Do you want to use a patch list?	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 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, 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 installation for sccheck errors? (sccheck verifies that preconfiguration requirements are met)	Yes  |  No
    (single-node cluster only)	Do you want to run the sccheck 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.

Steps

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. (Optional) To use the scinstall(1M) utility to install patches, download patches to a patch directory.

   • If you use Typical mode to install the cluster, use a directory named either /var/cluster/patches/ or /var/patches/ to contain the patches to install.

     In Typical mode, the scinstall command checks both those directories for patches.

     • If neither of those directories exist, then no patches are added.

     • If both directories exist, then only the patches in the /var/cluster/patches/ directory are added.

   • If you use Custom mode to install the cluster, you specify the path to the patch directory. Specifying the path ensures that you do not have to use the patch directories that scinstall checks for in Typical mode.

   You can include a patch-list file in the patch directory. The default patch-list file name is patchlist. For information about creating a patch-list file, refer to the patchadd(1M) man page.

3. Become superuser on the cluster node from which you intend to configure the cluster.

4. Start the scinstall utility.

   # /usr/cluster/bin/scinstall

5. From the Main Menu, choose the menu item, Install a cluster or cluster node.

   *** Main Menu *** Please select from one of the following (*) options: * 1) Install a cluster or cluster node 2) Configure a cluster to be JumpStarted from this install server 3) Add support for new data services to this cluster node 4) Upgrade this cluster node * 5) Print release information for this cluster node * ?) Help with menu options * q) Quit Option: 1

6. From the Install Menu, choose the menu item, Install all nodes of a new cluster.

7. From the Type of Installation menu, choose either Typical or Custom.

8. 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.

9. For the Solaris 10 OS, verify on each node that multi-user services for the Service Management Facility (SMF) are online.

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

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

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

    Run the scstat(1M) command to display a list of the cluster nodes. You do not need to be logged in as superuser to run this command.

    % scstat -n

    Output resembles the following.

    -- Cluster Nodes -- Node name Status --------- ------ Cluster node: phys-schost-1 Online Cluster node: phys-schost-2 Online

11. Install any necessary patches to support Sun Cluster software, if you have not already done so.

12. To re-enable the loopback file system (LOFS), delete the following entry from the /etc/system file on each node of the cluster.

    exclude:lofs

    The re-enabling of LOFS 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 enable LOFS and later choose to add Sun Cluster HA for NFS on a highly available local file system, you must do one of the following:

    • Restore the exclude:lofs entry to the /etc/system file on each node of the cluster and reboot each node. This change disables 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 Types of File Systems in System Administration Guide, Volume 1 (Solaris 8) or 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 2–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 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.

  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 sccheck on "phys-schost-1".
    Started sccheck on "phys-schost-2".

    sccheck completed with no errors or warnings for "phys-schost-1".
    sccheck 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 …

Next Steps

If you intend to install data services, go to the appropriate procedure for the data service that you want to install and for your version of the Solaris OS:

Otherwise, go to the next appropriate procedure:

• If you installed a single-node cluster, cluster establishment is complete. Go to Configuring the Cluster 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.

Troubleshooting

You cannot change the private-network address and netmask after scinstall processing is finished. If you need to use a different private-network address or netmask and the node is still in installation mode, follow the procedures in How to Uninstall Sun Cluster Software to Correct Installation Problems. Then perform the procedures in How to Install Sun Cluster Framework and Data-Service Software Packages (Java ES installer) and then perform this procedure to reinstall the software and configure the node with the correct information.