Your filers are having to pass traffic to each other. Read up on alua and if you use MPIO 3.4 or 3.5 with the appropriate versions of DSM, you need to set your igroups to alua=yes.
-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Stuart Kendrick Sent: Monday, November 12, 2012 2:50 PM To: toasters@teaparty.net Subject: how significant / non-optimal path error
How substantially can this affect performance?
scsitarget.partnerPath.misconfigured:error]: FCP Partner Path Misconfigured - Host I/O access through a non-primary and non-optimal path was detected.
We have a two-node FAS3020 cluster running 7.2.4, serving two clients via Fibre Channel. [More precisely, four clients: two pairs of Active/Standby SQL Server clusters. A pair of Fibre Channel switches provide the fabric for this tiny SAN.]
Cleverly, we've configured the clients to cross the cluster interconnect in order to reach their shelves.
i.e. under normal operation, Client1's traffic must traverse the fabric, ToasterA, the cluster interconnect, and ToasterB, before reaching its shelves. Conversely, Client2's traffic must traverse the fabric, ToasterB, the cluster interconnect, and ToasterA before reaching its shelves.
Occasionally, we see the error message above in the logs ... sometimes just once/week, occasionally twice/day.
We'd like to ignore this ... we hope to retire the installation sometime next year ... but on the other hand, if this degrades performance substantially, then we'll reconsider.
?
--sk
Stuart Kendrick FHCRC
_______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters