Veritas Storage Foundation and High Availability Solutions Release Notes

136About Veritas Storage Foundation and High Availability SolutionsSoftware limitationsInterface object name must match net/v4static for VCS networkreconfiguration script in Solaris 11 guest domain [2840193]If the Solaris 11 guest domain is configured for DR and its interface object namedoes not match the net/v4static pattern then the VCS guest networkreconfiguration script (VRTSvcsnr) running inside the guest domain adds a newinterface object and the existing entry will remain as is.Share agent limitation (2717636)If the Share resource is configured with VCS to share a system directory (forexample, /usr) or Oracle Solaris 11 which gets mounted at boot time, the VCSshare resource detects it online once VCS starts on the node after a panic or halt.This can lead to a concurrency violation if the share resource is a part of a failoverservice group, and the group has failed over to another node in the cluster. VCSbrings down the Share resource subsequently. This is due to the share commandbehavior or Oracle Solaris 11, where a directory shared with share commandremains persistently on the system across reboots.Agent directory base name must be type name for an agentusing out-of-the-box imf_init IMF entry point to get IMF support[2858160]To get IMF support for an agent which uses the out-of-the-box imf_init IMF entrypoint, the base name of agent directory must be the type name. When AgentFileis set to one of the out-of-the-box agents like Script51Agent, that agent will notget IMF support.Workaround:1 Create the following symlink in agent directory (for example in/opt/VRTSagents/ha/bin/WebSphereMQ6 directory).# cd /opt/VRTSagents/ha/bin/# ln -s /opt/VRTSvcs/bin/Script51Agent Agent2 Run the following command to update the AgentFile attribute based on valueof VCS_HOME.■If VCS_HOME is /opt/VRTSvcs:# hatype -modify AgentFile/opt/VRTSvcs/bin//Agent■If VCS_HOME is /opt/VRTSagents/ha: