README VERSION : 1.1 README CREATION DATE : 2014-04-03 PATCH-ID : VRTSvxfen-6.0.500.000 PATCH NAME : VRTSvxfen 6.0.500.000 BASE PACKAGE NAME : VRTSvxfen BASE PACKAGE VERSION : 6.0.100.000 SUPERSEDED PATCHES : 6.0.300.000 REQUIRED PATCHES : NONE INCOMPATIBLE PATCHES : NONE SUPPORTED PADV : sol11_sparc (P-PLATFORM , A-ARCHITECTURE , D-DISTRIBUTION , V-VERSION) PATCH CATEGORY : OTHER PATCH CRITICALITY : CRITICAL HAS KERNEL COMPONENT : YES ID : NONE REBOOT REQUIRED : NO REQUIRE APPLICATION DOWNTIME : YES PATCH INSTALLATION INSTRUCTIONS: -------------------------------- Please refer to Install Guide for install instructions and Release Notes for other information. PATCH UNINSTALLATION INSTRUCTIONS: ---------------------------------- Please refer to Install Guide for uninstall instructions and Release Notes for other information. SPECIAL INSTRUCTIONS: --------------------- NONE SUMMARY OF FIXED ISSUES: ----------------------------------------- PATCH ID:VRTSvxfen-6.0.500.000 3343012 (3302091) VCS and SFRAC fail to start after a reboot on Solaris version 11. 3346420 (3246141) The vxfenswap(1M) utility does not work in the clusters where rsh/ssh logins to other nodes are disabled. PATCH ID:6.0.300.000 2977049 (2861253) In vxfen driver log statement, jeopardy membership is printed as garbage. SUMMARY OF KNOWN ISSUES: ----------------------------------------- NONE KNOWN ISSUES : -------------- NONE FIXED INCIDENTS: ---------------- PATCH ID:VRTSvxfen-6.0.500.000 * INCIDENT NO:3343012 TRACKING ID:3302091 SYMPTOM: On Solaris 11, VCS and SFRAC fail to start after a reboot. DESCRIPTION: The fencing module is unable to start when the add_drv(1M) command from the fencing init script fails. The command fails because another module runs the add_drv(1M) command simultaneously. The VCS/SFRAC kernel modules often call the add_drv(1M) command in their respective init scripts. However, a race condition is caused when different modules call the add_drv(1M) command at the same time. RESOLUTION: Two new Service Management Facility (SMF) services are created to manage package installation operations. The add_drv(1M)/rem_drv(1M) command are removed from the start/stop script and added to the package installation SMF services. These changes are made in the VRTSllt, VRTSgab, VRTSvxfen, and VRTSdbac packages. * INCIDENT NO:3346420 TRACKING ID:3246141 SYMPTOM: The vxfenswap(1M) utility does not work in the clusters where remote shell (rsh) and secure shell (ssh) logins to other nodes are disabled. DESCRIPTION: In some cluster environments, ssh/rsh logins within the cluster nodes are disabled by the Administrator. The vxfenswap(1M) utility fails to work in such environments since it requires either ssh or rsh to be functional to execute the remote commands. RESOLUTION: The hacli(1M) command support is enabled in the vxfenswap(1M) utility. Now, with a new command line option -p, you can specify the protocol, which the vxfenswap(1M) utility can use to communicate with other nodes of the cluster. The supported values are ssh, rsh, and hacli. By default, the hacli(1M) command is disabled in the cluster. Hence, before using the vxfenswap(1M) with the hacli(1M) command, change the HacliUserLevel value from NONE to COMMANDROOT. To change the HacliUserLevel value: 1. Enable the write access in the VCS configuration using: # haconf -makerw 2. Change the HacliUserLevel value using: # haclus -modify HacliUserLevel COMMANDROOT 3. Verify the new hacli value using: # haclus -value HacliUserLevel COMMANDROOT After the vxfenswap utility swaps the values: 1. Change the HacliUserLevel value to NONE # haclus -modify HacliUserLevel NONE 2. Disable the write access in the VCS configuration using: # haconf -makero PATCH ID:6.0.300.000 * INCIDENT NO:2977049 TRACKING ID:2861253 SYMPTOM: Jeopardy membership status is printed as garbage in vxfen driver debug log message. DESCRIPTION: The variable which is supposed to contain the jeopardy membership for displaying in vxfen driver debug log message, was not populated with correct value. Hence some garbage value was getting printed. RESOLUTION: Symantec has fixed this issue by properly populating the variable with correct jeopardy membership value. INCIDENTS FROM OLD PATCHES: --------------------------- NONE