* * * READ ME * * * * * * Veritas Cluster Server 6.0.3 * * * * * * Public Hot Fix 1 * * * Patch Date: 2013-03-26 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.3 Public Hot Fix 1 OPERATING SYSTEMS SUPPORTED BY THE PATCH ---------------------------------------- SLES11 x86-64 PACKAGES AFFECTED BY THE PATCH ------------------------------ VRTSamf BASE PRODUCT VERSIONS FOR THE PATCH ----------------------------------- * Veritas Cluster Server 6.0.1 * Veritas Storage Foundation for Oracle RAC 6.0.1 * Veritas Storage Foundation Cluster File System 6.0.1 * Veritas Storage Foundation High Availability 6.0.1 * Symantec VirtualStore 6.0.1 SUMMARY OF INCIDENTS FIXED BY THE PATCH --------------------------------------- Patch ID: 6.0.300.100 * 3090243 (3090229) AMF driver panics the node when vxconfigd is unresponsive. * 3097346 (3097342) AMF driver panics the node when AMF is being stopped. DETAILS OF INCIDENTS FIXED BY THE PATCH --------------------------------------- This patch fixes the following Symantec incidents: Patch ID: 6.0.300.100 * 3090243 (Tracking ID: 3090229) SYMPTOM: AMF driver panics the node when vxconfigd is unresponsive. DESCRIPTION: The libusnp_vxnotify.so library, used for disk group notifications, goes into an infinite loop when vxconfigd daemon is unresponsive. This causes AMF to enter an inconsistent state; as a result, the AMF driver panics the node. RESOLUTION: Symantec has modified the AMF driver and libusnp_vxnotify.so library to address this issue. * 3097346 (Tracking ID: 3097342) SYMPTOM: AMF driver panics the node when AMF is being stopped. DESCRIPTION: When AMF driver is being stopped, it stops the IMFD daemon. The code to handle this sleeps while holding a lock. This causes AMF driver to panic the node. RESOLUTION: Symantec has modified the AMF driver to fix this issue. INSTALLING THE PATCH -------------------- The VRTSamf-6.0.300.100 patch may be installed either manually (see below) or using the included installer. * To apply the patch using the installer, enter the commands # cd && ./installAMF603P1 [ ... ] where is the directory where you unpacked this hotfix , , ... are the nodes to be patched. If none are specified, you will be prompted to enter them interactively. All nodes must belong to a single cluster. For information about installer options, run './installAMF603P1 -help'. * To apply the patch manually, perform the steps listed below on each node. 1) Unconfigure AMF: # /opt/VRTSamf/bin/amfconfig -Uof This will disable IMF functionality for all agents. 2) Stop AMF: # /etc/init.d/amf stop 3) Uninstall the older version of AMF: # rpm -e VRTSamf 4) Install this AMF Patch: # rpm -Uvh VRTSamf-6.0.300.100-GA_SLES11.x86_64.rpm 5) Start AMF: # /etc/init.d/amf start 6) Install VRTSvcsag 6.0.300.100 (or higher) patch [refer to section ``SPECIAL INSTRUCTIONS'' below]. REMOVING THE PATCH ------------------ 1) Unconfigure AMF: # /opt/VRTSamf/bin/amfconfig -Uof This will disable IMF functionality for all agents. 2) Stop AMF: # /etc/init.d/amf stop 3) Uninstall AMF: # rpm -e VRTSamf NOTE: This operation will remove the entire VRTSamf package. 4) To fully revert your systems, install the previous version of VRTSamf from original source media and re-enable AMF. SPECIAL INSTRUCTIONS -------------------- After this VRTSamf package has been successfully installed, it is recommended to install VRTSvcsag 6.0.300.200 (or higher) package. OTHERS ------ NONE