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


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
------------------------------
VRTSgab


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
* 3151131 (3151130) GAB fails to load during bootup due to a add_drv race with LMX.


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

Patch ID: 6.0.300.100

* 3151131 (Tracking ID: 3151130)

SYMPTOM:
On Solaris 11, sometimes during bootup, GAB fails to get added in the system 
because of add_drv race with LMX.

DESCRIPTION:
When SMF framework starts adding/removing drivers, sometimes race happens 
between GAB and LMX and causes operation failure.

RESOLUTION:
Symantec is handling GAB driver add/remove failure by increasing retry count in 
the GAB init script for add_drv/rem_drv operations (which was not sufficient 
earlier) and by increasing GAB SMF service timeout.



INSTALLING THE PATCH
--------------------
Before installing VRTSgab p-patch on a Solaris 11 host, you can optionally
create a boot environment (BE) and install VRTSgab 6.0.300.100 p-patch on the
new BE.  Doing this makes it easier to revert to the current version of VRTSgab
if required in future.

To create a new boot environment, perform steps 1-4 below on each node.

 1. Identify the active boot environment (BE) by looking at the NR tag:
        # beadm list 

 2. Create a new boot environment: 
        # beadm create <new_BE_name> 
    
    where <new_BE_name> is any valid name not listed in step 1.
    Example:
        # beadm create sfha_gab_patch

 3. Activate the newly-created boot environment:
        # beadm activate <new_BE_name> 

 4. Reboot the node so that the new boot environment is active:
        # reboot 


The VRTSvcsag-6.0.300.100 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>  && ./installGAB603P1  [ <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  './installGAB603P1 -help'.
    

 *  To apply the patch manually, perform the steps listed below on each node 
    in the cluster.

 1. Save the configuration:
        # haconf -dump

 2. Stop VCS, vxfen, gab:
        # hastop -local -force 
        # svcadm disable -s vxfen 
        # svcadm disable -s gab 
    (Stop all the dependent services of GAB before stopping GAB)

 3. Apply the gab patch by issuing the following commands:

   a. Set the publisher
        # pkg set-publisher -p <patch_file_pathname>  Symantec 
      e.g:
        # pkg set-publisher -p /hotfix_dir/patches/VRTSgab.p5p  Symantec 
    
   b. Install the package
        # pkg install --accept VRTSgab 

 4. Verify that the new patch is installed.  The output of the following
    command should display the version for VRTSgab package as 6.0.300.100:
        # pkg info VRTSgab 

 5. Start gab and all its dependent services:
        # svcadm enable -s gab 
        # svcadm enable -s vxfen 
        # hastart 
    etc.


REMOVING THE PATCH
------------------
On Solaris 11, patch removal is not supported.  If you created a new boot
environment before installing the new VRTSgab package, you can revert to
the boot environment which was in effect prior to that installation.

 *  To revert to previous boot environment, perform steps 1-3 below on each
    cluster node.

 1. Activate the boot environment which was in effect prior to installing this
    patch (noted in step 1 of 'To create a new boot environment' above):
        # beadm activate <prev_BE_name> 

 2. Reboot the node so that the new boot environment takes effect:
        # reboot 

 3. (optional) If you have no further use for the boot environment on which
    you installed the patch, you may destroy it:
        # beadm destroy <new_BE_name> 
    
    Example:
        # beadm destroy sfha_gab-patch 

If you did not create a new boot environment, you must uninstall the version
of VRTSgab included in this patch and then re-install the prior version of
the package (6.0.300.0) from original source media.


SPECIAL INSTRUCTIONS
--------------------
NONE


OTHERS
------
NONE