Hello,   If you open a support case, they will likely tell you it's working as designed.  Since EQL FW 6.x our MPIO code negotiates connections as needed.  To insure proper performance and minimize connection count.    The event message you included confirms that.  The "requested logout" is coming from the HIT MPIO code.  The 6210 has vertical failover so with little traffic only one connection is needed. A cable or switch failure will not bring down your volume.   If the load goes up another connection will be established.   The settings in the registry that Michael mentioned will no longer override the negotiation code in the firmware and HIT.    There is a feature request to make the minimum two connections to better provide peace-of-mind to our customers over this behavior.     Since you are dealing with a single member, the greatest benefit to our MPIO code isn't being leveraged.   That requires multiple members in one pool.   With a single member, you won't notice any difference w/LQD over Round Robin.    Regards,  Don  
Hi there, I've enabled ISOE on partition 0 in our FC630, broadcom/qlogic 10GbE card. After configured everything on MS iscsi initator then I've seen all the paths were active for a while (10-20min) then one of the paths is just disappeared and never reconnected. I can see "logout request was received from the initiator" message on the EQL log but that is not very helpful. Interestingly enough, this was just happened to the LUN; I've seen no issue for vss-control. So I was checking out the option and I've noticed that if I change the MPIO from "least queue depth" to "fail over only" then I dont see any path disappearance. As I'm not quite sure why the default option "least queue depth" is not working, I'd appreciate for any insight and details. Thanks,   
broadcom/qlogic npar isoe and MPIO policy on Windows 2012R2