Hi, Failure Reason: SNMPv3 - Not in Time Windows - The agent determined that the packets timeliness was not within the threshold. Do another discovery to re-synchronize. This is the error shown by my customer when doing snmp walk, i saw the resolution online. CAUSEThis is an environmental issue and is not related to SolarWinds software.RESOLUTION * Assuming that you have SNMP v3 correctly configured on the nodes and on NCM, check the packet timeout by going to File > Settings > Network > SNMP Settings. * If your timeout setting is expiring before the job is complete, adjust the top bar according to your preferences. Use 3000ms and check the results with SNMP v3. Alternatively, you can bounce the SNMP daemon to resolve the issue. So may i ask this resolution should be done by me or my customer?

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

SNMPv3 password

Hi,

Failure Reason: SNMPv3 - Not in Time Windows - The agent determined that the packets timeliness was not within the threshold. Do another discovery to re-synchronize.

This is the error shown by my customer when doing snmp walk, i saw the resolution online.

CAUSE

This is an environmental issue and is not related to SolarWinds software.

RESOLUTION

Assuming that you have SNMP v3 correctly configured on the nodes and on NCM, check the packet timeout by going to File > Settings > Network > SNMP Settings.
If your timeout setting is expiring before the job is complete, adjust the top bar according to your preferences. Use 3000ms and check the results with SNMP v3.

Alternatively, you can bounce the SNMP daemon to resolve the issue.

So may i ask this resolution should be done by me or my customer?

Find more posts tagged with

Accepted answers

All comments

Zack_Diddy

Hi,

Does anybody have an idea regarding this?

marcrobinson

I dont think that I have seen this exact message before, but both links below state that the snmp request is taking too long and timing out. Increase the timeout on the SNMP polling settings to 3000 ms. Looks like default is 2500 ms, so increasing by half a second. They both say that the timeout can be increased on the target node too.

Soo, to answer the question of who does what - yes you can increase the snmp timeout on the solarwinds server. Updating the node itself - depends on who configures the snmp for the monitored node (dont recall ever needing that bit done).

If they are using the solarwinds snmpwalk tool, this can be changed on the fly and tested. It is located in the solarwinds installation directory. //%program files%/Solarwinds/Orion/Snmpwalk.exe. This is great troubleshooting tool. It can use it with SNMP v2 and v3.

SNMPv3 Error - Not in Time Windows - The agent determined that the packets timeliness was not within the threshold (site.com)

Inventory Failure Reason: SNMPv3 - Not in Time Windows (site.com)