README VERSION : 1.1 README CREATION DATE : 2014-04-03 PATCH-ID : 148498-02 PATCH NAME : VRTSamf 6.0.500.000 BASE PACKAGE NAME : VRTSamf BASE PACKAGE VERSION : 6.0.100.000 SUPERSEDED PATCHES : 148498-01 REQUIRED PATCHES : NONE INCOMPATIBLE PATCHES : NONE SUPPORTED PADV : sol10_sparc (P-PLATFORM , A-ARCHITECTURE , D-DISTRIBUTION , V-VERSION) PATCH CATEGORY : HANG , PANIC , PERFORMANCE PATCH CRITICALITY : CRITICAL HAS KERNEL COMPONENT : YES ID : NONE REBOOT REQUIRED : NO REQUIRE APPLICATION DOWNTIME : YES PATCH INSTALLATION INSTRUCTIONS: -------------------------------- Please refer to Install Guide for install instructions and Release Notes for other information. PATCH UNINSTALLATION INSTRUCTIONS: ---------------------------------- Please refer to Install Guide for uninstall instructions and Release Notes for other information. SPECIAL INSTRUCTIONS: --------------------- NONE SUMMARY OF FIXED ISSUES: ----------------------------------------- PATCH ID:148498-02 3145057 (3145047) The Asynchronous Monitoring Framework (AMF) driver causes a panic in the node after VXFS driver is unloaded. 3342983 (3341320) The "Cannot delete event (rid %d) in reaper" error message is repeatedly logged in the Syslog file. 3343002 (3338946) The Process resource fails to register for offline monitoring with the AMF kernel driver. 3343013 (3090229) The Asynchronous Monitoring Framework (AMF) driver panics the node when the vxconfigd daemon is unresponsive. 3343015 (3097342) The Asynchronous Monitoring Framework (AMF) driver causes a panic in the node when AMF is being stopped. 3343018 (3259682) If vxconfigd daemon hangs, then the registration thread of IMFD daemon trying to get disk group status from vxconfigd daemon also hangs. Therefore, the amfregister command waiting for IMFD daemon gets stuck. PATCH ID:148498-01 2937687 (2937673) AMF driver panics the machine when amfstat is executed. 3033604 (2848009) AMF panics the machine when an Agent is exiting. SUMMARY OF KNOWN ISSUES: ----------------------------------------- NONE KNOWN ISSUES : -------------- NONE FIXED INCIDENTS: ---------------- PATCH ID:148498-02 * INCIDENT NO:3145057 TRACKING ID:3145047 SYMPTOM: The Asynchronous Monitoring Framework (AMF) driver causes a panic in the machine after VXFS driver is unloaded. DESCRIPTION: Due to the way Asynchronous Monitoring Framework (AMF) interacts with VxFS, AMF has access into VXFS driver even if no file system is mounted without actually holding a module reference on it. Therefore, VxFS can get unloaded despite AMF having access into it. RESOLUTION: The code is modified so as to allow the AMF driver to access the VxFS driver only if at least one file system is mounted. * INCIDENT NO:3342983 TRACKING ID:3341320 SYMPTOM: The "Cannot delete event (rid %d) in reaper" error message is repeatedly logged in the Syslog file. DESCRIPTION: This message is logged redundantly into Syslog when the agent calls unregister request to Asynchronous Monitoring Framework (AMF) for an event whose state has already changed. RESOLUTION: The AMF code is modified so that the error message does not appear in the Syslog. * INCIDENT NO:3343002 TRACKING ID:3338946 SYMPTOM: The Process resource fails to register for offline monitoring with the AMF kernel driver. DESCRIPTION: Sometimes when a process offline registration is requested and the system is under a heavy load, the Asynchronous Monitoring Framework (AMF) library fails to verify if the resource is actually offline. This failure results in registration fails. RESOLUTION: The AMF library code is modified to handle the failure. * INCIDENT NO:3343013 TRACKING ID:3090229 SYMPTOM: The AMF driver panics the node when the vxconfigd daemon is unresponsive. DESCRIPTION: When the vxconfigd daemon is unresponsive, the libusnp_vxnotify.so library used for disk group notifications goes into an infinite loop. The loop causes AMF to enter an inconsistent state resulting the AMF driver to panic the node. RESOLUTION: The code of AMF driver and libusnp_vxnotify.so library is modified to address infinite loop issue. * INCIDENT NO:3343015 TRACKING ID:3097342 SYMPTOM: The Asynchronous Monitoring Framework (AMF) driver causes a panic in the node when AMF is being stopped. DESCRIPTION: When AMF driver is being stopped, it stops the IMFD daemon. The code to handle this sleeps while holding a lock. This causes AMF driver to panic the node. RESOLUTION: The code is modified for the AMF driver to fix this issue. * INCIDENT NO:3343018 TRACKING ID:3259682 SYMPTOM: Intelligent Monitoring Framework (IMF) registrations for disk group resources fail. DESCRIPTION: If the vxconfigd daemon is unresponsive, then IMFD daemon becomes unresponsive and the IMF registrations fail for the disk group resources. Subsequent attempts to un-configure AMF also fail. RESOLUTION: The IMFD code is modified to fix this problem. PATCH ID:148498-01 * INCIDENT NO:2937687 TRACKING ID:2937673 SYMPTOM: AMF driver panics the machine when amfstat is executed. DESCRIPTION: There was a race condition between amfstat, group unregistration and event notification contexts which gave rise to a corner case that caused the panic. RESOLUTION: Symantec has modified the AMF driver to address this race condition. * INCIDENT NO:3033604 TRACKING ID:2848009 SYMPTOM: AMF panics the machine when an Agent is exiting. DESCRIPTION: If an agent exits while AMF is notifying it about some events, sometimes AMF causes the machine to panic. RESOLUTION: Symantec has fixed code to close the panic window. INCIDENTS FROM OLD PATCHES: --------------------------- NONE