cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
536
Views
0
Helpful
1
Replies

Call Manager Publisher strange behaviour

bobby.jacob
Level 1
Level 1

Dears,

I had done a CUCM cluster upgrade from 6.1.4 to 8.6.2a  two weeks back.

The new system was in production for 1 week, last week client had shutdown the system for their power maintanence.

After powered on the system back (done in a sequence-Pub 1st and then the Sub), there are phones which registered with Pub and Sub.

The Phones which are registered with PUB cannot recieve any call from phones which are registered with SUB.

Even i can see on PUB administration page- devices shows unregistered even the devices are registered.

i verified the DB Replication which shows 2- good.

As a temp solution now, I had moved all the devices to one CUCM group so that all the phones are registred to CUCM SUB and they are able to make calls now.

The system is in production, so i couldnt make a restart for the PUB. Anyone came across similar issues?

Thanks

Bobby

1 Reply 1

nikshah
Cisco Employee
Cisco Employee

I think you dbreplication is hosed,

you might want to run the following steps

utils network host (ip add, hostname of the sub ) on the pub

utils network host (ip add, hostname of the pub) on the sub

utils diagnose test on both the nodes.

utils network connectivity on sub

you can run this during production

If the above is good,  try the following

utils dbreplication stop on sub (wait for it to complete)

utils dbreplication stop on pub (wait for it to complete)

utils dbreplication dropadmindb on pub (wait for it to complete)

utils dbreplication dropadmindb on sub (wait for it to complete)

utils dbreplication reset all on the pub.

hope this helps

Niket