OS: Linux
OS Version: SLES9 ( x86_64 )
Fixes Applied for Products:
	VRTSvxfen - Veritas I/O Fencing by Symantec

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

 PATCH VxFEN 5.0 MP3 RP2 HF1 for VxFEN 5.0 MP3 RP2 (Linux)
=============================================================

 Patch Date:  Aug, 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 only applies to:
	VxFEN 5.0 MP3 RP2 running on Linux (SLES9 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 VRTSvxfen-5.0.30.21-MP3RP2HF1_SLES9.x86_64.rpm
3698281067	1471978	VRTSvxfen-5.0.30.21-MP3RP2HF1_SLES9.x86_64.rpm


FIXES AND ENHANCEMENTS INCLUDED IN THE PATCH: 
--------------------------------------------
Etrack Incidents: 1779129

SDR's of Fixed Symantec Incidents:
--------------------------------
Symantec Incident : 1779129
Symptom:
  The command "/etc/init.d/vxfen stop" fails with the error in console :
     "ERROR: failed to stop vxfen" 
  and the following error appears in /var/VRTSvcs/log/vxfen/vxfen.log:
     "VXFEN vxfenconfig ERROR V-11-2-1071 Ioctl VXFEN_IOC_CLUSTSTAT failed!"
Defect Description:
  VxFEN was using a variable without proper memory allocation. The problem 
  occurred when, the variable failed to store a large amount of data, 
  due to its size limitation. Hence, recovering information correctly 
  from the variable was not possible and the error messages are seen.
Resolution:
  The variable now have proper memory allocation.

PACKAGES AFFECTED BY THE PATCH:
-------------------------------
This patch updates the following VCS package(s) 
	VxFEN from 5.0MP3RP2 (5.0.3.20) to 5.0MP3RP2HF1 (5.0.3.21)

INSTALLING THE PATCH:
--------------------
The following steps should be run on all nodes in a VCS cluster:

Stopping VCS on the cluster node:
--------------------------------
1. Verify that /opt/VRTSvcs/bin is set in the PATH variable 
   so you can execute all VCS commands.

2. Ensure that none of the service groups are online on this system.
2a. For each failover group online on this sytem, switch over 
    the service group to a node that is running:
        # hagrp -switch [service_group] -to [node]
2b. Offline every parallel group online on this system:
	# hagrp -offline [service_group] -sys [this_node]

3. Make the VCS configuration writable. On a node that you want 
   to upgrade, type:
        # haconf -makerw

4. Freeze the service group operations. Perform this task on each node 
   if you had selected a group of nodes to upgrade:
        # hasys -freeze -persistent [node]

5. Make the VCS configuration read-only:
        # haconf -dump -makero

6. Stop VCS, using the following command, in each node in 
   the group that is being upgraded:
        # hastop -local

7. Stop the VCS command server:
       # killall CmdServer

8. Stop VxFEN module using the following command:
	# /etc/init.d/vxfen stop

9. If the above command fails to stop VxFen module with symptoms
   documented in the "Symptom" section, then follow the steps mentioned
   below for the same:
   To remove vxfen script from all the run-levels for next boot, 
   run the following command as appropriate on all nodes:
	For RHEL:
		# chkconfig --del vxfen
	For SUSE:
		# insserv -r vxfen
   Reboot the node, which will stop vxfen from running in any run-level.
   Note that a forced reboot may be necessary. Also, if VCS was
   configured to make use of fencing (Cluster Attribute "UseFence" set to
   "SCSI3"), the "had" process will not come up immediately after the
   reboot. This is expected.


Installing the Patch:
--------------------
1. Gunzip & untar the downloaded patch from Symantec.
   Change directory to the unzipped patch location. 
   Install the VxFEN 5.0MP3RP2HF1 patch using the following command:
	# rpm -Uvh VRTSvxfen-5.0.30.21-MP3RP2HF1_SLES9.x86_64.rpm

2. Verify that the new patch has been installed:
	# rpm -qa | grep VRTSvxfen
   You will find the following output on display with 
   the patch installed properly:
	VRTSvxfen-5.0.30.21-MP3RP2HF1_[OS Version]

Re-starting VCS on the cluster node:
-----------------------------------
1. Re-start VxFEN on the node using the command :
	# /etc/init.d/vxfen start

2. If VCS was configured to make use of fencing, a re-start of VCS is
   required :
	# /etc/init.d/vcs start

3. Make the VCS configuration writable. Run the following command 
   from any node in the upgraded group.
        # haconf -makerw

4. Unfreeze the service group operations. Perform this task on 
   each node if you had upgraded a group of nodes.
        # hasys -unfreeze -persistent [node]

5. Make the configuration read-only.
        # haconf -dump -makero

6. Start the parallel service groups that were stopped as part of step 2a.
	# hagrp -online [service_group] -sys [this_node]

7. Switch back the service group to the original node.
        # hagrp -switch [service_group] -to [node]

For each cluster node, repeat all the steps above, starting with Step 1
of subsection "Stopping VCS on the cluster node".

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

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

2. Remove the package by the following command:
	# rpm -e VRTSvxfen

3. Verify that the patch has been removed from the system:
	# rpm -qa | grep VRTSvxfen
   There will be no result displayed at the console.

4. Install VRTSvxfen package from VCS 5.0MP3 Installer CD 
   and upgrade to VxFEN 5.0MP3RP2.

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