* * * READ ME * * *
                          * * * CPI 6.1 * * *
                      * * * Patch 6.1.0.100 * * *
                         Patch Date: 2014-06-20


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.100


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
RHEL5 x86-64
RHEL6 x86-64
SLES11 x86-64



BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * 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 HA 6.1
   * Symantec Volume Manager 6.1


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: 6.1.0.100
* 3390290 (3542842) SMI Label changed to EFI during upgrade leaving diskgroup un-importable


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

Patch ID: 6.1.0.100

* 3390290 (Tracking ID: 3542842)

SYMPTOM:
The Symantec Product Installer attempts to start vxconfigd before upgrade, which 
may lead data corruption.

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

RESOLUTION:
CPI provides a patch for customer to avoid vxconfigd get started when upgrade 
from 5.1SP1, 5.1SP1RP1, 5.1SP1RP2 or 5.1SP1RP3.



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


REMOVING THE PATCH
------------------
1. Copy the hot-fix CPI_6.1.0_P1.pl to /tmp
2. Run uninstall scripts with the hot-fix
Example:
./installer -uninstall -require /tmp/CPI_6.1.0_P1.pl


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


OTHERS
------
NONE