vcs-Hotfix_5_1_20009_2271384

 Basic information
Release type: Hot Fix
Release date: 2011-03-14
OS update support: None
Technote: TECH153698 - Regular VXIO messages stating error 80000011 followed by SCSI bus resets
Documentation: None
Popularity: 4449 viewed    downloaded
Download size: 2.06 MB
Checksum: 1700841217

 Applies to one or more of the following products:
Storage Foundation HA 5.1SP2 On Windows 32-bit
Storage Foundation HA 5.1SP2 On Windows IA64
Storage Foundation HA 5.1SP2 On Windows x64

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

 Fixes the following incidents:
2271384

 Patch ID:
None.

Readme file
Date: 2011-03-04
OS: Windows
OS Version: 2003, 2008, 2008 R2
Packages: Hotfix_5_1_20009_2271384_x86.exe, Hotfix_5_1_20009_2271384_x64.exe, Hotfix_5_1_20009_2271384_ia64.exe
Etrack Incidents: 2271384

Errors/Problems Fixed
---------------------+
This hotfix addresses an issue where the VCS VMDg agent causes frequent bus resets on passive cluster nodes resulting in several vxio STATUS_DEVICE_BUSY errors in the event log of the active cluster node.

Overview
--------+
During the offline monitoring function, the VMDg agent validates the GUID of the disk groups on the passive cluster nodes. As the disk groups are in deported state, the storage agent may not have the disk group details. It therefore invokes a bus reset for every disk that is part of the cluster configuration.

This issue occurs if SFW is configured to use SCSI-2.

Resolution
-----------+
The VMDg agent is updated to address this issue.
The agent validates the disk group GUID only once, during its first monitor cycle. The agent skips the validation during all subsequent monitor cycles on the passive nodes.

Note: If there is any change in the storage configuration in the cluster, the VMDg agent then validates the GUID again.


Fixes Applied for Products
---------------------------+
Storage Foundation and High Availability Solutions 5.1 SP2 for Windows


Install/Uninstall Instructions
-------------------------------+
Download the appropriate hotfix executable to a temporary location on your system.
You can install this hotfix using the GUI or from the command line.
Instructions for both options are provided below.

This hotfix includes the following updated files:
-------------------------------
File name  | New Version number
-------------------------------
VMDg.dll   |   5.1.20009.451
-------------------------------

To install the hotfix using the GUI
-----------------------------------+
1. Double-click the appropriate 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 Shared\WxRTPrivates"

On 64-bit systems, the files are extracted to:
"%commonprogramfiles(x86)%\Veritas Shared\WxRTPrivates"

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

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

3. Click "Install Hotfix" to install the hotfix.
The status of each task is updated as it gets completed.

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

5. If prompted to restart the server, do so.

6. If this is a clustered configuration (SFW-HA or MSCS), please perform these steps 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:\temp><HotfixName_Platform.exe> /x
or
C:\temp><HotfixName_Platform.exe> /extract

For example, to extract this hotfix on a 32-bit cluster node, the command is:
C:\temp>Hotfix_5_1_20009_2271384_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 Shared\WxRTPrivates"

On 64-bit systems, the files are extracted to:
"%commonprogramfiles(x86)%\Veritas  Shared\WxRTPrivates"

3. At the command prompt, run the following command to install the hotfix:
vxhf.exe /install:<HotfixName> /silent

Here, <HotfixName> is the name of the hotfix file without the platform and the .exe extension.

For example, to install this hotfix the command is:
vxhf.exe /install:Hotfix_5_1_20009_2271384 /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 these steps on all additional nodes in the cluster.


Additional notes
----------------+
- To confirm the installation of the hotfix, run the following command:
vxhf.exe /list

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

- For details about a particular hotfix, run the following command:
vxhf.exe /display:<HotfixName>

Here, <HotfixName> is the name of the hotfix file without the platform and the .exe extension.

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

- For general information about the hotfix installer (vxhf.exe), please refer to the following technote:
http://www.symantec.com/business/support/index?page=content&id=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/business/support/index?page=content&id=TECH73438

- For information on uninstalling a hotfix, please refer to the steps mentioned in the following technote: 
http://www.symantec.com/business/support/index?page=content&id=TECH73443


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 and HA 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.