README VERSION : 1.0 README Creation Date : 2011-09-16 PATCH-ID : PHKL_42252 PATCH NAME : VRTSvxfen 5.1SP1RP1-HP BASE PACKAGE NAME : VRTS 5.1 SP1RP1 VRTSvxfen Kernel Patch for Windows BASE PACKAGE VERSION : VRTSvxfen 51SP1 OBSOLETE PATCHES : NONE SUPERSEDED PATCHES : NONE REQUIRED PATCHES : NONE INCOMPATIBLE PATCHES : NONE SUPPORTED PADV : hpux1131 (P-Platform , A-Architecture , D-Distribution , V-Version) PATCH CATEGORY : OTHER REBOOT REQUIRED : YES KNOWN ISSUES : FIXED INCIDENTS: ---------------- Patch Id::PHKL_42252 * Incident no::2400485 Tracking ID ::2400473 Symptom::When the Veritas fencing module (VxFEN) starts, it may encounter issues in reading coordination point information. VxFEN may display an error such as: V-11-2-1036 Unable to configure VxFEN since daemon failed to talk to the driver. The user mode process that processes coordination point information may abort. If you then try to configure the driver in another fencing mode, VxFEN displays the following error: V-11-2-1050 Mismatched modes on local node and running cluster. Unable to configure vxfen Description::The problem occurs because the variable that tracks the fencing mode is incorrectly passed from the user land configuration files to the VxFEN kernel driver. Resolution::Symantec has modified the VxFEN kernel driver to properly reset the fencing mode variables when it receives an error from the user land. * Incident no::2426663 Tracking ID ::2426659 Symptom::If you run the 'vxfenswap' command to change the fencing mode from 'customized' to 'scsi3', the vxfend process continues to run. Description::The kernel driver of the Veritas fencing module (VxFEN) starts the vxfend process only when VxFEN is configured in a customized mode. However, when you change the fencing mode to 'scsi3', the VxFEN kernel driver fails to terminate the vxfend process. Resolution::Symantec has modified the VxFEN kernel driver to appropriately terminate the vxfend process. INCIDENTS FROM OLD PATCHES: --------------------------- NONE