locked
event id 21502 processor mismatch fail over cluster RRS feed

  • Question

  • Situation was a customer took direct lightning hit. Both identical VMHOSTs lost their motherboard.  Replaced  boards brought back the fail-over cluster, everything looked fine except we could not move machines from host to host.  Error 1069 and 21502.  Trouble shot everything possible such as quorum disk, iscsi availability, lowered cpu cores. Cluster validation worked 100%. Error IDs would fluctuate every time we tried to move.  Turns out on one of the boards when I upgraded BIOS it turned off hyper-v setting on the motherboard. After this feature was enabled VMs failed back and forth without issue. DOH! 

    Just thought I would post this to save somebody some time troubleshooting. 


    • Edited by tnaratil Friday, August 5, 2016 7:48 PM
    Friday, August 5, 2016 7:47 PM