F5 is upgrading its customer support chat feature on My.F5.com. Chat support will be unavailable from 6am-10am PST on 1/20/26. Refer to K000159584 for details.

Forum Discussion

ShawnC's avatar
ShawnC
Icon for Altostratus rankAltostratus
Oct 27, 2025

APM VPN LDAP POOL can't contact ldap server.

Hi, I have a question regarding APM VPN and LDAP authentication. When I configure the LDAP server using the direct LDAP Server IP, the authentication works fine. However, when I use a Pool with th...
APM
ldap
vpn
ShawnC's avatar
ShawnC
Icon for Altostratus rankAltostratus
Oct 29, 2025

I have confirmed that all POOL members are greenlit.

Shyy's avatar
Shyy
Icon for Cirrus rankCirrus
Oct 29, 2025

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's avatar
    ShawnC
    Icon for Altostratus rankAltostratus
    Nov 06, 2025

    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.