README VERSION : 1.0 README Creation Date : 2011-09-09 Patch-ID : 143288-12 Patch Name : VRTSvcsag 5.1SP1RP2-sol BASE PACKAGE NAME : Veritas Cluster Server Bundled Agents by Symantec BASE PACKAGE VERSION : VRTSvcsag 5.1SP1 Obsolete Patches : NONE Superseded Patches : NONE Required Patches : NONE Incompatible Patches : NONE Supported PADV : sol9_sparc , sol10_sparc (P-Platform , A-Architecture , D-Distribution , V-Version) Patch Category : MEMORYLEAK Reboot Required : NO KNOWN ISSUES : FIXED INCIDENTS: ---------------- Patch Id::143288-12 * 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::2275376 Tracking ID ::2423623 Symptom::If you do not specify a value for the BootState attribute, then the Zone agent does not automatically use the default value of the attribute. As a result, some of the commands that the Zone agent uses, may fail. Description::If you do not set the BootState attribute, then the Zone agent must use the default value, which is typically 'multi-user'. The Zone agent fails to do so. Resolution::Symantec has modified the Zone agent to ensure that if you do not specify the BootState attribute, then the Zone agent uses the default value, "multi-user". * Incident no::2298775 Tracking ID ::2298765 Symptom::If you use the 'hazonesetup' utility to configure a Zone group, then you cannot configure different local Zone names on the different nodes in a VCS cluster. Description::The 'hazonesetup' utility does not localize the ContainerInfo attribute. As a result, you cannot have different local Zone names on different nodes. Resolution::Symantec has fixed this issue by adding the parallel option to the 'hazonesetup' utility. You can use the new option to localize the ContainerInfo attribute. * Incident no::2317067 Tracking ID ::2317065 Symptom::Application resource fails to come online inside zones if PID files are specified. Description::Due to a program error, Application agent checked for the PID files in the global zone for applications running inside the local zone. Resolution::Symantec has modified the Application agent to first check if the application resource is configured to monitor applications running inside the local zone. If the resource is configured to monitor applications running inside the local zone then the Application agent checks for the PID files inside the local zone or else it checks in the global zone. * Incident no::2323312 Tracking ID ::2323311 Symptom::When you configure the MonitorProcesses attribute, if you specify a process name with more than 79 characters, then the Application agent fails to detect the process. Description::In order to accommodate the string termination character ('\0'), the Application agent trims the process name length (PRARGSZ) by one character. By default, the size limit on PRARGSZ is 80 characters. As a result, the Application agent detects a process name only if the process name is 79 characters in length, or less. Resolution::Symantec has increased the internal buffers in the Application agent code. As a result, the agent now correctly reads process names if the number of characters in the process name is equal to the maximum allowed value of PRARGSZ. * 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::2358616 Tracking ID ::2358476 Symptom::In case of certain network drivers, the MultiNICB agent may incorrectly report a link to be down. Description::If you set the IgnoreLinkStatus attribute to 0, then the MultiNICB agent tests the links for their status. However, the MultiNICB agent does not support certain versions of network drivers and the link test may fail. Resolution::Symantec has modified the MultiNICB agent code to fix this issue. * Incident no::2366701 Tracking ID ::2371667 Symptom::a. If you store the Start/Stop/Monitor programs on shared disks, and a VCS node is unable to access the shared disks, then the Application agent cannot monitor an application on the node. Further, VCS cannot fail over applications on such a node. b. The Monitor program returns UNIX style values, that is, "0" in case of success and "1" In case of failure. The Application Agent does not handle these values. Description::a. The Application agent checks for the existence of the Start/Stop/Monitor programs on a node. On nodes that cannot access the shared disk, this check fails. As a result, on such nodes, the agent marks the status of the application as Unknown. 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. b. 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 a monitor program returns "0" as success and "1" as failure, the Application agent returns the resource state as UNKNOWN. Resolution::a. Symantec has modified the Application agent to check for non-null values of the attributes associated with the Start/Stop/Monitor programs, instead of checking for the existence of the programs. 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. b. 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::2371652 Tracking ID ::2358594 Symptom::In a GCO (Global Cluster Option) setup, you may be unable to bring an IPMultiNIC resource online. Description::In a GCO setup, the IPMultiNIC resource may be unable to successfully use certain commands to detect the state of the corresponding MultiNICA resource. As a result, the IPMultiNIC resource does not come online. Resolution::Symantec has modified the IPMultiNIC agent code to fix this issue. * Incident no::2407872 Tracking ID ::2407871 Symptom::When VCS tries to bring an application resource online, or tries to take an application resource offline, the following error message appears in the engine log: "sh: setenv: not found" Description::The above error message appears when the following conditions simultaneously occur: a. The login shell of the root user is *csh b. The 'User' attribute is not set c. The value of the 'UseSUDash' attribute is '0' The Application agent sets the USER, HOME, and LOGNAME environment variables by using the 'setenv' command, before the agent executes the program specified for the user with the csh shell. For the root user (default user), the Application agent online/offline entry points execute the above program by directly using a system call. This internally executes the '/bin/sh -c' command. The csh shell command 'setenv' does not work in /bin/sh, and therefore the error occurs. Resolution::Symantec has modified the Application agent online/offline entry points such that the agent sets the environment variables, USER, LOGNAME, and HOME only if the user is a non-root user. * Incident no::2416956 Tracking ID ::2416950 Symptom::For VCS 5.1SP1 or later, if you do not set the value of the CleanProgram attribute, then the Application agent uses the StopProgram attribute to clean a resource during a clean entry point. This behavior may invalidate your agent configuration. Description::In VCS 5.1SP1, Symantec modified the Application agent code to use the StopProgram attribute to perform the clean operation, if a user does not configure the CleanProgram attribute. Resolution::Symantec has re-modified the Application agent to ensure that if you do not configure the CleanProgram attribute, the StopProgram attribute is not called, and the clean entry point fails. If you want the agent to clean the application, then you can configure the CleanProgram attribute. * Incident no::2423838 Tracking ID ::2301855 Symptom::If you configure IP resources, you may observe memory leaks in the IP agent process. Description::The IP agent fails to free internal memory allocations. This failure may lead to memory leaks. Resolution::Symantec has modified the IP agent code to fix this issue. * 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::2427464 Tracking ID ::2427433 Symptom::In an IPv6 setup, the MultiNICB agent incorrectly reports the state of a MultiNICB resource as UNKNOWN, if the following condition occurs: - Interfaces that are under MultiNICB control are on a subnet other than the subnet of interfaces that are not under MultiNICB Agent control Description::The MultiNICB agent compares the subnets of all the interfaces on a system, and in the above case, reports an incorrect resource state. Resolution::Symantec has modified the MultiNICB agent to skip the check for the subnet of IPv6 interfaces. * Incident no::2433347 Tracking ID ::2433325 Symptom::The Application agent searches for the user's home directory in the global zone for applications configured in the local zone. Description::Due to a program error, Application agent checked for home directory in the global zone for applications running inside the local zone. Resolution::Symantec has modified the Application agent to first check if the application resource is configured to monitor applications running inside the local zone. If the resource is configured to monitor applications running inside the local zone then the Application agent checks for home directory inside the local zone or else it will check in the global zone. * Incident no::2476897 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::2477268 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::2485202 Tracking ID ::2481411 Symptom::The Application agent monitor entry point fails when the 80th character in the value specified for MonitorProcesses attribute is a space. Description::The above issue is observed because Application agent internally removes spaces from the processes specified in MonitorProcesses attribute. Additionally, the Application agent reads pr_psargs value from psinfo structure by scanning the /proc file system. Therefore, the Application agent can detect a maximum of 80 characters of the command line processes specified in the MonitorProcesses attribute. Resolution::Symantec has modified the Application agent such that it does not remove spaces from the processes specified in MonitorProcesses attribute. Agent now uses "/usr/ucb/ps -ww pid" command to get the process COMMAND name from system which returns the complete COMMAND name without any limitation of characters. You must now configure the exact command line of the processes in the MonitorProcesses attribute as returned by the "/usr/ucb/ps -ww pid" command. * Incident no::2491635 Tracking ID ::2491627 Symptom::On Solaris systems when VxVM version 5.1 is installed with VCS version 5.1SP1, online entry point of DiskGroup resource logs the following error message "ERROR: vxdefault list autostartvolumes command failed". Description::VxVM introduced autostartvolumes feature in 5.1SP1 release. The DiskGroup agent online entry point in VCS 5.1SP1 fails to correctly verify the VxVM version to check the availability of autostartvolumes feature. Resolution::Symantec has modified the online entry point of DiskGroup agent to directly verify the availability of autostartvolumes feature in VxVM. * Incident no::2513928 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::2516807 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::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. * 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. Incidents from old Patches: --------------------------- NONE