equence of rebooting / shut down call manager publisher and subscriber

[susim]

Hi,

What is the sequence of rebooting / shut down call manager publisher and subscriber

What is the sequence of powering of  call manager publisher and subscriber

Thanks 

[Terry Cheema]

Restart the publisher, followed with TFTP nodes and then backup Subscriber, followed by the active subscribers in the end.

-Terry

[Amit Sharawat]

Hi Support sbt,

There is no such sequence, however, followings are recommended always to avoid unnecessary issues:

> If you are shutting down the cluster:

     * Shut the Publisher first, then all the servers running call manager service, then TFTP server and then remaining servers.

     * When powering on, Power on the Publisher first, then all the servers running call manager service, then TFTP server and then remaining servers.

> If you are rebooting the cluster:

    * Reboot the publisher first and make sure that it is completely up. Then reboot all the other servers.

    * Make sure you do not delay rebooting the subscriber too much after Publisher has come up to avoid any database replication issue.

>>Whatever is the case above, make sure that you monitor database replication after you have reboot/powered-up the cluster by using command "utils dbreplication runtimestate" on the publisher. All the server should be in state "2" after couple of hour of the reboot/power-up.

~Amit

[Jaime Valencia]

We actually recommend to follow the CTI ID numbers for the order on which you reboot the servers, and not in any random order. Same for shutting down, and bringing back up.

[BradleyWegner-BW]

You can find the CTI ID info doing this:

https://community.cisco.com/t5/ip-telephony-and-phones/what-is-the-cti-id-of-subscriber/td-p/2021922