Forum Discussion
NimbostratusConfigured SNMP traps and Email...Now Im getting spammed?
alert BIGIP_MCPD_MCPDERR_POOL_MEMBER_MON_STATUS {
snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.10";
email toaddress="XXXXXXX"
fromaddress="root"
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="XXXXXXX"
fromaddress="root"
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="XXXXXXX"
fromaddress="root"
body="Node Member 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="XXXXXXX"
fromaddress="root"
body="Node Address Monitor Status Up"
}
3 Replies
- JRahm
Admin
I've personally seen this when the poll interval is tighter than 5s/16s on systems with a) several hundred poll targets or b) greater than 80% load. Setting back to the default poll interval solved the up/down issues for me. 
NzYme_68513Posted By Jason Rahm on 10/29/2010 04:18 PM
I've personally seen this when the poll interval is tighter than 5s/16s on systems with a) several hundred poll targets or b) greater than 80% load. Setting back to the default poll interval solved the up/down issues for me.
Is that done within the trap definitions I've posted or is this done somewhere else? When I'm looking at the health monitor through the gui they aren't going up and down like the emails are indicating. I'm just wondering if these traps use a different poll interval? Can I explicitly define them separately from the default interval?- JRahmthe traps are a result of the monitoring process marking the nodes down. The pool interval is set on each individual monitor defined.
