I work in an industrial warehouse network environment and these errors seem to pickup during busier production times of the season like the holidays (Now). We get up to 5 alerts generated per day and then some days none at all.
Error: "Attention! The following critical system event occurred: Failed to connect to LDAP Identity Source"
I've done the ping test troubleshooting via the OC RSA console to the LDAP servers and I never see an issue. The failures seem to be so random and spread apart. Is there a polling settings or timers we can adjust to resolve this? There is hardly any slowdown on the network connections as they are mainly 1G and 10G backbone infrastructure of which these probes shouldn't even be scratching the surface. Also looking at our network connections they are always below 50% utilization. I'll also mention that the RSA server and LDAP are in separate domains if that makes a difference. We have other devices in those same domains that don't have this issue.
Hi Gervasee,
I am sorry I don't have any helpful response. These events are logged by the server when the LDAP connection encounters an error during an attempt to connect. This can occur during authentication or as a part of the LDAP "clean-up" job (to look for deleted or moved users).
If you have other monitors in place, I would look for network events that correlate with the times at which the failures occurred. While it may be possible to adjust some internal timeout parameters, I doubt that would address the issue. I believe these default to 30 seconds for the connection timeout (i.e., the AM server waits 30 seconds for the remote LDAP server to accept the connection).
I assume there's no complex network infrastructure between the AM and LDAP servers? LDAP load balancers? Anything fancy?