* * * READ ME * * *
                * * * Symantec Cluster Server 6.1 * * *
                      * * * Patch 6.1.0.028 * * *
                         Patch Date: 2017-02-06


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.1 Patch 6.1.0.028


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
Windows Server 2008 R2 X64
Windows 2012 X64
Windows Server 2012 R2 X64



BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Symantec Cluster Server 6.1
   * Symantec Storage Foundation HA 6.1


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: Patch_6_1_00028_3910006
* 3910006 (3910307) Issue 1: The status of a Symantec Cluster Server (VCS) cluster is displayed incorrectly on the Veritas Operations Manager interface.
Issue 2: CP4 and CP5 post-install tasks take a long time to complete or fail.


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

Patch ID: Patch_6_1_00028_3910006

* 3910006 (Tracking ID: 3910307)

SYMPTOM:
Issue 1: Even though a cluster is online and active, its information is displayed incorrectly on the Veritas Operations Manager interface.
Issue 2: After any one of the following patches is installed, the VCS engine fails to start on a local node:
- Hotfix_6_1_00018_3856596
- CP4  
- CP5

DESCRIPTION:
Issue 1: Veritas Operations Manager runs the HA commands to discover a cluster and its details. The HA commands from Veritas Operations Manager  work with the default %VCS_HOME% path, so they fail if VCS is installed at a custom location. Thus, when VCS is installed at a custom location, Veritas Operations Manager is unable identify its correct status.
Issue 2: An error message in the engine_A.log file indicates that the local node has left the cluster due to a difference in the VCS engine version. This issue occurs due to a version mismatch between the VCS engine on the upgraded node and the non-upgraded nodes. The engine version on the upgraded nodes is incorrectly set to 7.0.

RESOLUTION:
Issue 1: This patch addresses the issue by updating the HA executables to identify the home directory location from the appropriate registry key instead of the default %VCS_HOME% path.
Issue 2: This patch corrects the VCS engine version that was shipped in the hotfix 'Hotfix_6_1_00018_3856596' and the cumulative patches CP4 and CP5 from 7.0 to 6.1.

NOTE: You do not need to restart the system after installing this patch.

FILE / VERSION:
haagent.exe/6.1.28.315
haalert.exe/6.1.28.315
haattr.exe/6.1.28.315
hacf.exe/6.1.28.315
hacli.exe/6.1.28.315
haclus.exe/6.1.28.315
haconf.exe/6.1.28.315
had.exe/6.1.28.315
hadebug.exe/6.1.28.315
hagrp.exe/6.1.28.315
hadiscover.exe/6.1.28.315
hahb/6.1.28.315
halog/6.1.28.315
hamsg/6.1.28.315
hareg/6.1.28.315
hares/6.1.28.315
hashadow/6.1.28.315
hasite/6.1.28.315
hastart/6.1.28.315
hastatus/6.1.28.315
hastop/6.1.28.315
hasys/6.1.28.315
hatype/6.1.28.315
hauser/6.1.28.315
hanotify/6.1.28.315



INSTALLING THE PATCH
--------------------
This package contains self-extracting files that are specific to the processor architecture and operating system version.
Download the appropriate hotfix executable to a temporary location on your system.
You can install this hotfix using the GUI or the CLI. Instructions for both these options are provided below.


To install the hotfix on server systems using the GUI
---------------------------------------------------------------------------
1. Double-click the hotfix executable file to extract its contents to a default location on the cluster node.
By default, the files are extracted to:
"%programfiles(x86)%\Common Files\Veritas Shared\WxRTPrivates"

The Hotfix Installer Wizard is automatically launched after the files are extracted.

2. Click "Next" on the Welcome screen. 
The 'Hotfix Installation Task' screen lists the tasks that are performed by the installer.

3. Click "Install Hotfix" to begin the hotfix installation. 
The status of each installation task is updated as it completes.

4. After the tasks are complete, click "Next" and then click "Finish" to complete the installation process.

5. If this is a clustered configuration (VCS or MSCS), perform steps 1-4 on all additional nodes in the cluster.


To install the hotfix on server systems using the CLI
---------------------------------------------------------------------------
1. Navigate to the following location at the command prompt:
"C:\temp"

2. Run one of the following commands to extract the hotfix files to the default location:
<Hotfix_BuildVersion_IncidentNumber_OS_Platform> .exe /x
or
<Hotfix_BuildVersion_IncidentNumber_OS_Platform> .exe /extract

3. Navigate to the default location where the hotfix files are extracted.
By default, the files are extracted to:
"%programfiles(x86)%\Common Files\Veritas Shared\WxRTPrivates\<Hotfix_BuildVersion_IncidentNumber> "

4. Run the following command to install the hotfix:
VxHF.exe /install:<Hotfix_BuildVersion_IncidentNumber>  /silent
Here, <Hotfix_BuildVersion_IncidentNumber> is the name of the hotfix file excluding the OS, platform, and .exe extension.

5. To complete the hotfix installation, follow the instructions that are displayed at the command prompt.

6. If this is a clustered configuration (VCS or MSCS), perform steps 1-5 on all additional nodes in the cluster.


REMOVING THE PATCH
------------------
Additional Notes
------------------------
- To confirm the installation of a hotfix, run the following command:
vxhf.exe /list

On server systems, vxhf.exe is located at:
"%programfiles(x86)%\Common Files\Veritas Shared\WxRTPrivates\<Hotfix_BuildVersion_IncidentNumber> "

The output of this command lists the hotfixes installed on a system.

- The hotfix installer (vxhf.exe) creates and stores logs at:
"%allusersprofile%\Application Data\Veritas\VxHF"

- For general information about the hotfix installer (vxhf.exe), refer to the following technote:
http://www.veritas.com/docs/TECH73446

- To view a list of hotfixes already installed on a system, refer to the steps mentioned in the following technote: 
http://www.veritas.com/docs/TECH73438

- For information on uninstalling a hotfix, refer to the steps mentioned in the following technote: 
http://www.veritas.com/docs/TECH73443


SPECIAL INSTRUCTIONS
--------------------
DISCLAIMER: This fix is provided without warranty of any kind including the warranties of title or implied warranties of merchantability, fitness for a particular purpose and non-infringement. Veritas disclaims all liability relating to or arising out of this fix. It is recommended that the fix be evaluated in a test environment before implementing it in your production environment. When the fix is incorporated into an InfoScale for Windows maintenance release, the resulting Hotfix or Service Pack must be installed as soon as possible. Veritas Technical Services will notify you when the maintenance release (Hotfix or Service Pack) is available if you sign up for notifications from the Veritas support site http://www.veritas.com/support and/or from Services Operations Readiness Tools (SORT) http://sort.veritas.com.


OTHERS
------
NONE