They shouldn't be "fighting"   An MPIO connection managed by the HIT kit (Windows, Linux, ESX) should not be balanced by the Connection Load Balancer (CLB).   The path redundancy errors will always occur, ESX treats any connection balance as an error, even though it should not do so.  If the case is still open, please ask them to escalate it to Nashua.  They'd like to look at the logs from the arrays, ESX and MEM.   Do you have any non ESX hosts connecting to these volumes?  (e.g. A Windows Backup Server)   Regards, 
I raised this as a support ticket but it was suggested I post a question here to get a response from the experts. :emotion-1: After upgrading to firmware 6.0.1 we have observed different behaviour on load balancing requests... On firmware 5.2.2 On firmware 6.0.1 Delving into host logs to determine the reason for the additional logout we can see it is initiated by the equallogic MEM driver in response to it's first poll of the array following the completion of the load balance, at which point it is informed the new connection is invalid which results in it being torn down and recreated. I have been informed this behaviour is "as intended", but I'm having difficulty seeing the benefit/reason. To my untrained eye; array load balancing and the MEM driver appear to be fighting each other with the MEM driver undoing every load balance attempt by the array. Any reassurances would be welcome.
Info Request - Firmware 6.0.1 and Load balancing 