Veritas Storage Foundation and High Availability Solutions Release Notes
Veritas Storage Foundation⢠and High ... - SORT - Symantec
Veritas Storage Foundation⢠and High ... - SORT - Symantec
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
About <strong>Veritas</strong> <strong>Storage</strong> <strong>Foundation</strong> <strong>and</strong> <strong>High</strong> <strong>Availability</strong> <strong>Solutions</strong>Known issues103Application group attempts to come online on primary site before fire drillservice group goes offline on the secondary site (2107386)The application service group comes online on the primary site while the fire drillservice group attempts to go offline at the same time, causing the applicationgroup to fault.Workaround: Ensure that the fire drill service group is completely offline on thesecondary site before the application service group comes online on the primarysite.Second secondary cluster cannot take over the primary role when primary<strong>and</strong> 1st-secondary clusters panic [2858187]If there are three clusters(clus1, clus2, <strong>and</strong> clus3) in a GCO without a steward,when clus1 loses connection to clus2, it will send the inquiry to clus3 to check thestate of clus2:■■If it is able to confirm that clus2 is down, it will mark clus2 as FAULTED.If it is not able to send the inquiry to clus3, it will assume that a networkdisconnect has happened <strong>and</strong> mark clus2 as UNKNOWN. In this case, automaticfailover will not take place even if the ClusterFailoverPolicy is set to Auto. Ifthis happens, users would need to manually failover the global service groups.Workaround:Configure the steward at a location geographically distinct from those of the threeclusters above.LLT known issuesThis section covers the known issues related to LLT in this release.Cannot configure LLT if full device path is not used in the llttab file(2858159)(Oracle Solaris 11) On virtual machines ensure that you use the full path of thedevices corresponding to the links in llttab. For example, use /dev/net/net1 insteadof /dev/net/net:1 in the llttab file, otherwise you cannot configure LLT.LLT port stats sometimes shows recvcnt larger than recvbytes (1907228)With each received packet, LLT increments the following variables:■■recvcnt (increment by one for every packet)recvbytes (increment by size of packet for every packet)
Change language