What is an SNMP Trap?

The SNMP trap is a warning message sent from a SNMP-enabled remote device to the central collector, "SNMP manager". It can take a lot of time to configure and improve and also in very large environments using large computing power. This alternative is called 'SNMP Trap'. With SNMP Traps, instead of routers (for example) being surveyed to get information regularly by Opsview Monitor, the router itself will let Opsview Monitor find out about any problem or problem through a 'trap'.

Initial Settings SNMP Trap

See the SNMP Trap Collector for details about the SNMP Trap Collector. See MIB for SNMP Trap and Gets to add your MIB as needed to translate SNMP Traps. Every Service Check configured to receive SNMP traps has a list of rules ordered. Each rule is evaluated in turn. If the rule is wrong, then the next rule is evaluated. 

If the rules match correctly, the specified actions are taken and there are no more rules for Checking Services that are evaluated. send the passive inspection results to the Opsview Monitor with the appropriate message, or do nothing, and thus stop processing the rules further. If the incoming trap does not evaluate true for any rules, it becomes an exception and will appear on the SNMP Trap Exception page. 

This is needed so that the administrator knows that the rules need to be set to meet this particular trap. This is related to a Host. Hosts can have more than one SNMP trap service check. The illustration below shows the trap evaluated in four Service Examinations, represented as columns. This column is not ordered, so there is no guarantee which Check Service column will be evaluated first. 

The consequence of some Service Checks is that a trap can increase many warnings to the Opsview Monitor. However, there will only be one SNMP Trap Exception per trap. One example of using some Service Checks is if you want a Service Check to show the status of the interface, with other Service Checks that tell you about error log messages.

Note: Traps received will hide the value of the SNMP community so passwords are not stored in the file system.

Configuring SNMP Traps

This page will display a summary of the current SNMP Trap configuration along with details about each trap exception (a trap that fails to meet the rules) and search details: Summary information of all SNMP Trap settings will be displayed in five separate boxes:

• Host Expects SNMP Trap
• Host With Tracking Activated
• Inspection of SNMP Trap Services
• Exception of SNMP Traps
• SNMP Trap Debugging Line

Clicking on one of the 'Host with Tracking Enabled' boxes, 'SNMP Trap Exceptions' and 'SNMP Trap Debugging Rows' will take you to the appropriate tab. Making any changes on this tab will update the main summary when you return there.

Download SNMP Trap

Free Driver

SNMP Trap Exceptions Tab 

If the entry trap does not match the rules, it becomes an exception. The Exceptions tab will display a grid with the following data:

• IP Host - IP Source Exception Trap
• Date / Time - The date / time of the trap is returned
• Trap Name
• Reason - The reason for the incoming trap does not evaluate true for any rules
• Package

Clicking the Delete All button will delete all trap exceptions, no matter whether the filter is applied to one column. Or, you can delete individual traps by clicking on the contextual menu and selecting the 'Delete' option.

Debug Tab SNMP Trap

The Debug tab will display a grid with the following data:

• Time - The time of the debug trap is recorded
• Processing Time - Time of execution of rules
• Rules
• Package

Debug traps can only be deleted individually by clicking on the contextual menu and selecting 'Delete'; there is no option for bulk deletion, although when you delete a trace, all associated debug traps will be deleted.
Newer Post
This is the last post.