We’ve been analyzing an SNMP walk from one Edge-Core switches and noticed it returns non-consecutive interface indexes (like 1, 2, 54, 746, 1001, 1404, etc.).

Our driver polls the ifTable using this configuration:

OID

type="complete"

options=";instance;multipleGetNext"

I understand that this method assumes consecutive indexes and uses incremental GetNext requests instead of performing a full SNMP walk.
It works well with most models but can miss higher or non-sequential indexes — for example, VLAN or loopback interfaces.

I’d like to understand the design reasoning behind this choice, since it is not returning any information in one of our customers.

Any insights from those who’ve worked on similar drivers or protocols would be great.