Low level discovery works for some SNMP tables but I seem to have a problem with a table where the indexes do not start at 0 or 1.
The table contents looks like this:
VIPRINET-MIB::vpnRouterTunnelChannelIndex.100 = INTEGER: 0
VIPRINET-MIB::vpnRouterTunnelChannelIndex.101 = INTEGER: 0
VIPRINET-MIB::vpnRouterTunnelChannelIndex.102 = INTEGER: 0
VIPRINET-MIB::vpnRouterTunnelChannelIndex.103 = INTEGER: 0
VIPRINET-MIB::vpnRouterTunnelChannelIndex.104 = INTEGER: 0
I have used the same setup as other tables: discovery rule on the table entry and using the VIPRINET-MIB::vpnRouterTunnelChannelIndex.{#SNMPINDEX} for items
Although there is a server log, it is not helpful in detecting what went wrong.
Any suggestions on fixing this issue?
The table contents looks like this:
VIPRINET-MIB::vpnRouterTunnelChannelIndex.100 = INTEGER: 0
VIPRINET-MIB::vpnRouterTunnelChannelIndex.101 = INTEGER: 0
VIPRINET-MIB::vpnRouterTunnelChannelIndex.102 = INTEGER: 0
VIPRINET-MIB::vpnRouterTunnelChannelIndex.103 = INTEGER: 0
VIPRINET-MIB::vpnRouterTunnelChannelIndex.104 = INTEGER: 0
I have used the same setup as other tables: discovery rule on the table entry and using the VIPRINET-MIB::vpnRouterTunnelChannelIndex.{#SNMPINDEX} for items
Although there is a server log, it is not helpful in detecting what went wrong.
Any suggestions on fixing this issue?