SNMP::V3::Session
Constants
The largest snmpEngineBoots value; reaching it forces a re-keying (RFC 3414 3.2.7).
RFC 3414 3.2.7 tolerated clock skew for inbound authenticated messages. Distinct from TIMELINESS_THRESHOLD above, which drives local re-probing.
Timeliness is part of SNMP V3 Security The topic is described very nice here https://www.snmpsharpnet.com/?page_id=28 https://www.ietf.org/rfc/rfc2574.txt 1.4.1 Timeliness The probe is outdated after 150 seconds which results in a PDU Error, therefore it should expire before that and be renewed The 150 Seconds is specified in https://www.ietf.org/rfc/rfc2574.txt 2.2.3
Constructors
Instance methods
Enforce the RFC 3414 3.2.7 time window on an inbound authenticated message and advance the local notion of the remote engine's (boots, time).
Only authenticated messages carry a meaningful timeliness, and a baseline
must already have been established (via discovery/validate); otherwise the
call is a no-op. Raises Security::NotInTimeWindowError on a replayed or
out-of-window message.
Multi-varbind Get: one GetRequest carrying every OID (RFC 3416), answered by a single Response with N varbinds.
GetBulk (RFC 3416): up to max_repetitions successors per repeating varbind in one round-trip; the first non_repeaters OIDs act as plain GetNext.
Decode a v3 message, rejecting any other version. security defaults to this
session's so the HMAC is verified and the message timeliness checked; pass
nil to decode without verification (e.g. an engine-discovery probe).
Re-sync the local engine identity / clock from an authoritative message (typically a usmStats Report), so a retried request carries fresh values. The engine id is only overwritten when the message actually carries one.
Multi-varbind Set: one SetRequest assigning every OID => value pair (Hash keeps insertion order).