Forum Discussion
Pronlem with a monitor
We got a fix from F5.
I'd never have guessed this one but here it is.
In the Monitor config, change the "Count" to anything other than a value of 0 I changed it to one and the monitor fired straight off and marked the server up. See text below from F5
I've checked over the QKview you've supplied us, it looks like we may be seeing an issue with the SQL monitor that can happen when it's disconnected from the database, but doesn't necessary realize that it's been disconnected from the database. For the future, using a non-0 value for "count" will prevent this from happening In this instance, I'd like to recommend that you set the "count" value on PROD_SQL2 to a non-0 number, and then reboot your LTM using the procedure found here: https://support.f5.com/kb/en-us/solutions/public/13000/000/sol13030.html. This process causes the LTM to reload its binary database from the configuration. Needless to say, it should not be performed on a system currently passing traffic. I'd recommend a minimum of a failover, preferably a work window.
Thanks again for your help .
Cheers
Drew
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