09-27-2018 02:14 PM - edited 03-18-2019 12:31 PM
I am continuously told by Cisco UC engineers you cannot live vMotion CUCM and CUC, yet the Cisco Virtualization Wiki says otherwise. Anyone care to elaborate?
If the UC app is listed as "Supported with Caveats", which CUCM and CUC are, then support is as described below:
09-27-2018 05:41 PM
I can say I have seen someone vmotion CUCM and CUC from host to host in the middle of the day and caused a major outage. This was years ago and I am pretty sure it was across a wan link. I would not recommend doing this. Instead my recommendation would be if you have to do it do it doing a maintenance window or do it as a cold migration. I typically take the cold migration route. Last time I had to move vms from one host to another I did a cold migration vm by vm. This works well if you have true redundancy you barely notice the phone switch from one CUCM to the other.
What is your end goal or what your trying to do is just worried about redundancy if you lose one host... this is built into CUCM/ CUC clustering and design.
09-28-2018 05:01 AM
My goal is to try to understand why Cisco.com says its OK to do in a maintenance type scenario, yet their field engineers say it cannot be done.
09-28-2018 05:18 AM
Safest and supported method for most UC apps is to shutdown the application and perform vMotion while it's shut down. I have done it hundreds of times with many apps without issues. Vmotioning running VM is not supported by Cisco, but I have seen that go without an issue too, though proceed with caution.
09-28-2018 06:27 AM
09-28-2018 06:30 AM
Greg,
Why would you not recommend it if it's supported?
09-28-2018 07:37 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide