Brocade Virtual ADX Server Load Balancing Guide (Supporting ADX v03.1.00) - Manual (Page 188)

172 Brocade Virtual ADX Server Load Balancing Guide
53-1003247-01
Layer 7 health checks
4
Authenticated bonding
If a username and password are configured, the Brocade Virtual ADX sends an authenticated bind
request to the LDAP server that includes three configurable parameters: the version number, the
name of the directory object that the client wants to bind to, and information used to authenticate
the Distinguished Name (DN).
Brocade Virtual ADX then queries the LDAP directory using a user-configured search.
• If the server sends a bind reply with a result code of any status (no error), the Brocade Virtual
ADX resets the connection and marks the port ACTIVE.
• If the result of the query is any error value, the Brocade Virtual ADX marks the server port
DOWN and removes the server from the load-balancing rotation for LDAP service.
Performed:
• Immediately following a successful Layer 4 TCP health check
• At regular intervals, if keepalive is enabled for the port
Brocade Virtual ADX also supports server response threshold health checks for LDAP servers. To
learn more see
“Server response threshold health check” on page 164.
MMS
The Brocade Virtual ADX sends an intentionally invalid request to the server:
• If the server replies with a packet containing the value "MMS", the Brocade Virtual ADX marks
the port ACTIVE.
• If the server does not reply with a packet containing the value "MMS", the Brocade Virtual ADX
retries the health check up to the number of times configured (the default is two retries). If the
server still does not respond, the Brocade Virtual ADX marks the server port FAILED and
removes the server from the load-balancing rotation for MMS service.
NOTE
You can view the Brocade Virtual ADX’s invalid request in the MMS server log. The log entry has error
code 400.
Performed:
• Immediately following a successful Layer 4 TCP health check
• At regular intervals, if keepalive is enabled for the port