|
---|
Release type: | Hot Fix |
Release date: | 2010-11-17 |
OS update support: | None |
Technote: | TECH140245 - VMDg / MountV resources fail to online or probe when Microsoft MS10-066 "Vulnerability in remote procedure call could allow remote code execution" is applied |
Documentation: | None |
Popularity: | 5859 viewed downloaded |
Download size: | 1.59 MB |
Checksum: | 1239967867 |
Storage Foundation 5.1SP1 On Windows IA64
Storage Foundation 5.1SP1AP1 On Windows IA64 Storage Foundation 5.1SP1 On Windows x64 Storage Foundation 5.1SP1AP1 On Windows x64 Storage Foundation HA 5.1SP1 On Windows IA64 Storage Foundation HA 5.1SP1AP1 On Windows IA64 Storage Foundation HA 5.1SP1 On Windows x64 Storage Foundation HA 5.1SP1AP1 On Windows x64 |
None.
|
2147847
|
None.
|
Date: 2010-10-07 OS: Windows OS Version: 2003 Packages: VxBridge.exe, cluscmd64.dll, vxcmd64.dll, vxcmd.dll, VxAssist.exe, VxSnap.exe Etrack Incidents: 2147847 Errors/Problems Fixed ----------------------+ This hotfix addresses an issue where storage related operations in a clustered environment fail due to the Microsoft Hotfix 982802. Overview --------- After installing the Microsoft security update 982802 on clustered systems where SFW is used to manage storage, some of the storage related operations may fail. - In a Veritas Cluster Server (VCS) environment, the cluster disk group resources (MountV, VMDg) do not come online on the nodes. The Windows Event Viewer may contain the following events: Event ID: 9515 Event Source: Agent Framework Description: VMDg:nodename-VMDg:online:Init diskgroup : Unrecognized error code. 800706C6 Event ID: 31201 Event Source: RPC Description: Application "%vcs_home%\bin\VCSAgDriver.exe" type VMDg with process id 2980 has failed to complete a COM/RPC call because of an invalid message from server. Here, %vcs_home% is typically C:\Program Files\Veritas\Cluster Server. - In an Microsoft Cluster Server (MSCS) environment, the Volume Manager Disk Group resource creation may fail. Also, if the controlling node of the cluster becomes inactive, the quorum arbitration process may fail. This issue occurs due to a failure in some of the cluster calls to VxBridge.exe on 64-bit Windows Server 2003 systems. Resolution ----------- This issue is fixed in the SFW components. An additional memory buffer is allocated for the output parameters. This ensures that the arguments passed from VxBridge.exe reach the clients. Fixes Applied for Products --------------------------+ Storage Foundation 5.1 Service Pack 1 for Windows Storage Foundation and High Availability Solutions 5.1 SP1 for Windows Install/Uninstall Instructions ------------------------------+ This package contains self-extracting files that are specific to the processor architecture and operating system version. Choose the appropriate file for your computer's configuration. ========================================================================= Operating System Platform File Name ========================================================================= Windows Server 2003 IA64 Hotfix_5_1_10042_584_2147847_w2k3_ia64.exe x64 Hotfix_5_1_10042_584_2147847_w2k3_x64.exe ------------------------------------------------------------------------- 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. Each self-extracting file includes the following updated file(s): ================================================= Filename | Version | Windows 2003 | ================================================= VxBridge.exe | 5.1.10042.584 | x64, IA64 | ------------------------------------------------- cluscmd64.dll| 5.1.10042.584 | x64, IA64 | ------------------------------------------------- vxcmd64.dll | 5.1.10042.584 | x64, IA64 | ------------------------------------------------- vxcmd.dll | 5.1.10042.584 | x64, IA64 | ------------------------------------------------- vxassist.exe | 5.1.10042.584 | x64, IA64 | ------------------------------------------------- vxsnap.exe | 5.1.10042.584 | x64, IA64 | ------------------------------------------------- Before you begin ----------------- [1] In case of Windows Server 2003 systems, 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 website to download and install latest updates to Core XML Services 6.0. Refer to the following link for more information: http://www.microsoft.com/downloads/details.aspx?FamilyId=70C92E77-9E5A-41B1-A9D2-64443913C976&displaylang=en [2] The hotfix installation requires stopping the Storage Agent (vxvm) service which will cause the 'Volume Manager Disk Group' (VMDg) resources in a cluster environment (MSCS or VCS) to fault. If this hotfix is being applied to a server in cluster, make sure any cluster groups containing a VMDg resource are taken offline or moved to another node in the cluster before proceeding. [3] Sometimes the hotfix may fail to install due to some stray rhs.exe processes that keep running even after the cluster service has been stopped. In such a case, you should manually terminate all the running rhs.exe processes, confirm that the clussvc service is stopped, and then retry installing the hotfix. 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 Shared\WxRTPrivates" On 64-bit systems, the files are extracted to: "%commonprogramfiles(x86)%\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 prompted to restart the server, do so. 6. If this is a clustered configuration (VCS or MSCS), please perform steps 1-5 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><Hotfix_BuildVersion_IncidentNumber_OS_Platform>.exe /x or C:\temp><Hotfix_BuildVersion_IncidentNumber_OS_Platform>.exe /extract For example, to extract this hotfix on a 32-bit Windows 2003 system, the command is: C:\temp>Hotfix_5_1_10042_584_2147847_w2k3_x64.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\<Hotfix_BuildVersion_IncidentNumber_OS_Platform>" On 64-bit systems, the files are extracted to: "%commonprogramfiles(x86)%Veritas Shared\WxRTPrivates\<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 Here, <Hotfix_BuildVersion_IncidentNumber_OS_Platform> is the name of the hotfix file excluding the OS, platform, and .exe extension. For example, to install this hotfix on a 64-bit Windows 2003 system, the command is: VxHF.exe /install:Hotfix_5_1_10042_584_2147847 /silent Hotfix Executable Name is Hotfix_5_1_10042_584_2147847_w2k3_x64.exe. When installing the hotfix, the <Hotfix_BuildVersion_IncidentNumber_OS_Platform> name is Hotfix_5_1_10042_584_2147847. (note how the "_w2k3_x86.exe" is excluded). 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 (VCS or MSCS), please perform steps 1-5 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://seer.entsupport.symantec.com/docs/329713.htm - To view a list of hotfixes already installed on a system, please refer to the steps mentioned in the following technote: http://seer.entsupport.symantec.com/docs/329704.htm - For information on uninstalling a hotfix, please refer to the steps mentioned in the following technote: http://seer.entsupport.symantec.com/docs/329709.htm 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. |
Why Register?
Get notifications about ASLs/APMs, HCLs, patches, and high availability agents
As a registered user, you can create notifications to receive updates about NetBackup Future Platform and Feature Plans, NetBackup hot fixes/EEBs in released versions, Array Support Libraries (ASLs)/Array Policy Modules (APMs), hardware compatibility lists (HCLs), patches and high availability agents. In addition, you can create system-specific notifications customized to your environment.
Compare configurations
The Compare Configurations feature lets you compare different system scans by the data collector. When you sign in, you can choose a target system, compare reports run at different times, and easily see how the system's configuration has changed.
Save configurations
After logging in, you can retrieve past reports, share reports with colleagues, review notifications you received, and retain custom settings. Anonymous users cannot access these features.
Bulk uploader
As a registered user,you can upload multiple reports, using the Bulk Uploader.