![]() ![]() 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 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 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |