Hi Joerg, What is a [tag:SR]? I have opened a support case at 24 June and still waiting for Dell to contact me.  Ryan
Hello, We recently purchased 2 Equallogic SANs (PS6510ES) and enabled Synchronous replication between them. We are using ESXi 5.5 and followed the best practices guide to disable TCP ack and set logintimeout to 60. Everything seems working fine until we tried Storage vMotion/migration and cloning VM on the SANs. When we performed storage migration across 2 volumes on the EQL SAN (the target volume has syncrep enabled), the target volume will start to be out-of-sync and then the storage vMotion will sometimes hang.  The worst part is when such problem occurred, all other volumes on the EQL SANs will stop responding as well. All the volumes will not respond until we restarted the corresponding ESXi host (NOTE: Mere shut down/power off of the host will not help. The EQL SANs will only resume normal  after a successful restart of the ESXi host). If we paused/disabled the syncrep before Storage vMotion, the problem will not happen. Is it normal or not?  Furthermore, each time the problem occurred, the write latency of the corresponding volume will grow to secs and we will receive alerts similar to the following: iSCSI login to target 'xx.xx.xx.xx:3260, iqn.2001-05.com.equallogic:xxxxx-test-volume' from initiator 'xx.xx.xx.xx:xxxxx, eqlinitiatorsyncrep' failed for the following reason:  Initiator disconnected from target during login. Thanks in advance.
Storage vMotion with Syncrep on Equallogic SANs