README VERSION : 1.0 README Creation Date : 2011-09-08 Patch-ID : 143284-02 Patch Name : VRTSgab-5.1SP1RP2-sol10 BASE PACKAGE NAME : Veritas Group Membership and Atomic Broadcast by Symantec BASE PACKAGE VERSION : VRTSgab 5.1SP1 Obsolete Patches : NONE Superseded Patches : NONE Required Patches : NONE Incompatible Patches : NONE Supported PADV : sol10_sparc (P-Platform , A-Architecture , D-Distribution , V-Version) Patch Category : HANG Reboot Required : NO KNOWN ISSUES : FIXED INCIDENTS: ---------------- Patch Id::143284-02 * Incident no::2382380 Tracking ID ::2364959 Symptom::1. After installing 5.1sp1 without configuring when node is rebooted, LLT, GAB, FENCING and AMF goes in maintenance state. 2. After upgrade to 5.1SP1, local zones SMF dependencies complain about missing services and "svcs -x" is not clean Description::Install of 5.1SP1 or upgrade from 5.0 in a global zone only temporarily disables llt/gab/fencing/amf services. So after reboot they are re-enabled and SMF dependencies fail. Resolution::Changed the LLT, GAB, FENCING and AMF postinstall scripts to permanently disable services. Added a check not to create SMF service for non-global zones. * Incident no::2411653 Tracking ID ::2411651 Symptom::In the communication between GAB and GAB clients, GAB drops certain packets due to size restrictions and may cause the cluster to hang. Description::This is an enhancement required to ensure that when GAB drops a packet due to size restrictions, GAB logs an error message. In the absence of such an error message, a hung cluster condition may become difficult to troubleshoot. Resolution::Symantec has modified GAB to log an error message indicating the exceeded packet size. For example, the following error message: ---------------------- GAB ERROR V-15-1-20238 Client message size 66613 greater than GAB maximum allowed message size 66560 Incidents from old Patches: --------------------------- NONE