* * * READ ME * * *
    * * * Veritas Group Membership and Atomic Broadcast 6.2.1 * * *
                         * * * Patch 300 * * *
                         Patch Date: 2016-04-28


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 Group Membership and Atomic Broadcast 6.2.1 Patch 300


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


PACKAGES AFFECTED BY THE PATCH
------------------------------
VRTSgab


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


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: 6.2.1.300
* 3875807 (3875805) In some rare cases, if a few unicast messages are stuck in 
the Group Membership Atomic Broadcast (GAB) receive queue of a port, the port 
might receive a GAB I/O fence message.


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

Patch ID: 6.2.1.300

* 3875807 (Tracking ID: 3875805)

SYMPTOM:
A port on a node receives an I/O fence message when the membership for that 
port changes. This is caused by some unicast messages being stuck in the GAB 
receive queue of that port.

DESCRIPTION:
Under certain rare situation, a few unicast messages which belong to a future 
generation get stuck in the GAB receive queue of a port. This causes unintended 
consequences like preventing a RECONFIG message from being delivered to that 
port. In this case, the port receives an I/O fence message from the GAB to 
ensure the consistency in membership.

RESOLUTION:
The code is modified to ensure that the unicast messages belonging to future 
generation are never left pending in the GAB receive queue of a port.



INSTALLING THE PATCH
--------------------
Run the Installer script to automatically install the patch:
-----------------------------------------------------------
To install the patch perform the following steps on at least one node in the cluster:
1. Copy the patch gab-sles12_x86_64-Patch-6.2.1.300.tar.gz to /tmp
2. Untar gab-sles12_x86_64-Patch-6.2.1.300.tar.gz to /tmp/hf
    # mkdir /tmp/hf
    # cd /tmp/hf
    # gunzip /tmp/gab-sles12_x86_64-Patch-6.2.1.300.tar.gz
    # tar xf /tmp/gab-sles12_x86_64-Patch-6.2.1.300.tar
3. Install the hotfix
    # pwd /tmp/hf
    # ./installVRTSgab621P3 [<host1> <host2>...]

Install the patch manually:
--------------------------
Perform the following steps on the node on which this patch is being applied:
1. Take backup of your configurations
2. Stop VCS
3. Install the patch
4. Restart VCS on the node

Stopping VCS on the cluster node
--------------------------------

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

2. Freeze all the service groups persistently.
        # haconf -makerw
        # hagrp -freeze [group] -persistent

3. If the cluster is writable, you may close the configuration before stopping the cluster. 
   Stop the cluster on this node:
        # haconf -dump -makero

   Run the following command:
        # hastop -local
    
   Verify that the cluster is stopped by running the ha command:
        # hasys -state

   Make sure that both had and hashadow processes are stopped. Also, stop the VCS CmdServer:
        # CmdServer -stop

4. Stop the cluster services in order:
    - For AMF:
    # /etc/init.d/amf stop
    - For VxFEN:
    # /etc/init.d/vxfen stop
    - For GAB:
    # /etc/init.d/gab stop
    
    
Note: Stop any other services depending on GAB before stopping gab.

Installing the Patch
--------------------

1. Un-compress the downloaded patch from Symantec and change the directory to the uncompressed patch location.
   Install the patch using the following command:

    - For GAB:
    # rpm -Uvh VRTSgab-6.2.1.300-SLES12.x86_64.rpm

2. Run the following command to verify if the new patch has been installed:

    - For GAB:
    # rpm -q VRTSgab
        
   If the proper patch is installed, the following output is displayed:

    - For GAB:
    VRTSgab-6.2.1.300-SLES12.x86_64
                        
Re-starting the cluster services:
--------------------------------

1. To start the cluster services in order run the following command:
    - For GAB:
        # /etc/init.d/gab start
    - For VxFEN:
        # /etc/init.d/vxfen start
    - For AMF:
        # /etc/init.d/amf start
    - For VCS:
        # hastart
        # /opt/VRTSvcs/bin/CmdServer

2. Make VCS cluster writable:
         # haconf -makerw

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


REMOVING THE PATCH
------------------
Removal of the patch will result in removing the whole package
from the system/node. To go back to a previous installed version
of the package, you may need to re-install the package.
Run the following steps on the node where the patch is being uninstalled:

To remove the patch from a cluster node:
---------------------------------------------
1. Freeze all the service groups persistently.
        # haconf -makerw
        # hagrp -freeze [group] -persistent

2. Stop VCS on the node by running the following command:
    - Follow the stop sequence as mentioned in the PATCH INSTALLATION section.

3. Remove the patch by using the following command:
    - For GAB:
        # rpm -e VRTSgab



4. Verify that the patch has been removed from the system:
    - For GAB:
        # rpm -qa|grep VRTSgab
        
   Ensure that the package is not be displayed. This confirms that the package is removed.

5. Install the relevant package from the VCS base media. 
    Also refer to SORT for any applicable patches.

6. To start the cluster service, run the following command first on one node:
    - Follow the start sequence as mentioned in the PATCH INSTALLATION section.

7. Unfreeze all the groups.
         # hagrp -unfreeze [group] -persistent
         # haconf -dump -makero


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


OTHERS
------
NONE