OpManager Trap Processor Config

OpManager Trap Processor Config

OpManager Trap Processor Config

Trap processor can be edited to display a number of labels and information based on the markup language and variables (VarBinds)

https://pitstop.manageengine.com/portal/kb/articles/how-to-configure-trap-message

Changes to the MIB files

Sometimes there is a change in the MIB file with new Firmware upgrades, The file on the OpManager Probes will need to be updated
Using SSH to access the Server, navigate to the '/opt/ManageEngine/Opmanager_Server/mibs'  folder, delete the old MIB. Use a file transfer protocol such as SCP to transfer the new MIB to the 'mibs' folder. 

In Addition, if there is a change in description within the MIB file, OpManager may need the old Trap entries removed before adding all traps. It is not necessary to restart the server so it should be possible to add new Traps straight away.

Editing trap processor

While logged into the Central OpManager server, navigate to "Setting>Monitors>SNMP Trap Processors", select a trap you wish to edit the output of and edit Message field or the Description field. There is a search option near the top right of the page which can be used to search keywords such as 'mimo' or 'fail'

Other criteria can be edited at this time as well, such as Severity and Match

Example Message format from a MMX radio

"mwlLoginFailedTrap is received from $Source with the following related information : $* "

The resulting message will look like this;

mwlLoginFailedTrap is received from 172.26.19.120 with the following related information : sysUpTime.0: 5 hours, 23 minutes, 30 seconds. , snmpTrapOID.0: .1.3.6.1.4.1.31730.7.0.5 ,



$Source = IP Address of device

$SourceMO(displayName) = Device Name

$*, includes all of the OID information in the Trap

$N, selects specific OID data where N starts at Zero


Using the VarBinds that Manage Engine have supplied (See link), we can display specific variables from a trap '$N ' Where N = Variable. N starts at zero. 

If we use '$* ' OpManager displays all of the details from the OID;

"The trap is received from $SourceMO(displayName). The trap details are as follows, mwlGPIO1Digital=$* "

The trap is received from RRU-1-VHF. The trap details are as follows, mwlGPIO1Digital=sysUpTime.0: 113 days, 12 hours, 40 minutes, 49 seconds. , snmpTrapOID.0: .1.3.6.1.4.1.31730.7.0.12 , mwlGPIO1Digital.0: 0 ,

Critical

15 May 2018 02:30:57 AM UTC

The next example shows the I and O state when the GPIO trap is received. '$2 ' represents the third OID in the trap;

 "The trap is received from $SourceMO(displayName). The trap details are as follows, mwlGPIO1Digital=$2 "

The trap is received from RRU-1-VHF. The trap details are as follows, mwlGPIO1Digital=0

Critical

15 May 2018 02:05:11 AM UTC

The trap is received from RRU-1-VHF. The trap details are as follows, mwlGPIO1Digital=1

Critical

15 May 2018 02:05:01 AM UTC


 



    • Related Articles

    • Accessing OpManager PGSQL Database

      Accessing the Database · Although uncommon, accessing the OpManager database may be required to pull specific data, apply changes, or to troubleshoot an issue as directed by Manage Engine. · To access the Central database, navigate to the following ...

    • How to apply OpManager PPM Update and com.zip Patches

      Table of Contents Overview.. 2 Prep and file transfer. 2 Release Notes. 2 UpDate Manager for PPM... 2 Central Server upgrade. 4 Update files. 5 Discover Properties. 5 Edit list of Traps for auto-discovery. 7 Hardware Info in inventory. 7 To Enable ...

    • SQL Database query for OpManager

      SQL Database query for OpManager Database queries can be run from the web UI to pull various information from the database. In addition, Manage Engine may provide queries and request the output when troubleshooting an issue. To run a query, click the ...

    • Configuring configlets in OpManager NCM

      Manage Engine has written instruction on using and creating configlets. The link in this KB may be changed if Manage Engine update it, but for now it is a source for other NCM info as well ...

    • SCP files from OpManager using configlets

      OpManager can transfer files to MMX radios, this ability to push a file to the radio was added to help with firewall rules that prevented the MMX radio from getting a file. The firewall rule typically allowed SCP from the secure side out to a radio, ...