Forum Discussion
Deb_Allen_18
May 20, 2008Historic F5 Account
As long as the matched message string is different from that in alert.conf, you should be able to specify additional traps. This is what's in alert.conf for 9.2.x:
/*
* 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"
}
Note the comment at the top. I know you're not supposed to modify the base alert.conf file, so perhaps a call to Support is in order to clarify that comment. It may shed some light on what you are seeing.
HTH
/deb