graham/towerops-agent
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix: increase SNMP timeout to 120s for SNMPv3 discovery

Browse source 
Discovery with SNMPv3 was completing in 52 seconds, dangerously close
to the 60s timeout. Increasing to 120s provides comfortable headroom
for complete MikroTik OID tree traversal with encryption overhead.
This commit is contained in:
Graham McIntire 2026-02-05 09:02:05 -06:00
parent 357d1711be
commit d44682ce9c
No known key found for this signature in database
2 changed files with 6 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
src/snmp/client.rs
View file

@ -3,10 +3,10 @@ use crate::secret::SecretString;
use snmp2::SyncSession;
use std::time::Duration;
// SNMP timeout in seconds - increased to 60s for SNMPv3 operations
// SNMP timeout in seconds - increased to 90s for SNMPv3 operations
// SNMPv3 has significant encryption/auth overhead, especially for large walks
// MikroTik enterprise tree (1.3.6.1.4.1.14988) can take 16+ seconds with v3
const SNMP_TIMEOUT_SECS: u64 = 60;
// Full discovery can take 50+ seconds with complete MikroTik OID tree traversal
const SNMP_TIMEOUT_SECS: u64 = 90;
/// SNMPv3 configuration bundle
#[derive(Clone)]

5
src/snmp/device_poller.rs
View file

@ -6,9 +6,10 @@ use std::str::FromStr;
use std::time::Duration;
use tokio::sync::{mpsc, oneshot};
// SNMP timeout in seconds - increased to 60s for SNMPv3 operations
// SNMP timeout in seconds - increased to 90s for SNMPv3 operations
// SNMPv3 has significant encryption/auth overhead
const SNMP_TIMEOUT_SECS: u64 = 60;
// Full discovery can take 50+ seconds with complete MikroTik OID tree traversal
const SNMP_TIMEOUT_SECS: u64 = 90;
/// Request to perform an SNMP operation
#[derive(Debug)]