Date: 2008-10-21
OS: Linux
OS Version - RHEL4 U3+, RHEL5 U1+, SLES9 SP3+, SLES10 SP1+
RPMs: VRTSvcs
Etrack Incidents: 1404384, 1397692
=========================================================================
* * * READ ME - VERITAS CLUSTER SERVER 5.0 MP3 - VCS Engine HOT FIX * * *

                   Patch Date:  October 21, 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

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.0MP1 or earlier, you do not need this patch. 

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

    README (this file)

    VRTSvcs-5.0.30.01-MP3HF1_RHEL4.i686.rpm for RHEL4
    VRTSvcs-5.0.30.01-MP3HF1_RHEL5.i686.rpm for RHEL5
    VRTSvcs-5.0.30.01-MP3HF1_SLES9.i586.rpm for SLES9
    VRTSvcs-5.0.30.01-MP3HF1_SLES10.i586.rpm for SLES10

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

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

SUPPORTED OPERATING SYSTEMS
---------------------------
    Linux - RHEL4 U3+, RHEL5 U1+, SLES9 SP3+, SLES10 SP1+

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 required RPM to a directory on your system:

	# cp <patch.rpm> .

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

3.  Verify that the version of VRTSvcs is 5.0 MP3. Here is the output of rpm -qi.
 
    On each system, type:

	# rpm -qi VRTSvcs-5.0.30.00-MP3_RHEL4
	Name        : VRTSvcs                      Relocations: (not relocatable)
	Version     : 5.0.30.00                         Vendor: Symantec Corporation
	Release     : MP3_RHEL4                     Build Date: Wed 16 Jul 2008 04:24:10 AM PDT
	Install Date: Tue 21 Oct 2008 11:04:06 AM PDT      Build Host: chaparral.engba.veritas.com
	Group       : System/High Availability      Source RPM: VRTSvcs-5.0.30.00-MP3_RHEL4.src.rpm
	Size        : 96876304                         License: Copyright (c) 2008 Symantec and the 
	Symantec Logo are trademarks or registered trademarks of Symantec Corporation or its affiliates 
	in the U.S. and other countries. Other names may be trademarks of their respective owners. The 
	Licensed Software and Documentation are deemed to be commercial computer software as defined in 
	FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19 "Commercial 
	Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in Commercial Computer Software 
	or Commercial Computer Software Documentation", as applicable, and any successor regulations. Any 
	use, modification, reproduction release, performance, display or disclosure of the Licensed 
	Software and Documentation by the U.S. Government shall be solely in accordance with the terms 
	of this Agreement.
	Signature   : (none)
	URL         : www.support.veritas.com
	Summary     : Veritas Cluster Server by Symantec
	Description :
	Veritas Cluster Server and Commands by Symantec (i686)
	Build Stamp : Veritas-5.0-2008-07-16_02.01.00

4. Freeze all the service groups persistently. 
    # haconf -makerw
    # hagrp -freeze <group> -persistent

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

   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:
        # CmdServer -stop

6. Change directory to the patch location.

7. On each node in the cluster, install the patch that corresponds to the 
    version of the operating system running. We need to use -U and not -i 
    as it is rpm upgrade.: 
    
	# rpm -Uvh <patch.rpm>

	For RHEL4, install VRTSvcs-5.0.30.01-MP3HF1_RHEL4.i686.rpm
	For RHEL5, install VRTSvcs-5.0.30.01-MP3HF1_RHEL5.i686.rpm
	For SLES9, install VRTSvcs-5.0.30.01-MP3HF1_SLES9.i586.rpm
	For SLES10, install VRTSvcs-5.0.30.01-MP3HF1_SLES10.i586.rpm
	

8. After installation is complete, verify that the patch has been installed. 
   For example on each RHEL4 system, type:   
    
	# rpm -qa  | grep VRTSvcs-5.0.30.01-MP3HF1_RHEL4

   You will see output like,
	VRTSvcs-5.0.30.01-MP3HF1_RHEL4

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

10. Unfreeze all the groups.
    # haconf -makerw
    # hagrp -unfreeze <group> -persistent
    # haconf -dump -makero