Hello,  The best option to prevent the delay is use something like the broadcom iSCSI offload adapter.  The S/W iSCSI adapter would be bound to the NICs for the MD volumes, (or don't bind anything there and use multiple subnets instead)    The offload adapter would then handle the EQL triaffic.   This prevents the long boot up delay since all bound NICs are trying to reach all defined Discovery addresses.   I've never tried to just use static addresses w/ESXi so I can't really speak to why you are getting the extra connections.  Unless it's still doing a discovery, or the old static entries were still there after you changed to static.   Regards,   Don 
Hi all, Also posted here - How many iscsi logins should I be seeing? - Spiceworks and here - communities.vmware.com/.../520622 Running ESXi 5.5 and an Equallogic PS4100X, hoping someone point me in the right direction on something I've noticed. Recently installed an MD3220i ([URL] After the install boot up and iSCSI login times can be quite long (as expected using iSCSI port binding with multiple subnets) but my question is not related to that. I have come today to see what I can do to improve boot times, perhaps by using static discovery instead of dynamic, and I've noticed something odd. For the Equallogic we have 2 NICs, 10.11.14.1 and 10.11.14.2. When using dynamic discovery I enter the group IP (10.11.14.253) and I get 8 logins, one from each IP on the ESXi hosts to each of the IPs on the equallogic, see screenshot iscsi1.png All fine. If I then switch to static and put 2 entries in per datastore (one for each NIC on the equallogic) (see screenshot iscsi2.png) then what I see in the equallogic is 16 logins for the host. Each datastore is logged into twice from each NIC on the host, one each via the NICs on the equallogic, see screenshot iscsi3.png. I'm not sure if this is better or worse! I have more paths so it should be better? Or I have to many paths and the system is going to get confused? Thanks,
How many iSCSI logins should I be seeing?