03-26-2012 12:43 PM - edited 03-19-2019 04:39 AM
Hello all,
As we all know in the IT world, everything needs to be rebooted at times and CUCM is no exception. What is a good guideline to rebooting CUCM? Does Cisco have a specific guideline? I was trying to look through the SRND's for 7.x and 8.x and did not find any recommendations for maintenance. Any reference to a document would be greatly appreciated too!
Thanks,
Justin
06-12-2017 12:38 AM
Basic troubleshooting should be done first like probing the symptoms, patterns to isolate it to a certain extent. Then only you should get into restarting services or servers.
Manish
06-12-2017 05:57 AM
To reboot the cluster, you reboot the pub first. Use RTMT to verify it is completely back up. Then you reboot any TFTP servers (but if you only have 1 pub and 2 subs, I assume this does not apply to you). Then you reboot the subs. With just 2 subs, I would reboot them one at a time and verify all services are back up before doing the other. Also, check how many phones are registered at the beginning and make sure the same number a registered at the end.
09-24-2019 09:27 AM
To reboot the cluster you have to check en each Pub:
1-NTP Status( CLI :Utils ntp status, it should be Synchronized.
2-Db replication (CLI: utils dbreplication runtimestate, it should be without issue.
3-Backup from CUCM, CUC Backup for each server is separate, UCCX,IM&P.
4-Using RTMT check how many devices are registered before reboot and compare after rebooted.
Same thing , Cisco Recommended every 6 moths rebooted those Servers.
Thanks.
06-12-2017 06:27 AM
I recommend a quarterly reboot cycle to my customers.
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