Solved
Forum Discussion
IanB
Jan 29, 2016Employee
In my lab, your irule worked as expected - that is to say:
- When I request "/refresh", the node selected is 192.168.1.20:80
- When I request "/" (or any other URI), the pool member selected is 192.168.1.10:80
Because your rule explicitly sets the node/member for every request, you should not be seeing normal load balancing (round robin in your case) at all.
I'm not able to tell from the information here why it's not working for you. It might help to add logging in an LB_SELECTED event, for example:
when LB_SELECTED {
log local0. "[LB::server] was selected"
}
Then make some curl requests from the LTM itself, to eliminate anything else that might be getting in the way
ltm curl -v http://x.x.x.x/refresh
Also, make sure you're working with the active member of the HA pair, and that the pair is in config sync