Veritas Storage Foundation and High Availability Solutions Release Notes

82About Veritas Storage Foundation and High Availability SolutionsKnown issues■■■■I/O fencing known issuesIssues related to Intelligent Monitoring Framework (IMF)Issues related to the Cluster Manager (Java Console)Issues related to virtualizationNFS cluster I/O fails when storage is disabled [2555662]The I/O from the NFS clusters are saved on a shared disk or a shared storage.When the shared disks or shared storage connected to the NFS clusters aredisabled, the I/O from the NFS Client fails and an I/O error occurs.Workaround: If the application exits (fails/stops), restart the application.Operational issues for VCSSome VCS components do not work on the systems where a firewall isconfigured to block TCP trafficThe following issues may occur if you install and configure VCS on systems wherea firewall is installed:■■■If you set up Disaster Recovery using the Global Cluster Option (GCO), thestatus of the remote cluster (cluster at the secondary site) shows as "initing".If you configure fencing to use CP server, fencing client fails to register withthe CP server.Setting up trust relationships between servers fails.Workaround:■■Ensure that the required ports and services are not blocked by the firewall.Refer to the Veritas Cluster Server Installation Guide for the list of ports andservices used by VCS.Configure the firewall policy such that the TCP ports required by VCS are notblocked. Refer to your respective firewall or OS vendor documents for therequired configuration.Stale legacy_run services seen when VCS is upgraded to support SMF[2431741]If you have VCS 5.0MPx installed on a Solaris 10 system, VCS uses RC scripts tomanage starting services. If you upgrade VCS to any version that supports SMFfor VCS, you see stale legacy_run services for these RC scripts in addition to theSMF services.Workaround: There are two ways to remove these legacy services: