Date: 2008-10-17
OS: Solaris Opteron
OS Version: 10
Packages: VRTSvcs
Etrack Incidents: 1404384, 1397692
=========================================================================
* * * READ ME - VERITAS CLUSTER SERVER 5.0 MP3 - VCS Engine HOT FIX * * *

                   Patch Date:  October 17, 2008

This document provides information for:
    * POINT PATCH NAME
    * BEFORE GETTING STARTED
    * POINT PATCH SUMMARY OF CONTENT
    * PACKAGES AFFECTED BY PATCH
    * PATCH'S BASE VERSION
    * SUPPORTED OPERATING SYSTEMS
    * LIST OF INCIDENTS FIXED BY PATCH
    * INSTALLING THE PATCH
    * REMOVING THE PATCH

POINT PATCH NAME
----------------
Name: VCS50MP3HF1 

BEFORE GETTING STARTED
----------------------

This patch is for systems running VCS 5.0 MP3 only. If systems are 
running VCS 5.0 or earlier, you do not need this patch. 

POINT PATCH SUMMARY OF CONTENT
------------------------------
This point patch contains:

    README (this file)

    139154-01

PACKAGES AFFECTED BY PATCH
--------------------------
    VRTSvcs

PATCH'S BASE VERSION
--------------------
    VCS 5.0 MP3

SUPPORTED OPERATING SYSTEMS
---------------------------
    Solaris 10

LIST OF INCIDENTS FIXED BY PATCH
--------------------------------
1404384: HAD crashing when switching over a global group when PreSwitch is TRUE.

1397692: VCS engine clients hang in connect() if the target system is down.

INSTALLING THE PATCH
-------------------------------------------------------------------------------
1.  Copy the point patch to a directory on your system:

	# cp <patch.gz> .

2.  Unzip the compressed patch files that you want to install:

	# gunzip *.gz

3.  Extract the compressed patch files from the tar files:

	# tar -xvf <patch.tar>

4.  Verify that /opt/VRTS/bin is in your PATH so you can execute all the 
    product commands. Refer to the VCS Installation Guide for more 
    information.

5.  Verify that the version of VRTSvcs is 5.0 MP3. 
    On each system, type:

	# pkginfo -l VRTSvcs
    Output should resemble the following:
   PKGINST:  VRTSvcs
      NAME:  Veritas Cluster Server by Symantec
  CATEGORY:  system
      ARCH:  i386
   VERSION:  5.0
   BASEDIR:  /
    VENDOR:  Symantec Corporation
      DESC:  Veritas Cluster Server by Symantec
    PSTAMP:  Veritas-5.0MP3-08/29/08-16:43:00
  INSTDATE:  Oct 17 2008 12:07
    STATUS:  completely installed
     FILES:      174 installed pathnames
                  27 shared pathnames
                   4 linked files
                  50 directories
                  88 executables
              153779 blocks used (approx)

6. Stop the cluster on all nodes. If the cluster is writable, you may
   close the configuration before stopping the cluster.

	# haconf -dump -makero

   From one node, execute the following command.

	# hastop -all -force

   Verify that the cluster is stopped on all nodes 
   by running the ha command.

	# hasys -state

   On all nodes, make sure that both had & hashadow processes are stopped.
   Also, stop the VCS CmdServer on all nodes. 
   Determine the PID of the CmdServer and enter:
        # kill -9 <PID>

7. Change directory to the patch location.

8. On each node in the cluster, install the patch that corresponds to the 
   version of the operating system running:
        # cd patches
	# patchadd <patch_id>

	Install patch 139154-01.
    Output resembles:
        Checking installed patches...
	Executing prepatch script...
	Verifying sufficient filesystem capacity (dry run method)...
	Installing patch packages...
	/var/sadm/pkg
	Patch number 139154-01 has been successfully installed.
	See /var/sadm/patch/139154-01/log for details
	Patch packages installed:
	  VRTSvcs

9.  After installation is complete, verify that the patch has been installed. 
   On each system, type:   
	# showrev -p | grep <patch_id>
    The information displayed after successful installation resembles the 
    following :

	# showrev -p | grep 139154
	Patch: 139154-01 Obsoletes:  Requires: 128048-03 Incompatibles:  Packages: VRTSvcs

10. At this time, you can start cluster services on all cluster nodes.
    On one node, please verify that VCS configuration is valid.

	# hacf -verify config

    If the configuration is valid, start VCS:

	# hastart

    On all other nodes, start VCS by issuing hastart once the
    first node goes to LOCAL_BUILD or RUNNING state.

REMOVING VCS PATCH
----------------------------------------------------------------
To remove the patch from a running VCS cluster:

1.  Perform step 6 from INSTALLING THE PATCH procedure.

2.  On each node in the cluster, type the following command:

	# patchrm <patch_id>
3.  Verify that the patch has been removed from each system. 
	# showrev -p | grep 139154

	It should not list the patch on this system.

4. Restart the cluster by following step 10 from INSTALLING THE PATCH
   procedure.