* * * READ ME * * *
                * * * Veritas Cluster Server 6.0.3 * * *
                      * * * Public Hot Fix 2 * * *
                         Patch Date: 2013-10-24


This document provides the following information:

   * PATCH NAME
   * OPERATING SYSTEMS SUPPORTED BY THE PATCH
   * PACKAGES AFFECTED BY THE PATCH
   * BASE PRODUCT VERSIONS FOR THE PATCH
   * SUMMARY OF INCIDENTS FIXED BY THE PATCH
   * DETAILS OF INCIDENTS FIXED BY THE PATCH
   * INSTALLATION PRE-REQUISITES
   * INSTALLING THE PATCH
   * REMOVING THE PATCH


PATCH NAME
----------
Veritas Cluster Server 6.0.3 Public Hot Fix 2


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
Solaris 10 X64


PACKAGES AFFECTED BY THE PATCH
------------------------------
VRTSamf


BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Veritas Cluster Server 6.0.1
   * Veritas Storage Foundation for Oracle RAC 6.0.1
   * Veritas Storage Foundation Cluster File System 6.0.1
   * Veritas Storage Foundation High Availability 6.0.1
   * Symantec VirtualStore 6.0.1


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: 149789-02
* 3331065 (3338946) Process Offline resources fail to register with AMF.
* 3331998 (3341320) Syslog gets flooded with "Cannot delete event (rid %d) in
reaper" error messages.
Patch ID: 149789-01
* 3090243 (3090229) AMF driver panics the node when vxconfigd is unresponsive.
* 3097346 (3097342) AMF driver panics the node when AMF is being stopped.


DETAILS OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
This patch fixes the following Symantec incidents:

Patch ID: 149789-02

* 3331065 (Tracking ID: 3338946)

SYMPTOM:
Process Offline resources fail to register with AMF.

DESCRIPTION:
Sometimes when a process offline registration is requested and the
system is under heavy load, AMF library fails to verify whether the resource is
actually offline. As a result, registration fails.

RESOLUTION:
AMF library is fixed to handle this failure.

* 3331998 (Tracking ID: 3341320)

SYMPTOM:
Syslog gets flooded with "Cannot delete event (rid %d) in reaper" error
messages.

DESCRIPTION:
This was a harmless error message which appeared in syslog.

RESOLUTION:
AMF code is modified so that the error message does not appear in
the syslog.

Patch ID: 149789-01

* 3090243 (Tracking ID: 3090229)

SYMPTOM:
AMF driver panics the node when vxconfigd is unresponsive.

DESCRIPTION:
The libusnp_vxnotify.so library used for disk group notifications,
goes into an infinite loop when vxconfigd daemon is unresponsive. This causes
AMF to enter an inconsistent state as a result of which AMF driver panics the node.

RESOLUTION:
Symantec has modified the AMF driver and libusnp_vxnotify.so
library, to address this issue.

* 3097346 (Tracking ID: 3097342)

SYMPTOM:
AMF driver panics 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:
Symantec has modified the AMF driver to fix this issue.



INSTALLING THE PATCH
--------------------
1) Unconfigure AMF
 #/opt/VRTSamf/bin/amfconfig -Uof
 
 This will disable IMF functionality for all agents.
 
2) Disable AMF
 #svcadm disable amf
 
3) Apply the P-patch
 #patchadd  149789-02
 
4) Verify whether the patch has been applied successfully.
 #showrev -p | grep 149789-02     
 
5) Enable AMF
 #svcadm enable amf


REMOVING THE PATCH
------------------
1) Unconfigure AMF
 #/opt/VRTSamf/bin/amfconfig -Uof
 
 This will disable IMF functionality for all agents.
 
2) Disable AMF
 #svcadm disable amf
 
3) Remove the P-patch
 #patchrm 149789-02

4) Enable AMF
 #svcadm enable amf


SPECIAL INSTRUCTIONS
--------------------
After the VRTSamf patch has been successfully applied, it is recommended to install VRTSvcsag 6.0.300.100 (or higher) patch.


OTHERS
------
NONE