C
Chris
I've got two Win2k servers running IIS 5.0 and MS load balancing.
Each server hosts a static web site. Because Load Balancing itself
does not monitor for service failures, my task is to monitor IIS so
that if the web site should go down on one server, that server will be
removed from the cluster. From what I've read, HTTPMon coupled with
wlbs commands is a possible solution for this problem. However, I am
curious how this would work.
Although both the servers have 2 network cards, only one is enabled on
each server. There is no "private" connection between the servers for
heartbeats. Because the server is in Unicast mode, I understand that
they are not exchanging heartbeats. I am prepared to add this
connection, but we do not want to enable Multicast mode.
The currently enabled nic in each system is configured with 2 IP
addresses - 1) unique for the local system and 2) the shared cluster
IP. The web sites are associated with the shared cluster IP (as
opposed to <all unassigned>). If I were to set HTTPMon to monitor the
sites in this configuration, my understanding is that it would not be
able to tell which server it was monitoring.
Can I work around this by enabling the 2nd nic? Would I then also
have to change the IP address for the web site on both servers to <all
unassigned> so that HTTPMon can monitor each instance through the 2nd
adapter? Instead of a crossover between the two, I guess I'd have to
plug the 2nd nics into the switch so they can be monitored by a 3rd
computer (outside the cluster) running HTTPMon.
Thanks for any advice.
Each server hosts a static web site. Because Load Balancing itself
does not monitor for service failures, my task is to monitor IIS so
that if the web site should go down on one server, that server will be
removed from the cluster. From what I've read, HTTPMon coupled with
wlbs commands is a possible solution for this problem. However, I am
curious how this would work.
Although both the servers have 2 network cards, only one is enabled on
each server. There is no "private" connection between the servers for
heartbeats. Because the server is in Unicast mode, I understand that
they are not exchanging heartbeats. I am prepared to add this
connection, but we do not want to enable Multicast mode.
The currently enabled nic in each system is configured with 2 IP
addresses - 1) unique for the local system and 2) the shared cluster
IP. The web sites are associated with the shared cluster IP (as
opposed to <all unassigned>). If I were to set HTTPMon to monitor the
sites in this configuration, my understanding is that it would not be
able to tell which server it was monitoring.
Can I work around this by enabling the 2nd nic? Would I then also
have to change the IP address for the web site on both servers to <all
unassigned> so that HTTPMon can monitor each instance through the 2nd
adapter? Instead of a crossover between the two, I guess I'd have to
plug the 2nd nics into the switch so they can be monitored by a 3rd
computer (outside the cluster) running HTTPMon.
Thanks for any advice.