cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1468
Views
15
Helpful
18
Replies

Sub cannot take over the Pub after it is down

eigrpy
Level 4
Level 4

Hi, it looks like that the Pub and Sub can work well since "show ccm-manager" is normal. But after the Pub is shutdown, all the phones become Not registered. That means the Sub cannot take over it. Anyone can give some comments? Thank you.

2 Accepted Solutions

Accepted Solutions

Brandon Buffin
VIP Alumni
VIP Alumni

Does your CUCM group contain the pub and sub? The group will need both servers configured so the phones will know which server to contact should the primary go down.

Brandon

View solution in original post

Please provide specific answers to the queries posted by people trying to assist you:

Are both Pub and Sub added to the callmanager group applied on the DP of phones and gateways?

Is the callmanager service started on both servers?

Is the database replication status '2' for both the servers ( can be checked via RTMT ) ?

Can you try creating a new callmanager group with only the Sub added to it and see if a phone is able to register with that cm group in the device pool? If yes then the sub is okay, if not then the problem most likely lies on the sub.

Manish

View solution in original post

18 Replies 18

nalonsopresidio
Level 1
Level 1

Bring up the Pub, ssh into it and run via cli "utils dbreplication runtimestate" and post the output here.

If you have SRST enabled on the DP, what is the timer set to? Is the Pub the primary server on the DP or is it the Sub under call manager group?

"Show ccm-manager" is a gateway command to check mgcp registration, but you are referring to phones not registering, so I assume it happens to both phones and MGCP controlled devices?

Thanks for your reply. the output of  "utils dbreplication runtimestate" show Replication is not setup. exiting ... So, where to setup it? 

That's your issue. The sub doesn't have a copy of the database. How long ago was the sub added? Has the cluster security password been changed on the pub?

Try rebooting the pub after hours, give it 3 mins head start, then reboot the sub and check replication after both restart about 5-10 mins later.

I'm going out on a limb here, but the Call Manager service is started on the sub correct?

You are right you found right way to troubleshoot. I often restart the Pub and sub. but the issue lasts for a little long time.

Brandon saying is also right. I did not put two cucm into the group. but after i did it, the issue is still there. 

My suggestion is to exchange the role of pub and sub between the two cucm. Can you tell how to exchange it ? 

You cannot change the roles, if a server was installed as a PUB, it will remain a PUB so long it's up and running, same for a SUB. You only get one chance to choose, and it's upon installation.

HTH

java

if this helps, please rate

Thanks. But the Sub seems not working now.

Please provide specific answers to the queries posted by people trying to assist you:

Are both Pub and Sub added to the callmanager group applied on the DP of phones and gateways?

Is the callmanager service started on both servers?

Is the database replication status '2' for both the servers ( can be checked via RTMT ) ?

Can you try creating a new callmanager group with only the Sub added to it and see if a phone is able to register with that cm group in the device pool? If yes then the sub is okay, if not then the problem most likely lies on the sub.

Manish

Can you try creating a new callmanager group with only the Sub added to it 

Thank you for your reply. I am going to test all of them. now I created a new callmanager group. But I am thinking how to associated the Sub with a phone. Can you give some suggestion?

There is only ONE way to associate a CUCM group to a phone: Device Pool

HTH

java

if this helps, please rate

I associated the sub with device pool containing a phone. and then shut down the Pub. all the phones become down and cannot be up. At this moment, show ccm-manager tells that pub is down and sub is registered. After powering on the Pub, all of phones are up except the phone associated with the Sub. So it seems the Sub cannot work, right ? The sub can be reconfigured ? 


Can you verify replication is running clean now?

It is verified that the Sub cannot work at all. Certainly it cannot replicate. Your posts are good, but I missed yours. Sorry

We found the reason that is Sub cannot work, while Pub is good. So we close the post

Thank you all

You are all welcome to the post:

https://supportforums.cisco.com/discussion/12744976/sub-cannot-work-no-matter-pub-or-alone