* * * 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 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.200
* 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: 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.200

* 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: 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, the 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
--------------------
The VRTSamf-6.0.300.200 patch may be installed either manually (see below)
or using the included installer.

 *  To apply the patch using the installer, enter the commands 
        # cd <hotfix_directory>  && ./installAMF603P2  [ <node1> <node2>... ]
    
    where 
      <hotfix_directory>
                is the directory where you unpacked this hotfix
      <node1>, <node2>, ...
                are the nodes to be patched.  If none are specified, you
                will be prompted to enter them interactively.  All nodes
                must belong to a single cluster.
    
    For information about installer options, run  './installAMF603P2 -help'.
    

 *  To apply the patch manually, perform the steps listed below on each node.
 
 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 <patch_package_path>  Symantec 
      
      e.g.:
        # pkg set-publisher -p <hotfix_dir>/patches/VRTSamf.p5p  Symantec 
      
      where <hotfix_dir> is the directory where you unpacked this hotfix.

   (b) Install the patch
        # pkg install --accept VRTSamf 
 
 4) Verify that the patch has been applied successfully.
    Output from the following command should show version as 6.0.300.200:
        # pkg info VRTSamf
 
 5) Unset the publisher:
        # pkg unset-publisher Symantec
 
 6) Enable AMF:
        # svcadm enable amf
 
 7) Install VRTSvcsag 6.0.300.100 (or higher) patch [refer to section ``SPECIAL INSTRUCTIONS'' below].


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:
        # pkg uninstall VRTSamf
    
    NOTE:  This operation will remove the entire VRTSamf package.

 4) To fully revert your systems, install the previous version of VRTSamf from
    original source media and re-enable AMF.


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