README VERSION : 1.1 README CREATION DATE : 2014-07-03 PATCH-ID : 6.1.1.0 PATCH NAME : VRTSsfcpi61 BASE PACKAGE NAME : VRTSsfcpi61 BASE PACKAGE VERSION : 6.1.0.0 SUPERSEDED PATCHES : NONE REQUIRED PATCHES : NONE INCOMPATIBLE PATCHES : NONE SUPPORTED PADV : sol11_sparc (P-PLATFORM , A-ARCHITECTURE , D-DISTRIBUTION , V-VERSION) PATCH CATEGORY : PATCH CRITICALITY : RECOMMENDED HAS KERNEL COMPONENT : NO ID : NONE REBOOT REQUIRED : NO REQUIRE APPLICATION DOWNTIME : NO PATCH INSTALLATION INSTRUCTIONS: -------------------------------- Please refer the release notes for installation instructions. PATCH UNINSTALLATION INSTRUCTIONS: ---------------------------------- Please refer the release notes for un-installation instructions. SPECIAL INSTRUCTIONS: --------------------- NONE SUMMARY OF FIXED ISSUES: ----------------------------------------- PATCH ID:6.1.1.0 3442070 (3519322) CPI exit with error when selecting rolling upgrade task from install menu. 3499194 (3471289) CPI tries to stop vxglm even though Cluster Volume Manager (CVM) is online. 3491173 (3491172) The installer exits without printing any message after 'Verifying systems' when it reruns './installer -license' on an already licensed system. 3419772 (3448674) After upgrading from 5.0MP3RP5 to 6.0.5 using the base_path option, NFSRestart and NFS upper or lower resource cannot come online automatically. 3390290 (3542842) During upgrade, the Sun Microsystems Label (SMI) label changes to Extensible Firmware Interface (EFI) and makes the disk group un-importable. SUMMARY OF KNOWN ISSUES: ----------------------------------------- 3542302 (3518852) Relink Oracle Database Binary menu is missing from Upgrade and Rollback tasks. 3538577 (3532663) Refresh keys fail on a non-security cluster with fencing configured. 3541468 (3536921) On Solaris 11, drivers may not be loaded after reboot. 3556857 (3555013) Web-based installer doesn't support or block rolling upgrade from releases before 6.1 to 6.1.1. KNOWN ISSUES : -------------- * INCIDENT NO::3542302 TRACKING ID ::3518852 SYMPTOM::No menu "Relink Oracle Database Binary" for Upgrade and Rollback in option - makerespnosefile. Installer would skip relink OracleDB if user use the responsefile generated by -makeresponsefile. Workaround: Add the relink info to responsefile manually. Like: $CFG{crs_home}="/u01/app/grid/product/11.2.0/gridhome"; $CFG{db_home}="/u01/app/oracle/product/11.2.0/dbhome_1"; $CFG{oracle_group}="oinstall"; $CFG{oracle_user}="oracle"; $CFG{relink_oracle_database}=1; * INCIDENT NO::3538577 TRACKING ID ::3532663 SYMPTOM::In a non-security cluster, after the fencing is configured, if you use the -fencing option and select "refresh keys/registrations on the existing coordination pints", the installer reports "could not find the domain name!" error. Workaround:Use the -security option to enable security cluster, and then use the -security option again to change the cluster to non-security mode. * INCIDENT NO::3541468 TRACKING ID ::3536921 SYMPTOM::While CPI stopping the processes, it will use rem_drv command to ensure the driver will not be loaded back by OS. However, after reboot, OS will not be able to load those drivers back, which make our product unavailable after reboot. Workaround: On Solaris 11, if drivers such as vxdmp, vxio are not loaded after reboot, user need to manually execute comamnd: /opt/VRTS/install -start to start your product. * INCIDENT NO::3556857 TRACKING ID ::3555013 SYMPTOM::The web-based installer doesn't support or block rolling upgrade from releases before 6.1 to 6.1.1. Issues may occur if you use the web-based installer for rolling upgrade from releases before 6.1 to 6.1.1.. Workaround: Use the script-based installer with the -base_path option for the rolling upgrade from releases before 6.1 to 6.1.1. FIXED INCIDENTS: ---------------- PATCH ID:6.1.1.0 * INCIDENT NO:3442070 TRACKING ID:3519322 SYMPTOM: CPI exit with error when selecting rolling upgrade task with hotfix_path from install menu. DESCRIPTION: If customer run installer to do rolling upgrade with hotfix_path CPI will report the following error message: CPI ERROR V-9-40-3818 The rolling_upgrade option can be only used with upgrade and serial option RESOLUTION: The code is modified to make the rolling upgrade going further if hotfix_path is being used. * INCIDENT NO:3499194 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. * INCIDENT NO:3491173 TRACKING ID:3491172 SYMPTOM: Storage Foundation Basic (SF Basic): The installer exits without printing any message after 'Verifying systems' when you license the product on an already licensed system. DESCRIPTION: For SF Basic, if you run './installer -license' on a system that has already been licensed, the installer exits without printing any messages. The installer is expected to print the license status of the target system(s). RESOLUTION: The code is modified to display the following message: SF Basic is licensed on the systems. * INCIDENT NO:3419772 TRACKING ID:3448674 SYMPTOM: After upgrading from 5.0MP3RP5 to 6.0.5 using the base_path option, NFSRestart and NFS upper or lower resource cannot come online automatically. DESCRIPTION: Some NFSRestart and NFS lock files are not migrated from /var/VRTSvcs/lock to /var/VRTSvcs/log/volatile during upgrade. Thus, NFSRestart and NFS upper or lower resource cannot come online automatically. RESOLUTION: The upgrade script is modified to migrate the NFSRestart and NFS lock files from /var/VRTSvcs/lock to /var/VRTSvcs/lock/volatile during the upgrade using the base_path option. * INCIDENT NO:3390290 TRACKING ID:3542842 SYMPTOM: The Symantec Product Installer attempts to start the vxconfigd daemon before upgrade, which leads to data corruption. DESCRIPTION: In Volume Manager (VxVM), while upgrading from 5.1SP1 5.1SP1RP1, 5.1SP1RP2, or 5.1SP1RP3, the LUNs over 1 Terabyte(TB) in size encounter data corruption. TechNote: http://www.symantec.com/business/support/index? page=content&id=TECH188018 During upgrade from 5.1SP1, 5.1SP1RP1, 5.1SP1RP2, or 5.1SP1RP3 to 6.0 release, the Symantec Product Installer attempts to start vxconfigd daemon before upgrade which leads to data corruption. RESOLUTION: The code is modified to prevent the vxconfigd daemon from getting started while upgrading from 5.1SP1, 5.1SP1RP1, 5.1SP1RP2 or 5.1SP1RP3. INCIDENTS FROM OLD PATCHES: INCIDENTS FROM OLD PATCHES: --------------------------- NONE