Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Hostname Change in Cluster caused DB Replicates created = 0

Hi,

I am running CCM 8.5.1 and its a 2 node cluster installed in vmware machine.

Before changes to hostname, the DB replicate created is 530 and State is 2 for both PUB and SUB.

After changes to hostname in SUB, the DB replicate created for SUB is 0 PUB is 530 and State is 2 for both PUB and SUB.

What should I do to make the replicates created = 530 in SUB?

cheers,

TA

1 ACCEPTED SOLUTION

Accepted Solutions
Hall of Fame Super Red

Hostname Change in Cluster caused DB Replicates created = 0

Hi TA,

If everything looks OK on the 8.5 cluster as far as replication goes

then I do think your plan to move forward to 8.6(2a) and then do the

Hostname and IP change later sounds like a reasonable plan.

Cheers!

Rob

8 REPLIES
Hall of Fame Super Red

Hostname Change in Cluster caused DB Replicates created = 0

Hi TA,

Looks like this bug;

CSCtr33079 - CUCM 8.5 Change hostname breaks database replication (PMR 08324,49R,000)

Description

Symptom:

After changing hostname on a node running CUCM 8.5, datareplication breaks

Conditions:

CUCM 8.5, following the documented instruction for how to change hostname :

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/install/8_5_1/ipchange/ipchg851.html#wp42513

After the reboot and reset all the database replication is broken, cdr list serv is empty on both pub and sub.

Workaround:

To recover from this do a dbreplication dropadmindb on sub and pub and a reset all on pub.

Details

1st Found-in:                          (1)

8.5(1)

Status:

Fixed

Last Modified:

Oct 12,2011

Fixed-in:                          (3)

8.6(2.10000.30), 8.6(1.98000.46), 8.6(1.98000.107)

Product:

Cisco Unified Communications Manager (CallManager)

Platform:

Dependent

Severity:

2 - severe

Customer Reported:                          (4)

Cheers!

Rob

Please remember to tag your threads and help support "Teachers without Borders"

https://supportforums.cisco.com/community/netpro/idea-center/communityhelpingcommunity

New Member

Hostname Change in Cluster caused DB Replicates created = 0

Oh i c. Thanks Rob.

I believe it should be fixed in CCM 8.6.2.20000-2 ?

Hall of Fame Super Red

Hostname Change in Cluster caused DB Replicates created = 0

Hi TA,

Yes, this appears to be fixed in 8.6.2.20000-2

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/8_6_2/cucm-rel_notes-862a.html#wp2058233

But you would need to fix the problem using the listed work-around

before proceeding with any upgrade.

Cheers!

Rob

New Member

Hostname Change in Cluster caused DB Replicates created = 0

Thanks rob.

If the fix is in 8.6.2, y do we need to perform the workaround before the upgrade? Any reason for that?

Cheers,A

TA

Hall of Fame Super Red

Hostname Change in Cluster caused DB Replicates created = 0

Hi TA,

Well...I don't think it's ever a good idea to upgrade a cluster

that isn't working properly if you can avoid it. Replication issues

are probably at the top of the list of things that can really bite

you moving forward.

Don't forget that an upgrade to 8.6 requires the whole "new" refresh

process with a higher downtime etc. so you may not want to rush

down that road

The workaround is really your best bet here. The steps are highlighted in this good doc for reference;

https://supportforums.cisco.com/docs/DOC-13672#Publisher_syscdrdefine

utils dbreplication dropadmindbRun on a publisher or subscriber, this command is used to drop the syscdr database. This clears out configuration information from the syscdr database which forces the replicator to reread the configuration files. Later examples talk about identifying a corrupt syscdr database.
utils dbreplication clusterresetAlways run from the publisher node, used to reset replication connections and do a broadcast of all tables. Error checking is ignored. Following this command 'utils dbreplication reset all' should be run in order to get correct status information. Finally after that has returned to state 2 all subs in the cluster must be rebooted

Cheers!

Rob

Please remember to tag your threads and help support "Teachers without Borders"

https://supportforums.cisco.com/community/netpro/idea-center/communityhelpingcommunity

New Member

Hostname Change in Cluster caused DB Replicates created = 0

Yea mate. Totally agree. I'm just thinking if 8.5.1 cluster is fully working with db state =2 for all nodes, I will be able to upgrade it to 8.6.2 first and perform the hostname change and ip change after the upgrade right? Should the db state still not 2, I will perform the dropadmindb followed by cluster reset and reset all. Does it sound logical to you?

Hall of Fame Super Red

Hostname Change in Cluster caused DB Replicates created = 0

Hi TA,

If everything looks OK on the 8.5 cluster as far as replication goes

then I do think your plan to move forward to 8.6(2a) and then do the

Hostname and IP change later sounds like a reasonable plan.

Cheers!

Rob

New Member

Hostname Change in Cluster caused DB Replicates created = 0

Cool rob. Thanks for the prompt reply. I will proceed with that. Thanks.

560
Views
0
Helpful
8
Replies