codyhostermanI can see you have written several articles about ISCSI and MPIO

Great, thank you - i will looks into that

```Port Binding, Multi-Subnet Host I am not really going to spend any time on this, because it is exactly what you expect. Each bound port has paths to the target it can reach``` Is this scenario supported and does it make sense to use it? The KB from VMware above states that one should not use portbinding on a multihomed host (L2 to all targets on both arrays in the AC)

Generally I always recommend port binding because without it it is harder to track what NICs are being used or not used for iSCSI. Without it, the routing tables will be used which isnt a bad thing but just makes tracking/management trickier. For multiple subnets there used to be a benefit there for a path limit perspective but now that VMware supports 32 paths keeping the count down is less important (not all paths are available down all iSCSI targets with multiple subnets). There can be some benefit from availability to multiple subnets if certain ones are owned by specific switches. We dont really have a specific recommendation on subnets, but we do encourage port binding when possible

I have to agree with Cody here. After working with the vSphere TCP stack while at VMware, I've seen some interesting behaviors, often unexpected. More control can result in fewer surprises.