README VERSION : 1.1 README CREATION DATE : 2013-08-16 PATCH ID : 5.1.114.0 PATCH NAME : VRTSamf 5.1.114.0 BASE PACKAGE NAME : VRTSamf BASE PACKAGE VERSION : 5.1.100.0|5.1.110.0 SUPERSEDED PATCHES : NONE REQUIRED PATCHES : NONE INCOMPATIBLE PATCHES : NONE SUPPORTED PADV : aix53,aix61,aix71 (P-PLATFORM , A-ARCHITECTURE , D-DISTRIBUTION , V-VERSION) PATCH CATEGORY : PANIC 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:5.1.114.0 2535690 (2535680) The Veritas Cluster Server (VCS) engine log is flooded with error messages indicating that imf_getnotification failed. 2564376 (2564373) The MonitorMethod attribute does not change from IMF to Traditional, if the AMF module is unconfigured forcefully. 2937679 (2937673) While executing the amfstat command, the AMF driver causes a panic in the machine. 3140669 (2713877) The system panics when an event is registered with Asynchronous Monitoring Framework (AMF). 3140688 (2848009) Asynchronous Monitoring Framework (AMF) panics the system when an agent is exiting. 3222422 (3222541) The amfstat(1M) command prints erroneous column headings in the "Registered Reapers" section. SUMMARY OF KNOWN ISSUES: ----------------------------------------- NONE KNOWN ISSUES : -------------- NONE FIXED INCIDENTS: PATCH ID:5.1.114.0 * INCIDENT NO:2535690 TRACKING ID:2535680 SYMPTOM: The Veritas Cluster Server (VCS) engine log is flooded with error messages indicating that imf_getnotification failed. DESCRIPTION: If you unconfigure or stop the Asynchronous Monitoring Framework (AMF) module, the module fails to accordingly notify the script-based agents which are still registered with it. The agents continue to interact with AMF, and this leads to the error messages. RESOLUTION: The imf_getnotification binary has been fixed, so that it exits with appropriate values indicating that AMF is no longer available. * INCIDENT NO:2564376 TRACKING ID:2564373 SYMPTOM: MonitorMethod attribute does not change from IMF to Traditional, if the AMF module is unconfigured forcefully. DESCRIPTION: When AMF is unconfigured or stopped while some script based agents are still registered with it, these agents continue to try to interact with AMF because the agents have not received any indication that AMF has stopped. Hence, the MonitorMethod is still IMF rather than Traditional. RESOLUTION: The code is modified for the imf_getnotification binary to exit with appropriate values indicating that AMF is no longer available. * INCIDENT NO:2937679 TRACKING ID:2937673 SYMPTOM: When you execute the amfstat command, the AMF driver causes a panic in the machine. DESCRIPTION: A race condition between amfstat, group unregistration and event notification contexts gives a rise to a corner case causing a panic in the machine. RESOLUTION: The code is modified such that the AMF driver addresses this race condition. * INCIDENT NO:3140669 TRACKING ID:2713877 SYMPTOM: The system panics when an event is registered with Asynchronous Monitoring Framework (AMF). Here is the stack trace: amf_lock amf_s_wait_events amf_reaper_notify amfioctl amf_ioctl DESCRIPTION: VCS agents register resources with AMF for getting instantaneous notifications about state changes of those resources. During such a registration with AMF, if the resource state changes, the system may panic. RESOLUTION: The AMF driver is modified to handle this condition. * INCIDENT NO:3140688 TRACKING ID:2848009 SYMPTOM: Asynchronous Monitoring Framework (AMF) panics the system when an agent is exiting. DESCRIPTION: If an agent exits when AMF is notifying it about some events, sometimes AMF causes the system to panic. RESOLUTION: The code has been fixed to close the panic window. * INCIDENT NO:3222422 TRACKING ID:3222541 SYMPTOM: If you run the amfstat(1M) command, the output includes erroneous column headings in the "Registered Reapers" section. DESCRIPTION: The amfstat(1M) command output is erroneous because it uses the wrong message ID. RESOLUTION: The amfstat(1M) command has been modified to fix this problem. INCIDENTS FROM OLD PATCHES: --------------------------- NONE