19 Responses

  1. Hari
    Hari at |

    You can prevent this by having vmotion vmkernel in the clusters in 2 different subnets.
    your take.

    Reply
  2. NSX Link-O-Rama | vcdx133.com
    NSX Link-O-Rama | vcdx133.com at |

    […] A Caveat to Multi-Cluster VDS Design with NSX by Chris Wahl […]

  3. Alessandro
    Alessandro at |

    Thank you

    Reply
  4. Zsolt Pamuki
    Zsolt Pamuki at |

    Thank you for this post.

    Reply
  5. Mike Medrano
    Mike Medrano at |

    Nice blog. Thanks for sharing.

    Reply
  6. ScoZell
    ScoZell at |

    Nice article! Yes, there is no better way to learn technology then to break them first 🙂

    Reply
  7. Amit
    Amit at |

    Good Post

    Reply
  8. Andres Rojas
    Andres Rojas at |

    thx for the info/warning
    great stuff that take into consideration for the NSX deployment

    Reply
  9. Geoff Neish
    Geoff Neish at |

    Hopefully they add a feature that checks if the NSX bits are on the destination before allowing a migration.

    Reply
  10. Yuri Mendoza
    Yuri Mendoza at |

    This is a great tip so we can take into consideration the design of the vDS and NSX.

    Reply
  11. Ravi Venkatasubbaiah
    Ravi Venkatasubbaiah at |

    Tips and traps most helpful!!

    Reply
  12. vervoortjurgen
    vervoortjurgen at |

    wont this be solved in NSX 6 and vsphere 6? with the new nsx features?

    Reply
  13. Lalit
    Lalit at |

    Thanks for good information

    Reply
  14. Mohammed Sadiq
    Mohammed Sadiq at |

    Thanlks for the info .

    Reply
  15. Nipun
    Nipun at |

    Very helpful indeed !!

    Reply
  16. andynashers
    andynashers at |

    Nice blog on how vmotion can cause issues cross cluster when nsx is also installed

    Reply
  17. Rajesh Gundeti
    Rajesh Gundeti at |

    Good info.

    Reply
  18. dario
    dario at |

    great works!

    Reply

Share your point of view!