Skip to main content
NetApp Knowledge Base

How to verify Solaris fibre channel configurations with multipathing

Views:
1,100
Visibility:
Public
Votes:
4
Category:
flexpod-with-infrastructure-automation
Specialty:
san
Last Updated:

Applies to

  • Data ONTAP 8 7-Mode
  • FlexPod
  • Data ONTAP 7 and earlier

Description

Syslog and EMS messages

[hostname: scsitarget.partnerPath.misconfigured:error]: FCP Partner Path Misconfigured.
[hostname: scsitarget.partnerPath.misconfigured:error]: FCP Partner Path Misconfigured - Host I/O access through a non-primary and non-optimal path was detected. 

See article What do FCP Partner Path Misconfigured messages mean? for a complete discussion of this error message.

Problem Description

SANs often provide multiple paths to allow hosts to access LUNs. To maximize the redundancy of SAN, the host operating system must use multipathing I/O (MPIO) software. MPIO software monitors all available paths and will decide for the operating system which path should be used. NetApp currently supports two forms of MPIO software for Solaris, the native MPIO module (MPxIO) and Veritas Dynamic Multipathing (DMP). The following processes outline how to observe the MPxIO and Veritas DMP configurations. Steps to setup the MPIO configuration are documented in the FCP Solaris Host Utilities

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.