Forum Discussion
Create/Repeat Alert When A Pool or Node is Down
- Dec 11, 2019
I think an external monitor would be the good solution for this. You have to write your script along with some logger, so that it constantly throws logs about the status. But it will flood your log file for x intervals.
On good note, put the logging only for down state, for Up - do not put the logger.
Thanks for the response!
Unfortunately, it is a different branch of the organization that handles the monitoring and I do not know what the software is or how it works. The issue has been that after the patching, the servers in question have had issues coming back fully operational. The monitor I have on these is a SIP monitor. We are trying to see if there is a way for the F5 to periodically report the down condition. I agree that this should be handled elsewhere, not on the F5, but attempting to do my due diligence from an F5 perspective.
Additionally, there is no VIP. I simply have the Nodes for the servers and then a Pool that they belong to. The sole purpose is for the F5 to monitor the servers and throw the syslog errors when they are not reachable.
Thanks!
Eric
I think an external monitor would be the good solution for this. You have to write your script along with some logger, so that it constantly throws logs about the status. But it will flood your log file for x intervals.
On good note, put the logging only for down state, for Up - do not put the logger.
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