* * * READ ME * * * * * * CPI 6.0.1 * * * * * * Hot Fix 900 * * * Patch Date: 2014-04-01 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 Hot Fix 900 OPERATING SYSTEMS SUPPORTED BY THE PATCH ---------------------------------------- Linux BASE PRODUCT VERSIONS FOR THE PATCH ----------------------------------- * Veritas Cluster Server 6.0.1 * Veritas Storage Foundation for Oracle RAC 6.0.1 * Veritas Storage Foundation Cluster File System 6.0.1 * Veritas Storage Foundation 6.0.1 * Veritas Storage Foundation High Availability 6.0.1 * Veritas Storage Foundation Basic 6.0.1 * Veritas Dynamic Multi-Pathing 6.0.1 * Symantec VirtualStore 6.0.1 * Veritas Storage Foundation for Sybase ASE CE 6.0.1 SUMMARY OF INCIDENTS FIXED BY THE PATCH --------------------------------------- Patch ID: 6.0.1.900 * 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 * 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.900 * 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 . 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. * 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_P9.pl to /tmp 2. Run installation scripts with the hot-fix Example: ./installer -require /tmp/CPI_6.0.1_P9.pl REMOVING THE PATCH ------------------ 1. Copy the hot-fix CPI_6.0.1_P9.pl to /tmp 2. Run uninstall scripts with the hot-fix Example: ./installer -uninstall -require /tmp/CPI_6.0.1_P9.pl SPECIAL INSTRUCTIONS -------------------- NONE OTHERS ------ NONE