Kemp Support, how can we help?

The latest application delivery knowledge and expertise at your fingertips.

Monitoring Center - Alert - SNMP trap

 

Information

 

Summary:

A detailed description of SNMP traps generated by Alerts in Monitoring Center.

Environment:

Product: Flowmon OS

Version: Any

Platform: Any

Question/Problem Description:

Which MIB table should I use for SNMP traps generated by alerts?

Which OIDs are used in SNMP traps generated by alerts?

Steps to Reproduce:  
Error Message:  
Defect Number:  
Enhancement Number:  
Cause:  
Resolution:

Alert SNMP traps are described in the Flowmon Monitoring Center MIB file

The following OIDs are used:

  • 1.3.6.1.4.1.39499.1.0.1 - alert (notification-type)

OID parts explained:

  • 1.3.6.1.4.1 - enterprise OID (http://oid-info.com/get/1.3.6.1.4.1)
  • 39499 - flowmon enterprise identifier
  • 1 - flowmon
  • 0 - fmc

Traps must have zero indexes in order to be able to translate "alert" into TRAP_TYPE or SNMPv1 Trap-PDU.

  • 1.3.6.1.4.1.39499.1.2.1 - alertName
  • 1.3.6.1.4.1.39499.1.2.2 - alertTriggerCondition
  • 1.3.6.1.4.1.39499.1.2.3 - alertTriggerValueLow
  • 1.3.6.1.4.1.39499.1.2.5 - alertTriggerValueHigh
  • 1.3.6.1.4.1.39499.1.2.6 - alertTimeStamp
  • 1.3.6.1.4.1.39499.1.2.4 - alertDetails
  • 1.3.6.1.4.1.39499.1.2.7 - alertDisplayName

OID parts explained:

  • 1.3.6.1.4.1 - enterprise OID (http://oid-info.com/get/1.3.6.1.4.1)
  • 39499 - flowmon enterprise identifier
  • 1 - flowmon
  • 2 - fmc

Description:

  • alertName -> Alert name
  • alertTriggerCondition -> Alert trigger condition description
  • alertTriggerValueLow -> Value of flows, bytes or packets that triggered the alert low 32bit
  • alertTriggerValueHigh -> Value of flows, bytes or packets that triggered the alert high 32 bit
  • alertTimeStamp -> Timestamp when alert was triggered
  • alertDetails -> Alert details
  • alertDisplayName -> Alert display name

It is possible to import MIB to Wireshark to analyze the trap if necessary:

  • Rename the MIB file to flowmonFmcMIB.txt (object name)
  • Wireshark - Preferences - Name Resolution - SMI paths - add a path to the folder where MIB is located
  • Wireshark - Preferences - Name Resolution - SMI modules - add "flowmonFmcMIB"
  • Wireshark - Preferences - Name Resolution - Enable OID resolution
  • Restart Wireshark

Wireshark_kU0abLUDh6.png

Workaround:  
Notes: https://support.kemptechnologies.com/hc/en-us/articles/4406088157581-Flowmon-SNMP-MIBs

Was this article helpful?
0 out of 0 found this helpful

Comments