* * * READ ME * * * * * * Veritas Cluster Server 6.0.3 * * * * * * Public Hot Fix 2 * * * Patch Date: 2013-09-13 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 ---------- Veritas Cluster Server 6.0.3 Public Hot Fix 2 OPERATING SYSTEMS SUPPORTED BY THE PATCH ---------------------------------------- Solaris 11 SPARC PACKAGES AFFECTED BY THE PATCH ------------------------------ VRTSgab 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 High Availability 6.0.1 * Symantec VirtualStore 6.0.1 SUMMARY OF INCIDENTS FIXED BY THE PATCH --------------------------------------- Patch ID: 6.0.300.200 * 3302204 (3302091) [Pri-1][Globalfoundries Singapore Pte. Ltd][Could not up vcs after reboot first node in phase upgrade on solaris 11 sparc] DETAILS OF INCIDENTS FIXED BY THE PATCH --------------------------------------- This patch fixes the following Symantec incidents: Patch ID: 6.0.300.200 * 3302204 (Tracking ID: 3302091) SYMPTOM: VCS/SFRAC could not come up after reboot on Solaris 11. DESCRIPTION: The fencing module could not come up as it's add_drv command from fencing init script failed. The command failed due to another module's add_drv was running at very same time. This can happen to any VCS/SFRAC kernel module as these modules call add_drv in respective init scripts. This will cause race of different add_drv commands for different module. RESOLUTION: To resolve this, Two new SMF services are created for simulating postinstall and preremove operations. The add_drv command was moved out of start script and moved in to postinstall of the module. The rem_drv was moved from stop script to preremove operation. These changes made for the VRTSllt, VRTSgab, VRTSvxfen and VRTSdbac packages. #================================================================= ========== # SYMANTEC SUPPORT TO ENGINEERING ESCALATION TEMPLATE #================================================================= ========== Contract type (Business Critical, Essential, Basic): BC Legacy Support? [Yes/No]: No Operating System, Version and Architecture: Solaris 11 Severity and Priority: 1 Products and version: SFHA 6.0.3 Operating System, version and architecture: Solaris 11 Reason for advancement (e.g. management request, sales request, BCAM request, reached end of technical knowledge, etc.): end of tech knowledge Brief INSTALLING THE PATCH -------------------- Before installing VRTSgab-6.0.300.200 on a Solaris 11 host, you can optionally create a boot environment (BE) and install VRTSgab-6.0.300.200 on the new BE. Doing this makes it easier to revert to the current version of VRTSgab if required in future. To create a new boot environment, perform steps 1-4 below on each node. 1. Identify the active boot environment (BE) by looking at the NR tag: # beadm list 2. Create a new boot environment: # beadm create where is any valid name not listed in step 1. Example: # beadm create sfha_gab 3. Activate the newly-created boot environment: # beadm activate 4. Reboot the node so that the new boot environment is active: # reboot * To apply the patch manually, perform the steps listed below on each node in the cluster. 1. Save the configuration: # haconf -dump 2. Stop VCS, vxfen, gab: # hastop -local -force # svcadm disable -s vxfen # svcadm disable -s gab (Stop all the dependent services of GAB before stopping GAB) 3. Apply the gab patch by issuing the following commands: a. Set the publisher # pkg set-publisher -p Symantec e.g: # pkg set-publisher -p /hotfix_dir/patches/VRTSgab.p5p Symantec b. Install the package # pkg install --accept --no-backup-be VRTSgab 4. Verify that the new patch is installed. The output of the following command should display the version for VRTSgab package as 6.0.300.200: # pkg info VRTSgab 5. Start gab and all its dependent services: # svcadm enable -s gab # svcadm enable -s vxfen # hastart etc. REMOVING THE PATCH ------------------ On Solaris 11, patch removal is not supported. If you created a new boot environment before installing the new VRTSgab package, you can revert to the boot environment which was in effect prior to that installation. * To revert to previous boot environment, perform steps 1-3 below on each cluster node. 1. Activate the boot environment which was in effect prior to installing this patch (noted in step 1 of 'To create a new boot environment' above): # beadm activate 2. Reboot the node so that the new boot environment takes effect: # reboot 3. (optional) If you have no further use for the boot environment on which you installed the patch, you may destroy it: # beadm destroy Example: # beadm destroy sfha_gab If you did not create a new boot environment, you must uninstall the version of VRTSgab included in this patch and then re-install the prior version of the package (6.0.300.0) from original source media. SPECIAL INSTRUCTIONS -------------------- You need to install VRTSllt-6.0.300.100 and VRTSvxfen-6.0.300.100 patches with this patch. If you have SFRAC, VRTSdbac-6.0.100.100 patch need to be installed in addition to the patches mentioned above. OTHERS ------ NONE