README VERSION : 1.1 README CREATION DATE : 2013-01-18 PATCH-ID : 148496-01 PATCH NAME : VRTSvcsag 6.0.300.000 BASE PACKAGE NAME : VRTSvcsag BASE PACKAGE VERSION : 6.0.100.000 SUPERSEDED PATCHES : NONE REQUIRED PATCHES : NONE INCOMPATIBLE PATCHES : NONE SUPPORTED PADV : sol10_sparc (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:148496-01 2933305 (2737653) Incorrect descriptions on RVGPrimary online script 2938979 (2980002) High availability support for logical domain when control domain is down with multiple I/O domains in Oracle VM (OVM) for SPARC environment. 2967539 (2967536) MonitorProgram of Application does not work correctly with C shell of User env. 2986205 (2979745) MultiNICA unable to detect Network connectivity lost 2999849 (2964772) If you take an NFSRestart resource offline, the NFSRestart Agent may unexpectedly stop NFS processes in a local container (Zones on Solaris or WPARs on AIX). SUMMARY OF KNOWN ISSUES: ----------------------------------------- KNOWN ISSUES : -------------- FIXED INCIDENTS: ---------------- PATCH ID:148496-01 * INCIDENT NO:2933305 TRACKING ID:2737653 SYMPTOM: If you override the OnlineTimeout attribute value for RVGPrimary resource, the agent does not take it in account. DESCRIPTION: If the RLink of the RVG is connected but is not up-to-date, the RVGPrimary agent waits for it to become up-to-date till the OnlineTimeout attribute value expires. When this attribute value is overridden for the RVGPrimary resource in picture, it is not taken into account. Instead, the agent takes into account the OnlineTimeout defined for RVGPrimary resource type. RESOLUTION: Symantec has modified the RVGPrimary Agent to take into account the OnlineTimeout value when overridden by the RVGPrimary resource. * INCIDENT NO:2938979 TRACKING ID:2980002 SYMPTOM: High availability support for logical domain when control domain is down with multiple I/O domains in Oracle VM (OVM) for SPARC environment. DESCRIPTION: When a logical domain is configured with I/O services from multiple I/O domains, the logical domain can survive the loss of any of the I/O domain. When a I/O domain fails the logical domain transparently uses the I/O services from other I/O domain. In OVM environment, the control domain is default I/O domain for any logical domain. The logical domain administration happens from control domain. When the control domain is shutdown or rebooted the logical domain cannot be managed from any other I/O domain. Veritas Cluster Server (VCS) which is running in the control domain manages the logical domain. By default, when the VCS node (primary/control domain) is down, VCS fails over the logical domain under its management, though the logical domain can continue to run. RESOLUTION: Symantec has enhanced its solution to support the high availability for the logical domain when the control domain is shutdown or rebooted. With the help of logical domain failure policy setting with its master(s) and VCS service group attributes, Symantec provided a mechanism to not to failover the logical domain resource when control domain is rebooted or shutdown. User can set logical domain master failure-policy for control domain to ignore and VCS service group attribute SysDownPolicy to AutoDisableNoFailover, so that VCS does not failover the logical domain. * INCIDENT NO:2967539 TRACKING ID:2967536 SYMPTOM: When Application resource is configured with MonitorProgram and non-default user (where default user is root), and if the user shell is C-shell, then the resource goes to UNKNOWN state. DESCRIPTION: Application agent invokes /usr/bin/test command to check whether the file configured under MonitorProgram is executable. When an Application resource is configured with a non-default user, Application agent invokes test command with "su - ". This does not work for C-shell as it requires the su command to be invoked with "-c" option (su - -c ). Thus, Application monitor reports UNKNOWN state for the resource. RESOLUTION: The Application agent is modified to ensure that the monitor reports correct state for the resource whenever the User configured is in C-shell environment. * INCIDENT NO:2986205 TRACKING ID:2979745 SYMPTOM: MultiNICA Agent is unable to detect loss of network connectivity DESCRIPTION: While monitoring the Network Interface Cards (NIC) configured with the MultiNICA Resource, if the NIC is not able to ping the NetworkHosts, the Agent tries to ping the broadcast address to check whether the NIC is healthy. The agent checks the packet count for the NIC to check if the network is reachable. The packet count may increase even due to the NIC replying to itself, without the replies from the systems in the network. Thus, Veritas Cluster Server(VCS) may incorrectly report the NIC as healthy. RESOLUTION: MultiNICA agent is modified to check whether the NIC replies to its own broadcast ping or whether the other systems in the network are replying to the NIC. If the replies to the broadcast ping are not from the systems in the network and the NetworkHosts are not reachable, the NIC is detected to have lost Network Connectivity. * INCIDENT NO:2999849 TRACKING ID:2964772 SYMPTOM: If you take an NFSRestart resource offline, the NFSRestart Agent may unexpectedly stop NFS processes in a local container (Zones on Solaris or WPARs on AIX). DESCRIPTION: As part of the offline operation, the NFSRestart agent is expected to stop NFS processes only in the global container. However, the agent does not perform a strict match of container IDs before terminating a process. As a result, the agent may also terminate certain NFS processes in a local container. RESOLUTION: Symantec has modified the NFSRestart Agent to ensure a strict container ID match, before terminating an NFS process. INCIDENTS FROM OLD PATCHES: --------------------------- NONE