Sun Cluster Software Installation Guide for Solaris OS

ProcedureHow to Configure Sun Cluster Software (SunPlex Installer)

Perform this procedure to use SunPlex Installer to configure Sun Cluster software and install patches on all nodes in the cluster in a single operation. In addition, you can use this procedure to install Solstice DiskSuite software and patches (Solaris 8) and to configure Solstice DiskSuite or Solaris Volume Manager mirrored disk sets.

Note –

Do not use this configuration method in the following circumstances:

The installation process might take from 30 minutes to two or more hours. The actual length of time depends on the number of nodes that are in the cluster, your choice of data services to install, and the number of disks that are in your cluster configuration.

Before You Begin

Perform the following tasks:

  1. Prepare file-system paths to a CD-ROM image of each software product that you intend to install.

    Follow these guidelines to prepare the file-system paths:

    • Provide each CD-ROM image in a location that is available to each node.

    • Ensure that the CD-ROM images are accessible to all nodes of the cluster from the same file-system path. These paths can be one or more of the following locations:

      • CD-ROM drives that are exported to the network from machines outside the cluster.

      • Exported file systems on machines outside the cluster.

      • CD-ROM images that are copied to local file systems on each node of the cluster. The local file system must use the same name on each node.

  2. x86: Determine whether you are using the Netscape NavigatorTM browser or the Microsoft Internet Explorer browser on your administrative console.

    • If you are using Netscape Navigator, proceed to Step 3.

    • If you are using Internet Explorer, skip to Step 4.

  3. x86: Ensure that the Java plug-in is installed and working on your administrative console.

    1. Start the Netscape Navigator browser on the administrative console that you use to connect to the cluster.

    2. From the Help menu, choose About Plug-ins.

    3. Determine whether the Java plug-in is listed.

    4. Download the latest Java plug-in from

    5. Install the plug-in on your administrative console.

    6. Create a symbolic link to the plug-in.

      % cd ~/.netscape/plugins/
      % ln -s /usr/j2se/plugin/i386/ns4/ .
    7. Skip to Step 5.

  4. x86: Ensure that Java 2 Platform, Standard Edition (J2SE) for Windows is installed and working on your administrative console.

    1. On your Microsoft Windows desktop, click Start, point to Settings, and then select Control Panel.

      The Control Panel window appears.

    2. Determine whether the Java Plug-in is listed.

      • If no, proceed to Step c.

      • If yes, double-click the Java Plug-in control panel. When the control panel window opens, click the About tab.

        • If an earlier version is shown, proceed to Step c.

        • If version 1.4.1 or a later version is shown, skip to Step 5.

    3. Download the latest version of J2SE for Windows from

    4. Install the J2SE for Windows software on your administrative console.

    5. Restart the system on which your administrative console runs.

      The J2SE for Windows control panel is activated.

  5. If patches exist that are required to support Sun Cluster or Solstice DiskSuite software, determine how to install those patches.

    • To manually install patches, use the patchadd command to install all patches before you use SunPlex Installer.

    • To use SunPlex Installer to install patches, copy patches into a single directory.

      Ensure that the patch directory meets the following requirements:

      • The patch directory resides on a file system that is available to each node.

      • Only one version of each patch is present in this patch directory. If the patch directory contains multiple versions of the same patch, SunPlex Installer cannot determine the correct patch dependency order.

      • The patches are uncompressed.

  6. From the administrative console or any other machine outside the cluster, launch a browser.

  7. Disable the browser's Web proxy.

    SunPlex Installer installation functionality is incompatible with Web proxies.

  8. Ensure that disk caching and memory caching is enabled.

    The disk cache and memory cache size must be greater than 0.

  9. From the browser, connect to port 3000 on a node of the cluster.


    The Sun Cluster Installation screen is displayed in the browser window.

    Note –

    If SunPlex Installer displays the data services installation screen instead of the Sun Cluster Installation screen, Sun Cluster framework software is already installed and configured on that node. Check that the name of the node in the URL is the correct name of the cluster node to install.

  10. If the browser displays a New Site Certification window, follow the onscreen instructions to accept the certificate.

  11. Log in as superuser.

  12. In the Sun Cluster Installation screen, verify that the cluster meets the listed requirements for using SunPlex Installer.

    If you meet all listed requirements, click Next to continue to the next screen.

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

  14. Click Begin Installation to start the installation process.

    Follow these guidelines to use SunPlex Installer:

    • Do not close the browser window or change the URL during the installation process.

    • If the browser displays a New Site Certification window, follow the onscreen instructions to accept the certificate.

    • If the browser prompts for login information, type the appropriate superuser ID and password for the node that you connect to.

    SunPlex Installer 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.

    During installation, the screen displays brief messages about the status of the cluster installation process. When installation and configuration is complete, the browser displays the cluster monitoring and administration GUI.

    SunPlex Installer installation output is logged in the /var/cluster/spm/messages file. Sun Cluster installation output is logged in a /var/cluster/logs/install/scinstall.log. N file.

  15. 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
  16. Verify the quorum assignments and modify those assignments, if necessary.

    For clusters with three or more nodes, the use of shared quorum devices is optional. SunPlex Installer might or might not have assigned quorum votes to any quorum devices, depending on whether appropriate shared disks were available. You can use SunPlex Manager to designate quorum devices and to reassign quorum votes in the cluster. See Chapter 5, Administering Quorum, in Sun Cluster System Administration Guide for Solaris OS for more information.

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


    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.

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:


Sun Cluster 2 of 2 CD-ROM 

(Sun Java System data services) 

Sun Cluster Agents CD 

(All other data services) 


Solaris 8 or 9 

Solaris 10 

Solaris 8 or 9 

Solaris 10 

How to Install Sun Cluster Framework and Data-Service Software Packages (Java ES installer)


How to Install Data-Service Software Packages (pkgadd)



How to Install Data-Service Software Packages (scinstall)


How to Install Data-Service Software Packages (Web Start installer)



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


You cannot change the private-network address and netmask after scinstall processing has 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 repeat this procedure to reinstall and configure the node with the correct information.