For example, if Microsoft Internet Information Server (IIS) does not work on a cluster node and WLBS or NLB is still running on the node, port 80 or Web packets continue to be routed to the WLBS or NLB node. You may receive program error messages on the host because the program is not running there, but the service does not failover to the other hosts because of WLBS and NLB design limitations.
When a program does not work, the cause is usually more complex than the service not responding on a port. WLBS and NLB rely on external monitoring tools for decision-making processes and remote control if a host needs to be removed from the cluster.
Some independent monitoring tools can control cluster membership based on the availability of content. You can use these tools to monitor programs and services and send a command to stop WLBS or NLB on the node with the unsuccessful program or service. The program or service is removed from the WLBS or NLB cluster and does not receive any further traffic until it rejoins the cluster.
Examples of monitoring tools
- Httpmon.exe: You can use Httpmon.exe on a Web server to monitor the status of the Web service. Httpmon.exe is included in the Microsoft Internet Information Server Resource Kit, or you can download it from the following Microsoft Web site:
- Exception Monitor: For additional information about this tool, including its download location, please contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: