For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

daboochmeister's avatar
daboochmeister
Icon for Cirrus rankCirrus
Oct 22, 2015

Controlling which VS do/don't trigger SNMP traps

Env: LTM 11.5.3, GTM 11.5.3   Hey all - on our F5s we co-manage both production and test/QA virtual servers. The test/QA variety are naturally less stable, as the teams bring down real servers f...
application delivery
BIG-IP DNS
LTM
management
snmp
snmp trap
Henrik_Gyllkran's avatar
Henrik_Gyllkran
Icon for Nimbostratus rankNimbostratus
Oct 22, 2015

My recommendation would be to put those environments in separate BIG-IP:s because there is a solution but it's kind of icky. What you would need to do is to disable the default trap in /etc/alertd/alert.conf, and then add custom traps for all the VS:es that you do want traps for in /config/user_alert.conf.

 

Read more about adding custom traps here:

 

https://support.f5.com/kb/en-us/solutions/public/3000/700/sol3727.html?sr=48907127

 

The reason why I say it's icky is because F5 does not recommend that you actually edit /etc/alertd/alert.conf, and it's a bit of a hassle to make sure that you have all the important VS:es covered by custom traps, but it is possible.