README VERSION		: 1.0
README Creation Date	: 2011-09-13
Patch-ID 		: 5.1.112.0 
Patch Name		: VRTSgab-5.1SP1RP2-aix
BASE PACKAGE NAME	: Veritas Group Membership and Atomic Broadcast by Symantec
BASE PACKAGE VERSION	: VRTSgab 5.1SP1/5.1SP1PR1
Obsolete Patches	: NONE
Superseded Patches	: NONE
Required Patches	: NONE
Incompatible Patches	: NONE
Supported PADV		: aix
(P-Platform , A-Architecture , D-Distribution , V-Version)
Patch Category		:  HANG ,  PANIC
Reboot Required		: YES

KNOWN ISSUES : 


FIXED INCIDENTS: 


 Patch Id::5.1.112.0

 * 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

 * Incident no::2508637	 Tracking ID ::2508633

 Symptom::If the GAB driver fails to unload due to a device removal error on a 
system, and if you repeatedly try to unload the GAB driver, the system crashes.

 Description::When the GAB driver fails to unload due to the device removal 
error, the GAB module deletes its data structures without checking for the 
device removal error. If you try to unload the GAB driver again, the GAB module 
attempts to access the deleted data structures, and the system crashes.

 Resolution::Symantec has modified the GAB module to check for the device 
removal error. If the check fails, the module does not delete its data 
structures, and the system crash is prevented.

Incidents from old Patches:
---------------------------
NONE