01-18-2025 06:12 AM
Hello,
we have a CUCM IM&P 15SU2 cluster (2 nodes) and we have issues with the IMDB replication (which are causing issues with the Jabber logins).
Based on the document at the link
we have followed the steps to resolve the IMDB replication issues but, after the procedure, we still have the following:
----------
admin:utils imdb_replication status
Running IMDB DSN (ttsoft, ttlogin, ttreg) replication checks on all nodes in cluster ...
NOTE: For diagnostic test to run, ports 6603, 6604 & 6605 must be open on any firewalls between IM&P Servers
Sub Cluster Name / Id :: DefaultCUPSubcluster / 1000
Checking connectivity & removing old data prior to running diagnostic
Cisco Presence Datastore Replication
<CUCM IM&P Subscriber> -> <CUCM IM&P Publisher> Failed
<CUCM IM&P Publisher> -> <CUCM IM&P Subscriber> Failed
Gathering Debug Info for failed DSN ... please wait
Traceback (most recent call last):
File "/usr/local/imdb/bin/imdb.py", line 539, in test_imdb
test_imdb_ttsoft_replication(nodename1,nodename2,subclustername)
File "/usr/local/imdb/bin/imdb.py", line 253, in test_imdb_ttsoft_replication
gather_failed_replication_info(node1, node2, TTSOFT_PORT)
File "/usr/local/imdb/bin/imdb.py", line 196, in gather_failed_replication_info
a.write_to_file("%s\n" % (result[0].decode('utf-8')))
AttributeError: 'str' object has no attribute 'decode'
'str' object has no attribute 'decode'
admin:
----------
N.B.: we have already checked that the ports 6603, 6604, and 6605 are open.
What's wrong?
TIA and regards.
01-19-2025 05:58 AM
01-19-2025 11:53 PM
Hello @Nithin Eluvathingal,
thanks for the link, but we already had checked the DB replication, which is fine; where we have issues is only with the IMDB (In-memory Database) replication, which is something else compared to the "classic" DB replication.
Regards.
01-20-2025 02:31 AM
As far as I know, both IMP and CUCM database troubleshooting remain the same. That’s why I sent you the link to fix the database.
What do the following commands say about the IMP nodes?
01-20-2025 03:47 AM
Hello @Nithin Eluvathingal,
at last, we had to solve the issue with the TAC, due to the following bug:
https://bst.cisco.com/bugsearch/bug/CSCwn54933
Regards.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide