OS: HP-UX OS Version: 11i v3 Fixes Applied for Products: VRTSvcsag - Veritas Cluster Server Bundled Agents Additional Instructions: Please read the instructions below before installing the patch. PATCH VCS 5.0RP3 HF1/11iv3 for VCS Bundled Agent 5.0RP3/11iv3 ================================================================ Patch Date: October, 2009 This README provides information on: * BEFORE GETTING STARTED * FIXES AND ENHANCEMENTS INCLUDED IN THE PATCH * PACKAGES AFFECTED BY THE PATCH * INSTALLING THE PATCH * UNINSTALLING THE PATCH BEFORE GETTING STARTED: ---------------------- This patch only applies to: VRTSvcsag 5.0RP3 running on HP-UX 11i v3 Ensure that you are running the supported configurations before installing this patch. FIXES AND ENHANCEMENTS INCLUDED IN THE PATCH: -------------------------------------------- Etrack Incidents: 1844884, 1867995 SDR's of Fixed Symantec Incidents: -------------------------------- Symantec Incident : 1844884 Symptom: The MultiNICB agent memory consumption keeps on increasing gradually. This can be observed by periodically referring to 'ps -elf' output for the '/opt/VRTSvcs/bin/MultiNICB/MultiNICBAgent' process. Defect Description: This behavior is seen due to memory leak in the MultiNICB agent. Resolution: The memory leak in MultiNICB agent is now fixed. Symantec Incident : 1867995 Symptom: In a configuration where an IP resources's Device name is a substring of the MultiNICB resource's Device name, when the MultiNICB resource performs an internal failover, the IP resource goes offline unexpectedly and faults. Defect Description: The MultiNICB agent logic that searches for the virtual IPs to migrate to new active interface was selecting any interfaces that matched as a left substring of the failed device name. Due to this, the virtual IP monitored by the IP resource was getting migrated to the new active interface monitored by the MultiNICB resource. This in turn resulted in IP resource going offline unexpected and thereby faulting. Resolution: The MultiNICB agent code logic that searches for virtual IPs is updated to migrate only appropriate virtual IPs to new active interface only. PACKAGES AFFECTED BY THE PATCH: ------------------------------- This patch updates the following VCS package(s) VRTSvcsag from 5.0RP3 /11i v3 to 5.0RP3HF1 /11i v3 Patch Information: Patch ID - PVCO_03900 Patch Supersedes - PVCO_03849, PVCO_03853, PVCO_03867, PVCO_03896 INSTALLING THE PATCH: -------------------- The following steps should be run on all nodes in the VCS cluster: Stopping VCS on the cluster node: -------------------------------- 1. Ensure that "/opt/VRTS/bin" directory is included in your PATH environment variable so you can execute all the VCS commands. Refer to Veritas Cluster Server Installation Guide for more information. 2. Verify that the version of VRTSvcsag is 5.0RP3 for HP-UX 11i v3. 3. Freeze all the service groups persistently, on all nodes: # haconf -makerw # hagrp -freeze [group] -persistent # haconf -dump -makero 4. Stop the cluster on all nodes. If the cluster is writable, you may close the configuration before stopping the cluster. # haconf -dump -makero From any node, execute the following command. # hastop -all or # hastop -all -force Verify that the cluster is stopped on all nodes by running the ha command. # hasys -state On all nodes, make sure that both had and hashadow processes are stopped. Installing the Patch: -------------------- 1. Un-compress the downloaded patch from Symantec. Change directory to the unzipped patch location. Install the VRTSvcsag 5.0RP3HF1/11iv3 (PVCO_03900) patch using the following command: # swinstall -s [dir]/patches PVCO_03900 2. Verify that the new patch has been installed: # swlist PVCO_03900 You will find the following output on display with the patch installed properly: PVCO_03900 1.0 VRTS 5.0 RP3 HF1 VRTSvcsag Command Patch Re-starting VCS on the cluster node: ----------------------------------- 1. At this time, you can start the cluster services on all cluster nodes. First start VCS on one node: # hastart On all the other nodes, start VCS by issuing hastart after the first node goes to LOCAL_BUILD or RUNNING state. 2. Unfreeze all the groups. # haconf -makerw # hagrp -unfreeze [group] -persistent # haconf -dump -makero UNINSTALLING THE PATCH: ----------------------- Follow the steps given below in all the systems: Steps to remove the Patch from a cluster node: --------------------------------------------- 1. Follow the steps provided under "Stopping VCS on the cluster node" section above, to stop VCS on the node. 2. Remove the patch by the following command: # swremove PVCO_03900 3. Verify that the patch has been removed from the system: # swlist PVCO_03900 If the patch gets removed successfully, the command will not display any output. 4. Follow the steps in "Re-starting VCS on the cluster node" section above to restart VCS on the node.