Which is required for configuring iSCSI Software Adapter network port binding?

IP Hash load balancing requires multiple active uplinks per vSwitch port group, which violates the single active adapter requirement for iSCSI port binding and is explicitly unsupported in this configuration.

Route based on Source Virtual Port ID is a standard vSwitch load balancing policy for general VM traffic and does not satisfy the iSCSI port binding requirement of one active adapter per VMkernel.

Route based on Source MAC Hash is another general vSwitch policy that allows multiple active adapters and therefore does not meet the iSCSI port binding constraint of a single active uplink per VMkernel.

Port binding enforces a one-to-one relationship between a VMkernel adapter and a single active uplink, ensuring iSCSI traffic always exits through a predictable physical NIC. This is required because the iSCSI initiator relies on stable, per-path sessions, and having multiple active uplinks on a VMkernel would break that determinism.