cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
216
Views
0
Helpful
6
Replies

Adding a Subscriber

dtom
Level 1
Level 1

We are currently running CallManager version 7.0.2 with one publisher and two subscribers.  Trying to add another subscriber.  The server and software has been installed, we can see it in CallManager System --> Server and System --> Cisco Unified CM.but have not yet added the new server to any Cisco Unified CM Group.  When we look at the Database Summary the replication status all nodes show a status of 2 except for the new server which shows a status of 4.

Do we just need to add the new server to our Cisco Unified CM Group? 

If we add the new server to our Cisco Unified CM Group and there is an issue with the new server, will it "hurt" anything? 

Can we just delete it if there is an issue? 

 

6 Replies 6

Jaime Valencia
Cisco Employee
Cisco Employee

That means replication is not working, you need to fix that in first place. There are plenty of threads on the topic if you need instructions.

Yes, if you add a server that is not pulling the same DB as the PUB you can have issues.

HTH

java

if this helps, please rate

How can I verify that the new server is part the cluster?

Simplest way to check the health of the cluster is to go to the CUCM webportal>CUCM reporting.

and go to Unified CM Data Base status. it gives you the replication status of each member.

DB replication issues are notoriously hard to fix though, you might want to consider raising the issue with TAC if you are not confident enough.

 

Please remember to rate useful posts, by clicking on the stars below.

Hi,

 

from CLI of PUB, u can run the command show network cluster and show tech network hosts.

In addition to what Dear friends have said, please check u have Node License avaialble for new SUB

regds,

aman

Just one simple thing

Please add IP Phone on subscriber then check same phone on Publisher
 

EmilTaghiyev
Level 1
Level 1

Depending of CallManager version can be license issue

Also please try to configure subscriber as IP address not as "name"

Then  try "utils dbreplication reset all" on publisher and restart publisher