* * * READ ME * * *
                         * * * CPI 7.0.1 * * *
                         * * * Patch 300 * * *
                         Patch Date: 2016-05-18


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 7.0.1 Patch 300


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
AIX
RHEL6 x86-64
RHEL7 x86-64
SLES11 x86-64
SLES12 x86-64
Solaris 10 SPARC
Solaris 11 SPARC



BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * InfoScale Availability 7.0
   * InfoScale Enterprise 7.0
   * InfoScale Foundation 7.0
   * InfoScale Storage 7.0


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: 7.0.1.300
* 3865899 (3866180) The installer fails to configure I/O fencing.
* 3866781 (3867243) After configuring CP based fencing, VxFEN fails to start.
* 3878735 (3879593) Veritas product installation fails for the new operating system (OS) update version since the installer cannot validate the correct version of dependency Operating System (OS) rpms for the new OS update.


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

Patch ID: 7.0.1.300

* 3865899 (Tracking ID: 3866180)

SYMPTOM:
After fencing is configured, VxFEN fails to start.

DESCRIPTION:
VxFEN fails to start if the installer uses the openssl command installed with 
OS, because the version of the openssl command is not latest enough to support 
the -sha256 option. As a result, the openssl command fails to generate the csr 
file. The fencing fails to start because of the csr file missing.

RESOLUTION:
The installer is modified to use the openssl command shipped with the VRTSperl 
package.

* 3866781 (Tracking ID: 3867243)

SYMPTOM:
After configuring CP based fencing, VxFEN fails to start.

DESCRIPTION:
On CP client side, the installer uses the openssl command shipped with VRTSperl. On CP server 
side, the installer still uses the openssl command installed with OS if the OS platforms of 
the CP client side and the CP server side are different. 
The version of the openssl command installed with OS may not be latest enough to support the 
-sha256 option, which is used on the server side when the installer sets up HTTPS trust 
between CP server and CP client. In this case, the openssl command fails to generate the csr 
file, causing the VxFEN to fail to start.

RESOLUTION:
The code is modified to use the openssl command shipped with the VRTSperl package on both the 
CP client side and the CP server side.

* 3878735 (Tracking ID: 3879593)

SYMPTOM:
Veritas product installation failed for the new OS update version.

DESCRIPTION:
During installation, the installer verifies the dependency rpms of OS for the
product. For the new OS update version, there is no defined
or set dependency rpms value. Hence, the product installation fails or the
installer displays incorrect versions of OS rpms.

RESOLUTION:
Set a default dependency OS rpms for each platform (RHEL6, RHEL7, SLES11, and
SLES12) and for each release. Remove the specific version for each rpm, just
keep the rpm name and architecture type, like: glibc.x86_64.



INSTALLING THE PATCH
--------------------
1. Copy the hot-fix CPI_7.0.1_P3.pl to /tmp
 2. Run installation or configuration scripts with the hotfix
Example:
./installmr -require /tmp/CPI_7.0.1_P3.pl


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


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


OTHERS
------
NONE