According to the information given below says that the amount of data is greater than the amount of time and makes part pass information to the partner and this gives an error fcp miss configured error.
I found this example in the now support:
In the example above, both Partner Ops and Partner Kbytes have exceeded the threshold in the given time interval. The hosts accessing the LUN in this way should be identified and the reasoning for the access evaluated. Possible solutions are to restrict access, or tune the host MPIO software so that it will not attempt access through the partner path.
Setting these options would not fix anything, it would just hide the problem. You have to find out why data is accessed via non-preferred paths and fix it. It could be host misconfiguration or real problems with connectivity (bad cable, port, switch, adapter, ...).
>lun stats -z will zero those lun stats, wait couple days and chek again output >lun stats Then you get better picture which LUNs are causing those errors. I can see the information in your example is from last 460days. so it doesen't tell too much. lots of chages may be done in that time.
When you find your LUNs, you need to fix the path settings from clients side. Ofcourse, if all the LUNs are going through partner node, then there might be something else wrong as well.
Why this happens, takeover/giveback can be one reason, during takeover all the paths goes through one node, and when giveback is done, paths may remain.
Client doesen't care about "optimal" path, it's ok when it sees the LUN, but from netapps view, client is using a wrong path.