Rebooting CUCM 7.1 cluster

Unanswered Question
Mar 6th, 2012

We have Call Manager  ( Publisher and two Subscribers

Just wanted to know if there is any protocol in rebooting the entire cluster:

Is there any order that needs to be followed?

It will be after normal business hours, so no one will be affected by the reboot.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (4 ratings)
Chris Deren Tue, 03/06/2012 - 13:49

Nope, simply issue Utilis system restart from CLI one by one.

The real question though is why do you need to reboot the cluster?

Sent from Cisco Technical Support iPhone App

wilson_1234_2 Tue, 03/06/2012 - 13:58

After looking into this, reboot may not be needed.

We are experiencing what looks like a memory leak.

We have a Pub and two subs and the Virtual Memory usage is 48%, 60% and 72%, it looks like Tomcat.

Probably a bug, but I should be able to just restart Tomcat correct?

Chris Deren Tue, 03/06/2012 - 17:12

High usage of virtual memory is expected on Linux, so this should be nothing to worry about it.



Vipul Jindal Tue, 03/06/2012 - 14:01

you have to restart the pub first, make sure it comes back up and than you can reboot any of the subs.

alwazs a best practice is to make sure we reboot second server once first comes back up!!


Vipul Jindal

David Hailey Tue, 03/06/2012 - 20:28

If you think that Tomcat may be the culprit then yes, you could first restart the Tomcat service via CLI by issuing "utils service restart Cisco Tomcat".  Ultimately if you do reboot the cluster then the traditional sequence is to reboot the Publisher first.  Once the Pub is back online and healthy, you can begin to reboot Subscribers.


Please rate helpful posts!


This Discussion