01-06-2017 08:54 AM - edited 03-17-2019 09:07 AM
We recently did an upgrade from CUCM ver 8.6.2 to 10.5.2. Everything went smoothly but we did notice after the upgrade that we receive the error message when trying to initiate a reboot/shutdown of our servers via CLI (screenshot attached). Error states "Restart operation appears to be stuck, Would you like to force restart?". After that the system restarts/shutdown normally. I have opened a TAC case and they say that after upgrades this will happen if you do not change the VM specs properly prior to the upgrade which we did. The only VM spec adjustments needed for us per the upgrade guide was to change the guest OS version to RHELM 6 64-bit and modify the vNIC adapter to VMXNET 3 which we did before initiating the 10.5.2 upgrade. Seems more cosmetic and does not cause any issues with users but was curious of a root cause/fix. Any ideas? Possible bug? Thanks!!
01-06-2017 11:00 PM
Hi Jason,
Can you check if your Vmtools are running fine on that node after the upgrade to 10.5 ?
Regards,
Hitesh
01-09-2017 08:47 AM
Looks to be fine, i checked as well had our vSphere admin verify. They are outdated but communicating properly. Thanks
01-08-2017 07:36 PM
Actually, you also had to change the size of the 2nd vDisk to 110 GB
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/upgrade/10_0_1/CUCM_BK_U4214F9D_00_upgrade-guide-cucm-100/CUCM_BK_U4214F9D_00_upgrade-guide-cucm-100_chapter_011.html
http://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_system/virtualization/virtualization-cisco-unified-communications-manager.html#v10
I see that every once in a while even in my lab, where most servers where installed on the major base version, and I just update them with SU's. I also see that when I try to shutdown the server, it seems like something times out and then it's forced to complete when you tell it to force the shutdown/restart, but I've never seen any issues in the machines, and it doesn't happen all the time, at least for me.
01-09-2017 07:44 AM
I read that as well in the upgrade guide but it was optional and we had enough space in the common partition to perform the upgrade so we chose not to adjust the vdisk space. Per the notes for a 10.x deployment a vDisk 2 x 80 is a valid config. Thanks!!
http://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/uc_system/virtualization/virtualization-cisco-unified-communications-manager.html#10000userVM
Upgrades from 8.x VMs with 2x80GB vdisks to 9.1 or higher are not required to change the vdisk. 9.1 and higher will support these two-vdisk options: 2x80GB and 1x80GB+1x110GB (where auto-grow COP was used on second vdisk).
01-09-2017 09:50 AM
Hi Jason,
Maybe it's related to this "Open" (Sev.-4) bug;
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