* * * READ ME * * *
                          * * * CPI 6.1 * * *
                      * * * Patch 6.1.0.300 * * *
                         Patch Date: 2015-06-10


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
----------
CPI 6.1 Patch 6.1.0.300


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
AIX 6.1
AIX 7.1
RHEL5 x86-64
RHEL6 x86-64
SLES11 x86-64
Solaris 10 SPARC
Solaris 11 SPARC



BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Symantec Application HA 6.1
   * Symantec Cluster Server 6.1
   * Symantec Dynamic Multi-Pathing 6.1
   * Symantec Storage Foundation 6.1
   * Symantec Storage Foundation Cluster File System HA 6.1
   * Symantec Storage Foundation for Oracle RAC 6.1
   * Symantec Storage Foundation for Sybase ASE CE 6.1
   * Symantec Storage Foundation HA 6.1
   * Symantec Volume Manager 6.1


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: 6.1.0.300
* 3390290 (3542842) During upgrade, the Sun Microsystems Label (SMI) label changes to Extensible 
Firmware Interface (EFI) and makes the  disk group un-importable.
* 3658198 (3658195) Since RHEL 6.6 is released, installer should notify users to download Symantec 
product patches when they install SFHA on RHEL 6.6.
* 3796899 (3800404) Oracle agent user configuration is not migrated during 
upgrade.


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

Patch ID: 6.1.0.300

* 3390290 (Tracking ID: 3542842)

SYMPTOM:
The Symantec Product Installer attempts to start the vxconfigd daemon before 
upgrade, which leads to data corruption.

DESCRIPTION:
In Volume Manager (VxVM), while upgrading from 5.1SP1 5.1SP1RP1, 5.1SP1RP2, or 
5.1SP1RP3, the LUNs over 1 Terabyte(TB) in size encounter data corruption.
TechNote: http://www.symantec.com/business/support/index?
page=content&id=TECH188018
 
During upgrade from 5.1SP1, 5.1SP1RP1, 5.1SP1RP2, or 5.1SP1RP3 to 6.0 release, 
the Symantec Product Installer attempts to start vxconfigd daemon before 
upgrade which leads to data corruption.

RESOLUTION:
The code is modified to prevent the vxconfigd daemon from getting started while 
upgrading from 5.1SP1, 5.1SP1RP1, 5.1SP1RP2 or 5.1SP1RP3.

* 3658198 (Tracking ID: 3658195)

SYMPTOM:
In previous release, if users install SFHA on RHEL 6.6, installer gives an 
error and notifies users that the current kernel release is not supported.

DESCRIPTION:
Since RHEL 6.6 is released, SFHA now supports it with branches including 
6.0.1/6.0.5/6.1/6.1.1. Installer need to change the notification to guide 
customers to find corresponding patches.

RESOLUTION:
Installer notifies customers to download Symantec product patches when they 
install SFHA on RHEL 6.6.

* 3796899 (Tracking ID: 3800404)

SYMPTOM:
After using the Common Product Installer to upgrade, the previous agent 
user configurations are not migrated.

DESCRIPTION:
While upgrading to 6.1, the installer does not migrate user 
configurations such as Netlsnr ToleranceLimit and OnlineRestartlimit. This is 
because the installer fails to recognize user's existing agent configurations 
during dynamic upgrade.

RESOLUTION:
The dynamic upgrade function is changed to differentiate user's 
existing agent configurations before upgrade, so that all user configurations 
can be kept after upgrade.



INSTALLING THE PATCH
--------------------
1. Copy the hot-fix CPI_6.1_P3.pl to /tmp
2. Run installation scripts with the hot-fix
Example:
./installer -require /tmp/CPI_6.1_P3.pl


REMOVING THE PATCH
------------------
NONE


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


OTHERS
------
NONE