Skip to main content

SNMP Trap Monitoring

Overview​

One of the key features of Motadata ObserveOps (formerly known as AIOps) is its ability to monitor and analyze SNMP traps. SNMP (Simple Network Management Protocol) is a standard protocol used for managing and monitoring network devices.

By leveraging SNMP traps, ObserveOps is able to provide instant notifications for critical events occurring within your network environment. This allows you to identify and resolve issues before they make a massive impact on your business operations. With the ObserveOps trap explorer, you can easily view the traps being sent by your infrastructure devices and gain valuable insights into your network performance.

When there is a very large count of devices in an infrastructure, requesting data from several devices to monitor them seems like a very inefficient option. This brings SNMP traps into the picture. Instead of ObserveOps going to every device and seeking information for monitoring, we can configure network devices to send traps to ObserveOps as and when needed to inform ObserveOps about any device health related issue.

SNMP Trap is a passive mode of monitoring that helps us to detect any concerns related to device health that occurs between the two polls. This ensures that any major event that occurs between two polls is not missed because sending SNMP traps does not require polling of data from monitors.

In this section, we will provide step-by-step instructions on how to send SNMP traps to Motadata ObserveOps for monitoring, as well as understand the SNMP traps processing mechanism in ObserveOps, followed by guidance on how to view the traps in ObserveOps. This will ensure the optimal performance and reliability of your network infrastructure.

Pre-requisites for SNMP Trap Monitoring in ObserveOps​

  • Configure devices to send SNMP traps to the Motadata ObserveOps server.
  • Make sure the UDP port 1620 and 1630 are open on the server for SNMP v1/v2c and SNMP v3 respectively.
  • The SNMP trap listener has to be configured on the Motadata ObserveOps server.