I am a huge fan of the one click functionality in PRISM and things are getting even better as Lifecycle Manager progresses. One of the options you have with one click is to upgrade your hypervisor and I tend to use this instead of VMware's Update Manager. Just a few days ago I was updating another cluster and to my surprise it failed after upgrading first node successfully.
After a bit of investigation it turned out the UVM could not migrate and this was all due to a misconfigured VMotion interface. So how do you resume the process after fixing said VMotion issue? Pretty simple actually. Log into CVM and issue
allssh 'genesis restart' command.
Log out of PRISM and back in again and the process will happily continue
No comments:
Post a Comment