* * * READ ME * * * * * * Veritas Cluster Server 6.0.4 * * * * * * Public Hot Fix 1 * * * Patch Date: 2013-11-01 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.4 Public Hot Fix 1 OPERATING SYSTEMS SUPPORTED BY THE PATCH ---------------------------------------- SLES10 x86-64 PACKAGES AFFECTED BY THE PATCH ------------------------------ VRTSvcsag BASE PRODUCT VERSIONS FOR THE PATCH ----------------------------------- * Veritas Cluster Server 6.0.2 * Veritas Storage Foundation High Availability 6.0.2 SUMMARY OF INCIDENTS FIXED BY THE PATCH --------------------------------------- Patch ID: 6.0.400.100 * 3323833 (3318335) VMwareDisks resource faults during data store migration of VM or during creation, deletion, or reversal of the VMsnapshot. DETAILS OF INCIDENTS FIXED BY THE PATCH --------------------------------------- This patch fixes the following Symantec incidents: Patch ID: 6.0.400.100 * 3323833 (Tracking ID: 3318335) SYMPTOM: In a VMware environment, during virtual machine (VM) snapshot creation or deletion, or during datastore migration, the VMwareDisks resource may fault. In such cases, the DiskPath attribute may contain multiple entries for storage disks attached to the same SCSI target and port. DESCRIPTION: During snapshot creation or deletion, or during datastore migration, the VMwareDisks agent updates the DiskPath attribute. If you frequently create or delete VM snapshots, the DiskPath attribute may retain stale entries. If multiple stale entries have storage disks attached to the same SCSI target, port, and UUID, the VMwareDisks resource faults. RESOLUTION: The VMwareDisks agent is modified to automatically correct any stale entries in the DiskPaths attribute. INSTALLING THE PATCH -------------------- Perform the following steps on all nodes in the VCS cluster: 1. Take backup of your configurations. 2. Stop VCS on the cluster node. 3. Install the patch. 4. Restart VCS on the node. Stopping VCS on the cluster node -------------------------------- Perform the following steps: 1. Ensure that the "/opt/VRTSvcs/bin" directory is included in your PATH environment variable so that you can execute all the VCS commands. Refer to Veritas Cluster Server Installation Guide for more information. 2. Ensure that the version of VRTSvcsag for Linux is 6.0.3 3. Freeze all the service groups persistently. # haconf -makerw # hagrp -freeze [group] -persistent 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. Also, stop the VCS CmdServer on all nodes. # CmdServer -stop Installing the Patch -------------------- Perform the following steps: 1. Un-compress the downloaded patch from Symantec. Change the directory to the uncompressed patch location. Install the VRTSvcsag patch using the following command: i. For RHEL5: # rpm -Uvh VRTSvcsag-6.0.400.100-GA_RHEL6.i686.rpm ii. For RHEL6: # rpm -Uvh VRTSvcsag-6.0.400.100-GA_RHEL6.i686.rpm iii. For SLES10: # rpm -Uvh VRTSvcsag-6.0.400.100-GA_SLES10.i586.rpm iv. For SLES11: # rpm -Uvh VRTSvcsag-6.0.400.100-GA_SLES11.i586.rpm 2. Run the following command to verify if the new patch has been installed: # rpm -q VRTSvcsag If the proper patch is installed, the following output is displayed: i. For RHEL5: # VRTSvcsag-6.0.400.100-GA_RHEL6.i686 ii. For RHEL6: # VRTSvcsag-6.0.400.100-GA_RHEL6.i686 iii. For SLES10: # VRTSvcsag-6.0.400.100-GA_SLES10.i586 iv. For SLES11: # VRTSvcsag-6.0.400.100-GA_SLES11.i586 Re-starting VCS on the cluster node ----------------------------------- 1. To start the cluster services on all cluster nodes. Execute the following command first on one node: # hastart On all the other nodes, start VCS by executing the hastart command after the first node goes to LOCAL_BUILD or RUNNING state. 2. Make VCS cluster writable. # haconf -makerw 3. Unfreeze all the groups. # hagrp -unfreeze [group] -persistent # haconf -dump -makero REMOVING THE PATCH ------------------ Removal of the patch will result in removing the whole package from the system/node. To go back to a previous installed version of the package, you may need to re-install the package. Run the following steps on all the VCS cluster nodes: To remove the patch from a cluster node: --------------------------------------------- 1. Freeze all the service groups persistently. # haconf -makerw # hagrp -freeze [group] -persistent 2. Stop VCS on the node by following the steps provided in the section "Stopping VCS on the cluster node". 3. Remove the patch by using the following command: # rpm -e VRTSvcsag 4. Verify that the patch has been removed from the system: # rpm -qa | grep VRTSvcsag Ensure that the VRTSvcsag package is not be displayed. This confirms that the package is removed. 5. Install the VRTSvcsag package from the VCS 6.0.3 Installation DVD. 6. To start the cluster services on all cluster nodes, execute the following command first on one node: # hastart On all the other nodes, start VCS by executing hastart after the first node goes to LOCAL_BUILD or RUNNING state. 7. Unfreeze all the groups. # hagrp -unfreeze [group] -persistent # haconf -dump -makero SPECIAL INSTRUCTIONS -------------------- NONE OTHERS ------ NONE