The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Considerations for using software iSCSI port binding in ESX/ESXi (2038869)
Port BindingPort binding is used in iSCSI when multiple VMkernel ports for iSCSI reside in the same broadcast domain and IP subnet to allow multiple paths to an iSCSI array that broadcasts a single IP address. When using port binding, you must remember that:
- Array Target iSCSI ports must reside in the same broadcast domain and IP subnet as the VMkernel port.
- All VMkernel ports used for iSCSI connectivity must reside in the same broadcast domain and IP subnet.
- All VMkernel ports used for iSCSI connectivity must reside in the same vSwitch.
- Currently, port binding does not support network routing.
When not to use port bindingPort binding should not be used when:
In this sample scenario, there are multiple VMkernel ports in on different IP subnets and broadcast domains and the target ports also reside in a different IP subnet and broadcast domain. In this case, you should not use port binding.If you configure port binding in this configuration, you may experience these issues:
- Rescan times take longer than usual.
- Incorrect number of paths are seen per device.
- Unable to see any storage from the storage device.
When to use port binding
In this scenario, there are multiple VMkernel ports, all residing in the same IP subnet and broadcast domain. In this case, you must use port binding.If you do not configure port binding in this configuration, you may experience these symptoms:
- Unable to see storage presented to the ESXi/ESX host.
- Paths to the storage report as Dead.
- Loss of path redundancy messages in vCenter Server.
- Cannot reach iSCSI target after enabling iSCSI port binding on ESX/ESXi 4.x and ESXi 5.0
- Multi-homing on ESX/ESXi
- When using multiple VMkernel ports with port binding to access two or more storage arrays on different broadcast domains, rescan takes a long time
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.