How to Upgrade to Sun Cluster 3.1 4/04 Software (Nonrolling) (Sun Cluster Software Installation Guide for Solaris OS)

Sun Cluster Software Installation Guide for Solaris OS

Previous: How to Upgrade the Solaris Operating Environment (Nonrolling)
Next: How to Upgrade Sun Cluster-Module Software for Sun Management Center (Nonrolling)

How to Upgrade to Sun Cluster 3.1 4/04 Software (Nonrolling)

This procedure describes how to upgrade the cluster to Sun Cluster 3.1 4/04 software. You must also perform this procedure to complete cluster upgrade from Solaris 8 to Solaris 9 software.

Tip –

You can perform this procedure on more than one node at the same time.

Ensure that all steps in How to Prepare the Cluster for Upgrade (Nonrolling) are completed.

If you upgraded from Solaris 8 to Solaris 9 software, also ensure that all steps in How to Upgrade the Solaris Operating Environment (Nonrolling) are completed.

Become superuser on a node of the cluster.

Ensure that you have installed all required Solaris software patches and hardware-related patches.

For Solstice DiskSuite software (Solaris 8), also ensure that you have installed all required Solstice DiskSuite software patches.

Insert the Sun Java Enterprise System 2004Q2 2 of 2 CD-ROM into the CD-ROM drive on the node.

If the volume management daemon vold(1M) is running and configured to manage CD-ROM devices, the daemon automatically mounts the CD-ROM on the /cdrom/cdrom0 directory.

Upgrade the node to Sun Cluster 3.1 4/04 software.
1. From the /cdrom/cdrom0 directory, change to the Solaris_sparc/Product/sun_cluster/Solaris_ver/Tools directory, where ver is 8 (for Solaris 8) or 9 (for Solaris 9) .
  
  The following example uses the path to the Solaris 8 version of Sun Cluster software.
  # cd /cdrom/cdrom0/Solaris_sparc/Product/sun_cluster/Solaris_8/Tools
2. Upgrade the cluster framework software.
  - To upgrade from Sun Cluster 3.0 software, run the following command:
    # ./scinstall -u update -S interact -M patchdir=dirname
    -S
    
    Specifies the test IP addresses to use to convert NAFO groups to IP Network Multipathing groups
    
    interact
    
    Specifies that scinstall prompts the user for each test IP address needed
    
    -M patchdir=dirname[[,patchlistfile=filename]]
    
    Specifies the path to patch information so that the specified patches can be installed using the scinstall command. If you do not specify a patch-list file, the scinstall command installs all the patches in the directory dirname, including tarred, jarred, and zipped patches.
    
    The -M option is not required. You can use any method you prefer for installing patches.
  - To upgrade from Sun Cluster 3.1 software, run the following command:
    # ./scinstall -u update -M patchdir=dirname
    -M patchdir=dirname[[,patchlistfile=filename]]
    
    Specifies the path to patch information so that the specified patches can be installed using the scinstall command. If you do not specify a patch-list file, the scinstall command installs all the patches in the directory dirname, including tarred, jarred, and zipped patches.
  The -M option is not required. You can use any method you prefer for installing patches.
  
  See “Patches and Required Firmware Levels” in Sun Cluster 3.1 Release Notes for the location of patches and installation instructions.
  
  Upgrade processing is finished when the system displays the message Completed Sun Cluster framework upgrade and the path to the upgrade log.
  
  See the scinstall(1M) man page for more information. See the IP Network Multipathing Administration Guide (Solaris 8) or System Administration Guide: IP Services (Solaris 9) for information about test addresses for IP Network Multipathing.
  
  Note –
  Sun Cluster 3.1 4/04 software requires at least version 3.5.1 of Sun Explorer software. Upgrade to Sun Cluster software includes installing Sun Explorer data collector software, to be used in conjunction with the sccheck utility. If another version of Sun Explorer software was already installed before Sun Cluster upgrade, it is replaced by the version that is provided with Sun Cluster software. Options such as user identity and data delivery are preserved, but crontab entries must be manually recreated.
  
  During Sun Cluster upgrade, scinstall might make one or more of the following configuration changes:
  - Convert NAFO groups to IP Network Multipathing groups but keep the original NAFO-group name.
  - Rename the ntp.conf file to ntp.conf.cluster, if ntp.conf.cluster does not already exist on the node.
  - Set the local-mac-address? variable to true, if the variable is not already set to that value.
3. Change to the CD-ROM root directory and eject the CD-ROM.

Upgrade software applications that are installed on the cluster.

Ensure that application levels are compatible with the current version of Sun Cluster and Solaris software. See your application documentation for installation instructions. In addition, follow these guidelines to upgrade applications in a Sun Cluster 3.1 4/04 configuration:
- If the applications are stored on shared disks, you must master the relevant disk groups and manually mount the relevant file systems before you upgrade the application.
- If you are instructed to reboot a node during the upgrade process, always add the -x option to the command.
  
  The -x option ensures that the node reboots into noncluster mode. For example, either of the following two commands boot a node into single-user noncluster mode:
  # reboot -- -xs ok boot -xs

(Optional) Upgrade Sun Cluster data services to the Sun Cluster 3.1 4/04 software versions.

Note –
You must upgrade the Sun Cluster HA for Oracle 3.0 64–bit for Solaris 9 data service to the Sun Cluster 3.1 4/04 version. Otherwise, you can continue to use Sun Cluster 3.0 data services after upgrade to Sun Cluster 3.1 4/04 software.

Only those data services that are delivered on the Java Enterprise System Accessory CD 3 CD-ROM are automatically upgraded by the scinstall(1M) utility. You must manually upgrade any custom or third-party data services. Follow the procedures provided with those data services.
1. Insert the Java Enterprise System Accessory CD 3 CD-ROM into the CD-ROM drive on the node to upgrade.
2. Upgrade the data-service software.
  # scinstall -u update -s all -d /cdrom/cdrom0
  -u update
  
  Specifies upgrade
  
  -s all
  
  Updates all Sun Cluster data services that are installed on the node
  
  Upgrade processing is finished when the system displays the message Completed upgrade of Sun Cluster data services agents and the path to the upgrade log.
3. Change to the CD-ROM root directory and eject the CD-ROM.
4. As needed, manually upgrade any custom data services that are not supplied on the Java Enterprise System Accessory CD 3 CD-ROM.
5. Install any Sun Cluster 3.1 4/04 data-service patches.
  
  See “Patches and Required Firmware Levels” in Sun Cluster 3.1 Release Notes for the location of patches and installation instructions.

After all nodes are upgraded, reboot each node into the cluster.
# reboot

Verify that all upgraded software is at the same version on all upgraded nodes.
1. On each upgraded node, view the installed levels of Sun Cluster software.
  # scinstall -pv
2. From one node, verify that all upgraded cluster nodes are running in cluster mode (Online).
  # scstat -n
  See the scstat(1M) man page for more information about displaying cluster status.

Did you upgrade from Solaris 8 to Solaris 9 software?
- If no, skip to Step 14.
- If yes, proceed to Step 11.

On each node, run the following command to verify the consistency of the storage configuration:

# scdidadm -c

-c: Perform a consistency check

Caution –

Do not proceed to Step 12 until your configuration passes this consistency check. Failure to do so might result in errors in device identification and cause data corruption.

The following table lists the possible output from the scdidadm -c command and the action you must take, if any.

Example Message	Action to Take
`device id for 'phys-schost-1:/dev/rdsk/c1t3d0' does not match physical device's id, device may have been replaced`	Go to Recovering From Storage Configuration Changes During Upgrade and perform the appropriate repair procedure.
`device id for 'phys-schost-1:/dev/rdsk/c0t0d0' needs to be updated, run scdidadm –R to update`	None. You update this device ID in Step 12.
No output message	None

See the scdidadm(1M) man page for more information.

On each node, migrate the Sun Cluster storage database to Solaris 9 device IDs.
# scdidadm -R all
-R

Perform repair procedures

all

Specify all devices

On each node, run the following command to verify that storage database migration to Solaris 9 device IDs is successful:
# scdidadm -c
- If the scdidadm command displays a message, return to Step 11 to make further corrections to the storage configuration or the storage database.
- If the scdidadm command displays no messages, the device-ID migration is successful. If device-ID migration is verified on all cluster nodes, proceed to Step 14.

Does your configuration use dual-string mediators for Solstice DiskSuite/Solaris Volume Manager?
- If no, proceed to Step 15.
- If yes, restore the mediator configurations.
1. Determine which node has ownership of a diskset to which you will add the mediator hosts.
  # metaset -s setname
  -s setname
  
  Specifies the diskset name
2. If no node has ownership, take ownership of the diskset.
  # metaset -s setname -t
  -t
  
  Takes ownership of the diskset
3. Recreate the mediators.
  # metaset -s setname -a -m mediator-host-list
  -a
  
  Adds to the diskset
  
  -m mediator-host-list
  
  Specifies the names of the nodes to add as mediator hosts for the diskset
4. Repeat Step a through Step c for each diskset in the cluster that uses mediators.

Did you upgrade VxVM?
- If no, proceed to Step 16.
- If yes, upgrade all disk groups.
  
  To upgrade a disk group to the highest version supported by the VxVM release you installed, run the following command from the primary node of the disk group:
  # vxdg upgrade dgname
  See your VxVM administration documentation for more information about upgrading disk groups.

Do you use Sun Management Center to monitor the cluster?
- If yes, go to How to Upgrade Sun Cluster-Module Software for Sun Management Center (Nonrolling).
- If no, go to How to Finish Upgrading to Sun Cluster 3.1 4/04 Software (Nonrolling).

Example—Upgrade From Sun Cluster 3.0 to Sun Cluster 3.1 4/04 Software

The following example shows the process of a nonrolling upgrade of a two-node cluster from Sun Cluster 3.0 to Sun Cluster 3.1 4/04 software on the Solaris 8 operating environment. The cluster node names are phys-schost-1 and phys-schost-2.

(On the first node, upgrade framework software from the Sun Java Enterprise System 2004Q2 2 of 2 CD-ROM)
phys-schost-1# cd /cdrom/cdrom0/Solaris_sparc/Product/sun_cluster/ \
Solaris_8/Tools
phys-schost-1# ./scinstall -u update -S interact
 
(On the first node, upgrade data services from the Java Enterprise System Accessory CD 3 CD-ROM)
phys-schost-1# ./scinstall -u update -s all -d /cdrom/cdrom0
 
(On the second node, upgrade framework software from the Sun Java Enterprise System 2004Q2 2 of 2 CD-ROM)
phys-schost-2# cd /cdrom/cdrom0/Solaris_sparc/Product/sun_cluster/ \
Solaris_8/Tools
phys-schost-2# ./scinstall -u update -S interact
 
(On the second node, upgrade data services from the Java Enterprise System Accessory CD 3 CD-ROM)
phys-schost-2# ./scinstall -u update -s all -d /cdrom/cdrom0
 
(Reboot each node into the cluster)
phys-schost-1# reboot
phys-schost-2# reboot
 
(Verify cluster membership)
# scstat
-- Cluster Nodes --
                   Node name      Status
                   ---------      ------
  Cluster node:    phys-schost-1  Online
  Cluster node:    phys-schost-2  Online