* * * READ ME * * * * * * Symantec Storage Foundation HA 6.1.1 * * * * * * Patch 6.1.1.100 * * * Patch Date: 2016-05-27 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 ---------- Symantec Storage Foundation HA 6.1.1 Patch 6.1.1.100 OPERATING SYSTEMS SUPPORTED BY THE PATCH ---------------------------------------- AIX 7.1 PACKAGES AFFECTED BY THE PATCH ------------------------------ VRTSamf VRTSdbac VRTSgab VRTSllt VRTSvxfen BASE PRODUCT VERSIONS FOR THE PATCH ----------------------------------- * Symantec Cluster Server 6.1 * Symantec Storage Foundation Cluster File System HA 6.1 * Symantec Storage Foundation for Oracle RAC 6.1 * Symantec Storage Foundation HA 6.1 SUMMARY OF INCIDENTS FIXED BY THE PATCH --------------------------------------- Patch ID: VRTSdbac-6.1.1.100 * 3879316 (3879995) The LMX module did not load on AIX 7.1 TL4 Patch ID: VRTSllt-6.1.1.100 * 3877581 (3875938) Veritas Cluster Server (VCS) does not support AIX 7.1 TL4. Patch ID: VRTSllt-6.1.1.000 * 3390268 (3333290) Low Latency Transport (LLT) module may panic the node when module is unloaded. Patch ID: VRTSgab-6.1.0.100 * 3877582 (3875938) Veritas Cluster Server (VCS) does not support AIX 7.1 TL4. Patch ID: VRTSvxfen-6.1.1.100 * 3877583 (3875938) Veritas Cluster Server (VCS) does not support AIX 7.1 TL4. Patch ID: VRTSvxfen-6.1.1.000 * 3370486 (3031216) The dash (-) in a disk group name causes vxfentsthdw(1M) and Vxfenswap(1M) utilities to fail. * 3530046 (3471571) Cluster nodes may panic if you stop the HAD process by force on a node and reboot that node. * 3532861 (3532859) The Coordpoint agent monitor fails if the cluster has a large number of coordination points. Patch ID: VRTSamf-6.1.1.200 * 3877584 (3875938) Veritas Cluster Server (VCS) does not support AIX 7.1 TL4. Patch ID: VRTSamf-6.1.1.100 * 3576215 (3574612) After Asynchronous Monitoring Framework (AMF) is unconfigured and unloaded, the system panics during a file operation (for example: remove, rename or directory remove) on a Network File System (NFS). DETAILS OF INCIDENTS FIXED BY THE PATCH --------------------------------------- This patch fixes the following Symantec incidents: Patch ID: VRTSdbac-6.1.1.100 * 3879316 (Tracking ID: 3879995) SYMPTOM: The LMX modules did not load appropriately on AIX 7.1 TL4 DESCRIPTION: After configuring SFRAC , the LMX driver was not loaded. # /etc/rc.d/rc2.d/S71lmx start Starting LMX # /etc/methods/lmxext -status lmx: unloaded RESOLUTION: Appropriate changes are made to load the lmx module. Patch ID: VRTSllt-6.1.1.100 * 3877581 (Tracking ID: 3875938) SYMPTOM: VCS does not support AIX 7.1 TL4. DESCRIPTION: VCS does not support AIX versions higher than AIX 7.1 TL3. RESOLUTION: VCS support for AIX 7.1 TL4 is now introduced. Patch ID: VRTSllt-6.1.1.000 * 3390268 (Tracking ID: 3333290) SYMPTOM: Low Latency Transport (LLT) module may panic the node when module is unloaded. DESCRIPTION: LLT uses the xmfree() function of the AIX operating system to free network messages. This function takes a heap as an argument. This heap is created before allocating memory in AIX. In rare cases, during an LLT module unload, due to a race condition LLT may destroys this heap while LLT frees messages using the xmfree() function. This causes LLT to panic the node. RESOLUTION: The code is modified to prevent such race conditions. Patch ID: VRTSgab-6.1.0.100 * 3877582 (Tracking ID: 3875938) SYMPTOM: VCS does not support AIX 7.1 TL4. DESCRIPTION: VCS does not support AIX versions higher than AIX 7.1 TL3. RESOLUTION: VCS support for AIX 7.1 TL4 is now introduced. Patch ID: VRTSvxfen-6.1.1.100 * 3877583 (Tracking ID: 3875938) SYMPTOM: VCS does not support AIX 7.1 TL4. DESCRIPTION: VCS does not support AIX versions higher than AIX 7.1 TL3. RESOLUTION: VCS support for AIX 7.1 TL4 is now introduced. Patch ID: VRTSvxfen-6.1.1.000 * 3370486 (Tracking ID: 3031216) SYMPTOM: 1. If the specified disk group name contains a dash (-), (e.g. vxfendg-vmax) and there is another disk group in the system (e.g. vxfendg) whose name matches the characters to the left of the dash in the specified disk group name, the vxfentsthdw(1M) utility fails. 2. If the current disk group name contains a dash (-), (e.g. vxfendg-vmax) and the replacement disk group name (e.g. vxfendg) matches the characters to the left of the dash in the current disk group name, the vxfenswap(1M) utility fails with the following message: vxfenconfig ERROR V-11-2-1004 There must be an odd number of coordinator disks defined DESCRIPTION: 1. Under condition 1, the "vxfentsthdw -g ||replacementDiskGroup!!" command attempts to test all the disks in both the replacement disk group and the current fencing disk group. Since the disks in the current disk group are in use and have keys, the utility fails, which requests the user to shut down fencing and continue. 2. Under condition 2, the "vxfenswap -g ||replacementDiskGroup!!" command fails to validate the new coordination points because it conflates the disks in the replacement disk group with the disks in the original disk group, which leads to an even number of coordinator disks. RESOLUTION: The code is modified to correctly determine the disks of the disk group which has a dash (-) in its name. * 3530046 (Tracking ID: 3471571) SYMPTOM: Cluster nodes may panic if you stop the HAD process by force on a node and reboot or shutdown that node. DESCRIPTION: When you execute the following steps on any of the nodes in a cluster, the kernel may panic on any of the nodes in the cluster: 1. Stop the HAD process with the force flag: # hastop -local -force or # hastop -all -force 2. Reboot or shut down the node. Cluster nodes may panic because forcefully stopping VCS on a node leaves all the applications, file systems, CVM, and other processes on that node online. If you reboot the node with applications and processes in online state, VCS triggers a fencing race to avoid data corruption. The sub-cluster that loses the race panics. To ensure that rebooted node loses the race, increase LLT peerinact timeout on that node by running the lltconfig command. RESOLUTION: Symantec has fixed this issue such that rebooted node loses the fencing race and panics. The fix prevents the case where the rebooted node can win the fencing race and therefore cause other nodes in the cluster to panic. * 3532861 (Tracking ID: 3532859) SYMPTOM: The Coordination Point (Coordpoint) agent monitor fails if the cluster includes more than 15 disks, or disks in raw mode with more than 15 paths, or 15 disks and 1 or more Coordination Point Servers. DESCRIPTION: The Coordpoint agent issue is caused because the data used by the agent about the coordination points is acquired using the vxfenconfig -L(1M) command which is not able to handle these many coordination points and prints invalid message. RESOLUTION: The code is modified to fix this issue. Patch ID: VRTSamf-6.1.1.200 * 3877584 (Tracking ID: 3875938) SYMPTOM: VCS does not support AIX 7.1 TL4. DESCRIPTION: VCS does not support AIX versions higher than AIX 7.1 TL3. RESOLUTION: VCS support for AIX 7.1 TL4 is now introduced. Patch ID: VRTSamf-6.1.1.100 * 3576215 (Tracking ID: 3574612) SYMPTOM: After Asynchronous Monitoring Framework (AMF) is unconfigured and unloaded, the system panics during a file operation (for example: remove, rename or directory remove) on a Network File System (NFS). DESCRIPTION: Under certain circumstances, after AMF is unconfigured and unloaded, the system panics during a file operation (for example: remove, rename or directory remove) on a Network File System (NFS) . RESOLUTION: The AMF driver has been modified to fix this issue. INSTALLING THE PATCH -------------------- Run the Installer script to automatically install the patch: ----------------------------------------------------------- To install the patch perform the following steps on at least one node in the cluster: 1. Copy the hot-fix sfha-aix71-Patch-6.1.1.100.tar.gz to /tmp 2. Untar sfha-aix71-Patch-6.1.1.100.tar.gz to /tmp/hf # mkdir /tmp/hf # cd /tmp/hf # gunzip /tmp/sfha-aix71-Patch-6.1.1.100.tar.gz # tar xf /tmp/sfha-aix71-Patch-6.1.1.100.tar 3. Install the hotfix # pwd /tmp/hf # ./installSFHA611P100 [ ...] Install the patch manually: -------------------------- To apply the patch manually, perform the steps listed below on each node in the cluster. 1. Stop VCS vcsmm and lmx: #hastop -local #/etc/init.d/vcsmm.rc stop #/etc/init.d/lmx.rc stop 2. Apply the VRTSdbac patch by issuing the following commands: #installp -aX -d ./VRTSdbac.bff VRTSdbac 3. Verify that the new patch is installed. The output of the following command should display the version for VRTSdbac package as 6.1.1.100 #lslpp -l VRTSdbac 4. Start vcsmm lmx and VCS: #/etc/init.d/vcsmm.rc start #/etc/init.d/lmx.rc start # hastart REMOVING THE PATCH ------------------ Run the Uninstaller script to automatically remove the patch: ------------------------------------------------------------ To uninstall the patch perform the following step on at least one node in the cluster: # /opt/VRTS/install/uninstallSFHA611P100 [ ...] Remove the patch manually: ------------------------- 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 the node where the patch is being uninstalled: To remove the patch from a cluster node: --------------------------------------------- 1. Stop VCS vcsm and lmx: #hastop -local #/etc/init.d/vcsmm.rc stop #/etc/init.d/lmx.rc stop 2. Remove the patch by using the following command: # installp -r VRTSdbac 6.1.1.100 3. Verify that the patch has been removed from the system: # lslpp -l VRTSdbac Ensure that the package is not be displayed. This confirms that the package is removed. 4. Install the relevant package from the SFRAC base media. 5. start the vcsmm lmx and VCS: #/etc/init.d/vcsmm.rc start #/etc/init.d/lmx.rc start #hastart SPECIAL INSTRUCTIONS -------------------- NONE OTHERS ------ NONE