* * * READ ME * * *
             * * * Veritas Cluster Server 5.1 SP1 RP4 * * *
                         * * * P-patch 1 * * *
                         Patch Date: 2015-12-16


This document provides the following information:

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


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


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
Solaris 10 SPARC
Solaris 9 SPARC


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


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


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: 152132-01
* 3810895 (3862959) Due to RSM mismatch, the service group was reported online on
multiple nodes.


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

Patch ID: 152132-01

* 3810895 (Tracking ID: 3862959)

SYMPTOM:
When a system re-joins a cluster after fault recovery, the value of the
CurrentLimits attribute on that system is not correctly reflected in the other
member nodes of the cluster, resulting in RSM mistmatch.

DESCRIPTION:
CurrentLimits is not sent as part of the engine snapshot.

RESOLUTION:
VCS engine code is modified to fix this issue. Included "CurrentLimits"
attribute in the engine snapshot as well.



INSTALLATION PRE-REQUISITES
---------------------------
VRTSvcs package


INSTALLING THE PATCH
--------------------
To install the patch perform the following steps on all nodes in the VCS cluster:

1. Stop VCS on the cluster node.
2. Install the patch.
3. Restart VCS on the node.

Stopping VCS on the cluster node
--------------------------------
To stop VCS on the cluster node:

1. Ensure that the "/opt/VRTS/bin" directory is included in your PATH environment variable so that you can execute all the VCS commands. For more information, refer to the Veritas Cluster Server Installation Guide.

2. Verify that the version of VRTSvcs is 5.1SP1RP4.

3. Persistently freeze all the service groups:
   # haconf -makerw
   # hagrp -freeze [group] -persistent
   # haconf -dump -makero

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

   On any node, run the following command to stop the cluster:
   # hastop -all -force

5. Verify that the cluster is stopped on all nodes: 
   # hasys -state

6. On all nodes, make sure that both the had and hashadow processes are stopped. 

Installing the patch
--------------------
To install the patch:

1. Log in as superuser on the system where you are installing the patch.

2. Uncompress the patch that you downloaded from Symantec.

3. Change the directory to the uncompressed patch location.
 
4. Install the patch: 
   # patchadd 152132-01

5. After the installtion completes, verify that the patch is installed.
   On each system type:
   # showrev -p | grep 152132-01

The following output is displayed if the patch
   is installed successfully:

Patch: 152132-01 Obsoletes:  Requires: 143287-09 Incompatibles:  Packages: 
VRTSvcs

Restarting VCS on the cluster node
----------------------------------
To restart VCS on the cluster node:

1. Start the cluster services on all cluster nodes. 

   # hastart

   On all the other nodes, start VCS by issuing the hastart command after the first node's state changes to LOCAL_BUILD or RUNNING.

2. Unfreeze all the service groups:
   # haconf -makerw
   # hagrp -unfreeze [group] -persistent
   # haconf -dump -makero


REMOVING THE PATCH
------------------
To remove the patch:

1. Stop VCS on the node by following the steps in the section "Stopping VCS on the cluster node".
 
2. Remove the patch:
   # patchrm 152132-01

3. After the removal completes, verify that the patch has been removed from all the system in the cluster. On each system type:
   # showrev -p | grep 152132-01

No information is displayed after the patch is removed.

4. Start the cluster services on all cluster nodes. First start VCS on 
   one node:
   # hastart

   On all the other nodes, start VCS by issuing the hastart command after the first node's state changes to LOCAL_BUILD or RUNNING.

5. Unfreeze all the service groups:
   # haconf -makerw
   # hagrp -unfreeze [group] -persistent
   # haconf -dump -makero


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


OTHERS
------
NONE