* * * READ ME * * *
* * * CPI 6.2.1 * * *
* * * Patch 400 * * *
Patch Date: 2015-09-14
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.2.1 Patch 400
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
-----------------------------------
* Symantec Application HA 6.2
* Symantec Application HA 6.2.1
* Symantec Cluster Server 6.2
* Symantec Cluster Server 6.2.1
* Symantec Dynamic Multi-Pathing 6.2.1
* Symantec Dynamic Multi-Pathing 6.2
* Symantec Storage Foundation 6.2.1
* Symantec Storage Foundation 6.2
* Symantec Storage Foundation Cluster File System HA 6.2.1
* Symantec Storage Foundation Cluster File System HA 6.2
* Symantec Storage Foundation for Oracle RAC 6.2
* Symantec Storage Foundation for Oracle RAC 6.2.1
* Symantec Storage Foundation HA 6.2
* Symantec Storage Foundation HA 6.2.1
SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: 6.2.1.400
* 3789486 (3789485) On Solaris 11, in some scenarios, after upgrading SF Oracle RAC, VCS, SFHA, or
SFCFSHA to version 6.2.1, the following error may occur:
"llt failed to start on <server_name>".
* 3794821 (3801924) On Solaris 11, on MPXIO-enabled boot-devices such as T3, T4, or T5, when
you
upgrade SF, SFHA, SFCFSHA or SF Oracle RAC from 6.2 to 6.2.1, the following
error message will be displayed:
"Failed to turn on dmp_native_support tunable on xxx. Refer to Dynamic
Multi-
Pathing".
* 3833269 (3832218) The Installer enables automatically downloading SFHA patches for new
platform update.
* 3851011 (3846363) When upgrading SFHA environments to SFHA 6.0.5 or higher, the CVMTypes.cf
is NOT updated with the VCS ClearClone attribute. Customers are unable to
specify the ClearClone attribute in main.cf to update the on-disk UDID
content for DMP detected hardware replicated devices.
* 3851013 (3814804) Fail to configure the CP server because the network interface name for VIP
is not recognized, such as bond0.636.
* 3851205 (3847737) The installation and upgrade may be blocked due to kernel release version
mismatch.
DETAILS OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
This patch fixes the following Symantec incidents:
Patch ID: 6.2.1.400
* 3789486 (Tracking ID: 3789485)
SYMPTOM:
On Solaris 11, in some scenarios, after upgrading SF Oracle RAC, VCS, SFHA, or
SFCFSHA to version 6.2.1, the following error may occur: "llt failed to start on
<server_name>".
DESCRIPTION:
Due to the LLT driver unload issue, the LLT module version persists with 6.2.0,
even after the product is upgraded to version 6.2.1.
RESOLUTION:
The code is modified to unload the module prior to package upgrade for LLT, GAB
and vxfen on Solaris 11.
* 3794821 (Tracking ID: 3801924)
SYMPTOM:
On Solaris 11, on MPXIO-enabled boot-devices such as T3, T4, T5, when you
upgrade SF, SFHA, SFCFSHA or SF Oracle RAC from 6.2 to 6.2.1, the following
error message will be displayed:
"Failed to turn on dmp_native_support tunable on xxx. Refer to Dynamic
Multi-
Pathing".
DESCRIPTION:
When DMP and MPxIP coexist, the command 'vxdmpadm settune
dmp_native_support=off' will fail.
RESOLUTION:
The code is modified to not turn off the tunable dmp_native_support before
the
patch upgrade, and not turn on dmp_native_support after the upgrade. During
the
upgrade, the product doesnt stop VxVM or VxFS processes. After the
upgrade,
you need to reboot to reload the VxVM or the VxFS module.
* 3833269 (Tracking ID: 3832218)
SYMPTOM:
In previous releases, if users try to install SFHA on unconfirmed platform,
the installer displays an error message and advices users to find
corresponding patches through SORT website:
DESCRIPTION:
In this patch release, the installer uses dynamic data from web service to
check the patch status for new platform update. If there is a patch for new
platform update on SORT website, the installer automatically downloads and
applies it.
RESOLUTION:
If there is a patch for new platform update on SORT website, the installer
automatically downloads and applies it.
* 3851011 (Tracking ID: 3846363)
SYMPTOM:
When upgrading SFHA environments to SFHA 6.0.5 or higher, the CVMTypes.cf
is NOT updated with the VCS ClearClone attribute. Customers are unable to
specify the ClearClone attribute in main.cf to update the on-disk UDID
content for DMP detected hardware replicated devices.
DESCRIPTION:
The ClearClone attribute was introduced from 6.0.5 onwards. The installer
doesn't update CVMTypes.cf with the VCS ClearClone attribute.
RESOLUTION:
The code is modified to add the VCS ClearClone attribute to CVMTypes.cf.
* 3851013 (Tracking ID: 3814804)
SYMPTOM:
Fail to configure the CP server because the network interface name for VIP
is not recognized, such as bond0.636.
DESCRIPTION:
The Symantec product installer has some limitations for the network
interface name.
RESOLUTION:
The code is modified to remove the limitations for the network interface
name.
* 3851205 (Tracking ID: 3847737)
SYMPTOM:
When install or upgrade products in SFHA environment, the system displays
an error message after the installer performs pre-check operation. The
message reports the Linux kernel version is not supported despite of the
fact that the version is actually supported. The error message is as
follows:
CPI ERROR V-9-40-1395 Kernel Release 3.0.101-0.47.55-default is detected on
vmr720-31-v01, which is not supported for this product.
DESCRIPTION:
The issue occurs because the Linux kernel version you use is not 100% match
the kernel version stored in database.
RESOLUTION:
The code is modified to match only the core part of the kernel version
string in database.
INSTALLING THE PATCH
--------------------
1. Copy the hotfix CPI_6.2.1_P4.pl to /tmp
2. Run installation or configuration scripts with the hotfix
Example:
./installmr -require /tmp/CPI_6.2.1_P4.pl
REMOVING THE PATCH
------------------
NONE
SPECIAL INSTRUCTIONS
--------------------
NONE
OTHERS
------
NONE