Forum Discussion
cvrnr_18603
Nimbostratus
NimbostratusMonitoring website with different header packets
We have created a pool with 2 web server serving with three different headers
webserver header header header
1st x y z
2nd x y z
using rules we were able to load balance between 1st and 2nd webserver based on headers
But we are unable to configure monitoring on this scenario .How can we configure monitoring so that even if header site x goes down on 1st web server the other y and z should be served from the webserver
i tried to acheive this one but because the monitor is associated to node if x dies all y and z are down
is there any way to acheive this monitoring
cvrnr_18603can someone pls rely to thsi if the question is not clear i can explain more clearly
hoolioCirrostratus
Hello,
It sounds like you have three virtual hosts running on the same IP and port, using host headers to differentiate which web application the request is for.
You can configure one monitor per HTTP host header that you want to check. If you configure the send string with the Host header, you can differentiate in the monitor between the three virtual hosts:
GET /path/to/file.ext HTTP/1.1\r\nHost: virtualhost1.example.com\r\nConnection: close\r\n\r\n
The Host header sent in this example is virtualhost1.example.com.
The receive string could be 200 or OK or HTTP depending on what headers/data your servers respond with.
For more info, you can check the reference guide on AskF5 for your version (). SOL3224 has some additional info as well ().
If this isn't what you're looking for, please explain further. I'm still a bit unclear about whether you want the other two virtual hosts to be left up if only virtualhost1 is marked down by a monitor.
Aaron- cvrnr_18603Thanks aaron
I want the other hosts to be left up. I will try this solution and checkout - As of LTMv9, multiple instances of the same pool member can be independently monitored.
If I understand your requirements correctly, I think the best way to accomplish what you're after is to create 3 separate pools, all with the same members, and monitor each with a single Host-header specific monitor:VS:80 resource: rule=pick_a_pool_by_Host_header pool site_x member 10.1.1.1:80 member 10.1.1.2:80 monitor app_x (sends site_x-specific host header) pool site_y member 10.1.1.1:80 member 10.1.1.2:80 monitor app_y (sends site_x-specific host header) pool site_z member 10.1.1.1:80 member 10.1.1.2:80 monitor app_z (sends site_x-specific host header)
HTH
/deb - I just noticed you were posting in the v4 iRules forum: If you are using BIG-IP v4, there really is no way to monitor the pool members separately like this.
(Moved your posts over to Monitoring & Mgmt forum. Click here to get to the new forum)
/d
