Load balancer application profile
LDAP and Active Directory
Spread directory lookups across domain controllers with Direct Routing, so replies bypass the load balancer.
What the profile sets up
- Layer
- Layer 4, Direct Routing (DR)
- Ports
- 389 and 636
- Balancing
- Weighted least connections
- Persistence
- Source IP, 5 minutes
- Health check
- TCP connect on 389
Why it helps
- Direct Routing needs each directory server to accept traffic for the virtual IP (the usual loopback and ARP change for DR).
Choose LDAP and Active Directory in Guided Setup on Hawkfend Load Balancer. All values can be changed after the profile is applied.
Product names are trademarks of their owners and are used only to describe compatibility. No certification or partnership is implied.
Try Hawkfend for 30 days
Request a trial licence, install on a Linux server or virtual machine you already have, and decide with your own traffic.