Forum Discussion
Handling sideband server failure
A few options maybe.
1. Do you have a monitor assigned to the pool? A failed pool should automatically flag the VIP as offline. You may also consider setting the pool's "Action On Service Down" option to Reject.
2. Use the 'active_members' condition in an iRule:
when CLIENT_ACCEPTED {
if { [active_members sideband_pool] < 1 } {
reject
}
}Hi Kevin,
Please find my answers to your question sbelow:-
1. Do you have a monitor assigned to the pool? A failed pool should automatically flag the VIP as offline. You may also consider setting the pool's "Action On Service Down" option to Reject.
Yes.However our pool has an ec2 node that stays green even when the service is down as seen in the below image.Hence the member check fails.
Which brings me to your next question
2. Use the 'active_members' condition in an iRule:
I already have this rule enabled but this fails due to the above mentioned issue.
Not only this, the problem is that i need to handle the send command error so that the moment any TCP error happens while the traffic is mirrored from the LB to the external mirror pool, the exception is thrown and the execution stops thereby allowing the traffic to move to the client website
when HTTP_RESPONSE{
set send_data [send -timeout $connectionTimeout -status send_status $conn_id $responseData]
close conn_id ;
}
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com