(FCP PARTNER PATH MISCONFIGURED) ERROR

[satechelp]

Hello,

When i check the autosupport of my storage I noticed (FCP PARTNER PATH MISCONFIGURED) ERROR.
I readed some articles on NOW about this case, and i can't get nothing.

I changed the options of thresholds that control the trigger issued next lines:

Options lun.use_partner.cc.warn_limit 300
Options lun.use_partner.cc.bytes 2457600

And the fail continued.

I saw the config check in autosupport the follow WWPN:

===== LUN CONFIG CHECK =====  

The following FCP Initiators are sending Read/Write i/o over the
FCP Partner Paths during the last 304 seconds
WWPN                      Partner's Port       ops         bytes      ostype
21:00:00:24:ff:04:91:ed               0a    270993     522878976     windows

Offending OS: windows
Proxy ops exceeded 273 out of 300 times
Proxy bytes exceed 27 out of 300 times

Then, I displayed the status of adapters, and both are online.

> fcp show adapters
Slot:                    0a
Description:             Fibre Channel Target Adapter 0c (Dual-channel, QLogic 2432 (2462) rev. 2)
Adapter Type:            Local
Status:                  ONLINE

Slot:                    0b
Description:             Fibre Channel Target Adapter 0d (Dual-channel, QLogic 2432 (2462) rev. 2)
Adapter Type:            Local
Status:                  ONLINE

I checked then the MPIO, and the path status is Active.

I use DSM-MPIO native (2008R2)

What can i do now?

Thanks.

[jakob_bena]

hi,

here is a detailed knowledgebase articel, how to solve this problem.

this can help you maybe out.

Identifying Affected LUNs and Hosts
The following steps provide a procedure that can be used to identify the I/O access that is responsible for triggering the error. The process of identifying the I/O access begins by identifying the LUNs receiving the I/O through the partner node's FCP target port. With the LUNs identified, the next step is to identify the initiators performing the I/O. Next, identify the FCP target ports on the storage controller that host the LUNs. The host should have access to at least one port on each node of the storage controller cluster. Once the host initiators and primary FCP target ports have been identified, the fabric can be inspected for correct and functioning connections and finally the hosts' multipath configurations can be inspected for correct operation.

1. Identify the LUNs being accessed through the partner node's FCP Target port.
       a. lun stats -o  (LUN STATISTICS)
2. Identify the host initiators that are performing the I/O through the partner path
       a. lun config_check -A (LUN CONFIG CHECK) - output is only valid when viewed in AutoSupport
       b. lun show -v  (LUN CONFIGURATION)
       c. igroup show -v  (INITIATOR GROUPS)
      
3. Identify the primary storage controller FCP target ports available for access to the LUN.
       a. fcp show cfmode  (FCP CFMODE)
       b. fcp show adapters  (FCP TARGET ADAPTERS)
      
4. Verify the host initiator connectivity to primary FCP target ports and the host MPIO software configuration.
5. Verify use of the partner path has ceased from both cluster nodes.
       a. sysstat -b 1

https://kb.netapp.com/support/index?page=content&id=3010111

regards

[eric_barlier]

jakob is on the money here. to add to Jakobs posting, You ve got the offender mentioned in your messages file.

21:00:00:24:ff:04:91:ed

Do an igroup show or look it up in OM/DFM and look for the HBA mentioned above. thats the host where you ll need to get pathing set properly.

[satechelp]

Thanks for your answers.

I tried these commands before.

The information of the command "igroup show" is:

===== INITIATOR GROUPS =====

    SQL_MMADCL11_MMADCL12 (FCP):

        OS Type: windows

        Host Multipathing Software: Required

        Member: 21:00:00:24:ff:04:91:ed (logged in on: vtic)

        Member: 21:00:00:24:ff:04:91:ef (logged in on: 0a)

        Member: 21:00:00:24:ff:04:91:e8 (logged in on: 0b)

        Member: 21:00:00:24:ff:05:72:b8 (logged in on: vtic)

    SQL_MMADCL11 (FCP):

        OS Type: windows

        Host Multipathing Software: Required

        Member: 21:00:00:24:ff:04:91:ed (logged in on: vtic)

        Member: 21:00:00:24:ff:04:91:ef (logged in on: 0a)

    SQL_MMADCL12 (FCP):

        OS Type: windows

        Host Multipathing Software: Required

        Member: 21:00:00:24:ff:04:91:e8 (logged in on: 0b)

        Member: 21:00:00:24:ff:05:72:b8 (logged in on: vtic)

===== LUN CONFIG CHECK =====

The following FCP Initiators are sending Read/Write i/o over the

FCP Partner Paths during the last 304 seconds

WWPN                      Partner's Port       ops         bytes      ostype

21:00:00:24:ff:04:91:ed               0a    270993     522878976     windows

What must i do now??

[peter_lehmann]

There is an excellent write-up on NOW:

https://kb.netapp.com/support/index?page=content&id=3010111&actp=search&viewlocale=en_US&searchid=1310045898129

Peter

[satechelp]

Thanks everybody for your help.

How can i verify the host initiator connectivity to primary FCP target ports and the host MPIO software configuration???? (point number 4 in the article)

[andrc]

You can see from the `igroup show` output that the initiator in question is accessing via vtic rather than local ports:

Member: 21:00:00:24:ff:04:91:ed (logged in on: vtic)

You then need to identify the host in question from it's WWPN and check your MPIO config i.e. which path(s) have been set as preferred for the LUN(s) in question. Ensure you set the path using local ports as preferred and you shouldn't receive the error messages anymore.

[bsh_suzhouyu]

I just give you the solution:

enable ALUA of the igroup and chose "round robin" policy for MPIO.