README VERSION : 1.1 README CREATION DATE : 2013-01-18 PATCH ID : 6.0.300.000 PATCH NAME : VRTSvcs 6.0.300.000 BASE PACKAGE NAME : VRTSvcs BASE PACKAGE VERSION : 6.0.100.000 SUPERSEDED PATCHES : NONE REQUIRED PATCHES : NONE INCOMPATIBLE PATCHES : NONE SUPPORTED PADV : aix61_ppc,aix71_ppc (P-PLATFORM , A-ARCHITECTURE , D-DISTRIBUTION , V-VERSION) PATCH CATEGORY : OTHER PATCH CRITICALITY : CRITICAL HAS KERNEL COMPONENT : NO ID : NONE REBOOT REQUIRED : NO REQUIRE APPLICATION DOWNTIME : Yes PATCH INSTALLATION INSTRUCTIONS: -------------------------------- Please refer to Release Notes for install instructions PATCH UNINSTALLATION INSTRUCTIONS: ---------------------------------- Please refer to Release Notes for uninstall instructions SPECIAL INSTRUCTIONS: ---------------------- NONE SUMMARY OF FIXED ISSUES: ----------------------------------------- PATCH ID:6.0.300.000 2947204 (2736627) REMOTE CLUSTER STATE remains in INIT state and Icmp heartbeat status is UNKNOWN 2947236 (2941155) Group is not marked offline on faulted cluster in a GCO environment after a cluster failure is declared. SUMMARY OF KNOWN ISSUES: ----------------------------------------- KNOWN ISSUES : -------------- FIXED INCIDENTS: PATCH ID:6.0.300.000 * INCIDENT NO:2947204 TRACKING ID:2736627 SYMPTOM: REMOTE CLUSTER STATE remains in INIT state and Icmp heartbeat status remains UNKNOWN if IPv6 is disabled on the cluster. DESCRIPTION: When Icmp agent opens a connection with wide area connector(WAC), it first tries IPv6. If IPv6 connection fails, it checks if the error is protocol specific and tries with IPv4. In this particular case, Icmp agent was receiving EADDRNOTAVAIL(i.e. address not found) and did not try with IPv4. RESOLUTION: Modified the code to retry with IPv4 if the error is EADDRNOTAVAIL. * INCIDENT NO:2947236 TRACKING ID:2941155 SYMPTOM: Veritas Cluster Server (VCS) does not mark a group as offline on a failed cluster when the 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 type of failure 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, in case of a cluster failure, if a 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: Symantec has improvised HAD and haclus utility such that when you declare the cluster failure, the groups that are online on the failed cluster are marked offline. When a you use the "-failover" option with "haclus -declare" command, you are prompted to reconfirm whether you want to go ahead as your action would mark the groups offline on the failed cluster. If you decline to go ahead, failure is not declared and no action is taken. No action is taken when the cluster failure is of the type disconnect as a disconnected cluster might be down temporarily INCIDENTS FROM OLD PATCHES: --------------------------- NONE