CUCM - LDAP Synchonization Not Working If One of the LDAP Servers Is Not Reachable
I have two separate Communications Manager clusters running 22.214.171.12400-5. It was brought to my attention that a user was not showing up with the correct extension. When I performed a manual synchronization I could see an error displayed on the screen showing that it failed to connect to LDAP server x.x.x.x.
I have three LDAP servers defined for both and in one cluster the LDAP server that couldn't be reached was the first one in the list. In the second cluster it was the last one in the list. As soon as I removed the LDAP server that the CUCM couldn't communicate with and performed a manual synchronization the update occurred.
Is anyone aware of a bug related to this? LDAP synchronization shouldn't fail if only one of the servers defined isn't reachable.
I checked the bug toolkit but don't see any open bugs related to this and I am currently running the latest version of code that I am aware of.
Configuring Cloud Connected PSTN (CCP) – Easy as 1-2-3!
STEP 1: PREPARE
Before you can configure your CCP in Control Hub, you must procure PSTN services from an authorized Webex Calling CCP Partn...
To participate in this event, please use the button to ask your questions
This topic is a chance to discuss more about how to read Cisco Unified Communications trace files. In this session, Cisco D...