* * * READ ME * * *
          * * * Veritas Co-ordination Point Server 6.2.1 * * *
                         * * * Patch 300 * * *
                         Patch Date: 2017-09-27


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 Co-ordination Point Server 6.2.1 Patch 300


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


PACKAGES AFFECTED BY THE PATCH
------------------------------
VRTScps


BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Symantec Cluster Server 6.2
   * Symantec Storage Foundation Cluster File System HA 6.2
   * Symantec Storage Foundation for Oracle RAC 6.2
   * Symantec Storage Foundation HA 6.2


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: 6.2.1.300
* 3926490 (3930936) Some CP server operations cannot simultaneously handle 
writes from multiple clients.
Patch ID: 6.2.1.200
* 3930633 (3862152) The log messages at the CP server must contain a reference to
node that requested the operation and the size of CPS log file should be more.
Patch ID: 6.2.1.100
* 3919629 (3920058) CP server does not boot up if it starts on a port which is
not in the dynamic port range (49152-65535).


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

Patch ID: 6.2.1.300

* 3926490 (Tracking ID: 3930936)

SYMPTOM:
The CP Server logs errors about operation failures when multiple clients of CP
server run similar commands in parallel. These operation errors are flagged as
CRITICAL.

DESCRIPTION:
When clients of CP servers run multiple commands in parallel, sometimes, such
operations return the value SQLITE_BUSY to the client. The operation returns
SQLITE_BUSY, because another operation has locked the database. In such case
where operation fails due to database lock being busy the server does not 
retry
these commands.

RESOLUTION:
The VxCPS program is modified to handle a SQLITE_BUSY value and the program
retries the operation on the server.

Patch ID: 6.2.1.200

* 3930633 (Tracking ID: 3862152)

SYMPTOM:
The messages logging cps actions at the CP server end do not show which node has
requested the actions. The size of CP server log files could only be increased
up to 4 GB which is a problem when the CP server has many clients.

DESCRIPTION:
The Log messages for certain cps actions do not log the peer node that requested
the action due to the logging being reduced at the cp server end. The size of CP
server log files could only be increased to up to 4 GB that led to loss of logs.

RESOLUTION:
The logging at the CP server is reduced.The CPS code is modified to log the peer
node name when any actions are requested for the CP server and CPS log file size
can be increased to up to 16 GB

Patch ID: 6.2.1.100

* 3919629 (Tracking ID: 3920058)

SYMPTOM:
CP server does not boot up if it starts on a port which is not in the 
dynamic port range (49152-65535).

DESCRIPTION:
If you attempt to start the CP server on a valid port not in the TCP dynamic port
range (49152-65535), the CP server configuration fails. Restrictions in the
VxCPS code does not allow configuring CP server on a port that is not in the
dynamic port range.

RESOLUTION:
The VxCPS code is modified to allow the configuration if the TCP port on which
CP server starts is in the range 1-65535.



INSTALLING THE PATCH
--------------------
Run the Installer script to automatically install the patch:
-----------------------------------------------------------
Please be noted that the installation of this P-Patch will cause downtime.

To install the patch perform the following steps on at least one node in the cluster:
1. Copy the patch cps-rhel7_x86_64-Patch-6.2.1.300.tar.gz to /tmp
2. Untar cps-rhel7_x86_64-Patch-6.2.1.300.tar.gz to /tmp/hf
    # mkdir /tmp/hf
    # cd /tmp/hf
    # gunzip /tmp/cps-rhel7_x86_64-Patch-6.2.1.300.tar.gz
    # tar xf /tmp/cps-rhel7_x86_64-Patch-6.2.1.300.tar
3. Install the hotfix(Please be noted that the installation of this P-Patch will cause downtime.)
    # pwd /tmp/hf
    # ./installVRTScps621P3 [<host1> <host2>...]

You can also install this patch together with 6.2.1 maintenance release using Install Bundles
1. Download this patch and extract it to a directory
2. Change to the Veritas InfoScale 6.2.1 directory and invoke the installmr script
   with -patch_path option where -patch_path should point to the patch directory
    # ./installmr -patch_path [<path to this patch>] [<host1> <host2>...]

Install the patch manually:
--------------------------
Install VRTScps on  CP server:
1. Run the following command on any node of CP server cluster to stop HAD service .
# hastop -local -force 
2. Perform this step on all nodes of the CP server cluster. Go to the directory where the patch is downloaded and run the following command.
# rpm -Uvh VRTScps-6.2.1.300-RHEL7.i686.rpm
3. Start HAD again on the node where it was previously running.
# hastart -onenode


REMOVING THE PATCH
------------------
Uninstall the patch

Uninstall VRTScps on  CP server:
1. Run the following command on any node of CP server cluster to stop HAD.
# hastop -local -force
2. Perform these steps on all nodes of the CP server cluster.
i. Uninstall VRTScps package:
# rpm -ev VRTScps
ii. Install previous version of VRTScps package from the original source media.
3. Start HAD again on the node where it was previously running.
# hastart 
or
# hastart -onenode


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


OTHERS
------
NONE