Forum Discussion
Don_22992
Jan 28, 2008Nimbostratus
Email notification of node/vs down
I have searched for a while now, and have not found a solution.
Alertd appears to be the method of sending an email alert; how do I tell it a node is down?
Or a custom scripted monitor looked like a candidate.
I am not necessarily looking for the solution - just guidance of where to investigate further.
- Daniel_55334AltostratusThanks hoolio. I'll give it a shot.
- rlong_77885NimbostratusHi Aaron,
- Heiko_Engemann_NimbostratusHello,
/* * from bigd (CR36393) -- changed from mcpd messages in v9.2.0 (CR46190) and hotfix v9.0.5 * For the following 4 alerts, messages need to be used in pattern match to * distiguish different ipaddr, port, etc. So, if these messages are changed, * the changes in alert system need to be done accordingly. */ alert BIGIP_MCPD_MCPDERR_POOL_MEMBER_MON_DOWN "Pool member (.*?).*?) monitor status down." { snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.10" } alert BIGIP_MCPD_MCPDERR_POOL_MEMBER_MON_UP "Pool member (.*?).*?) monitor status up." { snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.11" } alert BIGIP_MCPD_MCPDERR_NODE_ADDRESS_MON_DOWN "Node (.*?) monitor status down." { snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.12" } alert BIGIP_MCPD_MCPDERR_NODE_ADDRESS_MON_UP "Node (.*?) monitor status up." { snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.13" }
alert BIGIP_MCPD_MCPDERR_POOL_MEMBER_MON_STATUS { snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.10"; email toaddress="support@example.com" fromaddress="root@bigip.example.com" body="Pool Member Status Down!" } alert BIGIP_MCPD_MCPDERR_POOL_MEMBER_MON_STATUS_UP { snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.11"; email toaddress="support@example.com" fromaddress="root@bigip.example.com" body="Pool Member Monitor Status Up" } alert BIGIP_MCPD_MCPDERR_NODE_ADDRESS_MON_STATUS { snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.12"; email toaddress="support@example.com" fromaddress="root@bigip.example.com" body="Node Address Monitor Status Down!" } alert BIGIP_MCPD_MCPDERR_NODE_ADDRESS_MON_STATUS_UP { snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.13"; email toaddress="support@example.com" fromaddress="root@bigip.example.com" body="Node Address Monitor Status Up" }
- Heiko_Engemann_NimbostratusHello,
- ingardNimbostratusHey guys. I have this setup working for all our health monitors, but i would like to change 2 things. 1) Add/change hostname (instead of ip). 2) (and this is the most important) I want to include which health monitor has marked the node down.
- hooleylistCirrostratusingard,
- ingardNimbostratusI just did, its too bad really as it would be very usefull to know which monitor did the flapping that occured "last night"
- hooleylistCirrostratusYou could enable logging on bigd, but I think you'd get too much logging for everyday use if you have a large number of pools. To enable logging, you can run 'b db bigd.debug enable'. The output is written to /var/log/bigdlog. To disable the logging, run 'b db bigd.debug.disable'.
- ingardNimbostratusWilldo, that debug output is really nice. I wish i knew about that option last time i was debugging a health monitor. All output from the health monitors goes there - really nice when u're trying to see whats going on.
- ingardNimbostratusAfter beeing pointed towards numerous links in the kb I think we finally got a breakthrough. Excerpt - mail from f5 support:
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