Hi,
Here I got response from switch manufacturer:
Cause
These OIDs are time-filtered, so per the RFCs (e.g. RFC3512, RFC4502) must return entries for all valid timeMarks.
The SNMP browser should understand the behavior of a timeFiltered MIB and move on after seeing the timeFilter index increment. However, not all browsers behave in this manner.
Solution/Workaround
Ensure you are using an appropriate SNMP tool - such as NetSight MIB tools - that behaves correctly.
Workaround:
DFE firmware 6.01.01.0020 introduced a new command which can accommodate SNMP browsers that are not timeFilter-aware.
Release notes state, in the "Software Changes and Enhancements" section:
A new SNMP control, "set snmp timefilter break", allows users to configure the
GET-NEXT behavior of MIBs indexed with timeMark. When this is set to 'enabled',
SNMP will not return incrementing index values. Many SNMP tools do not properly
support timefiltered MIBs and will benefit from this new setting. When disabled,
SNMP returns RFC conformant indexing.
Here is the command syntax, as seen in a sample cli session:
NSeries(rw)->set snmp timefilter
Command: set snmp Create SNMP agent entries
Object: timefilter SNMP timefilter configuration
Usage: set snmp timefilter break {disable | enable}
So maybe NetXMS doesn't support timeFiltered MIBs, or it could be something else?
Best Regards,
Nikk