Installation and Upgrade Information

The Sun Cluster 2.2 release consists of four CD-ROMs:

• Sun Cluster 2.2 software

• Solstice DiskSuite 4.2 software and online (AnswerBook2^TM) documentation

• Cluster Volume Manager 2.2.1 software for customers running Oracle Parallel Server (OPS)

• Sun StorEdge Volume Manager 2.6 software

For more information about installing Solstice DiskSuite 4.2 software and documentation, see "Installing and Upgrading Solstice DiskSuite 4.2".

For details about installing and configuring CVM, see the Sun Cluster 2.2 Cluster Volume Manager Guide.

For instructions on installing and configuring SSVM, see your Sun StorEdge Volume Manager documentation and the Sun Cluster 2.2 Software Installation Guide.

CVM 2.2.1 will be replaced by CVM 3.0. At that time, CVM 2.2.1 users will be required to upgrade to CVM 3.0 to retain support for their configurations.

Changes to Installation Procedures

The Sun Cluster installation procedures have changed significantly from Solstice HA 1.3 and Sun Cluster 2.1. In Sun Cluster 2.2, the interactive command scinstall(1M) is used to install the software and to set up cluster components such as logical hosts and network interfaces.

The steps to install and configure Sun Cluster are grouped into three procedures:

1. Preparing the administrative workstation and installing the client software.

   This entails installing the Solaris operating environment and Sun Cluster 2.2 client software on the administrative workstation.

2. Installing the server software.

   This includes using the Cluster Console to install the Solaris operating environment and Sun Cluster 2.2 software on all cluster nodes; using scinstall(1M) to set up network interfaces, logical hosts, and quorum devices; and selecting data services and volume manager support packages.

3. Configuring and bringing up the cluster.

   This includes setting up paths; installing patches; installing and configuring your volume manager, SCI, PNM backup groups, logical hosts, and data services; and bringing up the cluster.

   See Chapter 3, "Installing and Configuring Sun Cluster Software, in the Sun Cluster 2.2 Software Installation Guide for the detailed procedures.

Installing and Upgrading Solstice DiskSuite 4.2

Existing Solstice HA 1.3 customers must upgrade to Solstice DiskSuite 4.2 to use Sun Cluster 2.2. The Solstice DiskSuite 4.2 software and documentation is provided on a separate CD-ROM containing the following:

• Solstice DiskSuite 4.2 software.

• AnswerBook2 server.

• Solstice DiskSuite 4.2 AnswerBook^TM. The Solstice DiskSuite 4.2 AnswerBook contains all Solstice DiskSuite 4.2 user documentation, including the Solstice DiskSuite 4.2 Installation and Product Notes which describes how to install and configure Solstice DiskSuite 4.2.

The Solstice DiskSuite 4.2 documentation refers to Solaris Easy Access Server documentation, Solaris Web Start, and i386. This special edition of Solstice DiskSuite 4.2 for Sun Cluster 2.2 is completely standalone; disregard these references.

Accessing Solstice DiskSuite 4.2 Installation Instructions

To access Solstice DiskSuite 4.2 installation procedures, do these steps:

1. Open the README file contained on the Solstice DiskSuite 4.2 CD-ROM, using a browser to access the menu options that enable you to read an HTML file. For example, in Netscape, do the following:

   1. From the Netscape browser menu bar, choose File>Open Page>Choose File. This opens the File Browser dialog box.

   2. Choose the file /cdrom/cdrom0/README.html. The browser brings up the README.html file.

2. Install the AnswerBook2 server and the Solstice DiskSuite 4.2 AnswerBook using the README file instructions.

3. Access the Solstice DiskSuite 4.2 AnswerBook and follow the online instructions found in the Solstice DiskSuite 4.2 Installation and Product Notes to install Solstice DiskSuite.

The latest version of Patch 106627 is required for Solstice DiskSuite 4.2 running on either Solaris 2.6 or Solaris 7. The patch is available from all Sun service providers and from the SunSolve^SM web site (http://sunsolve.sun.com/).

Upgrading to Solstice DiskSuite 4.2

As part of the upgrade from earlier versions of Solstice DiskSuite, you are asked to add the SUNWmd package. In the following example, note that several files are shown with an asterisk, indicating that they are in conflict. When you answer y at each prompt, the new commands are installed, but the conflicting files are not overwritten.

Do not remove the old SUNWmd package before adding the new one. Doing so will make all data inaccessible.

# pkgadd -d . SUNWmd
 Processing package instance <SUNWmd> from 
 </net/sag/export/unbundled/Solstice/disksuite/disksuite_4_2_seas/sparc>
 Solstice DiskSuite
 (sparc) 4.2,REV=1998.02.09.12.47.28
 Copyright 1998 Sun Microsystems, Inc. All rights reserved.
 ## Executing checkinstall script.
 This is an upgrade. Conflict approval questions may be displayed. 
 The listed files are the ones that will be upgraded. Please answer "y" 
 to these questions if they are presented.
 Using </> as the package base directory.
 ## Processing package information.
 ## Processing system information.
    26 package pathnames are already properly installed.
 ## Verifying package dependencies.
 ## Verifying disk space requirements.
 ## Checking for conflicts with packages already installed.
 The following files are already installed on the system and are 
 being used by another package:
 ../etc/init.d/SUNWmd.init
 /etc/init.d/SUNWmd.sync
 /etc/opt/SUNWmd/lock
 /etc/opt/SUNWmd/md.cf
 /etc/opt/SUNWmd/md.ctlrmap
 * /etc/opt/SUNWmd/md.tab
 /etc/opt/SUNWmd/mddb.cf
 /kernel/drv/md
 * /kernel/drv/md.conf
 /kernel/misc/md_hotspares
 /usr/opt/SUNWmd/man/man7/md.7
 /usr/opt/SUNWmd/sbin/growfs
 /usr/opt/SUNWmd/sbin/metaclear
 /usr/opt/SUNWmd/sbin/metadb
 /usr/opt/SUNWmd/sbin/metadetach
 /usr/opt/SUNWmd/sbin/metahs
 /usr/opt/SUNWmd/sbin/metainit
 /usr/opt/SUNWmd/sbin/metaoffline
 /usr/opt/SUNWmd/sbin/metaonline
 /usr/opt/SUNWmd/sbin/metaparam
 /usr/opt/SUNWmd/sbin/metarename
 /usr/opt/SUNWmd/sbin/metareplace
 /usr/opt/SUNWmd/sbin/metaroot
 /usr/opt/SUNWmd/sbin/metaset
 /usr/opt/SUNWmd/sbin/metastat
 /usr/opt/SUNWmd/sbin/metasync
 /usr/opt/SUNWmd/sbin/metattach
 /usr/opt/SUNWmd/sbin/rpc.metad
 /usr/opt/SUNWmd/sbin/rpc.metamhd

 * - conflicts with a file which does not belong to any package.
 Do you want to install these conflicting files [y,n,?,q] y

Configuring Mediators When Migrating From Solstice HA 1.3 to Sun Cluster 2.2

This section is only relevant to clusters that were originally set up under Solstice HA 1.3 using Solstice DiskSuite mediators (two-string configurations). It describes changes that are automatically made to a mediator configuration when you upgrade from Solstice HA 1.3 to Sun Cluster 2.2. There is no direct user impact, but you should note the changes in any configuration information you keep on the cluster.

The Solstice HA 1.3-to-Sun Cluster 2.2 upgrade procedure documented in the Sun Cluster 2.2 Software Installation Guide changes the Solstice HA 1.3 mediator configuration. The original Solstice HA 1.3 mediator configuration resembles the following:

After running the Sun Cluster 2.2 upgrade procedure, this configuration is converted to one similar to the following:

In Solstice HA 1.3, the hosts referred to the private links by physical names, whereas in Sun Cluster 2.2, the private link IP addresses are used.

For more information about configuring mediators for Sun Cluster 2.2, see Chapter 9, "Using Dual-String Mediators, in the Sun Cluster 2.2 System Administration Guide.

Sun Cluster HA for SAP Upgrade Issues

Before performing an upgrade to Sun Cluster 2.2 from Solstice HA 1.3 or Sun Cluster 2.1, note these SAP-related issues.

• On each node, if you customized hasap_start_all_instances or hasap_stop_all_instances scripts in Solstice HA 1.3 or Sun Cluster 2.1, save them to a safe location before beginning the upgrade to Sun Cluster 2.2. Restore the scripts after completing the upgrade. Do this to prevent loss of your customizations when Sun Cluster 2.2 removes the old scripts.

• The configuration parameters implemented in Sun Cluster 2.2 are different from those implemented in Solstice HA 1.3 and Sun Cluster 2.1. Therefore, after upgrading to Sun Cluster 2.2, you must reconfigure Sun Cluster HA for SAP by running the hadsconfig(1M) command.

  Before starting the upgrade, view the existing configuration and note the current configuration variables.

  • For Solstice HA 1.3, use the hainetconfig(1M) command to view the configuration.

  • For Sun Cluster 2.1, use the hadsconfig(1M) command to view the configuration.

  After upgrading to Sun Cluster 2.2, use the hadsconfig(1M) command to re-create the instance.

• In Sun Cluster 2.2, the hareg -n command shuts down the entire Sun Cluster HA for SAP data service, including all instances and fault monitors. In previous releases, the hareg -n command, when used with Sun Cluster HA for SAP, shuts down only the fault monitors.

  Additionally, before turning on the Sun Cluster HA for SAP data service using hareg -y, you must stop the SAP central instance. Otherwise, the Sun Cluster HA for SAP data service will not be able to start and monitor the instance properly.