What is the difference between max_repetitions and maxoids?
Why would you lower max_repetitions or maxoids?
You would lower max_repetitions when a device is responding to SNMP, but it cannot reliably handle large SNMP GETBULK requests. Statseeker uses GETBULK during discovery and rewalks to retrieve multiple OIDs in a single request. A higher value is more efficient, but some devices, firewalls, UPSs, wireless controllers, and older network gear struggle with large responses
https://docs.statseeker.com/administration/snmp-config/
You would lower MaxOIDs when a device can be discovered successfully but has trouble keeping up with ongoing polling requests. Statseeker specifically recommends reducing MaxOIDs if a device responds to SNMP walks but reporting is missing, intermittent, or generating SNMP polling issues.
MaxOIDs is the polling equivalent of max_repetitions.
- max_repetitions controls how many OIDs are requested per SNMP GETBULK during Discovery/Rewalk.
- MaxOIDs controls how many OIDs are requested per SNMP polling request during normal data collection
Summary
| MaxOIDs | Max Repetitions |
|---|---|
| Limits OIDs requested | Limits table rows returned |
| Primarily request size control | Primarily response size control |
| Used heavily in older polling models | Used with SNMP GETBULK polling |
MaxOIDs controls the maximum number of OIDs included in a single SNMP request.
For example:
- MaxOIDs = 10
- Statseeker needs to collect 100 interface counters
- Statseeker sends approximately 10 requests containing 10 OIDs each
A lower value:
- Generates more SNMP packets
- Reduces the amount of data returned per packet
- Can help with devices that have limited SNMP capabilities
A higher value:
- Reduces packet count
- Improves polling efficiency
- May cause some devices to timeout or truncate responses
Max Repetitions is an SNMPv2/v3 GETBULK parameter defined by the SNMP protocol itself.
It specifies how many rows of a table the device should return for each requested OID during a GETBULK operation.
For example:
If Statseeker requests:
ifDescr ifInOctets ifOutOctets
and:
max_repetitions = 25
the device may return up to:
25 ifDescr entries 25 ifInOctets entries 25 ifOutOctets entries
in a single response.
A higher value:
- Fewer SNMP requests
- Faster discovery and polling
- Larger response packets
- Greater risk of timeouts, packet fragmentation, or buggy device behavior
A lower value:
- More requests required
- Less efficient polling
- Often more reliable for firewalls, WAN links, and older devices
For more information on how to modify max_repetitions please see the following article:
Why does my SNMP device not return all data?