Date: 2010-01-20
OS: Windows
OS Version: Windows 2003, Windows 2008
Packages:  cluscmd64.dll, vxres.dll
Etrack Incidents:  1923059, 1939313
Errors/Problems Fixed: Fixed issue where MSCS cluster service was unable to start if
quorum resource was on a dynamic disk. Also fixed issue where vxio times out when
cluscmd64 calls are made through vxbridge.
Fixes Applied for Products: SFW 5.1 SP1
Install/Uninstall Instructions: This package contains the following
self-extracting files. Each file is the hotfix for a specific processor
architecture and operating system version. Choose the appropriate file
for your computer's configuration.
Operating System		Platform	File Name
-------------------------------------------------------------------------------------------
Microsoft Windows Server 2003	IA64		Hotfix_5_1_10003_584_1923059_w2k3_ia64.exe
Microsoft Windows Server 2003	x64		Hotfix_5_1_10003_584_1923059_w2k3_x64.exe
Microsoft Windows Server 2003	x86		Hotfix_5_1_10003_584_1923059_w2k3_x86.exe
Microsoft Windows Server 2008	IA64		Hotfix_5_1_10003_584_1923059_w2k8_ia64.exe
Microsoft Windows Server 2008	x64		Hotfix_5_1_10003_584_1923059_w2k8_x64.exe
Microsoft Windows Server 2008	x86		Hotfix_5_1_10003_584_1923059_w2k8_x86.exe
Extract the hotfix
==================
The hotfix can be extracted from a file in one of two ways:
* Method 1
  Double-click the hotfix. The hotfix will be extracted and the install
  wizard will automatically start and guide you through the installation
  after the extraction has completed.
* Method 2
  Save your selected file to a local folder and then extract the hotfix
  with the /x option.  For example, enter the command in the c:	mp
  directory
  c:	mp>Hotfix_5_1_10003_584_1923059_w2k8_x64.exe /x
Hotfix files will be extracted to "Hotfix_5_1_10003_584_1923059" folder at:
on 32-bit system: "%CommonProgramFiles%Veritas SharedWxRTPrivates"
on 64-bit system: "%CommonProgramFiles(x86)%Veritas SharedWxRTPrivates"
Install the hotfix
==================
Refer to README.RTF file in "Hotfix_5_1_10003_584_1923059" folder for details on installation
options for the hotfix.
To install the hotfix on Widows 2003 servers, Microsoft Core XML Services
(MSXML) 6.0 need to be installed first. Please download and install
MSXML 6.0 before installing the hotfix.  Refer to the following link
for more information:
http://www.microsoft.com/downloads/details.aspx?FamilyId=993c0bcf-3bcf-
4009-be21-27e85e1857b1&displaylang=en
Microsoft posted service pack and/or security updates for Core XML
Services 6.0.  Please contact Microsoft or refer to Microsoft web-site to
download and install latest updates to Core XML Services 6.0.
Additional Notes:
Contents
1. Overview
2. Resolution
3. Before you begin
4. Installing the hotfix
     - GUI Install
     - Command Line Install
     - Additional Notes
5. Disclaimer
1. Overview
This hotfix addresses two issues:
Issue 1:
        On converting the quorum disk from a Basic disk to a Dynamic
	disk, the clussvc service hangs.
Issue 2:
        On 64-bit systems, with NBU installed, vmdg resource suddenly
	fails over.
2. Resolution
Issue 1 occurred because the scenario had not been handled properly,
whereas Issue 2 was a timeout problem, leading to the node mistakenly
believing that the resource was dead. Once installed, the hotfix fixes
both issues and normal operations can be resumed.
3. Before you begin
This hotfix requires Microsoft Core XML Services (MSXML) 6.0 pre-installed
in your setup. Download and install MSXML 6.0 before installing the hotfix.
Refer to the following link for more information:
http://www.microsoft.com/downloads/details.aspx?FamilyId=993c0bcf-3bcf-4009-be21-27e85e1857b1&displaylang=en
Microsoft posted service pack and/or security updates for Core XML Services
6.0.  Please contact Microsoft or refer to Microsoft web-site to download
and install latest updates to Core XML Services 6.0.
Before installing the hotfix, care should be taken that:
If the cluster service is in a hung state, i.e. neither started nor
stopped, the user should terminate the clussvc service from the task
manager before installing the hotfix. The hotfix installer stops and
starts the clussvc service during installation, but the installation
can fail if the cluster service is hung.
Once the clussvc service is terminated, the user should check to see
if all "rhs.exe" processes have been killed. If not, user should
terminate them manually. If these processes are not terminated, the
hotfix will fail to replace the old vxres.dll with the new one in the
patch
NOTE: This process is called rhs.exe in Windows Server 2008. Under
Windows Server 2003 and Windows Server 2000, this process is called
"resmon.exe"
4. Installing the hotfix
Extract the hotfix to a temporary location on the server. The hotfix
archive contains a hotfix installer for the following Windows Server versions
and architectures:
Operating System		Platform	File Name
-------------------------------------------------------------------------------------------
Microsoft Windows Server 2003	IA64		Hotfix_5_1_10003_584_1923059_w2k3_ia64.exe
Microsoft Windows Server 2003	x64		Hotfix_5_1_10003_584_1923059_w2k3_x64.exe
Microsoft Windows Server 2003	x86		Hotfix_5_1_10003_584_1923059_w2k3_x86.exe
Microsoft Windows Server 2008	IA64		Hotfix_5_1_10003_584_1923059_w2k8_ia64.exe
Microsoft Windows Server 2008	x64		Hotfix_5_1_10003_584_1923059_w2k8_x64.exe
Microsoft Windows Server 2008	x86		Hotfix_5_1_10003_584_1923059_w2k8_x86.exe
This hotfix includes the following updated file(s):
================================================================================
Filename      | Version 	|  Windows 2003   | Windows 2008   |
================================================================================
vxres.dll     | 5.1.10003.584   |  x86, x64, ia64 | x86, x64, ia64 |
--------------------------------------------------------------------------------
cluscmd64.dll | 5.1.10003.584   |  x64, ia64      | x64, ia64      |
--------------------------------------------------------------------------------
The hotfix can be installed using the GUI or CLI. Instructions for both
options are provided below:
To install the hotfix using the GUI
------------------------------------
1. Double click the hotfix executable file to extract the contents to a
default location on the cluster node.
- On 32-bit systems, the files are extracted to:
"%commonprogramfiles%Veritas SharedWxRTPrivates"
- On 64-bit systems, the files are extracted to:
"%commonprogramfiles(x86)%Veritas SharedWxRTPrivates"
* The Hotfix Installer Wizard is automatically launched after the files have
been extracted.
2. Click "Next" on the Welcome screen.
3. The 'Hotfix Installation Task' screen lists the tasks that are performed
by the installer.
4. Select the "Install Hotfix" button to install the hotfix.
5. While the hotfix installation updates the system, the status of each
task is updated as it completes.
6. After all tasks have completed, select 'Next', then 'Finish' to complete the
installation process.
7. If prompted to restart the server, do so.
8. If this is a clustered configuration (SFW-HA or MSCS), please perform steps 1-7
on all additional nodes in the cluster.
To install the hotfix using the Command Line
---------------------------------------------
1. At the command prompt, run one of the following commands to extract the hotfix
files to the default location:
C:	emp><Hotfix_BuildVersion_IncidentNumber_OS_Platform>.exe /x
C:	emp><Hotfix_BuildVersion_IncidentNumber_OS_Platform>.exe /extract
Example:
For Windows Server 2003 32-bit: C:	emp>Hotfix_5_1_xxxxx_xxx_xxxxxxx_w2k3_x86.exe /x
2. From the command prompt, navigate to the default location where the hotfix
files are extracted.
On 32-bit systems, the files are extracted to:
"%commonprogramfiles%Veritas SharedWxRTPrivates<Hotfix_BuildVersion_IncidentNumber_OS_Platform>"
On 64-bit systems, the files are extracted to:
"%commonprogramfiles(x86)%Veritas SharedWxRTPrivates<Hotfix_BuildVersion_IncidentNumber_OS_Platform>"
3. At the command prompt, run the following command to install the hotfix:
VxHF.exe /install:<Hotfix_BuildVersion_IncidentNumber_OS_Platform> /silent
Note: <Hotfix_BuildVersion_IncidentNumber_OS_Platform> is the name of the hotfix file excluding the OS, platform,
and .exe extension. This is also the name of the folder where the hotfix was
extracted to under the WXRTPRIVATES directory.
Example:
Hotfix Executable Name: Hotfix_5_1_xxxxx_xxx_xxxxxxx_w2k3_x86.exe
When installing the hotfix, the <Hotfix_BuildVersion_IncidentNumber_OS_Platform> name is
Hotfix_5_1_xxxxx_xxx_xxxxxxx (note how the '_w2k3_x86.exe' was excluded).
Command:
VxHF.exe /install:Hotfix_5_1_xxxxx_xxx_xxxxxxx /silent
4. Follow the instructions displayed in the command prompt to complete the hotfix
installation.
5. If prompted to restart the server, do so at this time.
6. If this is a clustered configuration (SFW-HA or MSCS), please perform steps 1-5
on all additional nodes in the cluster.
Additional Notes
----------------
- VxHF.exe logs are located at the following location:
"%allusersprofile%Application DataVeritasVxHF"
- For general information about the VXHF installer, please refer to the following
technote: http://seer.entsupport.symantec.com/docs/329713.htm
- To view a list of hotfixes already installed on a system, please refer to the
following technote: http://seer.entsupport.symantec.com/docs/329704.htm
- For information on uninstalling a hotfix, please refer to the following
technote: http://seer.entsupport.symantec.com/docs/329709.htm
5. DISCLAIMER:
----------------+
This fix has not been fully tested. 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.