Last week when the Storage vMotion / HA problem went public I asked both William Lam and Alan Renouf if they could write a script to detect the problem. I want to thank both of them for their quick response and turnaround, they cranked the script out in literally hours. The scripts were validated multiple times in a VDS environment and worked flawless. Note that these scripts can detect the problem in an environment using a regular Distributed vSwitch and a Nexus 1000v, the script can only mitigate the problem though in a Distributed vSwitch environment. Here are the links to the scripts:
- Perl: Identifying & Fixing Virtual Machines Affected By SvMotion / VDS Issue (William Lam)
- PowerCLI – Identifying and fixing VMs Affected By SvMotion / VDS Issue (Alan Renouf)
Once again thanks guys!
Thanks Duncan. I tested this out at a customer’s site and there were about 6 VMs which were found and repaired. Great effort by William and Alan to get this out so quickly. Thanks to you as well for such a quick identification and resolution :).
This great post saved my day! I’ve test this script and the fix works without a pinglost. I hope, this problem will be fixed soon from VMware.
Great stuff!!! Thanks to Duncan, Alan and William for going above and beyond as this found a few flaws in one of the environments I was recently working on. Time to test a few others. 🙂
Vmware KB 2013639 about this issue no longer available.
The last esxi update from 03/05 fix the issue ?
No it did not fix the issue!
Would it be expected that this issue would affect a cluster of ESXi4.1 hosts being managed by vCenter 5.0? It seems if it is vCenter and FDM related then it probably does (and on which case the KB article may need to be updated ?)