Join fellow LogicMonitor users at the Elevate Community Conference and get hands-on with our latest product innovations.

Register Now

Resources

Explore our blogs, guides, case studies, eBooks, and more actionable insights to enhance your IT monitoring and observability.

View Resources

About us

Get to know LogicMonitor and our team.

About us

Documentation

Read through our documentation, check out our latest release notes, or submit a ticket to our world-class customer service team.

View Resources

Troubleshooting SNMP Traps Issues

Last updated on 21 April, 2025

SNMP trap type LogSource enables LogicMonitor Collector to ingest SNMP traps to LogicMonitor logs without configuring alerts. While using SNMP v1, v2c, and v3 traps if you get errors, you can troubleshoot them.

Not In Time Window Error

When processing SNMP v3 traps, you may get the following error message in the Wrapper log:

error=Not in time window

The message indicates that due to authentication failure, the collector cannot process SNMP v3 traps.

Some of the known causes of the error are:

  • The SNMP v3 trap sender’s snmpEngineTime value in the incoming trap differs by more than 150 seconds (ahead or behind) from the trap sender’s snmpEngineTime value cached by the receiver (collector).
  • The sender and receiver’s system clocks are not in sync.

Resolving Not in Time Window Issue

To resolve the issue, follow these guidelines:

  • Restart the SNMP service on the trap sender’s machine.
  • Ensure that the sender and receiver’s system clocks are in sync.
In This Article

Start Your Trial

Full access to the LogicMonitor platform.
Comprehensive monitoring and alerting for unlimited devices.