I guess you do have another port bound to the virtual server - something like:
port 1234 of the real server is bound to the virtual server but you
would like to base the real servers health at a health check which is
getting done to port 80 of the real server - correct?
If so: The ServerIron offers port-policies and healthck's to do
something like this:
healthck:
healthck myhck tcp
dest-ip 1.2.3.4
port http
protocol http
protocol http url "GET /something.html"
interval 6
retries 2
l7-check
server real test 1.2.3.4
port 1234
port 1234 healthck myhck
server virtual whatever 5.6.7.8
port 1234
bind 1234 test 1234
port-policies are slightly different:
server port 1235
tcp
server port-policy mpp
port http
protocol http
protocol http url "GET /whatever.html"
keepalive-interval 6
server real test 1.2.3.4
port 1235
port 1235 use-port-policy mpp
server virtual whatever 5.6.7.8
port 1235
bind 1235 test 1235
You do not have to define a destination IP in a port-policy which
allow it to reuse port-policies. Healtck's do require an IP address
and you need to define a single healthck per real server which is
some more work but more flexible.
R, Oliver
L4-7 SE
Brocade
At 21:40 02.04.2009, Ryan DeBerry wrote:
Is it possible to have a healthcheck to a port that is not bound on
the virtual server?
_______________________________________________
foundry-nsp mailing list
[email protected]
http://puck.nether.net/mailman/listinfo/foundry-nsp
_______________________________________________
foundry-nsp mailing list
[email protected]
http://puck.nether.net/mailman/listinfo/foundry-nsp
