* * * READ ME * * *
                * * * Veritas Cluster Server 6.0.3 * * *
                      * * * Public Hot Fix 1 * * *
                         Patch Date: 2013-04-25


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 1


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
Solaris 11 SPARC
Solaris 11 X86


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: 6.0.300.100
* 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: 6.0.300.100

* 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 patch by using the following commands:

   (a) Set the publisher
       #pkg set-publisher -p VRTSamf.p5p Symantec
   (b) Install the patch
       #pkg install --accept --no-backup-be VRTSamf

4) Verify whether the patch has been applied successfully.
   Output for the following command should show version of VRTSamf as 6.0.300.100
 #pkg info VRTSamf

5) Enable AMF
 #svcadm enable amf

6) Install VRTSvcsag 6.0.300.100 (or higher) patch.


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) Uninstall AMF
Note: Uninstalling the patch will remove the entire package. If you need earlier version of the package, install it from the original source media.
 #pkg uninstall VRTSamf


SPECIAL INSTRUCTIONS
--------------------
After this VRTSamf package has been successfully installed, it is recommended to install VRTSvcsag 6.0.300.100 (or higher) package.


OTHERS
------
NONE