custom snmp traps
4 TopicsCan't find SNMP email id configured on the bigip
Hey Guys, One of our email ids was added to f5 for snmp alerts, and the emails have a from id of root@hostname.local . We now need to remove this id and it should be easy, as the only file where we configure snmp alerts in /config/user_alerts.conf . In the file I can see other email ids but not this particular one, is there some other place where this can be configured. In the qkview I can see this particular email id in mcp_module.xml . Totally lost on where this id is the box, also there is not such thing as a group id or alias id. UPDATE-19 aug 2018 Is there some log I can check to see all the email id which were sent an email?299Views0likes7CommentsExpiring SSL certificate alerts
I want to send out a mail from F5 when a certificate is about to expire. so far i have done this. Configured mail. did a test mail with the below code. echo "ssmtp test mail" | mail -vs "Test email for SOL15288" user@mydomain.com Below code in "/config/user_alert.conf" alert CERTIFICATE_EXPIRED "Certificate (.*) expired" { snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.300"; email toaddress="user@mydomain.com" body="Certificate Expired on " } alert CERTIFICATE_WILL_EXPIRE "Certificate (.*) will expire" { snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.301"; email toaddress="user@mydomain.com" body="Certificate will Expire on " } and then i run "run sys crypto check-cert" from tmsh. Still i dont get any alert mails420Views0likes1CommentSNMP traps for a specific pool
I am having trouble with a custom SNMP trap with which I am trying trigger alert only if a member from a specific pool goes down or comes back up. From all the articles i could find on the subject as well as using the knowledge from the questions asked on this forum in the past i have created the following SNMP trap and added it to the user_alert.conf file; alert BIGIP_MCPD_MCPDERR_POOL_MEMBER_MON_STATUS "Pool /Common/MyPool_pool80 member monitor status down." { snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.302"; email toaddress="myemail@company.com" fromaddress="root" body="Server node is down" } alert BIGIP_MCPD_MCPDERR_POOL_MEMBER_MON_STATUS_UP "Pool /Common/MyPool_pool80 member monitor status up."{ snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.303"; email toaddress="myemail@company.com" fromaddress="root" body="Server node is back up" } The issue is that, while this SNMP trap does trigger alerts and sends email notifications as expected, it triggers alert for ANY pool member that goes down and not just the one for the specified pool. I tried adding IP addresses in the line "Pool /Common/MyPool_pool80 member 1.1.1.1|1.1.1.2:80 monitor status down." – however, it still behaves the same way which is it sends alert for any node going down. I would appreciate if someone can point out if I am making a mistake somewhere in the trap format and if it is even possible to configure SNMP trap to trigger alert notifications only for a specific pool or a pool member. Thanks!341Views0likes0Comments