iSCSI port binding + Route Based on IP Hash

[nem1s1s]

I'm trying to find the official statement from VMware that states iSCSI port binding + Route Based on IP Hash is an unsupported configuration.

vSphere 6.7 + vSS OR vDS

[berndweyand]

Page 81: https://docs.vmware.com/en/VMware-vSphere/6.7/vsphere-esxi-vcenter-server-67-networking-guide.pdf?hW...

[nem1s1s]

Thanks.

The LACP is not supported with software iSCSI port binding. iSCSI multipathing over LAG is supported, if port binding is not used

When they say LACP, does this also mean EtherChannel?

[berndweyand]

yes. Etherchannel was an invention from Cisco, other company uses other terms as trunk, lacp etc. - but its all teaming-related

[nem1s1s]

Is there a specified impact to when iSCSI port binding is used with the Route Based on IP hash LB policy? The client currently has this configuration and I'm trying to persuade them it's not correct.

Both iSCSI vmk's in the same subnet as is the SAN.

[petergsk]

Customer has useless configuration. Until explicit port binding is done, vSwitch determines by default which vmnic uplink the ISCSI traffic will take via related vmkernel portgroup.