Veritas Storage Foundation and High Availability Solutions Release Notes

98About Veritas Storage Foundation and High Availability SolutionsKnown issuesWorkaround: Unmount the file system manually from global zone and then haltthe zone. For VxFS, use following commands to unmount the file system fromglobal zone.To unmount when VxFSMountLock is 1umount -o mntunlock=VCS /To forcefully unmount when VxFSMountLock is 1:# umount -f -o mntunlock=VCS /To unmount when VxFSMountLock is 0:# umount /To forcefully unmount when VxFSMountLock is 0:# umount -f /To halt the zone, use following command:# zoneadm -z haltPrevention of Concurrency Violation (PCV) is not supported for applicationsrunning in a container [2536037]For an application running in a container, VCS uses a similar functionality as ifthat resource is not registered to IMF. Hence, there is no IMF control to take aresource offline. When the same resource goes online on multiple nodes, agentdetects and reports to engine. Engine uses the offline monitor to take the resourceoffline. Hence, even though there is a time lag before the detection of the sameresource coming online on multiple nodes at the same time, VCS takes the resourceoffline.PCV does not function for an application running inside a local Zone on SolarisWorkaround: No workaround.For IPv6 configuration, the MultiNICA Agent is unable to detect loss ofnetwork connectivity (2979745)While monitoring the Network Interface Cards (NIC) configured with the MultiNICAResource, if the NIC is not able to ping the Network Hosts, the Agent tries to pingthe broadcast address to check whether the NIC is healthy. The agent uses thepacket count of the NIC to check if the network is reachable. But the packet countmay increase even due to the NIC replying to itself rather than the replies fromthe systems in the network. Thus, Veritas Cluster Server (VCS) may incorrectlyreport the NIC as healthy. This issue exists only for IPv6 addresses.