* * * READ ME * * *
                * * * Veritas Cluster Server 6.0.2 * * *
                      * * * Patch 6.0.2.100 * * *
                         Patch Date: 2014-11-11


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 6.0.2 Patch 6.0.2.100


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
Windows 2012 X64



BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Veritas Cluster Server 6.0.2


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: VCSW CP1
* 3457742 (3457733) High Availability (HA) commands take time to execute in a secure cluster.
* 3445216 (3445213) In a cluster configured to use single sign-on authentication (secure cluster), the application service group configuration wizards fail with a 
"CmdServer service not running on system:<nodename>" error.
* 3423660 (3423657) A FileShare service group faults after switching back to the node on which it was online, after the node restarts.
* 3314656 (3279413) In a network using tagged VLAN configuration, the VCS NIC agent may monitor an incorrect network interface, if the interfaces have same MAC address.
* 3314655 (3279413) In a network using tagged VLAN configuration, the VCS IP agent may assign the virtual IP address or the virtual server name to an incorrect network interface, if the interfaces have same MAC address.
* 3113889 (3111144) After every 49.7 days, VCS logs report that the GlobalCounter VCS attribute is not updated.
* 3099946 (3098019) [Issue 1] An online Lanman resource takes 1 minute or longer to go offline. [Issue 2] A newly created Lanman resource appears ONLINE even though the service group is not brought online.


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

Patch ID: VCSW CP1

* 3457742 (Tracking ID: 3457733)

SYMPTOM:
High Availability (HA) commands take long time to execute in a secure cluster.

DESCRIPTION:
Executing HA commands may take approx 5 to 7 seconds in case when PDC is located in different geographical location.  This happens because DC related APIs take long time to get completed, when they are invoked from AT for creating AT credentials.

RESOLUTION:
This issue is fixed wherein time consuming AT APIs are only invoked first time when they are executed. For subsequent execution of HA command, cached credentials are used.

To resolve the issue, 
1) Install the hotfix
2) Run HA command to see the result. For example: hagrp -list.

Binary File / Version:
haagent.exe / 6.0.20006.58
haalert.exe / 6.0.20006.58
haattr.exe  / 6.0.20006.58
hacli.exe   / 6.0.20006.58
haclus.exe / 6.0.20006.58
haconf.exe / 6.0.20006.58
hadebug.exe / 6.0.20006.58
hagrp.exe / 6.0.20006.58
hahb.exe / 6.0.20006.58
halog.exe / 6.0.20006.58
hanotify.exe / 6.0.20006.58
hareg.exe / 6.0.20006.58
hares.exe / 6.0.20006.58
hastatus.exe / 6.0.20006.58
hastop.exe / 6.0.20006.58
hasys.exe / 6.0.20006.58
hatype.exe / 6.0.20006.58
hauser.exe / 6.0.20006.58

* 3445216 (Tracking ID: 3445213)

SYMPTOM:
In a cluster configured to use single sign-on authentication (secure cluster), the application service group configuration wizards fail with a 
"CmdServer service not running on system:<nodename>" error.

DESCRIPTION:
If a cluster is configured to use single sign-on authentication (secure cluster), then the application service group configuration wizards fail to connect to the remote cluster nodes with the following error:
"CmdServer service not running on system: <nodename>"
This error is displayed even though the VCS Command Server service is running on all the nodes. 
The wizard displays the error on the System Selection panel.
The issue occurs because the remote node IP address used for its authentication is not reachable.

RESOLUTION:
This hotfix enhances the wizard behaviour.
If the IP address of the remote cluster node is not reachable, then the wizard uses the hostname to connect to the nodes.

To resolve the issue, 
1) Exit the service group configuration wizard
2) Install the hotfix
3) Run the service group configuration wizard again

Binary File / Version:
WizCmdClient.dll / 6.0.20005.57

* 3423660 (Tracking ID: 3423657)

SYMPTOM:
The FileShare service group faults after switching back to the node on which it was online before the node was restarted.

DESCRIPTION:
If the node on which a FileShare service group is online is restarted, the service group fails over successfully. However, when the node becomes available again, the FileShare service group faults after switching back to the node. This happens only if the 'Everyone' group is not given permissions on the FileShare resource.

RESOLUTION:
This hotfix resolves the issue only if the AutoControl attribute of the FileShare resource is set to True.

NOTE: After applying the hotfix, if you attempt to bring the service group online while the AutoControl attribute is set to False, the FileShare resource goes in to the Unknown state (as expected). The resource remains in the Unknown state even if you do the following:
- Even if you flush the service group
- Set the AutoControl attribute to True, and then probe the resource
WORKAROUND:
If you encounter this situation, perform the following tasks:
1. Take the service group offline.
2. Probe the FileShare resource. The resource will no longer be in the Unknown state.
3. Bring the service group online.

FILE / VERSION:
FileShare.dll / 6.0.20004.55

* 3314656 (Tracking ID: 3279413)

SYMPTOM:
In a network using tagged VLAN configuration, the VCS NIC agent may monitor an incorrect network interface, if the interfaces have same MAC address.

DESCRIPTION:
In tagged VLAN network configurations; there are multiple independent logical network interfaces that are created within a physical network interface or a teamed network interface. Each of these logical network interfaces may have the same MAC address.  
During the application service group configuration, the VCS application configuration wizard enables you to select an interface for each VCS cluster system and internally sets the MAC address of the selected interface as the value of the "MACAddress" attribute of the NIC agent. While selecting the interface, if you choose any of the logical interfaces that share the MAC address with other logical interfaces, then the NIC agent may begin to monitor an interface other than the selected one.
This issue occurs because the NIC agent uses the MAC address of the interface to monitor and determine the status. Since the MAC address of all the logical interfaces is identical, the agent may fail to identify the selected interface.

RESOLUTION:
The NIC agent currently uses the MAC address specified in the "MACAddress" attribute to monitor and determine the interface status. The agent is now enhanced to use either the MAC address or the interface name to monitor and determine the status.
To monitor the interface based on the its name, you must edit the “MACAddress” attribute of the NIC agent, after you configure the application service group.
Use the VCS Java Console to edit the “MACAddress” attribute and enter the interface name instead of the MAC address. You must enter the interface name in double quotes.
For example, 
MACAddress = “InterfaceName”

Notes: 

- After you specify the interface name as the “MACAddress” attribute value, if you want to use the VCS wizards to modify any settings, then you must first reset the value of the “MACAddress” attribute to the MAC address of the interface.
Failing this, the VCS wizard may fail to identify and populate the selected interface. 
Use the VCS Java Console to edit the attribute values.

- If you change the interface name, you must update the “MACAddress” attribute value to specify the new name. 
Failing this, the NIC resource will go in an UNKNOWN state.

- While editing the “MACAddress” attribute to specify the interface name, you must specify the name of only one interface.  

Binary File / Version:
NIC.dll, 6.0.20002.50

* 3314655 (Tracking ID: 3279413)

SYMPTOM:
In a network using tagged VLAN configuration, the VCS IP agent may assign the virtual IP address or the virtual server name to an incorrect network interface, if the interfaces have same MAC address.

DESCRIPTION:
In tagged VLAN network configurations; there are multiple independent logical network interfaces that are created within a physical network interface or a teamed network interface. Each of these logical network interfaces may have the same MAC address.
During the application service group configuration, the VCS application configuration wizard enables you to provide the virtual IP address or the virtual server name for the application to be configured. The wizard also enables you  to select an interface to which the specified virtual IP address or the virtual server name should be assigned.
After you select the required interface, the wizard internally sets the MAC address of the selected interface as the value of the "MACAddress" attribute of the IP agent. While selecting the interface, if you choose any of the logical interfaces that share the MAC address with other logical interfaces, then the IP agent may assign the specified virtual IP address or the virtual server name to an interface other than the one selected.
This issue occurs because the IP agent uses the MAC address of the interface to identify and assign the IP address. Since the MAC address of all the logical interfaces is identical, the agent may fail to identify the selected interface and as a result assign the IP address or virtual server name to an incorrect interface.

RESOLUTION:
The IP agent currently uses the MAC address specified in the "MACAddress" attribute to identify the interface to which the IP address should be assigned. The agent is now enhanced to use either the MAC address or the interface name as the parameters to identify the interface.
To identify the interface based on its name, you must edit the “MACAddress” attribute of the IP agent, after you configure the application service group. 
Use the VCS Java Console to edit the “MACAddress” attribute and enter the interface name instead of the MAC address. You must enter the interface name in double quotes.
For example, 
MACAddress = “InterfaceName”

Notes:
- After you specify the interface name as the “MACAddress” attribute value, if you want to use the VCS wizards to modify any settings, then you must first reset the value of the “MACAddress” attribute to use the MAC address of the interface.
Failing this, the VCS wizard may fail to identify and populate the selected interface. 
Use the VCS Java Console to edit the attribute values.

- If you change the interface name, you must update the “MACAddress” attribute value to specify the new name. 
Failing this, the IP resource will go in an UNKNOWN state.

- While editing the “MACAddress” attribute to specify the interface name, you must specify the name of only one interface.

Binary File / Version:
IP.dll / 6.0.20001.50

* 3113889 (Tracking ID: 3111144)

SYMPTOM:
After every 49.7 days, VCS logs report that the Global Counter VCS attribute is not updated. This error is reported on all nodes in the cluster, except the node with the lowest node ID value. The 'GloablCounter not updated' error also appears in the Event Viewer.

DESCRIPTION:
The error indicates that there could be communication issues between the cluster nodes. However, this error is incorrectly reported, and no communication issues actually occur.

RESOLUTION:
This issue has been fixed and the error is no longer reported at that odd interval.

FILE / VERSION:
had.exe / 6.0.20008.62
hacf.exe / 6.0.20008.62

NOTE: This hotfix supersedes Hotfix_6_0_20008_3113889, which was released earlier.

* 3099946 (Tracking ID: 3098019)

SYMPTOM:
[Issue 1] An online Lanman resource takes 1 minute or longer to go offline. [Issue 2] A newly created Lanman resource appears ONLINE even though the service group is not brought online.

DESCRIPTION:
The Lanman agent does not correctly identify the virtual name (configured under the Lanman resource) that is being monitored or taken offline on a cluster node.
This happens if the following conditions are satisfied on the node where the operation is being performed:
(a) NetBIOS over TCPIP (NetBT) is disabled on the network adapter.
(b) The first few characters of the virtual name (for example, Site10_Svr_ExchApp) are identical to any other virtual name (configured under another Lanman resource) or physical computer name registered on the node (for example, Site10_Svr).
No issues occur if the first few characters of the virtual name configured under the Lanman resource (for example, Site10_Svr_ExchApp) are not identical to any other computer name registered on the node (for example, Site10_Svr_EV or
Site11_Svr).

RESOLUTION:
The Lanman agent has been updated to correctly identify the Lanman resource on which an operation is being performed; it now reports the accurate resource status.

FILE / VERSION:
Lanman.dll / 6.0.20007.62



INSTALLING THE PATCH
--------------------
What's new in this CP
=====================|

The following hotfixes have been added in this CP:
 - Hotfix_6_0_20001_3314655
 - Hotfix_6_0_20002_3314656
 - Hotfix_6_0_20004_3423660
 - Hotfix_6_0_20005_3445216
 - Hotfix_6_0_20006_3457742
 - Hotfix_6_0_20007_3099946
 - Hotfix_6_0_20008_3113889a
 
For more information about these hotfixes, see the "FIXED_INCIDENTS" section in this Readme.


Install instructions
====================|

Download the appropriate cumulative public patch (CP) executable file to a temporary location on your system.

Each cumulative public patch includes the individual hotfixes that contain enhancements and fixes related to reported issues.
See the "FIXED_INCIDENTS" section for details.

Before you begin
----------------:
[1] Before installing the CP, ensure that you have installed Hotfix_6_0_20010_3557163 on the system.

[2] Ensure that the logged-on user has privileges to install the CP on the systems.

[3] One or more hotfixes that are included with this CP may require a reboot.
Before proceeding with the installation ensure that the system can be rebooted.

[4] Symantec recommends that you close the Cluster Manager (Java Console) and the Veritas Enterprise Administrator (VEA) Console before installing this CP.

[5] Ensure that you close the Windows Event Viewer before proceeding with the installation.

[6] Before installing the CP on Windows Server Core systems, ensure that Visual Studio 2005 x86 re-distributable is installed on the systems.


To install the CP in the silent mode
-----------------------------------:

Perform the following steps:

[1] Double-click the CP executable file to start the CP installation. 

The installer performs the following tasks:
    - Extracts all the individual hotfix executable files
      The files are extracted at %commonprogramfiles(x86)%\Veritas Shared\WxRTPrivates\<HotfixName>
    - Runs the pre-install tasks
    - Installs all the hotfixes sequentially
    - Runs the post-install tasks
The installation progress status is displayed in the command window.

[2] After all the hotfixes are installed, the installer prompts you to restart the system.
Type Y to restart the system immediately, or type N to restart the system later. 
You must restart the system for the changes to take effect.

Note that the installer prompts for a system restart only if hotfixes that require a reboot are included in the CP and are installed.

To install the CP using the command line
----------------------------------------:

Use the VxHFBatchInstaller.exe utility to install a CP from the command line.
The syntax options for this utility are as follows:

vxhfbatchinstaller.exe /CP:<CPName> [/PreInstallScript:<PreInstallScript.pl>] [/silent [/forcerestart]]

where,
    - CPName is the cumulative patch executable file name without the platform, architecture, and .exe extension.
For example, if CP executable name is CP1_VCSW_602_W2K12_x64.exe, specify it as CP1_VCSW_602

    - PreInstallScript.pl is the Perl script that includes the pre-installation steps. These steps forcefully kill the required services and processes in case a graceful stop request does not succeed.
    Symantec recommends that you use this option and script only in case the CP installer fails repeatedly while performing the pre-installation tasks.

    - /silent indicates the installation is run in a non-verbose mode; the installer does not prompt for any inputs during the installation.

    - /forcerestart indicates that the system is automatically restarted, if required, after the installation is complete.


Perform the following steps:
[1] From the command prompt, navigate to the directory where the CP executable file is located and then run the file to extract the contents to a default location on the system. 
The installer displays a list of hotfixes that are included in the CP.
    - On 64-bit systems, the hotfixes executable files are extracted to:
      "%commonprogramfiles(x86)%\Veritas Shared\WxRTPrivates\<CPName>"
      
[2] In the same command window, run the following command to begin the CP installation in the silent mode:
vxhfbatchinstaller.exe /CP:<CPName> /silent

For example, to install a VCSW 6.0.2 CP for Windows Server 2012, the command is:
vxhfbatchinstaller.exe /CP:CP1_VCSW_602 /silent

The installer performs the following tasks:

    - Extracts all the individual hotfix executable files
      The files are extracted at %commonprogramfiles(x86)%\Veritas Shared\WxRTPrivates\<HotfixName>
    - Runs the pre-install tasks
    - Installs all the hotfixes sequentially
    - Runs the post-install tasks
The installation progress status is displayed in the command window.

[3] After all the hotfixes are installed, the installer displays a message for restarting the system.
You must restart the system for the changes to take effect.

Note that the installer prompts for a system restart only if hotfixes that require a reboot are included in the CP and are installed. The installer automatically restarts the system if you had specified the /forcerestart option in step 2 earlier.

VxHFBatchInstaller usage example
---------------------------------:

[+] Install CP in silent mode, restart automatically:

vxhfbatchinstaller.exe /CP:CP1_VCSW_602 /silent /forcerestart

Known issues
============|
The following section describes the issues related to the individual hotfixes:

[1] Hotfix_6_0_20004_3423660
If SFW HA or VCS for Windows is installed at a custom location, the hotfix installer fails to perform the post-installation tasks, and the HAD does not start. (3332129)
WORKAROUND:
After running the hotfix installer, set the custom installation directory path in the VCS_HOME and the VCS_ROOT environment variables, start the HAD again.

-------------------------------------------------------+


REMOVING THE PATCH
------------------
NO


SPECIAL INSTRUCTIONS
--------------------
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. Symantec 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 a Storage Foundation for Windows maintenance release, the resulting Hotfix or Service Pack 
must be installed as soon as possible. Symantec Technical Services will notify you when the maintenance release (Hotfix or Service Pack) 
is available if you sign up for notifications from the Symantec support site http://www.symantec.com/business/support and/or 
from Symantec Operations Readiness Tools (SORT) http://sort.symantec.com.

Additional notes
================|

[+] To confirm the list of cumulative patches installed on a system, run the following command from the directory where the CP files are extracted:
vxhfbatchinstaller.exe /list

The output of this command displays a list of cumulative patches and the hotfixes that are installed as part of a CP. 
This command also displays the hotfixes that are included in a CP but are not installed on the system.

[+] To confirm the installation of the hotfixes, perform one of the following:
    - Run the following command:
      vxhf.exe /list
      The output of this command lists the hotfixes installed on the system.
    - In the Windows Add/Remove program, click "View installed updates" to view the list of the hotfixes installed on the system.

[+] To confirm the latest cumulative patch installed on a system, run the following command from the directory where the CP files are extracted:
vxhfbatchinstaller.exe /cplevel

The output of this command displays the latest CP that is installed, the CP status, and a list of all hotfixes that were a part of the CP but not installed on the system.

[+] The CP installer (vxhfbatchinstaller.exe) creates and stores logs at:
"%allusersprofile%\Application Data\Veritas\VxHF\VxHFBatchInstaller.txt"

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

[+] For general information about the hotfix installer (vxhf.exe), please refer to the following technote:
http://www.symantec.com/docs/TECH73446

[+] To view a list of hotfixes already installed on a system, please refer to the steps mentioned in the following technote:
http://www.symantec.com/docs/TECH73438

[+] For information on uninstalling a hotfix, please refer to the following technotes:
http://www.symantec.com/docs/TECH225604
http://www.symantec.com/docs/TECH73443


OTHERS
------
NONE