Another interesting note. I had seen this recently with another customer. The situation was that he needed to un-prepare and prepare for VXLAN to change the VLAN in the config.
What happened was, on the first preparation, he setup the new vmk nic and changed the Default Gateway. The way the virtual adapters (vmk#) works, is that the default gateway should be the one of the primary service console you use. So don't update it each time you create a vmk nic ... or else it'll change ALL of the vmk nic default gateways.
After we reverted the vmk default gateway to the correct one for the primary service console, then everything worked as expected when using 'Resolve Issues'. The really odd thing ... 2 of 5 hosts prepared successfully ... but all had the wrong default gateway for the vmk nics.
I'm wondering if anyone else might have done the same thing.