SiteScope User's Guide
![]() |
![]() |
![]() |
![]() |
The SNMP Trap Monitor watches for SNMP Traps received by SiteScope from other devices. The agents for the SNMP enabled devices need to be configured to send traps to the SiteScope server.
Note: To have SiteScope query a specific device for a specific value, use the SNMP Monitor.
The SNMP Trap Monitor is useful for automatically collecting SNMP Traps from other devices. With SiteScope doing this for you at set intervals, you can eliminate the need to check for the SNMP Traps manually. In addition, you can be notified of warning conditions that you might have otherwise been unaware of until something more serious happened. Each time that it runs this monitor, SiteScope checks traps that have been received since the last time it ran.
Note: The SiteScope SNMP Trap Monitor uses port 162 for receiving traps. If another application or process on the machine where SiteScope is running has bound this port, the monitor will report an "Address in use" error and the monitor type will be unavailable.
To display the SNMP Trap Monitor Form, either click the Edit link for an existing SNMP Trap Monitor in a monitor table, or click the add a Monitor link on a group's detail page and choose the "Add SNMP Trap Monitor" link.
Complete the items on the SNMP Trap Monitor Form as follows. When the required items are complete, click the Add Monitor button.
Note: You will also need to configure the network devices to send SNMP Traps to SiteScope. On Windows 2000 systems, this can be configured via the Admninistrative Tools-->Services-->SNMP Service-->Properties-->Traps screen. SNMP agents on UNIX platforms usually require that you edit the configuration files associated with the agent. For an example of working with other devices, see the instructions on the Cisco web site for SNMP Traps and Cisco Devices
All of the SNMP Traps received by SiteScope are logged to SiteScope/logs/SNMPTrap.log
For example, the following shows two traps received from one router and another trap received from a second router:
09:08:35 09/10/2001 from=router1/10.0.0.133 oid=.1.3.6.1.4.1.11.2.17.1 trap=link down specific=0 traptime=1000134506 community=public agent=router1/10.0.0.133 var1=The interface Serial1 is down 09:08:45 09/10/2001 from=router1/10.0.0.133 oid=.1.3.6.1.4.1.11.2.17.1 trap=link up specific=0 traptime=1000134520 community=public agent=router1/10.0.0.133 var1=The interface Serial1 is up 09:10:55 09/10/2001 from=router2/10.0.0.134 oid=.1.3.6.1.4.1.11.2.17.1 trap=enterprise specific specific=1000 traptime=1000134652 community=public agent=router2/10.0.0.134 var1=CPU usage is above 90%
Choose the method for running alerts. If "for each event matched" is chosen, then the monitor triggers alerts for every matching entry found.
NOTE When the SNMP Trap Monitor is run in the "for each event matched" alert method, the monitor will never report a status of error or warning, regardless of the results of the content match or even if the target SNMP Trap is not found.If the "once, after all events have been checked" method is chosen, then the monitor counts up the number of matches and triggers alerts based on the "Error If" and "Warning If" thresholds defined for the monitor in the Advanced Options section.
The advanced options give you the ability to customize error and warning thresholds. If you choose not to set them, SiteScope will use pre-set defaults if available. If a default is not available, SiteScope will not be able to utilize the condition.
Note: In order to change the run frequency of this monitor when an error is detected, use the Update every (on errors) option below.
Note: The status returned by the Verify Error run of the monitor will replace the status of the originally scheduled run that detected an error. This may cause the loss of important performance data if the data from the verify run is different than the initial error status.
Warning: Use of this option across many monitor instances may result in significant monitoring delays in the case that multiple monitors are rescheduled to verify errors at the same time.
The possible comparison values are:
![]() |
![]() |
![]() |
![]() |

Copyright © 2003 Mercury Interactive Corporation.
All rights reserved.