* * * 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 boot environment. This will help to rollback to previous version in future if required.

To create a new boot environment

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

2 Create the BE:
# beadm create bename
For example,
# beadm create sfha_gab_patch

3 Activate the BE:
# beadm activate bename
For example,
# beadm activate sfha_gab_patch

4 Reboot the node so that new be is active now.
# 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 VCS 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 using the following command:

a. Set the publisher
    # pkg set-publisher -p <location of the patch_file>     Symantec
    e.g: # pkg set-publisher -p /patch_location/VRTSgab.p5p Symantec

b. Install the package
    # pkg install --accept --no-backup-be 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, removing a patch  is
not supported. Instead, if you have already created a boot environment for installing
p-patch, you can roll back to the previous boot environment available before installing
p-patch.

To roll back to previous boot environment
1 Activate the boot environment available before installing p-patch:
# beadm activate bename
2 Reboot the node so that new BE is active now:
# reboot
3 You may optionally destroy the boot environment on which p-patch is installed:
# beadm destroy bename
For example,
# beadm destroy sfha_gab-patch


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


OTHERS
------
NONE