Support for long and string SNMP indexes - zabbix 2.2

[pjelou]

Hi!
I'm trying to monitor several Mikrotik routers with zabbix 2.2 I want to use LLD of SNMP OIDs and monitor these values:

snmpwalk -m ALL -v 2c -c public 10.1.1.25 mtxr 2>%1 | grep Rtab
MIKROTIK-MIB::mtxrWlRtabAddr.'..Bb..'.4 = STRING: 0:c:42:62:ed:b8
MIKROTIK-MIB::mtxrWlRtabAddr.'..B{O.'.13 = STRING: 0:c:42:7b:4f:b7
MIKROTIK-MIB::mtxrWlRtabAddr.'..B{P.'.1693 = STRING: 0:c:42:7b:50:15
MIKROTIK-MIB::mtxrWlRtabStrength.'..Bb..'.4 = INTEGER: -57
MIKROTIK-MIB::mtxrWlRtabStrength.'..B{O.'.13 = INTEGER: -57
MIKROTIK-MIB::mtxrWlRtabStrength.'..B{P.'.1693 = INTEGER: -79
MIKROTIK-MIB::mtxrWlRtabTxBytes.'..Bb..'.4 = Counter32: 1403192725
MIKROTIK-MIB::mtxrWlRtabTxBytes.'..B{O.'.13 = Counter32: 471748537
MIKROTIK-MIB::mtxrWlRtabTxBytes.'..B{P.'.1693 = Counter32: 3501943253
MIKROTIK-MIB::mtxrWlRtabRxBytes.'..Bb..'.4 = Counter32: 1407096665
MIKROTIK-MIB::mtxrWlRtabRxBytes.'..B{O.'.13 = Counter32: 57091893
MIKROTIK-MIB::mtxrWlRtabRxBytes.'..B{P.'.1693 = Counter32: 524033999
MIKROTIK-MIB::mtxrWlRtabTxPackets.'..Bb..'.4 = Counter32: 317406075
MIKROTIK-MIB::mtxrWlRtabTxPackets.'..B{O.'.13 = Counter32: 2467100
MIKROTIK-MIB::mtxrWlRtabTxPackets.'..B{P.'.1693 = Counter32: 17857918
MIKROTIK-MIB::mtxrWlRtabRxPackets.'..Bb..'.4 = Counter32: 227006377
MIKROTIK-MIB::mtxrWlRtabRxPackets.'..B{O.'.13 = Counter32: 323986
MIKROTIK-MIB::mtxrWlRtabRxPackets.'..B{P.'.1693 = Counter32: 3519667
MIKROTIK-MIB::mtxrWlRtabTxRate.'..Bb..'.4 = Gauge32: 240000000
MIKROTIK-MIB::mtxrWlRtabTxRate.'..B{O.'.13 = Gauge32: 150000000
MIKROTIK-MIB::mtxrWlRtabTxRate.'..B{P.'.1693 = Gauge32: 60000000
MIKROTIK-MIB::mtxrWlRtabRxRate.'..Bb..'.4 = Gauge32: 240000000
MIKROTIK-MIB::mtxrWlRtabRxRate.'..B{O.'.13 = Gauge32: 150000000
MIKROTIK-MIB::mtxrWlRtabRxRate.'..B{P.'.1693 = Gauge32: 54000000
MIKROTIK-MIB::mtxrWlRtabRouterOSVersion.'..Bb..'.4 = STRING: 
MIKROTIK-MIB::mtxrWlRtabRouterOSVersion.'..B{O.'.13 = STRING: 
MIKROTIK-MIB::mtxrWlRtabRouterOSVersion.'..B{P.'.1693 = STRING: 
MIKROTIK-MIB::mtxrWlRtabUptime.'..Bb..'.4 = Timeticks: (42359500) 4 days, 21:39:55.00
MIKROTIK-MIB::mtxrWlRtabUptime.'..B{O.'.13 = Timeticks: (11136300) 1 day, 6:56:03.00
MIKROTIK-MIB::mtxrWlRtabUptime.'..B{P.'.1693 = Timeticks: (42388100) 4 days, 21:44:41.00
MIKROTIK-MIB::mtxrWlRtabSignalToNoise.'..Bb..'.4 = INTEGER: 51
MIKROTIK-MIB::mtxrWlRtabSignalToNoise.'..B{O.'.13 = INTEGER: 50
MIKROTIK-MIB::mtxrWlRtabSignalToNoise.'..B{P.'.1693 = INTEGER: 33
MIKROTIK-MIB::mtxrWlRtabTxStrengthCh0.'..Bb..'.4 = INTEGER: -61
MIKROTIK-MIB::mtxrWlRtabTxStrengthCh0.'..B{O.'.13 = INTEGER: -63
MIKROTIK-MIB::mtxrWlRtabTxStrengthCh0.'..B{P.'.1693 = INTEGER: -77
MIKROTIK-MIB::mtxrWlRtabRxStrengthCh0.'..Bb..'.4 = INTEGER: -61
MIKROTIK-MIB::mtxrWlRtabRxStrengthCh0.'..B{O.'.13 = INTEGER: -57
MIKROTIK-MIB::mtxrWlRtabRxStrengthCh0.'..B{P.'.1693 = INTEGER: -79
MIKROTIK-MIB::mtxrWlRtabTxStrengthCh1.'..Bb..'.4 = INTEGER: -61
MIKROTIK-MIB::mtxrWlRtabTxStrengthCh1.'..B{O.'.13 = INTEGER: 0
MIKROTIK-MIB::mtxrWlRtabTxStrengthCh1.'..B{P.'.1693 = INTEGER: 0
MIKROTIK-MIB::mtxrWlRtabRxStrengthCh1.'..Bb..'.4 = INTEGER: -60
MIKROTIK-MIB::mtxrWlRtabRxStrengthCh1.'..B{O.'.13 = INTEGER: 0
MIKROTIK-MIB::mtxrWlRtabRxStrengthCh1.'..B{P.'.1693 = INTEGER: 0
MIKROTIK-MIB::mtxrWlRtabTxStrengthCh2.'..Bb..'.4 = INTEGER: -96
MIKROTIK-MIB::mtxrWlRtabTxStrengthCh2.'..B{O.'.13 = INTEGER: 0
MIKROTIK-MIB::mtxrWlRtabTxStrengthCh2.'..B{P.'.1693 = INTEGER: 0
MIKROTIK-MIB::mtxrWlRtabRxStrengthCh2.'..Bb..'.4 = INTEGER: -96
MIKROTIK-MIB::mtxrWlRtabRxStrengthCh2.'..B{O.'.13 = INTEGER: 0
MIKROTIK-MIB::mtxrWlRtabRxStrengthCh2.'..B{P.'.1693 = INTEGER: 0
MIKROTIK-MIB::mtxrWlRtabEntryCount.0 = Gauge32: 3

these values are represented with OIDs:

snmpwalk -m ALL -v 2c -c public 10.1.1.25 -On mtxr 2>%1
.1.3.6.1.4.1.14988.1.1.1.2.1.1.0.12.66.98.237.184.4 = STRING: 0:c:42:62:ed:b8
.1.3.6.1.4.1.14988.1.1.1.2.1.1.0.12.66.123.79.183.13 = STRING: 0:c:42:7b:4f:b7
.1.3.6.1.4.1.14988.1.1.1.2.1.1.0.12.66.123.80.21.1693 = STRING: 0:c:42:7b:50:15
.1.3.6.1.4.1.14988.1.1.1.2.1.3.0.12.66.98.237.184.4 = INTEGER: -57
.1.3.6.1.4.1.14988.1.1.1.2.1.3.0.12.66.123.79.183.13 = INTEGER: -57
.1.3.6.1.4.1.14988.1.1.1.2.1.3.0.12.66.123.80.21.1693 = INTEGER: -79
.1.3.6.1.4.1.14988.1.1.1.2.1.4.0.12.66.98.237.184.4 = Counter32: 1639744120
.1.3.6.1.4.1.14988.1.1.1.2.1.4.0.12.66.123.79.183.13 = Counter32: 474496865
.1.3.6.1.4.1.14988.1.1.1.2.1.4.0.12.66.123.80.21.1693 = Counter32: 3504711740
.1.3.6.1.4.1.14988.1.1.1.2.1.5.0.12.66.98.237.184.4 = Counter32: 1475879196
.1.3.6.1.4.1.14988.1.1.1.2.1.5.0.12.66.123.79.183.13 = Counter32: 57343723
.1.3.6.1.4.1.14988.1.1.1.2.1.5.0.12.66.123.80.21.1693 = Counter32: 524287844
.1.3.6.1.4.1.14988.1.1.1.2.1.6.0.12.66.98.237.184.4 = Counter32: 317824849
.1.3.6.1.4.1.14988.1.1.1.2.1.6.0.12.66.123.79.183.13 = Counter32: 2486545
.1.3.6.1.4.1.14988.1.1.1.2.1.6.0.12.66.123.80.21.1693 = Counter32: 17877555
.1.3.6.1.4.1.14988.1.1.1.2.1.7.0.12.66.98.237.184.4 = Counter32: 227247181
.1.3.6.1.4.1.14988.1.1.1.2.1.7.0.12.66.123.79.183.13 = Counter32: 325772
.1.3.6.1.4.1.14988.1.1.1.2.1.7.0.12.66.123.80.21.1693 = Counter32: 3521466
.1.3.6.1.4.1.14988.1.1.1.2.1.8.0.12.66.98.237.184.4 = Gauge32: 240000000
.1.3.6.1.4.1.14988.1.1.1.2.1.8.0.12.66.123.79.183.13 = Gauge32: 150000000
.1.3.6.1.4.1.14988.1.1.1.2.1.8.0.12.66.123.80.21.1693 = Gauge32: 60000000
.1.3.6.1.4.1.14988.1.1.1.2.1.9.0.12.66.98.237.184.4 = Gauge32: 240000000
.1.3.6.1.4.1.14988.1.1.1.2.1.9.0.12.66.123.79.183.13 = Gauge32: 135000000
.1.3.6.1.4.1.14988.1.1.1.2.1.9.0.12.66.123.80.21.1693 = Gauge32: 60000000
.1.3.6.1.4.1.14988.1.1.1.2.1.10.0.12.66.98.237.184.4 = STRING: 
.1.3.6.1.4.1.14988.1.1.1.2.1.10.0.12.66.123.79.183.13 = STRING: 
.1.3.6.1.4.1.14988.1.1.1.2.1.10.0.12.66.123.80.21.1693 = STRING: 
.1.3.6.1.4.1.14988.1.1.1.2.1.11.0.12.66.98.237.184.4 = Timeticks: (42458000) 4 days, 21:56:20.00
.1.3.6.1.4.1.14988.1.1.1.2.1.11.0.12.66.123.79.183.13 = Timeticks: (11234900) 1 day, 7:12:29.00
.1.3.6.1.4.1.14988.1.1.1.2.1.11.0.12.66.123.80.21.1693 = Timeticks: (42486700) 4 days, 22:01:07.00
.1.3.6.1.4.1.14988.1.1.1.2.1.12.0.12.66.98.237.184.4 = INTEGER: 51
.1.3.6.1.4.1.14988.1.1.1.2.1.12.0.12.66.123.79.183.13 = INTEGER: 49
.1.3.6.1.4.1.14988.1.1.1.2.1.12.0.12.66.123.80.21.1693 = INTEGER: 32
.1.3.6.1.4.1.14988.1.1.1.2.1.13.0.12.66.98.237.184.4 = INTEGER: -61
.1.3.6.1.4.1.14988.1.1.1.2.1.13.0.12.66.123.79.183.13 = INTEGER: -63
.1.3.6.1.4.1.14988.1.1.1.2.1.13.0.12.66.123.80.21.1693 = INTEGER: -77
.1.3.6.1.4.1.14988.1.1.1.2.1.14.0.12.66.98.237.184.4 = INTEGER: -62
.1.3.6.1.4.1.14988.1.1.1.2.1.14.0.12.66.123.79.183.13 = INTEGER: -57
.1.3.6.1.4.1.14988.1.1.1.2.1.14.0.12.66.123.80.21.1693 = INTEGER: -79
.1.3.6.1.4.1.14988.1.1.1.2.1.15.0.12.66.98.237.184.4 = INTEGER: -61
.1.3.6.1.4.1.14988.1.1.1.2.1.15.0.12.66.123.79.183.13 = INTEGER: 0
.1.3.6.1.4.1.14988.1.1.1.2.1.15.0.12.66.123.80.21.1693 = INTEGER: 0
.1.3.6.1.4.1.14988.1.1.1.2.1.16.0.12.66.98.237.184.4 = INTEGER: -61
.1.3.6.1.4.1.14988.1.1.1.2.1.16.0.12.66.123.79.183.13 = INTEGER: 0
.1.3.6.1.4.1.14988.1.1.1.2.1.16.0.12.66.123.80.21.1693 = INTEGER: 0
.1.3.6.1.4.1.14988.1.1.1.2.1.17.0.12.66.98.237.184.4 = INTEGER: -96
.1.3.6.1.4.1.14988.1.1.1.2.1.17.0.12.66.123.79.183.13 = INTEGER: 0
.1.3.6.1.4.1.14988.1.1.1.2.1.17.0.12.66.123.80.21.1693 = INTEGER: 0
.1.3.6.1.4.1.14988.1.1.1.2.1.18.0.12.66.98.237.184.4 = INTEGER: -96
.1.3.6.1.4.1.14988.1.1.1.2.1.18.0.12.66.123.79.183.13 = INTEGER: 0
.1.3.6.1.4.1.14988.1.1.1.2.1.18.0.12.66.123.80.21.1693 = INTEGER: 0

I created a Discovery rule with SNMP OID: mtxrWlRtabAddr. The value of #SNMPINDEX is treated as string so it has these 3 values:

[B].'..Bb..'.4[/B]
[B].'..B{O.'.13 [/B]
[B].'..B{P.'.1693[/B]

I created item prototypes but these indexes are not working even not with snmpwalk.
Is there any way to force zabbix to use number reprezentation of SNMPINDEX instead of string so in SNMPINDEX will be these 3 values?

[B]0.12.66.98.237.184.4
0.12.66.123.79.183.13
0.12.66.123.80.21.1693
[/B]

I tried to edit the Discovery rule SNMP OID to the number representation of mtxrWlRtabAddr - .1.3.6.1.4.1.14988.1.1.1.2.1.1 but the value of SNMPINDEX was still a string.