Hi,
I have the same behaviour on my systems (FAS6030 and FAS3140 : 7.3.2P5).
After a long diagnostic with Microsoft and Netapp, it apears that those messages can be ignored (leading to Netapp and Microsoft) : they are generated on each Hyper-V Hosts by a WMI request orchestrated by SCCM server : Microsoft's answer about this behaviour is : " this is done by Design".
My point of view is that this kind of behaviour could generate useless load, and can lead to freeze VMs, if it occur during an overload of the Storage system.
We have also seen sometime Lun reset messages in syslog comming from Hyper-V hosts, and I suspect that those messages are the consequences of an Iscsi New Session on heavy load, but I do not have any proof.
If you go further in debug or encounter problems with this behaviour in your environment please let me know.
I continue to investigate with Microsoft until they confirm me that there is no loose of connection and freeze of data access during an "ISCSI new session" (simultaeously on every Hyper-V host in a cluster configuration).
regards,
YL