vcs-win_x64-CP8_VCSW_601

 Basic information
Release type: Patch
Release date: 2016-12-12
OS update support: None
Technote: None
Documentation: None
Popularity: 516 viewed    downloaded
Download size: 23.54 MB
Checksum: 4218694902

 Applies to one or more of the following products:
Cluster Server 6.0.1 On Windows x64

 Obsolete patches, incompatibilities, superseded patches, or other requirements:

This patch supersedes the following patches: Release date
vcs-win_x64-CP7_VCSW_601 (obsolete) 2015-08-10
vcs-win_x64-CP6_VCSW_601 (obsolete) 2014-11-24
vcs-win_x64-CP5_VCSW_601 (obsolete) 2014-07-28
vcs-win_x64-CP4_VCSW_601 (obsolete) 2014-04-30

 Fixes the following incidents:
2938704, 3054751, 3062860, 3065921, 3099727, 3113887, 3164649, 3231486, 3247363, 3248926, 3314700, 3314705, 3334544, 3369234, 3503886, 3521509, 3615729, 3644019, 3694213, 3903259, 3905020

 Patch ID:
None.

Readme file
                          * * * READ ME * * *
                * * * Veritas Cluster Server 6.0.1 * * *
                      * * * Patch 6.0.1.800 * * *
                         Patch Date: 2016-12-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
----------
Veritas Cluster Server 6.0.1 Patch 6.0.1.800


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



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


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: VCSW CP7
* 3065921 (3065929) VMwareDisks agent does not work if ESX is not on the same network as VM.
* 2938704 (2907846) This hotfix addresses an issue where the MSMQ resource failed to bind to the correct port.
* 3099727 (3098019) An online Lanman resource takes 1 minute or longer to go offline.
* 3054751 (3053279) Windows Server Backup fails to perform a system state backup with the following error: Error in backup of C:\program files\veritas\\cluster server\ during enumerate: Error [0x8007007b] The filename, directory name, or volume label syntax is incorrect.
* 3164649 (3164604) The Exchange 2010 Database Agent Configuration Wizard does not create a MountV resource for certain transaction logs.
* 3334544 (3334542) Users are unable to add or modify custom settings on printers clustered under VCS.
* 3113887 (3111144) After every 49.7 days, VCS logs report that the Global Counter VCS attribute is not updated.
* 3247363 (3247361) The VCS for Windows FileShare and SQL Server 2008 agent configuration wizards do not recognize shared disks if they are available on same bus as the system LUN, for example, when booting from SAN.
* 3248926 (3248925) VCS for Windows does not support NetApp SnapDrive 6.4 or later.
* 3231486 (3231484) The SQL Server 2008 Agent Configuration Wizard crashes with an "VCS component - SQL server 2008 Wizard has stopped working" error, after you click Next on the User Databases List panel.
* 3369234 (3369209) When adding the relevant services after the initial configuration, the VCS SQL Server 2008 Agent Configuration Wizard does not update the paths to the shared storage.
* 3314700 (3279413) In a network using tagged VLAN configuration, the VCS IP agent may assign the virtual IP address to an incorrect network interface, if the interfaces have same MAC address.
* 3314705 (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.
* 3062860 (3062849) If LLT is running alongside a utility like Network Monitor, a system crash (BSOD) occurs when shutting down Windows.
* 3503886 (3503880) Provide an option to forcefully unmount the Mount resource.
* 3521509 (3521503) This hotfix addresses two issues: 1. a Lanman resource faults with the error code: [2, 0x0000006F], and 2. the Lanman resources fault after upgrading VCS or SFW HA from 5.1 SP2 to 6.0.1.
* 3644019 (3644017) A system crash occurred when VxExplorer gathered the GAB/LLT logs.
* 3615729 (3615728) VMwareDisks agent supports only 'persistent' virtual disk mode.
* 3694213 (3773915) Lanman resource fails to come online.
* 3903259 (3890392) After every 49.7 days, VCS logs report that the GlobalCounter VCS attribute is not updated.
* 3905020 (3905019) WAC resource stops sending IAmAlive messages after a certain duration of time and reports the TCP/IP connection as unresponsive.


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

Patch ID: VCSW CP7

* 3065921 (Tracking ID: 3065929)

SYMPTOM:
VMwareDisks agent does not work if ESX is not on the same network as VM.

DESCRIPTION:
VMwareDisks agent accepts an ESXDetails attribute which contains the details of ESX to be used to perform online/offline operations. In case ESX is not accessible from the VM network, agent will not work.

RESOLUTION:
VMwareDisks agent has been modified to work with vCenter details as well. ESXDetails attribute will now accept either ESX details or vCenter details.No attribute change is involved, the same attribute will be used.

Limitation - With vCenter given in the ESXDetails attribute, and if VMHA is not enabled, then if the ESX of the node where application is running faults, then the agent will not be able to detach disks from the faulted ESX's VM. Application failover will not be impacted. The subsequent power ON of the faulted ESX's VM will involve extra manual step to detach disks from the VM. Otherwise VM power ON will not go through.

File Name / Version:
VMwareDisks.dll / 6.0.10002.264
VMwarelib.dll /  6.0.10002.264

* 2938704 (Tracking ID: 2907846)

SYMPTOM:
This hotfix addresses an issue where the MSMQ resource failed to bind to the correct port.

DESCRIPTION:
When the MSMQ agent was brought online, the Event Viewer reported an error stating that Message Queuing failed to bind to port 1801. This error could occur due to various reasons. Even though the binding failed, the agent reported the MSMQ resource as Online.

RESOLUTION:
The MSMQ agent has been enhanced to verify that the clustered MSMQ service is bound to the correct virtual IP and port. By default, the agent performs this check only once during the Online operation. If the clustered MSMQ service is not bound to the correct virtual IP and port, the agent stops the service and the resource faults. You can configure the number of times that this check is performed. To do so, create the DWORD tunable parameter 'VirtualIPPortCheckRetryCount' under the registry key 'HKLM\SOFTWARE\VERITAS\VCS\BundledAgents\MSMQ'. If this parameter is set to a value greater than 1, the agent starts the clustered MSMQ service again and verifies its virtual IP and port binding as many times. It waits 2 seconds between each verification attempt. If the clustered MSMQ service is bound to the correct virtual IP and port, the agent reports Online.

File Name / Version:
MSMQ.dll / 6.0.10004.268

* 3099727 (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 Name / Version:
Lanman.dll / 6.0.10005.269

* 3054751 (Tracking ID: 3053279)

SYMPTOM:
Windows Server Backup fails to perform a system state backup with the following error: Error in backup of C:\program files\veritas\\cluster server\ during enumerate: Error [0x8007007b] The filename, directory name, or volume label syntax is incorrect.

DESCRIPTION:
The backup operation fails because the VCS service image path contains an extra backslash (\) character, which Windows Server Backup is unable to process.

RESOLUTION:
This issue has been fixed by removing the extra backslash character from the VCS service image path. 
This hotfix changes the following registry keys: 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Had\ImagePath 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HADHelper\ImagePath 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Cmdserver\ImagePath 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VCSComm\ImagePath

NOTE: 
#1. This hotfix supersedes Hotfix_6_0_10006_3054751a, which was released earlier.

* 3164649 (Tracking ID: 3164604)

SYMPTOM:
The Exchange 2010 Database Agent Configuration Wizard does not create a MountV resource for certain transaction logs.

DESCRIPTION:
This issue occurs only if the transaction logs folder of the Exchange 2010 database is located directly on the folder mount, instead of being located within another folder on the root drive.

RESOLUTION:
The Exchange 2010 Database Agent Configuration Wizard has been updated to resolve this issue. It now creates the MountV resource for the transaction logs even if they are located in a subfolder on the root drive.

File Name / Version:
Exch2010Wizard.exe / 6.0.10007.274

* 3334544 (Tracking ID: 3334542)

SYMPTOM:
Issue 1:
Users are unable to add or modify custom settings on printers clustered under VCS.

Issue 2:
The memory usage of the PrintSpool agent increases continuously. This might result in a low virtual memory condition, following which the system reboots and a message similar to following error appears in the Event Viewer Log: Log Name: System Source: Microsoft-Windows-Resource-Exhaustion-Detector Event ID: 2004 Task Category: Resource Exhaustion Diagnosis Events Level: Warning Keywords: Events related to exhaustion of system commit limit (virtual memory). User: SYSTEM Computer: <system_name> Description: Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: VCSAgDriver.exe (<process_ID>) consumed <number_of_bytes> bytes

Fix for issue #1 was earlier released as Hotfix_6_0_10008_3186666. It is now included in this hotfix.

DESCRIPTION:
Issue 1:
When a printer with custom settings (like printing shortcuts) is added to VCS clustered virtual name, the printer settings become unavailable. This issue occurs because any customizations to printer settings are not recognized after a printer is clustered.

Issue 2:
The memory leak occurs only while adding or deleting printers, or while modifying printer settings.

RESOLUTION:
Issue 1:
This hotfix addresses the issue. However, for the hotfix to work, you need to perform the following tasks manually. Create the following DWORD registry key and set its value to 1. - For global configurations, create: HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VCS\BundledAgents\PrintSpool\__GLOBAL__\PrinterDriverSupport - For per resource configurations, create: HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VCS\BundledAgents\PrintSpool\ <resource_name>\PrinterDriverSupport After creating this key, do one of the following: - If a PrintSpool resource if offline, bring it online. - If a PrintSpool resource is already online, probe it. Upon installing the hotfix, the PrintSpool agent creates the 'HKEY_LOCAL_MACHINE\Cluster' key. Make sure that the key exists, and then add printers to the virtual name. NOTE: Existing printers will continue to have this issue. Symantec recommends deleting and re-creating such printer resources. CAUTION: This hotfix may cause unexpected effects on other applications that can be clustered (or are already clustered) on the same node.

Issue 2:
This hotfix fixes the memory leak issue.

File Name / Version:
PrintSpool.dll / 6.0.10019.286

* 3113887 (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 Name / Version:
had.exe / 6.0.10010.277
hacf.exe / 6.0.10010.277

* 3247363 (Tracking ID: 3247361)

SYMPTOM:
The VCS for Windows FileShare and SQL Server 2008 agent configuration wizards do not recognize shared disks if they are available on same bus as the system LUN, for example, when booting from SAN.

DESCRIPTION:
Even though the necessary shared disks are attached, the VCS for Windows configuration wizards display the following error: "No shared drives discovered. Possibly the volumes are already part of another service group in the current configuration."

RESOLUTION:
This hotfix addresses the issue. However, for the hotfix to work, you must create the following DWORD registry key and set its value to 1, on all the nodes in the cluster: HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VCS\BundledAgents\DiskRes\__global__\AllowDisksOnOSPort Relaunch the configuration wizards after applying this hotfix and creating this registry key.

KNOWN ISSUE: The VCS for Windows FileShare and SQL Server 2008 agent configuration wizards allow you to select system volumes for application clustering. However, when the configuration is complete, the corresponding mount resource goes into the UNKNOWN state. (3270171)
File Name / Version:
DiskResDiscover.dll / 6.0.10011.279

* 3248926 (Tracking ID: 3248925)

SYMPTOM:
VCS for Windows does not support NetApp SnapDrive 6.4 or later.

DESCRIPTION:
Support for NetApp SnapDrive 6.4 onwards is required.

RESOLUTION:
This hotfix adds support for NetApp SnapDrive 6.4 and 6.5 to VCS for Windows.

* 3231486 (Tracking ID: 3231484)

SYMPTOM:
The SQL Server 2008 Agent Configuration Wizard crashes with an "VCS component - SQL server 2008 Wizard has stopped working" error, after you click Next on the User Databases List panel.

DESCRIPTION:
This issue occurs while configuring a SQL Server service group (SQL Server 2008, 2008 R2, and 2012). The SQL Server 2008 Agent Configuration Wizard displays the instances of the selected SQL Server version and the corresponding installed services, on the SQL Server Instance Selection panel. If you select only the SQL Server instances and click Next, the wizard proceeds to the User Databases List panel. However, due an internal error the wizard crashes after you click Next on the User Databases List panel.

RESOLUTION:
The wizard behavior is now modified to address this issue. Even if you select only the SQL Server instances on the SQL Server Instance Selection panel, the wizard now proceeds with the configuration without an error.

File Name / Version:
SQL2008Wizard.exe / 6.0.10009.280

* 3369234 (Tracking ID: 3369209)

SYMPTOM:
When adding the relevant services after the initial configuration, the VCS SQL Server 2008 Agent Configuration Wizard does not update the paths to the shared storage.

DESCRIPTION:
The initial SQL Server agent configuration was done, and the Analysis service was added. When the VCS SQL Server 2008 Agent Configuration Wizard was run again, although the resources were created, the paths for those resources were not in sync.

RESOLUTION:
This hotfix resolves the issue by updating the OLAP path after running the initial configuration.

File Name / Version:
SQL2008Wizard.exe / 6.0.10020.289

* 3314700 (Tracking ID: 3279413)

SYMPTOM:
In a network using tagged VLAN configuration, the VCS IP agent may assign the virtual IP address 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 for the application to be configured. The wizard also enables you  to select an interface to which the specified virtual IP address 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 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 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. 
For example, 
MACAddress = 'InterfaceName' (without quotes)

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.

- If you manually edit the attribute value in main.cf, you must enter the interface name in double quotes.

File Name / Version:
IP.dll / 6.0.10016.292

* 3314705 (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. 
For example, 
MACAddress = 'InterfaceName' (without quotes)

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.  

- If you manually edit the attribute value in main.cf, you must enter the interface name in double quotes.

File Name / Version:
NIC.dll / 6.0.10017.292

* 3062860 (Tracking ID: 3062849)

SYMPTOM:
If LLT is running alongside a utility like Network Monitor, a system crash (BSOD) occurs when shutting down Windows.

DESCRIPTION:
The system crashes due to a time out that occurs while waiting for LLT to unbind from the adapters during a shutdown operation. This issue occurs when LLT is configured over Ethernet.

RESOLUTION:
The LLT driver has been updated to properly handle unbind calls so that Windows can shut down gracefully.

File Name / Version:
llt.sys / 6.0.10003.267

* 3503886 (Tracking ID: 3503880)

SYMPTOM:
The Mount resource in a service group takes a long time to go offline.

DESCRIPTION:
If the Mount resource takes a long time go offline, an option should be provided for the ForceUnmount attribute to forcefully unmount the resource.

RESOLUTION:
This hotfix provides the CLOSE_FORCE option for the ForceUnmount attribute to resolve this issue. This option works as follows: If the Mount resource takes a long time to go offline, set its ForceUnmount attribute to the value CLOSE_FORCE. If this value is set, the agent does not try to lock the configured mount points, and proceeds directly with the forceful unmount operation. Note: Forceful unmount may potentially cause a data corruption. When you use ForceUnmount with CLOSE_FORCE, then before you switch or take the Mount resources offline, verify that none of the applications are accessing the configured mount points.

File Name / Version:
Mount.dll / 6.0.10024.295
Mount.xml / N/A

* 3521509 (Tracking ID: 3521503)

SYMPTOM:
Issue 1:
A Lanman resource faults with the error code: [2, 0x0000006F].

Issue 2:
After you upgrade VCS or SFW HA from 5.1 SP2 to 6.0.1, the Lanman resources fault when checking whether the virtual server name is alive. 

NOTE: Fix for issue #1 was earlier released as Hotfix_6_0_10023_3492551. It is now included in this hotfix (Hotfix_6_0_10025_3521509).

DESCRIPTION:
Issue 1:
This occurs due to an internal issue with the Lanman agent.

Issue 2:
This issue occurs if your setup contains DNS entries that point to a virtual IP address that is online. The Lanman agent faults when it performs a duplicate name check if a flag 'DisablePingCheckForDND' is specified in the registry.

RESOLUTION:
Issue 1:
The Lanman agent has been updated so that the Lanman resource does not fault due to this issue.

Issue 2:
This hotfix addresses the issue by updating the Lanman agent to skip the duplicate name check. ADDITIONAL TASKS: After you apply this hotfix, perform the following tasks on all the nodes in the cluster. 1. Open the registry editor. 2. Navigate to the registry key: 'HKLM\SOFTWARE\VERITAS\VCS\BundledAgents\Lanman\<Lanman_Resource_Name>' or 'HKLM\SOFTWARE\VERITAS\VCS\BundledAgents\Lanman\__GLOBAL__' 3. Create the DWORD key 'DisablePingCheckForDND' with the value '1'. Note: If you create this tunable parameter under the '__GLOBAL__' key, it applies to all the Lanman resources configured in the cluster.

File Name Name / Version
Lanman.dll / 6.0.10025.297

* 3644019 (Tracking ID: 3644017)

SYMPTOM:
When VxExplorer gathers the GAB/LLT logs, the program crashes or causes a system crash.

DESCRIPTION:
This issue occurs when the lltshow utility attempts to fetch information about the LLT nodes or links using the following options:
lltshow -n -1
lltshow -l -1
VxExplorer executes these commands when gathering the logs. Therefore, you might encounter the issue when you run VxExplorer with the GAB/LLT option.

RESOLUTION:
This hotfix addresses the issue by updating the lltshow utility to identify the correct sizes of the LLT nodes and links.

FILE / VERSION:
lltshow.exe / 6.0.10028.300

* 3615729 (Tracking ID: 3615728)

SYMPTOM:
VMwareDisks agent supports only 'persistent' virtual disk mode.

DESCRIPTION:
The VMwareDisks agent currently supports only 'persistent' virtual disk mode.
If you have configured the disk in 'independent' mode, in the event of a failover, the VMwareDisks agent sets the mode to 'persistent'.

RESOLUTION:
The behaviour of VMwareDisks agent is modified through this hotfix. 
The VMwareDisks agent now supports 'independent' disk mode.
An attribute 'VirtualDiskMode' is now added to the VMwareDisks agent's attributes. 
You can set the value of this attribute to 'persistent', 'independent_persistent' or 'independent_nonpersistent'.
By default the value is set to 'persistent'. You must modify the value after you configure application monitoring.
Note: The VMwareDisks agent does not detect the mode in which the disk is configured. After a fail over the disk is attached in the mode as that defined 
in the attribute value. 
For more details about the disk modes, refer to VMware documentation.

To modify the value use the VCS Java Console or perform the following steps through command line:
1.	If you have configured the disk in 'persistent' mode, bring the service group offline.
hagrp -offline service_group -sys system_name
2.	Change the cluster configuration to read-write mode
haconf -makerw
3.	Modify the attribute value
hares -modify resource_name VirtualDiskMode independent_persistent
4.	Save config
haconf -dump
5.	Change the cluster configuration to read-only mode
haconf -makero  

FILE / VERSION:
VMwareDisks.dll 6.0.10027.299
VMwarelib.dll 6.0.10027.299
VMwareDisks.xml

* 3694213 (Tracking ID: 3773915)

SYMPTOM:
The Lanman resource fails to come online due to certain DNS settings.

DESCRIPTION:
This issue occurs if your setup uses CNAME records instead of  HOST (A) records for the virtual name. The Lanman agent faults when it performs a duplicate name check, because it incorrectly looks at non-HOST records.

RESOLUTION:
This hotfix addresses the issue by updating the Lanman agent to look at only the HOST records from a DNS query.

FILE / VERSION:
Lanman.dll / 6.0.10029.301

* 3903259 (Tracking ID: 3890392)

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. VCS resets the GlobalCounter attribute every 49.7 days, but a delay might occur in synchronizing this change across all the cluster nodes. The error is reported if this delay occurs, but no communication issues actually occur.

RESOLUTION:
This issue has been fixed by increasing the buffer size to hold the GlobalCounter attribute value, so that it does not need to be reset. 

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

* 3905020 (Tracking ID: 3905019)

SYMPTOM:
WAC resource stops sending IAmAlive messages after a certain duration of time and reports the TCP/IP connection as hung.

DESCRIPTION:
VCS incorrectly calculates the current time for a WAC resource due to the limitation of a Microsoft API (GetTickCount()). This current time is further used to control the sending of IAmAlive messages betweeen the WAC resources. Therefore, after a certain duration of time, the WAC resource stops sending IAmAlive messages to its peer and causes the connection to become unresponsive.

RESOLUTION:
This hotfix addresses the issue by correctly calculating the current time for a WAC resource using of a different API (GetTickCount64()). 

FILE / VERSION: 
wac.exe/6.0.10031.301



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

The following hotfix has been added in this CP:
 - Hotfix_6_0_10029_3694213
 - Hotfix_6_0_10030_3903259
 - Hotfix_6_0_10031_3905020
 
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] Ensure that the logged-on user has privileges to install the CP on the systems.

[2] 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.

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

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

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

[6] Before installing CP, ensure that the Startup type of the VCS Authentication Service is set to Automatic. This is applicable only if you have configured a secure cluster.


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 CP7_VCSW_601_W2K8_x64.exe, specify it as CP7_VCSW_601

    - 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.1 CP for Windows Server 2008, the command is:
vxhfbatchinstaller.exe /CP:CP7_VCSW_601 /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:CP7_VCSW_601 /silent /forcerestart


Known issues
============|
The following section describes the issue related to the 6.0.1 CP7:

[1] After uninstalling this CP, the Startup type of the VCS Authentication Service resets to manual mode. As a result, the service stops after a system restart, and you might encounter issues with the configuration wizards.
Workaround: After uninstalling the CP, change the Startup type of the VCS Authentication Service to Automatic.

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


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%\Veritas\VxHF\VxHFBatchInstaller.txt"

[+] The hotfix installer (vxhf.exe) creates and stores logs at:
"%allusersprofile%\Veritas\VxHF\VxHFBatchInstaller.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

[+] For general information about the CP, please refer to the following technote:
http://www.symantec.com/docs/TECH209086


OTHERS
------
NONE