I'm currently using Priority Group Activation method to accomplish my first objective and it's been working great. However, I have more requirements than just active standby real servers. The situation gets complicated when my primary server fails and later comes back online. When it fails, there is no question about it, all requests will hit the standby server. Here's a tricky part when the primary comes back online. Because of the Priority Group Activation that I have above, when the primary comes back, all traffic would go back to the primary. This is NOT what I want. My new requirement is that when the primary comes back, I still want my traffic to hit the standby unless I want to manually force the standby offline. Some people in this forum have suggested to use Destination Address Affinity in combination with Priority Group Activation. Now before I go into details, I wanted to be clear on my objectives.
How do I achieve all of those objectives above? Please advise.
Enable manual resume on your health monitor.
And change (under advanced configuration) your pool response to load balancing fail to reselect.
I don't want to manually re-enable the node. I know it's an option. However, this option doesn't appear to be the best option.
As for your second suggestion, that's how it is currently being configured today.
Quoting what you said: "I still want my traffic to hit the standby unless I want to manually force the standby offline."
How is that different form manual enabling the primary?
Good question. The difference is who is going to manually do it. The server guy or the F5 admin. In our case, the server guy wants the control. That's why that option is not the best option.
Ah, that makes more sense.
The solution is iCall
You can use alertd to create a trigger when a pool member in your pool gets marked down.
This triggers a tcl script that swaps the priority group activation settings for the pool members.
iCall has a few documents and examples, so have a look.