Forum Discussion

Techgeeeg_28888's avatar
Techgeeeg_28888
Icon for Nimbostratus rankNimbostratus
Jul 07, 2015

SNMP Alerts on creating objects and their status on LTM

Hi Everyone,

 

I would like to have the input from experts regarding the traps. I have LTM installed and it is also integrated to send SNMP Traps. My requirement is as follows,

 

  1. Whenever a node is created or deleted, Pool is created or deleted, VS is created or deleted I should receive an alert vis SNMP.

     

  2. When ever a Node is up or down, Pool/Pool member is up or down, VS is up or down, Any profile is added or removed or is attached or removed from a VS any irule is created or deleted or attached to a VS, a Snat is created or modified I should receive the alert via SNMP.

     

But in actual what all I am getting is if a VS or pool is down (when all the members of a pool fails only then) i receive the trap else I am not receiving anything. Is this normal or is this a bug what should I check or do. Kindly let me know if you guys have faced any similar issue.

 

Regards,

 

7 Replies

  • It is normal. These may be of some assistance to you:

     

    To get the full set of traps you want, you will need to configure some custom traps. If syslog messages aren't generated for all of the events that you wish, you may consider using an iCall periodic method to detect a desired condition, syslog it, then use the custom trap mechanism:

     

  • Hi Vernon,

     

    Thanks for the above, I also want to know if the syslog logs all the event happening on the box or it only logs selected events? Also regarding the request coming to the VS is it all logged by the SYSLOG to the configured remote server or not? If not then is it done by the HSL or just selecting the loggin option in the VS configuration is all we have to do to let the syslog send the logs n details of all the queries sent to and from VS.

     

    Regards,

     

    • shaggy's avatar
      shaggy
      Icon for Nimbostratus rankNimbostratus
      1) does syslog log all events - check out System | Logs | Configuration | Options 2) request logging - there is no request logging by default. you can use HSL by creating a custom logging profile, an iRule, or by using AFM logging if you have purchased and provisioned AFM on your BIGIP
  • Hi Vernon,

     

    Thanks for the above, I also want to know if the syslog logs all the event happening on the box or it only logs selected events? Also regarding the request coming to the VS is it all logged by the SYSLOG to the configured remote server or not? If not then is it done by the HSL or just selecting the loggin option in the VS configuration is all we have to do to let the syslog send the logs n details of all the queries sent to and from VS.

     

    Regards,

     

    • shaggy's avatar
      shaggy
      Icon for Nimbostratus rankNimbostratus
      1) does syslog log all events - check out System | Logs | Configuration | Options 2) request logging - there is no request logging by default. you can use HSL by creating a custom logging profile, an iRule, or by using AFM logging if you have purchased and provisioned AFM on your BIGIP
  • Hi Shaggy,

     

    Thanks for the reply I want to know when we use HSL by creating a custom logging profile does it capture everything like all the hits on VS along with the actual request from the client and the reply by the Servers??

     

    Regards,

     

  • There are two ways to employ HSL for logging: 1. use an iRule; 2. use a Request Logging Profile. With an iRule, what is logged and when is entirely dependent on the logic of the rule itself.

     

    I suspect, from your reply, that you are using a Request Logging Profile. More information is available here:

     

    https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip-external-monitoring-implementations-11-5-0/1.htmlconceptid

     

    If Request logging is enabled on a custom profile, and the profile is applied to a Virtual Server, then all requests through that Virtual Server will be logged. The specific fields logged is configurable in the profile as described above.