9 Responses

  1. Mike Brown
    Mike Brown at |

    Excellent point, Chris. Thanks for sharing. I hadn’t thought of this, but will make it a point to address this in my future UCS deployments.

    All the best,

    MIke

    http://VirtuallyMikeBrown.com
    https://twitter.com/VirtuallyMikeB
    http://LinkedIn.com/in/michaelbbrown

    Reply
  2. Eric Shanks
    Eric Shanks at |

    Nice write up Chris. Love that converged infrastructure.

    Reply
  3. Amy Manley
    Amy Manley at |

    I always pondered this and now I know. Thanks!

    Reply
  4. Drew Henning
    Drew Henning at |

    Nice write-up. UCS also allows for a great multi-nic vMotion experience. I’ve setup a vnic’s for vMotion on both the A fabric and the B fabric. Then put both the A side and B side on their own vlan/subnet. It is screaming fast.

    Here’s another blogger who detailed the setup – http://www.bussink.ch/?p=262

    Reply
  5. Think Outside the Box: HA in a Blade Environment | vSchu

    […] On a final note, Chris Wahl just posted a great blog article on how to keep vMotion within the Chassis or Chassis Uplinks (If your chassis’ support daisy chaining). Check out his post HERE. […]

  6. How Link Aggregation Affects vSphere Teaming Policies with Converged Infrastructure via @ChrisWahl | Wahl Network

    […] what makes the most sense based on your network topology – you may even want to pin traffic (here’s a vMotion example). The takeaway here is that you do not need to use IP Hash as the LAG does not touch the virtual […]

Share your point of view!