IIS Host Headers and ECV health monitoring

Hi Wes,

 

 

I don't think a rule will be necessary. In v9, monitors have some extra granularity that might help you solve this problem.

 

 

In v4, a monitor is applied to a node (IP:port combination) and affects all instances of that IP:port combo in any pool.

 

 

In v9, monitors are applied to pool members, so you can run different monitors against different instances of the same IP:port combo.

 

 

Name resolution doesn't come into play with monitors, since BIG-IP sends the request to the destination IP directly, and virtual hosting actually depends on the HTTP Host: header value, so instead of host file entries, you can just create a different HTTP monitor for each pool, with the appropriate host header value in the HTTP request string, and apply the monitor to the entire pool.

 

 

HTH

 

/deb