* * * READ ME * * *
               * * * Symantec Cluster Server 6.2.1 * * *
        * * * Patch 100 (Add RHEL 7 Update 1 and 2 support)* * *
                         Patch Date: 2016-04-07


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
----------
Symantec Cluster Server 6.2.1 Patch 100 (Add RHEL 7 Update 1 and 2 support)


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


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


BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Symantec Application HA 6.2
   * 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: VRTSvcs-6.2.1.100-RHEL7
* 3869873 (3869872) HAD (High Availability Daemon) starts in 'user.slice' after the 'hastart' operation.
Patch ID: VRTSvcsea-6.2.1.100-RHEL7
* 3871617 (3871614) With HAD in user.slice, Oracle (or applications) are not shut down gracefully during system reboot.


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

Patch ID: VRTSvcs-6.2.1.100-RHEL7

* 3869873 (Tracking ID: 3869872)

SYMPTOM:
After executing the hastart command, the HAD, hashadow and agent processes 
start in user.slice instead of system.slice.

DESCRIPTION:
After a reboot operation, HAD, hashadow, CmdServer and agent processes 
start in system.slice under vcs.service. But after executing the hastop operation 
followed by the hastart operation, CmdServer remains in 'system.slice', while HAD, 
hashadow and the agent processes wrongly start in 'user.slice'. If the system 
reboots or shuts down while HAD is in user.slice, the HAD gets killed before it can 
execute offline operations for the resources.

RESOLUTION:
The code is modified to start HAD, hashadow and agent processes under 
'system.slice'.
Note: This issue is specific to RHEL 7 Update 1 and 2

Patch ID: VRTSvcsea-6.2.1.100-RHEL7

* 3871617 (Tracking ID: 3871614)

SYMPTOM:
If HAD is running in the user.slice then during system reboot, Oracle (or its applications) running as a non-root user do not shut down gracefully.

DESCRIPTION:
On RHEL7 and SLES12, systemd is enabled. Therefore, all the processes running under user.slice are killed on system reboot. Since Oracle (or its applications) run under user.slice by default, a system reboot may cause Oracle to crash or udergo an abrupt shut down.

RESOLUTION:
Move the Oracle processes to system.slice to prevent them from an abrupt shut down during a system reboot.



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 vcs-rhel7_x86_64-Patch-6.2.1.100.tar.gz to /tmp
2. Untar vcs-rhel7_x86_64-Patch-6.2.1.100.tar.gz to /tmp/hf
    # mkdir /tmp/hf
    # cd /tmp/hf
    # gunzip /tmp/vcs-rhel7_x86_64-Patch-6.2.1.100.tar.gz
    # tar xf /tmp/vcs-rhel7_x86_64-Patch-6.2.1.100.tar
3. Install the hotfix
    # pwd /tmp/hf
    # ./installVRTSvcs621P1 [<host1> <host2>...]

Install the patch manually:
--------------------------
PATCH INSTALLATION INSTRUCTIONS:
--------------------------------
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/VRTSvcs/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. Persistently freeze all the service groups:
    # haconf -makerw
    # hagrp -freeze [group] -persistent
    # haconf -dump -makero
3. 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
4. Verify that the cluster is stopped on all nodes:
    # hasys -state
5. On all nodes, make sure that both the had and hashadow processes are stopped.
6. Stop the VCS CmdServer on all nodes:
        # /opt/VRTSvcs/bin/CmdServer -stop
7. Copy the /etc/VRTSvcs/conf/config/types.cf file to /etc/VRTSvcs/conf/config/types.cf.orig
8. Copy the /etc/VRTSvcs/conf/config/main.cf file to /etc/VRTSvcs/conf/config/main.cf.orig
Installing the patch
--------------------
To install the patch:
1. Log in as superuser on the system where you are installing the patch.
3. Uncompress the patch that you downloaded from Symantec.
3. Change the directory to the uncompressed patch location.
4. Install the patch using the following command:
        # rpm -Uvh VRTSvcs-6.2.1.100-RHEL7.i686.rpm
5. Run the following command to verify if the new patch has been installed:
        # rpm -q VRTSvcs
    If the proper patch is installed, the following output is displayed:
        VRTSvcs-6.2.1.100-RHEL7.i686
6. Run the following command to load updated scripts
        # systemctl daemon-reload
Starting VCS on the cluster node:
1. To start VCS run the following command:
        # 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
------------------
PATCH UNINSTALLATION INSTRUCTIONS:
----------------------------------
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:
    # hastop -all -force
3. Remove the patch by using the following command:
        # rpm -e VRTSvcs
4. Verify that the patch has been removed from the system:
        # rpm -qa|grep VRTSvcs
   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:
    # 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.
7. Unfreeze all the service groups:
    # haconf -makerw
    # hagrp -unfreeze [group] -persistent
    # haconf -dump -makero
8. Start the VCS CmdServer on all nodes
    # /opt/VRTSvcs/bin/CmdServer


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


OTHERS
------
NONE