17.08.2015 Views

Veritas Storage Foundation and High Availability Solutions Release Notes

Veritas Storage Foundation™ and High ... - SORT - Symantec

Veritas Storage Foundation™ and High ... - SORT - Symantec

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

108About <strong>Veritas</strong> <strong>Storage</strong> <strong>Foundation</strong> <strong>and</strong> <strong>High</strong> <strong>Availability</strong> <strong>Solutions</strong>Known issuesthe system. On Solaris 11, add_drv may fail if there is another add_drv comm<strong>and</strong>that is being run on the system at the same time.Workaround:Check the status of LLT, GAB <strong>and</strong> Vxfen modules. Ensure that all the three servicesare online in SMF. Then, retry starting VCS.After you run the vxfenswap utility the CoordPoint agent may fault(2846389)After you run the vxfenswap utility, if the value of the FaultTolerance attributeof the CoordPoint agent is more than the majority (more than 50%) of thecoordination points then the Coordination Point agent faults.Workaround: Manually set the value of the FaultTolerance attribute of CoordPointagent to be less than the majority (more than 50%) of the coordination points.When I/O fencing is not up, the svcs comm<strong>and</strong> shows VxFEN as online(2492874)Solaris 10 SMF marks the service status based on the exit code of the start methodfor that service. The VxFEN start method executes the vxfen-startup script in thebackground <strong>and</strong> exits with code 0. Hence, if the vxfen-startup script subsequentlyexits with failure then this change is not propagated to SMF. This behavior causesthe svcs comm<strong>and</strong> to show incorrect status for VxFEN.Workaround: Use the vxfenadm comm<strong>and</strong> to verify that I/O fencing is running.The vxfenswap utility does not detect failure of coordination pointsvalidation due to an RSH limitation (2531561)The vxfenswap utility runs the vxfenconfig -o modify comm<strong>and</strong> over RSH orSSH on each cluster node for validation of coordination points. If you run thevxfenswap comm<strong>and</strong> using RSH (with the -n option), then RSH does not detectthe failure of validation of coordination points on a node. From this point,vxfenswap proceeds as if the validation was successful on all the nodes. But, itfails at a later stage when it tries to commit the new coordination points to theVxFEN driver. After the failure, it rolls back the entire operation, <strong>and</strong> exits cleanlywith a non-zero error code. If you run vxfenswap using SSH (without the -n option),then SSH detects the failure of validation of coordination of points correctly <strong>and</strong>rolls back the entire operation immediately.Workaround: Use the vxfenswap utility with SSH (without the -n option).

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!