Forum Discussion
Keith_Richards_
Nimbostratus
Apr 02, 2007disable pool member on certain conditions
Hi,
I have a customer that would like to use the Passive Monitoring that is mentioned in the release notes for 9.4:
"Passive monitoring of pool members
The BIG-IP system now includes a feature known as passive monitoring. With passive monitoring, a pool member can be marked down sooner than the customary three successive bigd health check failures. Implementation of this feature requires the use of the iRulesTM feature."
I aim to write an iRule that tests the response time of a given server each time a client connects and if it responds too slowly then it will I want to disable sessions going to that server (ideally prevent even persistent connections to continue going to that server). I thought to get started I would see if I could use an iRule to set the status of a member and tried the following:
when CLIENT_ACCEPTED {
log local0. "Keith Rule hit OK!"
set [LB::status pool keithpool member 10.41.0.21 80] down
}
But despite the log showing that the rule matched when I connect to the VS the status of that pool member doesn't change and I don't see any other error messages.
Hope you can help, thanks, Keith
- Emilio_Torres_2Historic F5 AccountHi to all. I understand that LB::status command just recover or validate the state of the pool member, this command can't change their status. Then for the sentence "LB::status pool keithpool member 10.41.0.21 80 down" the irule just return 1 if the pool member (10.41.0.21:80) is down and returns 0 is up or other, but don't put down the member, just check their status. At least that is the behavior that i saw in my tests.
Recent Discussions
Related Content
DevCentral Quicklinks
* 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
Discover DevCentral Connects