Greetings,
We're seeing occasional autosupport riggers of (FCP PARTNER PATH MISCONFIGURED) ERROR. 99% of the time, there is usually a WWN listed under "lun config check" section of autosupport that stands way out and I can clearly say "this WWN did it" and we know the remedy is primary ports.
However, sometimes a message is triggered and the lun config check of the autosupport looks like this:
==== LUN CONFIG CHECK =====
The following FCP Initiators are sending Read/Write i/o over the
FCP Partner Paths during the last 19 seconds
WWPN Partner's Port ops bytes
21:00:00:1b:32:05:15:1c 0a 2 1024
21:00:00:1b:32:05:15:1c 0b 2 1024
21:00:00:1b:32:05:09:1c 0d 2 1024
21:00:00:1b:32:09:0b:47 0a 4 2048
21:00:00:1b:32:09:0b:47 0b 4 2048
21:00:00:1b:32:09:d9:48 0d 4 2048
21:00:00:1b:32:09:d9:48 0c 4 2048
Should 4 or 2 ops be triggering this error?