* * * READ ME * * * * * * CPI 6.2.1 * * * * * * Patch 1500 * * * Patch Date: 2018-06-08 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 1500 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.1 * Symantec Application HA 6.2 * Symantec Cluster Server 6.2.1 * Symantec Cluster Server 6.2 * Symantec Dynamic Multi-Pathing 6.2.1 * Symantec Dynamic Multi-Pathing 6.2 * Symantec File System 6.2.1 * Symantec File System 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.1 * Symantec Storage Foundation for Oracle RAC 6.2 * Symantec Storage Foundation HA 6.2.1 * Symantec Storage Foundation HA 6.2 * Symantec Volume Manager 6.2.1 * Symantec Volume Manager 6.2 SUMMARY OF INCIDENTS FIXED BY THE PATCH --------------------------------------- Patch ID: 6.2.1.1500 * 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 ". * 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. * 3854284 (3854453) The installation and upgrade may be blocked because the installer fails to detect VMware Tools installed. * 3857148 (3861130) On Solaris 11, in some scenarios, after upgrading SF Oracle RAC, VCS, SFHA, or SFCFSHA to version 6.2.1, LLT may fail to start. * 3859349 (3860738) The installer doesn't check for correct libraries in RHEL6.7 * 3871193 (3871601) CPI pre-check costs long time when dozens of service groups are configured in cluster. * 3872631 (3872630) When the network service is stopped during shutdown, Low Latency Transport (LLT) links go down and a fencing race is triggered. This causes node panic. * 3878779 (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. * 3895362 (3895368) The installer blocks the installation when you install an InfoScale product on the Linux platform with an unqualified Linux kernel. * 3908716 (3904943) The installer fails to recognize SLES 12 SP2. * 3930606 (3930575) Stop operation of vxcloud fails while installing vm-patch * 3932199 (3932127) when the users install vm product, CPI will try to start and stop vxcloud even do not have vxcloud. This will cause start/stop failed. * 3943784 (3943786) Installing SFHA patch for AIX OS update using patch installer program fails to generate the patch uninstaller script. * 3948968 (3948967) CPI failed to copy the required files on a remote system because it has atypical SSH software installed. DETAILS OF INCIDENTS FIXED BY THE PATCH --------------------------------------- This patch fixes the following incidents: Patch ID: 6.2.1.1500 * 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 ". 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. * 3854284 (Tracking ID: 3854453) SYMPTOM: For AppHA product, the installation and upgrade may be blocked because the installer fails to detect VMware Tools installed. The following error message is displayed: CPI ERROR V-9-40-6284 The installer did not detect vmware-tools installed on itgsydtst612 DESCRIPTION: Even though VMware Tools is already installed and running, the installer fails to detect them because the location of the VMware Tools control script is changed. RESOLUTION: The code is modified to detect the new location for VMware Tools control script. * 3857148 (Tracking ID: 3861130) SYMPTOM: On Solaris 11, in some scenarios, after upgrading SF Oracle RAC, VCS, SFHA, or SFCFSHA to version 6.2.1, LLT may fail to start. 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 remove the module prior to package upgrade for LLT, GAB and vxfen on Solaris 11. * 3859349 (Tracking ID: 3860738) SYMPTOM: When installing Infoscale 7.0 on RHEL 6.7 system without required x86 libraries installed, the installer fails to find the corresponding version of RPM packages. Instead, it checks for older versions. DESCRIPTION: The installer doesnt define the required OS RPMs for RHEL6.7, since RHEL6.7 is released after Infoscale 7.0 GA. To support Infoscale 7.0 in RHEL 6.7, the new patch infoscale-rhel6.7_x86_64-Patch-7.0.0.100 is published. The installer also needs to update required OS RPMs for it. RESOLUTION: The installer has been modified to add required OS RPMs for RHEL6.7. * 3871193 (Tracking ID: 3871601) SYMPTOM: CPI pre-check costs long time when dozens of service groups are configured in cluster. DESCRIPTION: Each service group status is checked many times on every system in the cluster, which would cost much time in pre-check process. RESOLUTION: The code is modified to check service group status once on system. * 3872631 (Tracking ID: 3872630) SYMPTOM: In RHEL7.X or SLES12 12.X, when the network service is stopped during shutdown, LLT links go down and a fencing race is triggered. This causes node panic. DESCRIPTION: If LLT, GAB or I/O fencing modules are manually started directly using the init scripts (i.e. /etc/init.d/vxfen start), the systemd are unaware of these services. As a result, these services have their shutdown scripts executed during a reboot or shutdown. RESOLUTION: The code is modified to start or stop llt/gab/vxfen/amf/vcs with 'systemctl start/stop' instead of '/etc/init.d/ start/stop'. * 3878779 (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. * 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. * 3908716 (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. * 3930606 (Tracking ID: 3930575) SYMPTOM: Stop operation of vxcloud fails while installing vm-patch DESCRIPTION: While installing the new vm-ptach that supports vxcloud, CPI does not start or stop vxcloud. This results in failure of the stop operation for vxcloud. RESOLUTION: This hotfix updates the CPI to support start and stop of vxcloud. * 3932199 (Tracking ID: 3932127) SYMPTOM: when the users install vm product, CPI will try to start and stop vxcloud even do not have vxcloud. This will cause start/stop failed. DESCRIPTION: when the users install vm product, CPI will try to start and stop vxcloud even do not have vxcloud. This will cause start/stop failed. RESOLUTION: CPI add judgement of vxcloud in installer when start and stop. If do no have vxcloud will not start&stop it. * 3943784 (Tracking ID: 3943786) SYMPTOM: Installing SFHA patch for AIX OS update using patch installer program fails to generate the patch uninstaller script. DESCRIPTION: When you install the SFHA patch for AIX OS update using the Patch Installer program, the installer fails to generate the patch uninstaller script inside the "/opt/VRTS/install/" directory. This issue occurs for the sfha-aix71-Patch-6.2.1.200 and other prior AIX OS update patches. For example, when you install the patch sfha-aix71-Patch-6.2.1.200 using the installSFHA621P2 script, the uninstaller script uninstallSFHA621P2 is not generated inside the directory "/opt/VRTS/install/". RESOLUTION: As a part of this hotfix, the installer code is modified to generate the patch uninstaller script for future releases. * 3948968 (Tracking ID: 3948967) SYMPTOM: A system may have a customized environment that uses an atypical SSH software, which does not provide the default SSH options. In such a scenario, CPI fails to copy the required files to remote systems. DESCRIPTION: In a customer environment, the "Reflection for Secure IT 8.0.1.74" product was installed, which provided the default SSH on the system. The specific version of this software did not have the default SSH option 'UserKnownHostsFile'. CPI launched the SCP command to copy the required files on the remote system, but encountered the error: Invalid option: 'UserKnownHostsFile=/dev/null' RESOLUTION: This hotfix updates the CPI to check whether the "Reflection for Secure IT" software is installed on a system. If this software is installed, CPI does not provide the options for SCP that are incompatible with this SSH configuration so that the files are copied to the remote system successfully. INSTALLING THE PATCH -------------------- 1. Copy the hot-fix CPI_6.2.1_P15.pl to /tmp 2. Run installation scripts with the hot-fix Example: ./installer -require /tmp/CPI_6.2.1_P15.pl REMOVING THE PATCH ------------------ NONE SPECIAL INSTRUCTIONS -------------------- NONE OTHERS ------ NONE