#Open source snmp trap receiver windows how to#
It shows various checkpoints where a trap can potentially be dropped and where and how to configure filters.
The Flow of SNMP Traps on the NNMi Management Serverįigure 2 demonstrates the detailed flow of SNMP traps on the NNMi management server. The next section describes the details of how NNMi Trap Service and Event Service process SNMP traps at various stages. It is important to understand the flow of SNMP traps within NNMi Trap Service. Each trap moves through various stages in NNMi Trap Service, and, if it passes various filters, eventually reaches the NNMi Event Pipeline. The process sends traps to a message queue, which is processed by the NNMi Trap Service. The Event Pipeline is visible and controlled through the NNMi console.Īs shown in the following diagram, incoming traps are received by the nnmtrapreceiver process. This service is controlled by ovjboss and managed through the nnmtrapconfig.ovpl CLI. The NNMi Trap Service maintains a separate data store of traps. This means that, during failover, no trap is lost. It runs on BOTH the nodes (active and standby) in the cluster. The nnmtrapreceiver process is especially useful in high availability (HA) and Application Failover clusters. In both cases, the Trap Service is started. The nnmtrapreceiver process sends traps into the NNMi Trap Service or queues traps until the ovjboss process is started. The ovstop command stops the nnmtrapreceivermd process, but leaves the nnmtrapreceiver process running The nnmtrapreceivermd process integrates with ovspmd and responds to ovstart/ovstop messagesĭuring ovstart, the nnmtrapreceivermd process starts the nnmtrapreceiver process The nnmtrapreceiver process runs as an operating system service and is comprised of the nnmtrapreceivermd and nnmtrapreceiver processes as shown in the following example output: The NNMi Event Pipeline (controlled by ovjboss) The NNMi Trap Service (controlled by ovjboss) The nnmtrapreceiver process (running as an operating system’s service) NNMi works with SNMP traps at the following three levels: Some screen captures might be slightly different from those that appear in the most recent NNMi graphical user interface. The example commands assume the system user is assigned the following password: mypassword
#Open source snmp trap receiver windows windows#
The example procedures in this document use a Linux NNMi management server, and can be followed on a Windows NNMi management server.When following the procedures in this document, note the following: Periodically trim the NNMi database to remove SNMP traps This document gives an overview on the flow of SNMP traps within NNMi, and then steps through the following three tasks for configuring and managing traps with NNMi:ĭetermine why SNMP traps are not appearing in the NNMi Console Managing SNMP trap configuration within NNMi is a key task that can be used to improve NNMi efficiency.
The Flow of SNMP Traps on the NNMi Management Server.
This topic includes the following sections: Administer > Administer SNMP Traps > SNMP Trap Management SNMP Trap Management