Forum Discussion

Sumanta_88744's avatar
Sumanta_88744
Icon for Cirrus rankCirrus
Jun 09, 2016

SNMP trap sent by F5 to NMS

Hi Experts

 

Apart from virtual server down/up event, other events are not sending SNMP traps to the NMS. Do I need to customize alert.conf? I would expect SNMP trap for any interface or pool member up/down.

 

Regards,

 

Sumanta.

 

application delivery
BIG-IP
TMOS

2 Replies

Sort By
  • Vijay_E's avatar
    Vijay_E
    Icon for Cirrus rankCirrus
    Jun 09, 2016

    Trap will be generated and sent to trap destinations for default settings. You shouldn't have to modify the alert.conf file. What logs are you trying to get ?

     

  • iamczar_12961's avatar
    iamczar_12961
    Icon for Cirrus rankCirrus
    Jun 10, 2016
    Pre-configured SNMP traps are contained in the /etc/alertd/alert.conf file. F5 does not recommend, or support, the addition or removal of traps or any other changes to the alert.conf file.

Custom, user-defined SNMP traps should be defined in the /config/user_alert.conf file.

Depending on what you what to monitor, you can add it to user_alert.conf, example:

alert BIGIP_LOG_WARNING ".*No members available for pool" {
        snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.201";
        email toaddress="your.textemail@company.com"
        fromaddress="root"
        body="No members available for pool"
}