Cisco Bug: CSCvv39783 - Redundancy mechanism is not working with Manual Sync
Oct 23, 2020
- Cisco Unified Communications Manager (CallManager)
Known Affected Releases
12.5(1)MN291 12.5(1.10000.22) 12.5(1.11900.146)
Symptom: Manual Sync will not be initiated when one of the ldap servers configured in the ldap agreement goes down. UI page will display the message as "Failed to connect to <non-working ldap server>, check the server IP address or the network connection." but after this sync will not be initiated. Ideally fix should be like below: If one or any of the servers is down and if user does the manual sync then UI can show below message and go for the sync. "Failed to connect to <non-working ldap server>, check the server IP address or the network connection.Sync will be initiated on <working ldap servers>" For example : If LDAP1 and LDAP2 are up and LDAP3 is down after submitting manual sync task UI will display below message before proceeding for the sync. "Failed to connect to ldap://LDAP3:389, check the server IP address or the network connection.Sync will be initiated on LDAP1 or LDAP2" Conditions: Manual directory sync when one of the ldap servers goes down.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases