This page lists publically-released patches for Veritas Enterprise Products.
For Product GA build, see Veritas Entitlement Management System(VEMS) by clicking the Veritas Support 'Licensing' option.
For information on private patches, contact Veritas Technical Support.
Veritas is making it easier to find all software installers and updates for Veritas products with a completely redesigned experience. NetBackup HotFixes and NetBackup Appliance patches are now also available at the new Veritas Download Center.
Patches for your product can have a variety of names. These names are based on product, component, or package names. For more information on patch naming conventions and the relationship between products, components, and packages, see the SORT online help.
cpi-6.0.1.1000
Obsolete
The latest patch(es) : cpi-6.0.1.1100 
Sign in if you want to rate this patch.

 Basic information
Release type: Patch
Release date: 2014-06-26
OS update support: None
Technote: None
Documentation: None
Popularity: 1196 viewed    206 downloaded
Download size: 20.03 KB
Checksum: 2032373594

 Applies to one or more of the following products:
VirtualStore 6.0.1 On RHEL5 x86-64
VirtualStore 6.0.1 On RHEL6 x86-64
VirtualStore 6.0.1 On SLES10 x86-64
VirtualStore 6.0.1 On SLES11 x86-64
VirtualStore 6.0.1 On Solaris 10 SPARC
VirtualStore 6.0.1 On Solaris 10 X64
VirtualStore 6.0.1 On Solaris 11 SPARC
VirtualStore 6.0.1 On Solaris 11 X64
Cluster Server 6.0.1 On AIX 6.1
Cluster Server 6.0.1 On AIX 7.1
Cluster Server 6.0.1 On HP-UX 11i v3 (11.31)
Cluster Server 6.0.1 On RHEL5 x86-64
Cluster Server 6.0.1 On RHEL6 x86-64
Cluster Server 6.0.1 On SLES10 x86-64
Cluster Server 6.0.1 On SLES11 x86-64
Cluster Server 6.0.1 On Solaris 10 SPARC
Cluster Server 6.0.1 On Solaris 10 X64
Cluster Server 6.0.1 On Solaris 11 SPARC
Cluster Server 6.0.1 On Solaris 11 X64
Dynamic Multi-Pathing 6.0.1 On AIX 6.1
Dynamic Multi-Pathing 6.0.1 On AIX 7.1
Dynamic Multi-Pathing 6.0.1 On HP-UX 11i v3 (11.31)
Dynamic Multi-Pathing 6.0.1 On RHEL5 x86-64
Dynamic Multi-Pathing 6.0.1 On RHEL6 x86-64
Dynamic Multi-Pathing 6.0.1 On SLES10 x86-64
Dynamic Multi-Pathing 6.0.1 On SLES11 x86-64
Dynamic Multi-Pathing 6.0.1 On Solaris 10 SPARC
Dynamic Multi-Pathing 6.0.1 On Solaris 10 X64
Dynamic Multi-Pathing 6.0.1 On Solaris 11 SPARC
Dynamic Multi-Pathing 6.0.1 On Solaris 11 X64
Storage Foundation 6.0.1 On AIX 6.1
Storage Foundation 6.0.1 On AIX 7.1
Storage Foundation 6.0.1 On HP-UX 11i v3 (11.31)
Storage Foundation 6.0.1 On RHEL5 x86-64
Storage Foundation 6.0.1 On RHEL6 x86-64
Storage Foundation 6.0.1 On SLES10 x86-64
Storage Foundation 6.0.1 On SLES11 x86-64
Storage Foundation 6.0.1 On Solaris 10 SPARC
Storage Foundation 6.0.1 On Solaris 10 X64
Storage Foundation 6.0.1 On Solaris 11 SPARC
Storage Foundation 6.0.1 On Solaris 11 X64
Storage Foundation Basic 6.0.1 On AIX 6.1
Storage Foundation Basic 6.0.1 On AIX 7.1
Storage Foundation Basic 6.0.1 On RHEL5 x86-64
Storage Foundation Basic 6.0.1 On RHEL6 x86-64
Storage Foundation Basic 6.0.1 On SLES10 x86-64
Storage Foundation Basic 6.0.1 On SLES11 x86-64
Storage Foundation Basic 6.0.1 On Solaris 10 SPARC
Storage Foundation Basic 6.0.1 On Solaris 10 X64
Storage Foundation Basic 6.0.1 On Solaris 11 SPARC
Storage Foundation Basic 6.0.1 On Solaris 11 X64
Storage Foundation Cluster File System 6.0.1 On AIX 6.1
Storage Foundation Cluster File System 6.0.1 On AIX 7.1
Storage Foundation Cluster File System 6.0.1 On HP-UX 11i v3 (11.31)
Storage Foundation Cluster File System 6.0.1 On RHEL5 x86-64
Storage Foundation Cluster File System 6.0.1 On RHEL6 x86-64
Storage Foundation Cluster File System 6.0.1 On SLES10 x86-64
Storage Foundation Cluster File System 6.0.1 On SLES11 x86-64
Storage Foundation Cluster File System 6.0.1 On Solaris 10 SPARC
Storage Foundation Cluster File System 6.0.1 On Solaris 10 X64
Storage Foundation Cluster File System 6.0.1 On Solaris 11 SPARC
Storage Foundation Cluster File System 6.0.1 On Solaris 11 X64
Storage Foundation for Oracle RAC 6.0.1 On AIX 6.1
Storage Foundation for Oracle RAC 6.0.1 On AIX 7.1
Storage Foundation for Oracle RAC 6.0.1 On HP-UX 11i v3 (11.31)
Storage Foundation for Oracle RAC 6.0.1 On RHEL5 x86-64
Storage Foundation for Oracle RAC 6.0.1 On RHEL6 x86-64
Storage Foundation for Oracle RAC 6.0.1 On SLES10 x86-64
Storage Foundation for Oracle RAC 6.0.1 On SLES11 x86-64
Storage Foundation for Oracle RAC 6.0.1 On Solaris 10 SPARC
Storage Foundation for Oracle RAC 6.0.1 On Solaris 10 X64
Storage Foundation for Oracle RAC 6.0.1 On Solaris 11 SPARC
Storage Foundation for Oracle RAC 6.0.1 On Solaris 11 X64
Storage Foundation for Sybase ASE CE 6.0.1 On SLES10 x86-64
Storage Foundation for Sybase ASE CE 6.0.1 On Solaris 10 SPARC
Storage Foundation HA 6.0.1 On AIX 6.1
Storage Foundation HA 6.0.1 On AIX 7.1
Storage Foundation HA 6.0.1 On HP-UX 11i v3 (11.31)
Storage Foundation HA 6.0.1 On RHEL5 x86-64
Storage Foundation HA 6.0.1 On RHEL6 x86-64
Storage Foundation HA 6.0.1 On SLES10 x86-64
Storage Foundation HA 6.0.1 On SLES11 x86-64
Storage Foundation HA 6.0.1 On Solaris 10 SPARC
Storage Foundation HA 6.0.1 On Solaris 10 X64
Storage Foundation HA 6.0.1 On Solaris 11 SPARC
Storage Foundation HA 6.0.1 On Solaris 11 X64

 Obsolete patches, incompatibilities, superseded patches, or other requirements:

This patch is obsolete. It is superseded by: Release date
cpi-6.0.1.1100 2015-01-06

This patch supersedes the following patches: Release date
cpi-6.0.1.900 (obsolete) 2014-04-07
cpi-6.0.1.800 (obsolete) 2013-11-17
cpi-6.0.1.700 (obsolete) 2013-09-27
cpi-6.0.1.600 (obsolete) 2013-09-05
cpi-6.0.1.500 (obsolete) 2013-08-29
cpi-6.0.1.400 (obsolete) 2013-07-13
cpi-6.0.1.300 (obsolete) 2013-06-17
cpi-6.0.1.200 (obsolete) 2013-03-21
cpi-6.0.1.100 (obsolete) 2012-11-05

 Fixes the following incidents:
2984386, 3125432, 3227558, 3228679, 3294945, 3298901, 3307508, 3360781, 3390290, 3448379, 3465678

 Patch ID:
None.

 Readme file  [Save As...]
                          * * * READ ME * * *
                         * * * CPI 6.0.1 * * *
                      * * * Patch 6.0.1.1000 * * *
                         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.0.1 Patch 6.0.1.1000


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
AIX 6.1
AIX 7.1
HP-UX 11i v3 (11.31)
RHEL5 x86-64
RHEL6 x86-64
SLES10 x86-64
SLES11 x86-64
Solaris 10 SPARC
Solaris 11 SPARC



BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * Symantec VirtualStore 6.0.1
   * Veritas Cluster Server 6.0.1
   * Veritas Dynamic Multi-Pathing 6.0.1
   * Veritas Storage Foundation 6.0.1
   * Veritas Storage Foundation Cluster File System HA 6.0.1
   * Veritas Storage Foundation for Oracle RAC 6.0.1
   * Veritas Storage Foundation for Sybase ASE CE 6.0.1
   * Veritas Storage Foundation HA 6.0.1


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: 6.0.1.1000
* 2984386 (3248893) If the Solaris 10 kernel patch is Update 10, the installer fails to 
detect the OS update level and issues a warning message.
* 3125432 (3125494) CPI fails with an error message while installing the product on a machine with BIOS vendor QEMU.
* 3227558 (3243089) During a live upgrade the installation process takes more
time than expected.
* 3228679 (3230218) The Common Product Installer (CPI) based installation fails
on Solaris version 11 because the nslookup command is missing.
* 3294945 (3295841) CPI patches 6.0.1_P4.pl and 6.0.3_P6.pl fails when ssh banner is enabled.
* 3298901 (3304955) The installer blocks upgrading the product to 6.0.1 if Veritas Cluster Server (VCS) is not configured.
* 3307508 (3309409) The installer displays a warning message about the
unsupported operating system version during CPI installation in Solaris 10
Update 11.
* 3360781 (3355748) Upgrade fails with multiple local zones in a service group
* 3390290 (3542842) SMI Label changed to EFI during upgrade leaving diskgroup un-importable
* 3448379 (3471289) CPI tries to stop vxglm even though Cluster Volume Manager (CVM) is online.
* 3465678 (3472265) The installvcs script cannot set the heartbeat NIC name to be
"L_101".


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

Patch ID: 6.0.1.1000

* 2984386 (Tracking ID: 3248893)

SYMPTOM:
If the Solaris 10 kernel patch is Update 10, the installer fails to 
detect the OS update level and issues the below warning message:
WARNING V-9-40-3995 Solaris 10 Update 6 is installed on <system>. It is strongly 
recommended to install Solaris 10 Update 8 or later.

DESCRIPTION:
When 6.0.1 was released, Solaris 10 u10 haven't been published. The installer
needs to 
support the latest kernel version during the pre-check procedure.

RESOLUTION:
It has been fixed and the installer supports Solaris 10 u10 now.

* 3125432 (Tracking ID: 3125494)

SYMPTOM:
CPI fails with an error message while installing the product on a machine with BIOS vendor QEMU.

DESCRIPTION:
If you have BIOS vendor QEMU, CPI reports the following error message: 
CPI ERROR V-9-0-0 1 thread 1 threw error: Can't locate object method "QEMU" via package "Padv::RHEL5x8664" 
The error message is displayed because of improper handling of QEMU.

RESOLUTION:
The CPI script is modified to handle vendor information such as QEMU.

* 3227558 (Tracking ID: 3243089)

SYMPTOM:
During a live upgrade on SunOS, the rsh or the ssh command use
approximately 3 minutes per node to verify if a node is alive. The verification
process causes a delay in the installation process.

DESCRIPTION:
During an installation process, when the rsh or the ssh command is
invoked, the command verifies the state of each node to understand if it is
alive. In the process of verification, the commands consume more time than
expected, which causes a delay in the installation process. The installer also
reports error messages during the rsh communication precheck. Some of these
error messages are invalid that leads to repeated verification of the ssh or the
rsh connection.

RESOLUTION:
Remove the invalid error messages while CPI verifies the rsh or the
ssh commands. CPI executes the rsh or the ssh communication only once regardless
of the failure that is observed in the rsh or the ssh verification process.

* 3228679 (Tracking ID: 3230218)

SYMPTOM:
With Solaris version 11, the Common Product Installer (CPI) based
installation process fails during a precheck because the nslookup command is
missing. 
After the failure, the installer reports the following error message:
CPI ERROR V-9-30-1446 
The following required OS commands are missing on system:
/usr/sbin/nslookup: No such file or directory.

DESCRIPTION:
The Internet Systems Consortium (ISC) has deprecated the use of
nslookup command instead has certified to use either the host or dig. The CPI
packages contain the nslookup command, which the standard build does not support. 
During an installation, the Storage Foundation (SF) CPI installer installs the
bind packages (pkg:/network/dns/bind) and later removes these bind packages to
comply with the ISC's new security guidelines. However, during a precheck when
the nslookup command is not found, the installer stops the installation with an
error.

RESOLUTION:
To prevent the installation failure, remove the nslookup command
from the preinstallation command checklist.

* 3294945 (Tracking ID: 3295841)

SYMPTOM:
When the user installs 6.0.1_P4.pl or 6.0.3_P6.pl with ssh or rsh
options enabled, the following error occurs:

  Checking system communication CPI ERROR V-9-0-0

1 thread 1 threw error: Can't locate object method "arch_sys" via 
package "Padv::" (perhaps you forgot to load "Padv::"?) 
at /opt/VRTSperl/lib/site_perl/UXRT60/EDR/EDR/systems.pm line 102.

DESCRIPTION:
During an installation process, when the rsh or the ssh command is
invoked, the command verifies the state of each node to check if it is
available. If the ssh or the rsh option is enabled, the existing diagnostic
method for a connection fails.

RESOLUTION:
The code is modified such that the $sys->{banner} is not enabled while testing
the ssh/rsh connection.

* 3298901 (Tracking ID: 3304955)

SYMPTOM:
The installer blocks upgrading the product to 6.0.1 if Veritas Cluster Server
(VCS) is not configured.

DESCRIPTION:
Some users have Storage Foundation and High Availability (SFHA) product
installed, but only with Dynamic Multi-Pathing (DMP) configured and running. In
this case, the installer blocks upgrading the whole product because VCS is not
configured.

RESOLUTION:
Use the hot fix provided to upgrade the whole product.

* 3307508 (Tracking ID: 3309409)

SYMPTOM:
During the installation of SFHA 6.0.1 in Solaris 10 Update 11, the CPI installer
displays the following warning messages:
"The following warnings were discovered on the systems:
CPI WARNING V-9-40-3995 Solaris 10 Update 6 is installed. It is 
strongly recommended to install Solaris 10 Update 8 or later."

DESCRIPTION:
148888-03 is the Solaris 10 Update 11 kernel patch ID, which was released in
January 2013. Since 6.0.1 was released before January 2013, it is not able to
recognize the correct operating system version for Solaris 10.

RESOLUTION:
The code is modified to support Solaris 10 Update 11.

* 3360781 (Tracking ID: 3355748)

SYMPTOM:
Upgrading VCS from 5.0MP3RP5 to 6.0.1 with SG containing multiple zones throws 
CPI errors

CPI ERROR V-9-40-3737 In the file '/etc/VRTSvcs/conf/config/main.cf' on 
sprsv480b7-09, the ContainerName and ContainerType value of all resources in 
group
'SAP-HAWKER-ITE1-SG' are not consistent :
    SAP-HAWKER-ITE1-SG   app-zone2-res  ContainerName  tstzone2
    SAP-HAWKER-ITE1-SG   app-zone2-res  ContainerType  Zone
    SAP-HAWKER-ITE1-SG   app-zone1-res  ContainerName  tstzone1
    SAP-HAWKER-ITE1-SG   app-zone1-res  ContainerType  Zone
CPI ERROR V-9-40-3738 In the file '/etc/VRTSvcs/conf/config/main.cf' on 
sprsv480b7-09, the group 'SAP-HAWKER-ITE1-SG' contains more than 1 Zone :
    SAP-HAWKER-ITE1-SG   Zone Name tstzone1
    SAP-HAWKER-ITE1-SG   Zone Name tstzone2

DESCRIPTION:
Since 6.0.1 VCS provide specific customer a hotfix to support multiple zones(via 
a new attribute ResContainerInfo in resource level) in a single service group as 
it's supported prior to 5.1. However CPI wasn't required to support this design 
change. So when the setup in such case upgrade from versions prior to 5.1 to 
6.x, CPI throw error and bail out.

RESOLUTION:
Add the ResContainerInfo support for upgrading from versions prior to 5.1 to 6.x 
to support multiple zones in a single service group.

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

* 3448379 (Tracking ID: 3471289)

SYMPTOM:
CPI tries to stop vxglm even though Cluster Volume Manager (CVM) is online.

DESCRIPTION:
During a rolling upgrade, CPI stops CVM, and then it stops vxglm. But if a CVM
service group is frozen, CVM will fail to stop, but CPI still tries to stop
vxglm, and this causes a system panic.

RESOLUTION:
The code is modified to block the rolling upgrade going further if vxglm is
being used.

* 3465678 (Tracking ID: 3472265)

SYMPTOM:
The installvcs script cannot set the heartbeat NIC name to be "L_101".

DESCRIPTION:
The Symantec product installer assumes the network interface name should not
include "_".

RESOLUTION:
The code is modified to remove the limitation that network interface name should
not include "_".



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


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


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


OTHERS
------
NONE





Read and accept Terms of Service