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

Vijay_1982_1648's avatar
Vijay_1982_1648
Icon for Nimbostratus rankNimbostratus
May 20, 2016

F5 snmp trap for node and pool members

Hi All,

 

we are planning to enable SNMP trap for node and pool members up and down. so how to start and can someone provide the implementation plan. I have tried to read multiple documents but no luck. Kindly help on.

 

BIG-IP
devops

2 Replies

  • nathe's avatar
    nathe
    Icon for Cirrocumulus rankCirrocumulus
    May 21, 2016

    We would probably need to understand more your requirement and what may not be working.

     

    The examples you give should already have SNMP traps. See /var/run/bigip_error_maps.dat to map a log entry to alert and then see /etc/alertd/alert.conf to map this to an OID and a SNMP trap.

     

    Then you should be able to configure a trap destination in the GUI to send them to a server.

     

    See if these links help further: https://support.f5.com/kb/en-us/solutions/public/6000/400/sol6420.html

     

    https://support.f5.com/kb/en-us/solutions/public/11000/100/sol11127.html

     

    Hope this helps,

     

    N

     

  • 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"
}