README VERSION : 1.1 README CREATION DATE : 2012-09-20 PATCH ID : 5.1.113.0 PATCH NAME : VRTSvcsag 5.1 SP1RP3 BASE PACKAGE NAME : Veritas Cluster Server Bundled Agents by Symantec BASE PACKAGE VERSION : VRTSvcsag 5.1SP1 SUPERSEDED PATCHES : NONE REQUIRED PATCHES : NONE INCOMPATIBLE PATCHES : NONE SUPPORTED PADV : aix53,aix61,aix71 (P-PLATFORM , A-ARCHITECTURE , D-DISTRIBUTION , V-VERSION) PATCH CATEGORY : OTHER PATCH CRITICALITY : OPTIONAL HAS KERNEL COMPONENT : NO ID : NONE REBOOT REQUIRED : NO PATCH INSTALLATION INSTRUCTIONS: -------------------------------- Please refer the release notes for installation instructions PATCH UNINSTALLATION INSTRUCTIONS: ---------------------------------- Please refer the release notes for un-installation instructions. SPECIAL INSTRUCTIONS: ---------------------- NONE SUMMARY OF FIXED ISSUES: ----------------------------------------- 1787018 (1919382) Mount agent fails to detect the mounted file system with trailing "/". 2619254 (2593173) DiskGroup agent do not detect serial split-brain situation. 2728805 (2728802) Apache agent should work correctly even if Mountpoint for httpd directory is not present on the failover node. 2781551 (2779780) haping command failure for AIX NIC interface 2788082 (2788059) System did not panic when "PanicSystemOnDGLoss" is set. 2818051 (2731133) When NFSRestart resource is brought offline, it forcefully stops automountd process. SUMMARY OF KNOWN ISSUES: ----------------------------------------- KNOWN ISSUES : -------------- FIXED INCIDENTS: PATCH ID:5.1.113.0 * INCIDENT NO:1787018 TRACKING ID:1919382 SYMPTOM: The Mount agent fails to detect the mounted file system if either the BlockDevice or MountPoint attribute contains a trailing forward slash ("/"). DESCRIPTION: If the value configured in either the BlockDevice or MountPoint attribute contains a trailing forward slash, the Mount agent online entry point does not remove it. The monitor entry point fails to record the entry in the mount table because the monitor entry point removes the trailing forward slash before searching the mount table. RESOLUTION: Symantec has modified the Mount agent code to remove the trailing forward slash while mounting the file system. * INCIDENT NO:2619254 TRACKING ID:2593173 SYMPTOM: Online entry point of DiskGroup agent do not detect the serial split-brain situation and fail to log warning about it. DESCRIPTION: Diskgroup agent check for incorrect return code of the vxdg import command expected during serial split-brain situation and thus do not recognize the serial split-brain situation. RESOLUTION: Symantec has now modified the DiskGroup agent to look for correct return code of vxdg import command during serial split-brain situation. * INCIDENT NO:2728805 TRACKING ID:2728802 SYMPTOM: If the directory or filename specified as part of 'httpdDir' attribute does not exist on the cluster node, the Apache agent cannot monitor the HTTP server correctly. And Apache agent logs error with following message id V-16-10061-20495. DESCRIPTION: As part of validations Apache agent checks existence of file or directory specified as part of 'httpdDir' attribute. However on a node where apache resource is offline, it is possible that even the mountpoint for httpd directory may not be present, in such a case Apache agent should report the resource state as offline instead of logging an error message. RESOLUTION: Symantec has update the Apache agent to report the resource state as offline when the directory or file specified as part of 'httpdDir' attribute is not present on the system. In such an event, during process level monitoring agent looks for the Apache processes assuming the value specified as part of 'httpdDir' attribute in following ways: 1 A directory name containing 'httpd' binary 2 Complete path to the binary name itself * INCIDENT NO:2781551 TRACKING ID:2779780 SYMPTOM: When the monitor of a MultiNICB resource and online of an IPMultiNICB resource are scheduled at the same time, one of the entry point fails. This leads to fault of one of the resources and may also trigger an incorrect failover. DESCRIPTION: The monitor of MultiNICB agent and online of IPMultiNICB agent ping using the interfaces configured in the MultiNICB resource. The synchronization between MultiNICB agent and IPMultiNICB agent was missing. Due to this, one of the agent failed to ping and the corresponding resource faulted. RESOLUTION: The pings in the monitor of MultiNICB agent and online of IPMultiNICB agent are now synchronized. * INCIDENT NO:2788082 TRACKING ID:2788059 SYMPTOM: System did not panic on loss of storage connectivity, even after the PanicSystemOnDGLoss attribute of DiskGroup resource is set to 1. DESCRIPTION: If a resource other than DiskGroup in a service group detects loss of storage connectivity, then that resource faults and the DiskGroup resource is brought offline. The offline entry point of DiskGroup agent does not check the state of the underlying disk group before deporting it. RESOLUTION: Symantec has modified the DiskGroup agent code to check the state of the underlying disk group before deporting. This ensures that if the offline entry point is called for DiskGroup resource due to loss of storage connectivity and PanicSystemOnDGLoss attribute of DiskGroup resource is set to 1, then the system will panic. * INCIDENT NO:2818051 TRACKING ID:2731133 SYMPTOM: When NFSRestart resource is brought offline, it forcefully stops automountd process. DESCRIPTION: When NFSRestart resource is brought offline, it terminates NFS daemons. It looks for 'mountd' daemon in running processes and stops the matching ones. It also matches 'automountd' process and subsequently forcefully stops it. RESOLUTION: The NFSRestart Agent behaviour is updated in VCS to do a strict matching for process name, which means only stop 'mountd' process. INCIDENTS FROM OLD PATCHES: --------------------------- Patch Id::5.1.112.0 * Incident no::2190142 Tracking ID ::2190134 Symptom::If physical volumes are added, deleted or replaced in a volume group on an active node, the volume group resource fails to come online on any other node in the cluster during a failover. Description::If physical volumes are added, deleted or replaced in a volume group, the disk entries in the ODM database of the local nodes are updated, but some or all of the ODM entries on other nodes remain stale. This causes the volume group resource online failure on those nodes. Resolution::A new action entry point updatepv is introduced in the LVMVG agent to resolve this issue. The updated disk information having the list of physical volume IDs stored in a temporary file can be propagated to all nodes in the cluster using the updatepv action entry point. The agent uses this disk information to bring the volume group resource online during a failover. Once the volume group is online on the failover node, the ODM entries get updated and then the temporary file is deleted. * Incident no::2253349 Tracking ID ::2253345 Symptom::The IP agent fails to go offline when NetMask is changed outside of VCS control for an online VCS IP resource. Description::The IP agent makes use of IP address and Netmask value pair to perform online and offline operations. When the Netmask value on the interface is changed outside of VCS control, the VCS expected value of Netmask mismatches with the netmask value present on the device and hence offline operation fails. Resolution::Symantec has modified the VCS IP agent to log a warning which prompts to update the NetMask attribute value if the Netmask value is changed outside of VCS control. * Incident no::2330045 Tracking ID ::2195569 Symptom::If you set the ControlMode attribute of a RemoteGroup resource to OnlineOnly or MonitorOnly, then the resource fails to go offline when it loses connectivity with the remote cluster. Description::The RemoteGroup resource tries to connect to the remote cluster even after the agent has invoked its offline entry point. If the connection to the remote cluster is not available, the resource goes into the UNKNOWN state and prevents the service group from going offline. Resolution::Symantec has modified the RemoteGroup resource to check for the remote cluster connection only when the resource is ONLINE. This fix is valid only if you set the ControlMode attribute of a RemoteGroup resource to OnlineOnly or MonitorOnly. * Incident no::2366701 Tracking ID ::2371667 Symptom::1. If you store the Monitor program on a shared disk and a VCS node is unable to access the shared disk, then: a) The Application agent cannot monitor an application on the node. b) VCS cannot fail over applications on such a node. 2. If the Monitor program returns UNIX style return values (0 for success and 1 for failure), the application agent reports the state of application as UNKNOWN. Description::1. The application agent checks for the existence of the Monitor program on a node. On nodes that cannot access the shared disk, this check fails. As a result, the agent marks the status of the application as UNKNOWN on such nodes. Further, if an application goes down on an active node, then the application cannot fail over to nodes where the status of the application is UNKNOWN. 2. The Application agent can handle only the following set of values returned by the monitor program: 100 --> OFFLINE 101 to 110 --> ONLINE Any other value --> UNKNOWN. If the monitor program returns "0" as success and "1" as failure, the Application agent reports the state of application as UNKNOWN. Resolution::1. Symantec has modified the Application agent to check for the existence of the Monitor program, instead of checking whether the Monitor program has executable permissions. As a result, for nodes that cannot access the shared disks, the agent now reports the application as OFFLINE, only if the previous state of the application was OFFLINE, and the application was not waiting for a state change. In all other cases, for nodes that cannot access the shared disks, the agent reports the state of the application as UNKNOWN. 2. The Application agent handles the standard UNIX style return values, that is, "0" for success and "1" for failure, and now reports the resource state based on following set of values: 100 or 1 --> OFFLINE 101 to 110 or 0 --> ONLINE Any other value --> UNKNOWN. * Incident no::2377788 Tracking ID ::2377791 Symptom::IPMultiNICB agent dumps core when configured for IPv6 and when IPv4-specific attributes, like NetMask, are not set. Description::IPMultiNICB agent Entry Points modify the value of arglist pointers. Therefore, the memory goes out of scope when the Entry Point exits and agent dumps core when the agent framework tries to free the arglist pointers. Resolution::ArgList pointers are not modified within IPMultiNICB agent Entry Points. * Incident no::2380922 Tracking ID ::2380918 Symptom::If multiple IPMultiNICB resources configured over a single MultiNICB resource are online and if one of them goes offline, the default route gets deleted. This leaves the other online virtual IPs unreachable from external networks. Description::When a IPMultiNICB resource goes online, it adds the default route and when it goes offline, it deletes the default route. However, IPMultiNICB resource does not check whether the default route getting deleted is required for any other IPMultiNICB resource. Resolution::The default route is added by MultiNICB agent for all the functional interfaces. Also, the default route is deleted by MultiNICB agent whenever the interface is found to be non-functional. * Incident no::2423990 Tracking ID ::2423984 Symptom::In a VCS Application agent configuration, if the administrator specifies a user name that is invalid on a system, then the agent may not correctly function on that system. Description::In the above case, the agent may display error messages or abruptly terminate. Resolution::Symantec has modified the Application agent to validate the user name configured as an User attribute. If the user name is not valid on a system, the agent reports the state of a configured resource on that system as UNKNOWN. * Incident no::2435596 Tracking ID ::2554151 Symptom::NFS resource failed to come online with NFSv4 on AIX, because of NFS local domain not set on machine. Description::NFSv4 requires nfsrgyd service to be running on AIX. If NFS domain name is not set on the machine, nfsrgyd service does not start and hence, the NFS resource fails to come online. Resolution::NFS domain name is set to allow the nfsrgyd service to start successfully. The NFS domain name is set with the domain name value, found in either system's local domain name or from the fully qualified host name. If the domain name is not found in both locations and if the NFS domain name is not set, only then the NFS resource fails to come online. * Incident no::2441471 Tracking ID ::2518606 Symptom::When VCS attempts to fail over a WPAR resource after calling clean entry point, where clean entry point is due to monitor time out, the failover does not happen. Description::When monitor timeout happens, VCS calls the clean EP for that resource. Clean entry point calls the wrong command to stop the WPAR forcefully. Due to this, the monitor timeout continues and failover does not happen. Resolution::Clean entry point calls the correct command to stop the WPAR forcefully. * Incident no::2476901 Tracking ID ::2476893 Symptom::In a Solaris Zone or an AIX WPAR environment, if you configure a resource for physical-to-virtual (P2V) failover on a VCS node, the configured resource may fail to come online. Description::Certain VCS agents fail to check the ContainerInfo attribute for P2V information. As a result, the agents may fail to bring the configured resource online. The affected agents include: Application, IP, IPMultiNICB, Mount, ASMInst, Oracle, Netlsnr, Sybase, SybaseBk Resolution::Symantec has modified the above agents to check the ContainerInfo attribute for P2V information. * Incident no::2477305 Tracking ID ::2477285 Symptom::In a Solaris zone or an AIX WPAR environment, if you configure a resource for physical-to-virtual (P2V) failover, the Zone agent or the WPAR agent may report incorrect state of the resource. Description::In certain corner cases, the Zone agent or the WPAR agent fails to correctly interpret the state of a resource. Resolution::Symantec has modified the Zone and WPAR agents to cover the corner cases in P2V configurations. * Incident no::2516856 Tracking ID ::2476893 Symptom::In a Solaris Zone or an AIX WPAR environment, if you configure a resource for physical-to-virtual (P2V) failover on a VCS node, the configured resource may fail to come online. Description::Certain VCS agents fail to check the ContainerInfo attribute for P2V information. As a result, the agents may fail to bring the configured resource online. The affected agents include: Application, IP, IPMultiNICB, Mount, ASMInst, Oracle, Netlsnr, Sybase, SybaseBk Resolution::Symantec has modified the above agents to check the ContainerInfo attribute for P2V information. * Incident no::2516926 Tracking ID ::2476893 Symptom::In a Solaris Zone or an AIX WPAR environment, if you configure a resource for physical-to-virtual (P2V) failover on a VCS node, the configured resource may fail to come online. Description::Certain VCS agents fail to check the ContainerInfo attribute for P2V information. As a result, the agents may fail to bring the configured resource online. The affected agents include: Application, IP, IPMultiNICB, Mount, ASMInst, Oracle, Netlsnr, Sybase, SybaseBk Resolution::Symantec has modified the above agents to check the ContainerInfo attribute for P2V information. * Incident no::2528475 Tracking ID ::2528470 Symptom::The preonline_ipc trigger functionality of VCS, that performs certain checks before bringing a group online, does not work for resources other than IP resources. Description::This is a known limitation. There is an enhancement requirement to extend preonline_ipc trigger support to other resources types. Resolution::Symantec has enhanced the preonline_ipc trigger to support the following types of resources on a system: IP, IPMultiNIC, and IPMultiNICB. * Incident no::2514514 Tracking ID ::2523471 Symptom::If the 'httpd' binary or the 'ab' binary is not present at the location that you specified in the 'httpdDir' attribute, the Apache agent cannot perform detail monitoring or start the HTTP server. Description::To start the HTTP server, the Apache agent uses the 'httpd' binary from the location specified in the 'httpdDir' attribute. To perform detail monitoring, the agent uses the Apache Benchmarking utility or 'ab' binary from the same location. If the binaries in that location use a slightly different name, such as say 'httpd2', the agent does not recognize the binary, and therefore cannot perform the desired actions. Resolution::Symantec has enhanced the 'httpdDir' attribute such that you can specify the full path of the binary (including the binary name). If you specify only the directory name, the agent assumes the default binary name 'httpd'. If the Apache Benchmarking binary in the specified directory does not use the default name, then the agent recognizes the alternative binary name 'ab2', and performs detail monitoring.