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
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.
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 : $* "
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
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 |
List of MIB files used by OpManager and SNMP Servers