* * * READ ME * * *
             * * * Veritas Cluster Server 5.1 SP1 RP3 * * *
                         * * * P-patch 1 * * *
                         Patch Date: 2012-12-05


This document provides the following information:

   * PATCH NAME
   * PACKAGES AFFECTED BY THE PATCH
   * BASE PRODUCT VERSIONS FOR THE PATCH
   * OPERATING SYSTEMS SUPPORTED BY THE PATCH
   * INCIDENTS FIXED BY THE PATCH
   * INSTALLATION PRE-REQUISITES
   * INSTALLING THE PATCH
   * REMOVING THE PATCH


PATCH NAME
----------
Veritas Cluster Server 5.1 SP1 RP3 P-patch 1


PACKAGES AFFECTED BY THE PATCH
------------------------------
VRTSvxfen


BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Veritas Cluster Server 5.1 SP1
   * Veritas Storage Foundation for Oracle RAC 5.1 SP1
   * Veritas Storage Foundation Cluster File System 5.1 SP1
   * Veritas Storage Foundation High Availability 5.1 SP1
   * Veritas Storage Foundation Cluster File System for Oracle RAC 5.1 SP1
   * Symantec VirtualStore 5.1 SP1


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
RHEL5 x86-64


INCIDENTS FIXED BY THE PATCH
----------------------------
This patch fixes the following Symantec incidents:

Patch ID: 5.1.133.100

* 3009882 (Tracking ID: 3002932)

SYMPTOM:
vxfen module fails to stop when you manually restart a node by issuing 
the shutdown -r now command

DESCRIPTION:
You cannot stop the vxfen module by restarting the node if any of 
its client processes, such as Veritas Cluster Server and so on, are running. 
Typically, a node reboot stops all the client processes of vxfen and 
subsequently stops the vxfen module. For some reason if the node restart does 
not stop the client processes, then the attempt to stop vxfen module also fails 
because client processes are still running.

RESOLUTION:
Symantec has implemented a retry logic such that after a node 
restart happens the vxfen module periodically tries to   stop itself for a 
specific number of times. The retry  logic gives client processes enough time 
to stop.


INSTALLING THE PATCH
--------------------
Perform the following steps on each cluster node, one node at a time:

1. Stop VCS:
# hastop -local

2. Stop vxfen:
# /etc/init.d/vxfen stop

3. Apply the patch:
# rpm -Uvh VRTSvxfen-5.1.133.100-SP1RP3P1_RHEL5.x86_64.rpm

Verify that proper VRTSvxfen is installed:
# rpm -qi VRTSvxfen
Name        : VRTSvxfen                    Relocations: (not relocatable)
Version     : 5.1.133.100                       Vendor: Symantec Corporation
Release     : SP1RP3P1_RHEL5                   Build Date: Fri 30 Nov 2012 05:13:32 PM IST
Install Date: Fri 30 Nov 2012 05:13:32 PM IST      Build Host: snapper53-64.engba.symantec.com
Group       : Applications/System           Source RPM: VRTSvxfen-5.1.133.100-SP1RP3P1_RHEL5.src.rpm
Size        : 1571215                          License: Symantec Proprietary
Signature   : (none)
Packager    : Enterprise_Support@symantec.com
URL         : http://www.symantec.com/business/support
Summary     : Veritas I/O Fencing by Symantec
Description :
Supported kernel(s): 2.6.18-128.el5
Build Stamp        : Veritas-5.1.133.100-SP1RP3P1-2012-11-30_01.12.17

4. Start vxfen:
# /etc/init.d/vxfen start

5. Start VCS:
# hastart


REMOVING THE PATCH
------------------
Perform the following steps on each node one at a time:

1. Stop VCS:
# hastop -local

2. Stop vxfen:
# /etc/init.d/vxfen stop

3. Uninstall VRTSvxfen package:
# rpm -ev VRTSvxfen

4. Install previous version of VRTSvxfen package.

5. Start vxfen:
# /etc/init.d/vxfen start

6. Start VCS:
# hastart


SPECIAL INSTRUCTIONS
--------------------
NONE


OTHERS
------
NONE