How Does LDAP Failover Work In Convergence?
(Doc ID 2256279.1)
Last updated on JULY 25, 2018
Applies to:Oracle Communications Convergence - Version 3.0.1 and later
Information in this document applies to any platform.
The Convergence Administrator's Guide details how to configure LDAP failover.
How does this mechanism actually work?
How does Convergence declare an LDAP server in ugldap.host "unavailable/down"? (TCP connect failure, failure to bind, other?)
Is there a "fail back" mechanism?
Is the mechanism round robin if both configured LDAP servers are available?
If #1 LDAP is down is #1 constantly checked for availability before failing to #2 (ie introducing some latency for every bind attempt?)
If #2 LDAP is down, and #1 is up, is #2 checked to see if it becomes available again?
Are there any differences in this fail-over mechanism between Convergence 2.x and 3.x?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document