* * * READ ME * * *
                          * * * CPI 7.1 * * *
                         * * * Patch 300 * * *
                         Patch Date: 2017-01-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.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.1
   * InfoScale Enterprise 7.1
   * InfoScale Foundation 7.1
   * InfoScale Storage 7.1


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: 7.1.0.300
* 3893137 (3893138) Secure Cluster configuration failed due to missing ksh package.
* 3895362 (3895368) The installer blocks the installation when you install an InfoScale product on the 
Linux platform with an unqualified Linux kernel.
* 3896140 (3896188) The installer blocks the configuration when you configure LLT over UDP with a 
private link using a different subnet on a cluster.
* 3908993 (3909010) One of the rpool devices display UNAVIL state after
upgrading from 6.1 to 7.1 on Solaris Sparc systems.


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

Patch ID: 7.1.0.300

* 3893137 (Tracking ID: 3893138)

SYMPTOM:
The secure cluster configuration fails after you install InfoScale Availability.

DESCRIPTION:
The secure cluster configuration depends on the presence of the ksh package. 
When you install InfoScale Availability, the installer does not check for the 
ksh package as the other packages do not have a dependency on ksh. So the 
installation is successful but the secure configuration fails.

RESOLUTION:
Add ksh package to the VRTSvcs dependency check list during the installation.

* 3895362 (Tracking ID: 3895368)

SYMPTOM:
The installer blocks the installation when you install an InfoScale product on the 
Linux platform with an unqualified Linux kernel.

DESCRIPTION:
If you attempt to install an InfoScale product on the Linux platform with an 
unqualified Linux kernel, the installer blocks the installation. But it is not 
necessary for the intaller to block the installation, it should just give a warning.

RESOLUTION:
The installer gives a warning message when you attempt to install an InfoScale 
product on the Linux platform with an unqualified Linux kernel.

* 3896140 (Tracking ID: 3896188)

SYMPTOM:
The installer blocks the configuration when you configure LLT over UDP with a 
private link using a different subnet on a cluster.

DESCRIPTION:
If you try to configure a VCS cluster with LLT over UDP mode with a private 
link using a different subnet, the installer blocks the configuration. But this 
kind of configuration is actually possible. The installer should not to forbid 
it.

RESOLUTION:
The installer allows the configuration of a cluster when you configure LLT over 
UDP with a private link using a different 
subnet on a cluster.

* 3908993 (Tracking ID: 3909010)

SYMPTOM:
One of the rpool devices display UNAVIL state after upgrading from 6.1
to 7.1 on Solaris Sparc systems. The device's vxdmp pseudo device was
disappeared when enable dmp
native support in 7.1 product and reboot.

DESCRIPTION:
One of the rpool devices display UNAVIL state after upgrading from 
6.1 to 7.1 on Solaris Sparc systems. The device's vxdmp pseudo device
disappears when the system is rebooted after enabling dmp native support in 
7.1. This is because the installer fails to process the configuration file 
/kernel/drv/vxdmp.conf appropriately during the upgrade.

RESOLUTION:
The installer code is modified to use the correct vxdmp.conf file
after the upgrade.



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


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


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


OTHERS
------
NONE