Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
en:documentation:03_monitoring:08_snmp_traps_monitoring [2021/08/06 16:41]
jimmy.olano [Adding an alert] He subido una nueva captura de pantalla. Estilo.
en:documentation:03_monitoring:08_snmp_traps_monitoring [2021/09/16 09:17] (current)
Line 175: Line 175:
  
 **Field 2** **Field 2**
-<code> 
  
-Field to set the command parameter of the ''Field 2'' alarm. In case of sending an email, it will be the subject of the message. If left blank, it would use what it had defined in the action. + Field to set the command parameter of the ''Field 2'' alarm. In case of sending an email, it will be the subject of the message. If left blank, it would use what it had defined in the action.
- +
-</code>+
  
 **Field 3** **Field 3**
-<code> 
-Field to set the command parameter of the ''Field 3'' alarm. In case of sending an email, it would be the text of the message. If left blank, it would use what it had defined in the action. 
  
-</code>+ Field to set the command parameter of the ''Field 3'' alarm. In case of sending an email, it would be the text of the message. If left blank, it would use what it had defined in the action.
  
 **Min. Number of Alerts** **Min. Number of Alerts**
Line 254: Line 249:
 === TRAP-Storm Protection === === TRAP-Storm Protection ===
  
-There are a couple of parameters in the server which are conceived to protect the system against the arrival of a Trap Storm, coming from a single location. Use the following settings in the ''pandora_server.conf''  file for this:+There are a couple of parameters in the server which are conceived to protect the system against the arrival of a Trap Storm, coming from a single location. Use the following settings in the ''pandora_server.conf'' file for this:
  
-  * ''snmp_storm_protection''The max. number of processed SNMP traps by the same source IP in a given interval (see below). +   * ''snmp_storm_protection'' The max. number of processed SNMP traps by the same source IP in a given interval (see below). 
-  * ''snmp_storm_timeout''The interval in seconds for protection against an SNMP Trap Storm. During this interval, the system will only process 'snmp_storm_protection' type traps from the same source (IP). +  * ''snmp_storm_timeout'' The interval in seconds for protection against an SNMP Trap Storm. During this interval, the system will only process 'snmp_storm_protection' type traps from the same source (IP). 
-  * ''snmp_storm_silence_period''If it is greater than 0 each time the storm protection is triggered for a particular source, the current time will be added plus the silence time. Until this time passes, no new traps will be registered for the specific source.+  * ''snmp_storm_silence_period'' If it is greater than 0 each time the storm protection is triggered for a particular source, the current time will be added plus the silence time. Until this time passes, no new traps will be registered for the specific source.
 When this protection fires, it is reflected in an event on the console: When this protection fires, it is reflected in an event on the console:
  
Line 264: Line 259:
  
 Trap storm protection combined with trap filtering (see below) allows that if you receive hundreds of thousands of traps per day, you work with only a few thousand traps to delete redundant or unhelpful traps. Trap storm protection combined with trap filtering (see below) allows that if you receive hundreds of thousands of traps per day, you work with only a few thousand traps to delete redundant or unhelpful traps.
 +
  
 === TRAP Filtering in the Server === === TRAP Filtering in the Server ===