CUCM LDAP integration

[mohsen a eleilimy]

I am facing 2 issues with CUCM 14 which i don't understand,

1-the application users (cisco unified CM Administration) are not synchronized across the cluster. user name and password used to access the publisher are not accepted when accessing the subscribers "Log on failed - Invalid User ID or Password". the same behavior happens on the self care portal i can log in to the publisher but not subscribers .

2-jabber log in does not work if we used LDAP for authentication, if the user are imported from LDAP jabber will give username or password is incorrect with discovery Failure: FAILED_UCM90_AUTHENTICATION. the same credentials will work on self care portal (publisher only). if i Convert LDAP Synchronized User to Local User and changed the password jabber will sign in and self care portal will still works on publisher only.

I don't know if the 2 issues are related . i checked the dereplication last night and I reset it but this didn't help.

Thank you for your help

[b.winter]

Sounds to me that you have a database replication issue.
I would advise you to go through the following steps, one after the other. Only proceed to the next step, if the current steps didn't resolve the issue:
https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200396-Steps-to-Troubleshoot-Database-Replicati.html#anc17

[mohsen a eleilimy]

I thought the same and i did all the steps mentioned in database replication issues guide but the problem still exists.

[Maren Mahoney]

When you did your utils dbreplication status command, and then ran the utils dbreplication runtimestate later it showed that replication was good an all tables were synchronized?

The only reason I can think of for the sort of symptoms you are describing is database replication issues. You may need TAC assistance.

Maren

[Nithin Eluvathingal]

As other members mentioned it looks like a DB issue. Can you share the output for the below.

Run utils dbreplication status wait few mins and run utils dbreplication runtimestate. 

Show network Cluster.

[mohsen a eleilimy]

admin:utils dbreplication status

Replication status check is now running in background.
Use command 'utils dbreplication runtimestate' to check its progress

The final output will be in file cm/trace/dbl/sdi/ReplicationStatus.2023_11_02_10_49_49.out

Please use "file view activelog cm/trace/dbl/sdi/ReplicationStatus.2023_11_02_10_49_49.out " command to see the output
admin:ut
admin:utils db
admin:utils dbreplication run
admin:utils dbreplication runtimestate

Server Time: Thu Nov 2 10:58:23 EDT 2023

Cluster Replication State: Replication status command started at: 2023-11-02-10-49
Replication status command ENDED. Checked 754 tables out of 754
Last Completed Table: elinmappingdynamic
No Errors or Mismatches found.

Use 'file view activelog cm/trace/dbl/sdi/ReplicationStatus.2023_11_02_10_49_49.out' to see the details

DB Version: ccm14_0_1_13900_155

Repltimeout set to: 300s
PROCESS option set to: 1

Cluster Detailed View from Publisher-FQDN (4 Servers):

PING DB/RPC/ REPL. Replication REPLICATION SETUP
SERVER-NAME IP ADDRESS (msec) DbMon? QUEUE Group ID (RTMT) & Details
----------- ---------- ------ ------- ----- ----------- ------------------
XXXX-R101-XXXX Publisher IP 0.013 Y/Y/Y 0 (g_2) (2) Setup Completed
XXXX-R102-XXXX Subscriber_2-IP N/A Y/Y/Y 0 (g_11) (2) Setup Completed
XXXX-R101-XXXX Subscriber_1-IP N/A Y/Y/Y 0 (g_7) (2) Setup Completed
XXXX-R102-XXXX Subscriber_3-IP N/A Y/Y/Y 0 (g_13) (2) Setup Completed

admin:sh
admin:show network clust
admin:show network cluster
IM&P_1-IP XXXX-R101-XXXX.XXXX.XXX XXXX-R101-XXXX Subscriber cups DBPub authenticated using TCP since Wed Nov 1 11:20:34 2023
Subscriber_2-IP XXXX-R102-XXXX.XXXX.XXX XXXX-R102-XXXX Subscriber callmanager DBSub authenticated using TCP since Wed Nov 1 11:17:37 2023
IM&P_2-IP XXXX-R102-XXXX.XXXX.XXX XXXX-R102-XXXX Subscriber cups DBSub authenticated using TCP since Wed Nov 1 11:17:18 2023
Subscriber_3-IP XXXX-R102-XXXX.XXXX.XXX XXXX-R102-XXXX Subscriber callmanager DBSub authenticated using TCP since Wed Nov 1 11:18:10 2023
Subscriber_1-IP XXXX-R101-XXXX.XXXX.XXX XXXX-R101-XXXX Subscriber callmanager DBSub authenticated using TCP since Wed Nov 1 11:17:17 2023
Publisher-IP XXXX-R101-XXXX.XXXX.XXX XXXX-R101-XXXX Publisher callmanager DBPub authenticated

Server Table (processnode) Entries
----------------------------------
IM&P_1-IP
Subscriber_2-IP
Publisher-IP
IM&P_2-IP
Subscriber_1-IP
Subscriber_3-IP