Web OS 10.0 Application GuideChapter 10: Health Checking n 243212777-A, February 2002Configuring the Switch for WTLS Health Checks1. Select the group with the WAP gateway.2. Use the sndcnt command to enter the content to be sent to the WSP gateway.3. Select a port number other than 9203, if you want to change the port number on whichyour gateway is listening to WTLS traffic.4. Apply and save your configuration.LDAP Health ChecksLightweight Directory Access Protocol (LDAP) health checks enable the switch to determinewhether the LDAP server is alive or not. LDAP versions 2 and 3 are described in RFC 1777and RFC 2251.The LDAP health check process consists of three LDAP messages over one TCP connection: Bind request: The switch first creates a TCP connection to the LDAP server on port 339,which is the default port. After the connection is established, the switch initiates an LDAPprotocol session by sending an anonymous bind request to the server. Bind response: On receiving the bind request, the server sends a bind response to theswitch. If the result code indicates that the server is alive, the switch marks the server asup. Otherwise, the switch marks the server as down even if the switch did this because theserver did not respond within the timeout window. Unbind request: If the server is alive, the switch sends a request to unbind the server.This request does not require a response. It is necessary to send an unbind request as theLDAP server may crash if too many protocol sessions are active.If the server is up, the switch closes the TCP connection after sending the unbind request. If theserver is down, the connection is torn down after the bind response, if one arrives. The connec-tion will also be torn down if it crosses the timeout limit, irrespective of the server’s condition.>> Main# /cfg/slb/group 1 (Select the Real Server Group 1 menu)>> Real server group 1# health wtls>> Main# /cfg/slb/adv/wap>> WAP Health Check Menu # wtlsprt 10203>> WSP Health Check# apply
