README VERSION : 1.1 README CREATION DATE : 2014-04-03 PATCH ID : VRTSvcs-6.0.500.000 PATCH NAME : VRTSvcs 6.0.500.000 BASE PACKAGE NAME : VRTSvcs BASE PACKAGE VERSION : 6.0.100.000 SUPERSEDED PATCHES : 6.0.300.000 REQUIRED PATCHES : NONE INCOMPATIBLE PATCHES : NONE SUPPORTED PADV : aix61_ppc,aix71_ppc (P-PLATFORM , A-ARCHITECTURE , D-DISTRIBUTION , V-VERSION) PATCH CATEGORY : CORE , CORRUPTION PATCH CRITICALITY : CRITICAL HAS KERNEL COMPONENT : NO 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:VRTSvcs-6.0.500.000 3125546 (3104071) The service group online propagate operation fails without giving proper error message. 3207666 (3207663) Incorrect user privileges are set in case of incorrect use of the '-group' option in command "hauser -addprive". 3211835 (3211834) CurrentLimits attribute value is not updated correctly when a service group faults. 3343020 (3090710) The High Availability Daemon (HAD) starts and stops before the VxFEN driver configuration completes. 3343028 (3079893) The value of LastSuccess attribute of the service group equals the GlobalCounter value of the cluster if the resource faults while you online the service group. Hence the service group fails to come online. 3343030 (3042450) A parent service group which is frozen and configured with online local hard dependency is brought offline when its child service group faults. 3343031 (3112608) Resource fails to become online after switch operations fails for a service group. 3346435 (3101761) The vcsauthserver process dumps core due to issues in VxAT library. 3364069 (3318764) Unexpected deletion of temporary files causes the VCS agents to report an incorrect state. 3373134 (3406176) The WPAR aware agents configured in the WPAR fail to log messages in the secure cluster. PATCH ID:6.0.300.000 2947204 (2736627) The remote cluster remains in INIT state, and the Internet Control Message Protocol (ICMP) heartbeat status is UNKNOWN. 2947236 (2941155) Veritas Cluster Server (VCS) does not mark a group as OFFLINE on a failed cluster when a cluster failure is declared in a Global Cluster Option (GCO) environment. SUMMARY OF KNOWN ISSUES: ----------------------------------------- NONE KNOWN ISSUES : -------------- NONE FIXED INCIDENTS: PATCH ID:VRTSvcs-6.0.500.000 * INCIDENT NO:3125546 TRACKING ID:3104071 SYMPTOM: The service group online propagate operation fails without giving proper error message. DESCRIPTION: Veritas Cluster Server (VCS) has two Service Groups (SG) configured with a local dependency. The child SG is online on one of the nodes in the cluster. When you start an online command for the parent SG on some other node in the cluster, the SG does not comes online but VCS does not log any error message. RESOLUTION: The High Availability Daemon (HAD) binary has been fixed. When the online of an SG fails, you can see the proper error message. * INCIDENT NO:3207666 TRACKING ID:3207663 SYMPTOM: When you run the command "hauser -addpriv" to set user privileges for a group, if you use the '-group' option incorrectly and leave out the dash (-) in this option, the incorrect privileges for the group are set. DESCRIPTION: You can set group privileges with the command "hauser -addpriv -group ". If you don't provide the dash (-) in the "-group" option, Veritas Cluster Server (VCS) does not detect this error. It instead sets Cluster Administrator privileges for that user. RESOLUTION: An enhancement is made to the hauser (1M) binary, so that proper error checks are added for the command line options. * INCIDENT NO:3211835 TRACKING ID:3211834 SYMPTOM: CurrentLimits attribute value is not updated correctly when a service group faults. DESCRIPTION: When you perform an online operation on a service group, the pre-requisites mentioned in the PreRequisites attribute of the service group is acquired before initiating online and the IState for its resource is marked as 'waiting_to_go_online (reverse/propagate)'. If you initiate an offline operation on the same service group while it is in the process of becoming online, the resource fails to go online and the service group is marked as FAULTED. The pre-requisites are also not released. Therefore, the value of CurentLimits attribute remains elevated. RESOLUTION: The code to calculate CurrentLimits value is modified to correctly calculate the value in case of a service group fault. * INCIDENT NO:3343020 TRACKING ID:3090710 SYMPTOM: The High Availability Daemon (HAD) starts and stops before the VxFEN driver configuration completes. DESCRIPTION: When you configure Veritas Cluster Server (VCS) with cluster level attribute UseFence set to SCSI3, HAD starts after the VCS Fencing module (VxFEN) at system startup. HAD checks whether VxFEN is configured when it starts. HAD tries to detect the VxFEN configuration and stops, if it fails to detect VxFEN within 180 seconds. The VxFEN configuration gets delayed beyond 180 seconds in some scenarios and hence HAD stops even before the VxFEN configuration is complete. RESOLUTION: The code has been modified such that HAD binary waits indefinitely for the Veritas Fencing (VxFEN) driver configuration to complete. * INCIDENT NO:3343028 TRACKING ID:3079893 SYMPTOM: A resource in the service group faults when a resource in the service group is brought online and the OnlineRetryLimit and OnlineRetryInterval for the service group is set to non -zero values. Veritas Cluster Server (VCS) fails to bring the service group online. DESCRIPTION: When you try to bring a service group online, if the resource faults, the LastSuccess attribute for the service group gets set to the current value of the GlobalCounter of the cluster. Hence, the attempt to bring the service group online fails as VCS treats the fault within the OnlineRetryInterval. RESOLUTION: The code has been modified to fix the High Availability Daemon (HAD) binary. Additional checks have been added so that LastSuccess attribute does not get set during resource fault. * INCIDENT NO:3343030 TRACKING ID:3042450 SYMPTOM: A parent service group which is frozen and configured with online local hard dependency is brought offline when its child service group faults. DESCRIPTION: When a service group is frozen in Veritas Cluster Server (VCS), all online and offline procedures on it are stopped. However, when you configure two service groups in an online local hard dependency and if the child service group faults, the parent service group is brought offline. RESOLUTION: The code is modified to check whether the parent service group is frozen before bringing it offline when its child service group faults. If the parent service group is detected as frozen, it remains unaffected. * INCIDENT NO:3343031 TRACKING ID:3112608 SYMPTOM: Resource fails to become online after switch operations fails for a service group. DESCRIPTION: When user tries to bring a service group online, VCS checks if the group has a resource capable of being online. If the parent resource has the Enabled attribute set to 0 (zero), VCS doesn't bring the service group online on the switch. However, the FromQ or the ToQ attribute for the system remains populated. Later when you try to bring any resource online manually, VCS detects that the FromQ or the ToQ attribute is not empty. As a result, VCS assumes that the service group is in transition and does not bring the resource online. RESOLUTION: The behavior in VCS is modified to clear the FromQ, the ToQ, or the MigrateQ attribute if the switch fails for a service group because of a resource not capable of being online. * INCIDENT NO:3346435 TRACKING ID:3101761 SYMPTOM: The vcsauthserver process dumps core due to issues in VxAT library. DESCRIPTION: Veritas Cluster Server (VCS) uses the VxAT library for configuring VCS in secure mode. The vcsauthserver logs messages in /var/VRTSvcs/log/vcsauthserver.log. Due to an issue in VxAT library, whenever the vcsauthserver.log file reaches 5MB size, the log file used to get rotated which results in a core dump for vcsauthserver. RESOLUTION: The code has been modified for the VxAT library such that the log file gets rotated when it reaches the limit and does not cause core dump. * INCIDENT NO:3364069 TRACKING ID:3318764 SYMPTOM: The checkboot utility core dump or time difference between a system and Network Time Protocol (NTP) time leads to unexpected deletion of the temporary files. The deletion causes the VCS agents to report an incorrect state. DESCRIPTION: The utmp(5M) file (file names are based on the operating system) contains a record of the reboots performed on a system. The hastart(1M) command uses checkboot utility, which uses the functions provided by the operating system. The operating systems in response use the utmp file to identify the systems that are rebooted so that the temporary files for various agents are deleted before the agent startup. The reboot check is performed when you run the commands like hastart-version rather than before the High Availability Daemon (HAD) is started. If the utmp file is deleted, the checkboot utility fails due to a NULL pointer dereference resulting in the deletion of the temporary files. The difference between the system time and the time provided by NTP server may also lead to an unexpected deletion of these temporary files. Thus, some of the agents which depend on these temporary files fail. RESOLUTION: The hastart(1M) command code is modified such that the checkboot test is done only when you start the HAD. Additionally, the checkboot utility code is modified to handle the NULL pointer return from the OS functions and to correctly check whether HAD is being restarted after a reboot despite of the time difference between NTP and a system. * INCIDENT NO:3373134 TRACKING ID:3406176 SYMPTOM: The WPAR aware agents configured in the WPAR fail to log messages in the secure cluster. DESCRIPTION: The utility hawparsetup.pl does not add group admin to the service group in the secure cluster. This results in failure to log messages in the engine log, because there is no group admin user to communicate with the engine running in the global partition. Therefore, WPAR aware agents fail to log messages in the secure cluster. RESOLUTION: The code of the hawparsetup.pl utility is modified to add group admin to the service group in a secure cluster. PATCH ID:6.0.300.000 * INCIDENT NO:2947204 TRACKING ID:2736627 SYMPTOM: If IPv6 is disabled on the cluster, the remote cluster remains in INIT state, and the ICMP heartbeat status remains UNKNOWN. DESCRIPTION: When the ICMP agent opens a connection with Wide Area Connector (WAC), it first tries with IPv6. If IPv6 connection fails, the ICMP agent checks if the error is specific to protocol. If yes, it then tries with IPv4. But for the error EADDRNOTAVAIL (i.e. address not found), the ICMP agent does not try with IPv4. RESOLUTION: The code has been modified, so that the ICMP agent retries the connection with IPv4 if the error is EADDRNOTAVAIL. * INCIDENT NO:2947236 TRACKING ID:2941155 SYMPTOM: VCS does not mark a group as OFFLINE on a failed cluster when a cluster failure is declared in a GCO environment. DESCRIPTION: When a remote cluster faults in a GCO environment and the ClusterFailOverPolicy attribute for a global group is not set to Auto, VCS prompts to declare the failure type of the remote cluster. You can declare the failure type with the "haclus -declare" command. You can also use the "-failover" flag with the "haclus -declare" command that suggests and performs the appropriate action required to fail over all the online groups from the failed cluster to an appropriate cluster. However, if you want to declare the failure without failing over the groups, VCS does not mark the online group as OFFLINE on the failed cluster. RESOLUTION: Enhancements have been made so that when you declare the cluster failure without failing over the groups, the groups that are online on the failed cluster are marked as OFFLINE. However, when you use the "-failover" option with the "haclus-declare" command, you will be prompted to reconfirm whether you want to go ahead as your action would mark the groups as OFFLINE on the failed cluster. If you decline to go ahead, the failure will not be declared, and no action will be taken when the cluster failure is of the disconnect type as a disconnected cluster might be down temporarily. INCIDENTS FROM OLD PATCHES: --------------------------- NONE