README VERSION : 1.1 README CREATION DATE : 2013-08-16 PATCH-ID : 145456-05 PATCH NAME : VRTSvxfen 5.1.104.000 BASE PACKAGE NAME : VRTSvxfen BASE PACKAGE VERSION : 5.1.100.000 SUPERSEDED PATCHES : NONE REQUIRED PATCHES : NONE INCOMPATIBLE PATCHES : NONE SUPPORTED PADV : sol10_x64 (P-PLATFORM , A-ARCHITECTURE , D-DISTRIBUTION , V-VERSION) PATCH CATEGORY : OTHER PATCH CRITICALITY : CRITICAL HAS KERNEL COMPONENT : YES ID : NONE REBOOT REQUIRED : NO REQUIRE APPLICATION DOWNTIME : Yes PATCH INSTALLATION INSTRUCTIONS: -------------------------------- Please refer to Release Notes for install instructions PATCH UNINSTALLATION INSTRUCTIONS: ---------------------------------- Please refer to Release Notes for uninstall instructions SPECIAL INSTRUCTIONS: --------------------- NONE SUMMARY OF FIXED ISSUES: ----------------------------------------- PATCH ID:145456-05 3002938 (3002932) The VxFEN module fails to stop on restarting a node that leads to a failure of removing the keys. 3143199 (3042545) Support for protocol 30 is required in 5.1SP1RP3 setups to enable RU to 6.0.1. SUMMARY OF KNOWN ISSUES: ----------------------------------------- NONE KNOWN ISSUES : -------------- NONE FIXED INCIDENTS: ---------------- PATCH ID:145456-05 * INCIDENT NO:3002938 TRACKING ID:3002932 SYMPTOM: In a Veritas Cluster Server (VCS) setup, if you attempt to restart a cluster node by running one of the following platform-specific commands, the fencing module VXFEN fails to stop. On Solaris: # /usr/sbin/shutdown -i6 -g0 -y On Linux: # /sbin/shutdown -r now On HPUX: # /usr/sbin/shutdown -r now On AIX: # /usr/sbin/shutdown -r DESCRIPTION: During a node restart, if one or more VxFEN client processes continue to run, then the VxFEN module fails to stop. RESOLUTION: The code is modified to implement a retry logic such that after a node is restarted the VxFEN module periodically tries to stop itself for a specific number of times. The retry logic gives client processes enough time to stop. * INCIDENT NO:3143199 TRACKING ID:3042545 SYMPTOM: Users may be unable to perform rolling upgrades from Veritas Cluster Server (VCS) 5.1SP1RP3 to 6.0 or 6.0.1. DESCRIPTION: This behavior occurs due to a protocol mismatch. The Veritas fencing module (VxFEN) 5.1SP1RP3 uses protocol version 23. However, in releases 6.0 and 6.0.1, the fencing module can only run on protocol versions 10, 20, or 30. As a result, the fencing module fails to start, during the above-mentioned rolling upgrade. RESOLUTION: The VCS fencing module is modified to operate with protocol version 30. With this change rolling upgrades from 5.1SP1RP4 to release 6.0 or 6.0.1 will be successful. INCIDENTS FROM OLD PATCHES: --------------------------- NONE