OS: Linux
OS Version: SLES9 (x86_64)
Fixes Applied for Products:
	VRTSgab - Veritas Group Membership and Atomic Broadcast By Symantec

Additional Instructions:
Please read the instructions below before installing the patch.

       PATCH GAB 5.0MP3RP2HF2 for VRTSgab on 5.0MP3RP2
======================================================================

 Patch Date:  September, 2009

This README provides information on:
 * BEFORE GETTING STARTED
 * CRC AND BYTE COUNT
 * FIXES AND ENHANCEMENTS INCLUDED IN THE PATCH
 * PACKAGES AFFECTED BY THE PATCH
 * INSTALLING THE PATCH
 * UNINSTALLING THE PATCH


BEFORE GETTING STARTED:
----------------------
This patch applies only to:
	VRTSgab 5.0MP3RP2 running on Linux (RHEL5 x86_64)

Ensure that you are running the supported configurations before
installing this patch.


CRC AND BYTE COUNT:
------------------
Ensure that the patch file you have downloaded matches the following
checksum and byte count.

The following command can be used to ascertain this:
# cksum VRTSgab-5.0.30.22-MP3RP2HF2_SLES9.x86_64.rpm
3727887430	1347089	VRTSgab-5.0.30.22-MP3RP2HF2_SLES9.x86_64.rpm


FIXES AND ENHANCEMENTS INCLUDED IN THE PATCH: 
--------------------------------------------
Etrack Incidents: 1831944, 1792341, 1509742

SDR's of Fixed Symantec Incidents:
----------------------------------
Symantec Incident : 1831944
Symptom:
	One cannot tune the GAB kernel tunable gab_conn_wait at 
	module load time.
Defect Description:
	There is no mechanism in the GAB init script to tune the 
	kernel tunable gab_conn_wait at module load time.
Resolution:
	Enhance the GAB init script to allow tuning the kernel tunable 
	gab_conn_wait at module load time.

Symantec Incident : 1792341
Symptom:
	GAB userland client hangs.
Description:
	GAB clients like vxconfigd may hang if GAB misses to send it the
	necssary poll wakeup. When a client uses poll to wait for a GAB message
	to arrive, GAB has to check if there are any messages to be read. If
	not, it must remember that this process has to be woken up when a new
	message arrives. However, if a message arrives in the window between
	the above two steps, the wakeup can be missed.
Resolution:
	The above window has been eliminated.


SDR's of Superseded Patch:
--------------------------

Symantec Incident : 1509742
Symptom:
	Clients of the GAB service may not get cluster membership.
Defect Description:
	Symantec recommends that GAB must be configured to provide 
	membership only	after a minimum quorum number of nodes join 
	the cluster. If a client of GAB comes up before GAB Port a formed 
	membership on that node, then this client may not get cluster 
	membership until it starts up on at least the (configured) quorum 
	number of nodes, not even if Port a or any other 
	GAB Ports receive cluster membership.
Resolution:
	Once GAB port a membership is delivered on a particular node, 
	GAB now waits for the (configured) gab_stable_timeout and 
	automatically starts the membership calculation for all ports 
	for which that node is the lowest node id.


PACKAGES AFFECTED BY THE PATCH:
-------------------------------
This patch updates the following VCS package:
	VRTSgab from 5.0MP3RP2(5.0.30.20) or higher to 5.0MP3RP2HF2 (5.0.30.22)


INSTALLING THE PATCH:
--------------------
This patch must be installed after installing Veritas Cluster Server 5.0MP3RP2.
The following steps should be run on all nodes in the VCS cluster:

Stopping VCS on the cluster node:
--------------------------------
1. Log on as superuser on the system on which the point patch is to be
   installed.

2. Presistently freeze that node in VCS:
	# /opt/VRTSvcs/bin/haconf -makerw
	# /opt/VRTSvcs/bin/hasys -freeze [nodename] -persistent
	# /opt/VRTSvcs/bin/haconf -dump -makero

3. Stop all clients of GAB. For example:
   a) For VCS, run the following command:
        # /etc/init.d/vcs stop

   b) For VxFEN:
        # /etc/init.d/vxfen stop

   Take care to also shutdown any components dependant on these clients.
   Take care to observe correct order.

4. Stop GAB:
        # /etc/init.d/gab stop

5. Stop LLT:
        # /etc/init.d/llt stop

Installing the Patch:
--------------------
1. Un-compress the downloaded patch from Symantec.
   Change directory to the unzipped patch location.
   Install the VRTSgab 5.0.30.22 patch using the following command:
	# rpm -Uvh VRTSgab-5.0.30.22-MP3RP2HF2_SLES9.x86_64.rpm

2. Verify that the new patch has been installed:
	# rpm -q VRTSgab

   You will find the following output on display with the patch 
   installed properly:
	VRTSgab-5.0.30.22-MP3RP2HF2


Re-starting VCS on the cluster node:
-----------------------------------
1. Start LLT by using the following command:
        # /etc/init.d/llt start

2. Start GAB by using the following command:
        # /etc/init.d/gab start

3. Start all the stopped GAB clients. For example:
   a) For VxFEN, run the following command:
       # /etc/init.d/vxfen start

   b) For VCS, run the following command:
        # /etc/init.d/vcs start

   Take care to also bring up any components that are dependent on the clients
   that were stopped in step 3. Take care to observe correct order.

4. Persistently unfreeze the system in VCS:
	# /opt/VRTSvcs/bin/haconf -makerw
	# /opt/VRTSvcs/bin/hasys -unfreeze [nodename] -persistent
	# /opt/VRTSvcs/bin/haconf -dump -makero

UNINSTALLING THE PATCH:
-----------------------
Un-install the GAB patch from each node following the steps given below:

Steps to remove the Patch from a cluster node:
---------------------------------------------
1. Follow the steps provided under "Stopping VCS on the cluster node" 
   section above, to stop VCS on the node & unload any drivers, as required.

2. Remove the patch by the following command:
	# rpm -e --nodeps VRTSgab

3. Verify that the patch has been removed from the system:
	# rpm -q VRTSgab
   You should see output similar to:
	package VRTSgab is not installed

4. Install VRTSgab package from VCS 5.0MP3 Installer CD 
   and upgrade to GAB 5.0MP3RP2 or higher.

5. Restart the node following the steps under 
   "Re-starting VCS on the cluster node" section above.