* * * READ ME * * *
                          * * * CPI 7.1 * * *
                         * * * Patch 900 * * *
                         Patch Date: 2018-03-02


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 900


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.900
* 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.
* 3904941 (3904943) The installer fails to recognize SLES 12 SP2.
* 3908993 (3909010) One of the rpool devices display UNAVIL state after 
upgrading from 6.1 to 7.1 on Solaris Sparc systems.
* 3915934 (3916443) The Veritas product installer fails to close the SSH socket connection, 
allowing the connection to run in the background 
indefinitely in some scenarios.
* 3917326 (3917771) The Veritas product installer blocks the steward process if InfoScale
Availability is not installed.
* 3938152 (3938139) After applying any of these patches  - 7.1.0.100, 7.1.0.200 or 7.1.0.300, the
VxFS File System fails to auto-mount on reboot.
* 3940064 (3940014) Rolling upgrade Phase2 fails if a patch is installed as a part of Rolling
upgrade Phase1.
* 3941517 (3941611) When you provide the "-patch_path" argument to the installer
during a rolling upgrade, the CPI performs a patch upgrade instead of first
performing phase 2 of the rolling upgrade.


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

Patch ID: 7.1.0.900

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

* 3904941 (Tracking ID: 3904943)

SYMPTOM:
The installer fails with the error message 'No padv object defined for padv 
SLESx8664 for system on Sles12 SP2.

DESCRIPTION:
The installer fails with the error message 'No padv object defined for padv 
SLESx8664 for system' on Sles12 SP2.

RESOLUTION:
The installer code is modified to resolve the issue.

* 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 devices 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 devices 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.

* 3915934 (Tracking ID: 3916443)

SYMPTOM:
The Veritas product installer fails to close the SSH socket connection, 
allowing the connection to run in the background 
indefinitely in some scenarios.

DESCRIPTION:
The Veritas product installer fails to close the SSH socket connection in the 
following scenarios:

> When customers use the comsetup or comcleanup options to create or remove the 
ssh password-less connection
> When customers choose to delete the ssh password-less connection at the end 
of the installer processes

RESOLUTION:
The installer code has now been updated to close the SSH socket 
connection

* 3917326 (Tracking ID: 3917771)

SYMPTOM:
The Veritas product installer blocks the steward process if InfoScale
Availability is not installed.

DESCRIPTION:
Running the Veritas product installer with the -securityonenode option blocks 
the steward process if InfoScale Availability is not installed and displays the 
following warning: 
# ./installer -securityonenode
CPI WARNING V-9-20-1198 -securityonenode is not a valid installer argument.

RESOLUTION:
Enable the -securityonenode option for the Veritas installer.

* 3938152 (Tracking ID: 3938139)

SYMPTOM:
After applying the patches 7.1.0.100, 7.1.0.200 or 7.1.0.300, the VxFS fails to
auto-mount on reboot, because the service 'vxvm-fstab-automount.service' gets
removed and is not automatically restored.

DESCRIPTION:
While applying the VxVM patch 7.1.0.100, the service
'vxvm-fstab-automount.service' gets removed from systemd during package upgrade.
Due to this, the VxFS File System fails to get auto-mounted upon system reboot.
The succeeding patches 7.1.0.200 and 7.1.0.300 also do not restore the
'vxvm-fstab-automount.service'.
This hotfix will enable the CPI to restore this service during the post upgrade tasks.

RESOLUTION:
The change has been made in the CPI to specifically restore the service
'vxvm-fstab-automount.service' during post upgrade tasks.

* 3940064 (Tracking ID: 3940014)

SYMPTOM:
When a patch is installed as a part of rolling upgrade Phase1, the rolling
upgrade Phase2 fails with the error:
A more recent version of InfoScale Enterprise, 7.1.0.xxx, is already
installed.

DESCRIPTION:
When a patch is installed as a part of rolling upgrade Phase1, the kernel
package version might get upgraded to a version that is higher than the version
considered for upgrade. 

This results in failure of the rolling upgrade Phase2 with the error:  A
more recent version of InfoScale Enterprise, 7.1.0.xxx, is already
installed.

RESOLUTION:
The CPI rolling upgrade prerequisites are modified to continue even if a patch
for InfoScale product is installed as part of Rolling upgrade Phase1.

* 3941517 (Tracking ID: 3941611)

SYMPTOM:
When you provide the "-patch_path" argument to the installer during a
rolling upgrade, the CPI performs a patch upgrade instead of first performing
phase 2 of the rolling upgrade.

DESCRIPTION:
This issue occurs because the CPI fails to detect the installed
product state correctly during the rolling upgrade phase 2 checks. It then
directly proceeds to perform the patch upgrade tasks without first performing
phase 2 of the rolling upgrade. For example: If CPI finds that the InfoScale 7.1
VRTSvxvm package is installed on system, it assumes that InfoScale 7.1 is
already installed. It then proceeds to perform the patch upgrade even though
phase 2 of the rolling upgrade from (say) SFHA 6.2.1 is not yet complete.

RESOLUTION:
The installer is updated to correctly detect the installed product
state during the rolling upgrade phase 2 checks, and accordingly proceed to
perform either phase 2 or the patch upgrades.



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


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


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


OTHERS
------
NONE