Forum Discussion
AltostratusAPM VPN LDAP POOL can't contact ldap server.
CirrusIt shouldn't be any different you're just using a pool instead of directly accessing the ldap.
Only thing I can advise is maybe check that the pool and the member you're using are actually available.
Go to pools search for your ldap pool and make sure it is green and available.
AltostratusI have confirmed that all POOL members are greenlit.
- Shyy
If the pool is available you should run a tcpdump to see where the traffic is coming from,
plus look at ltm logs /var/log/ltm once you get the error, might be more information there.- ShawnC
Using tcpdump, I discovered that when using a pool, port 389 always sends out through other floating IPs.
The problem was that the interface I needed to route to didn't have a floating IP configured, only its own IP. After configuring it, the connection worked.
I'm using two machines in HA mode. I found that using Direct routes sends the MGMT, while using Pool routes it sends the floating IP. I tried directly pointing the router to the VLAN, but without a floating IP, the data wasn't sent out at all.
The conclusion is that a floating IP must be configured. Thank you for your help.
