Forum Discussion

Prince_165600's avatar
Prince_165600
Icon for Nimbostratus rankNimbostratus
Apr 14, 2017

A service is detected DOWN - TRAP

Hi Team,

I would like to understand if this trap is really being generated by F5. If so how can i disable it ?

Example Event :

A service is detected DOWN. bigipNotifyObjMsg= Pool /Common/test_pool member /Common/1.2.3.4:443 monitor status down. [ /Common/test_pool: down ]  [ was up for 2hrs:41mins:36sec ] bigipNotifyObjNode= /Common/1.2.3.4 bigipNotifyObjPort= 443


I have checked the custom alert file /config/user_alert.conf and dont see any configurations created for this trap.

Any idea about this ?

  • This is a standard trap sent by the BIG-IP. Article K11234 discusses how to disable SNMP alerts for default traps.

     

3 Replies

  • This is a standard trap sent by the BIG-IP. Article K11234 discusses how to disable SNMP alerts for default traps.

     

    • Prince_165600's avatar
      Prince_165600
      Icon for Nimbostratus rankNimbostratus

      Hi Kevin,

      Thans for directing me to the article.

      So will i be correct to say that if i disable below alerts :

      alert BIGIP_MCPD_MCPDERR_POOL_MEMBER_MON_STATUS {
          snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.10"
      

      } alert BIGIP_MCPD_MCPDERR_POOL_MEMBER_MON_STATUS_UP { snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.11" }

      alert BIGIP_MCPD_MCPDERR_NODE_ADDRESS_MON_STATUS { snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.12" } alert BIGIP_MCPD_MCPDERR_NODE_ADDRESS_MON_STATUS_UP { snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.13" }

      I will stop receiving those alerts ?