13 Responses

  1. Tyson
    Tyson at |

    So if fan is a synonym for a nut. And I like your blog. Does that make me a Wahl Nut?
    ba dum tsshh.

    Reply
  2. Nimble Storage review : 3 Weeks at Ludicrous Speed | Agnostic Computing

    […] read a lot of thoughtful pieces from VMware colleagues about doing this, but from a Hyper-V perspective, this is supported, and from a Nimble […]

  3. CL
    CL at |

    Thanks for writing this article, this helps clarify a lot of questions that I had in mind.
    Just want to clarify one more thing, based on the above article and traffic flow diagram, are we saying that even if we set the uplinks in the PortGroup under DvSwitch (with LACP) to Active/Unused, there is no guarantee that LACP will honor that settings? i.e., traffic may still flow to the ‘Unused Uplink’ that is logically bound to a physical nic?

    Reply
  4. 5 Crazy-Good Network Admin Blogs You Should Read

    […] Avoid LACP With iSCSI Port Binding or Multi-NIC vMotion […]

  5. Eugene
    Eugene at |

    Chris, thank you for the great article, I could tell you still love the traffic flow diagrams and visualization 🙂
    – The port binding is to be used solely when ESXi iSCSI adapters (software one, for example) and storage target are residing within the same subnet; with multiple subnets involved, the port binding is not recommended/supported. Reference: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2038869
    Have you had a chance to test a setup with multiple subnets involved? I was wondering if that’s a valid alternative to non-LACP setup

    – Is there a good reason to still have multipath configured this way, instead of having one iSCSI VMkernel (if we were to use a single subnet on ESXi and Target storage). In this case there’s no routing table to be addressed through interfaces binding for Software adapter, where the path is still going to be redundant, just offloaded to the networking layer, instead of being addressed by hypervisor. Any known issues with this scenario?

    vSphere 5.5 or 6.0 are the versions I am messing with

    Reply

Share your point of view!