[ZBX-7595] Long SNMP OID Not supported Created: 2013 Dec 28  Updated: 2017 May 30  Resolved: 2016 Sep 23

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P), Server (S)
Affects Version/s: 2.2.1
Fix Version/s: 2.2.15rc1, 3.0.5rc1, 3.2.1rc1, 3.4.0alpha1

Type: Incident report Priority: Major
Reporter: Nick Zolot Assignee: Unassigned
Resolution: Fixed Votes: 1
Labels: item, oid, snmp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Hello, I have a problem with long SNMP OID item. The OID is: ifInUcastPkts.4194304000

If I will try snmpget from console, everything works fine:
snmpget -v 2c -c public 172.22.1.140 ifInUcastPkts.4194304000
IF-MIB::ifInUcastPkts.4194304000 = Counter32: 61556752

But in zabbix, item with this OID falls in "Not supported" status.
If I change OID to shorter one, for example ifInUcastPkts.234954816 (this is oid from port of the same device) it works fine.

The device is Huawei MA5680T chassis



 Comments   
Comment by Petr Petrovic [ 2014 Jun 27 ]

Hello,
I have the same problem.

When I try snmpwalk from console, it works fine:
snmpwalk -v2c -cpublic 192.168.250.2 ifInOctets
...
IF-MIB::ifInOctets.234938496 = Counter32: 0
IF-MIB::ifInOctets.234938560 = Counter32: 0
IF-MIB::ifInOctets.4194304000 = Counter32: 2879295579
IF-MIB::ifInOctets.4194304256 = Counter32: 1700152257
...

but snmpget of single value is not working:
snmpget -v2c -cpublic 192.168.250.2 ifInOctets.4194304000
ifInOctets.4194304000: Unknown Object Identifier (Index out of range: 4194304000 (ifIndex))

Execution of snmpwalk for IfIndexes returns following values:
snmpwalk -v2c -cpublic 192.168.250.2 ifIndex
...
IF-MIB::ifIndex.234938496 = INTEGER: 234938496
IF-MIB::ifIndex.234938560 = INTEGER: 234938560
IF-MIB::ifIndex.4194304000 = INTEGER: -100663296
IF-MIB::ifIndex.4194304256 = INTEGER: -100663040
...

I'm using Zabbix 2.2.4 and NET-SNMP v. 5.5-49.

The device is Huawei MA5603T.

Comment by Nick Zolot [ 2014 Jun 27 ]

Hello, Petr Petrovic. We've resolve this problem with our chassis. It isn't very good, but its working. If you would like to, we can have some conversation via email ( my email is [email protected], I'd like to speak about huawei devices, best practices, and some other stuff).
The problem is in IF-MIB oid tree, and the way NET-SNMP uses it. Its not zabbix problem. I found resolution in external check. I've made some template, which is based on "SNMP Interfaces Template", but I'm using external script, instead of SNMPGET. For example, if you use:

snmpget -v 2c -c public ipaddress ifInOctets.4194304000, u'll get
ifInOctets.4194304000: Unknown Object Identifier (Index out of range: 4194304000 (ifIndex))

but if you'll use:
snmpget -v 2c -c public -Ir ipaddress ifInOctets.4194304000, u'll get
IF-MIB::ifInOctets.4194304000 = Counter32: 2232987660

Option "-Ir" stands for
-I INOPTS Toggle various defaults controlling input parsing:
r: do not check values for range/type legality
(its is from net-snmp help)

Hope, it will help you. And I'd really like to have conversation with you. Good luck!

Comment by Pavel Savasin [ 2014 Sep 15 ]

Hello. I have same problem with Huawei S5700, S5710 and S9703 swithes.
On version 2.0.2 zabbix can get OID hwMemoryDevFree.0.0.0 ( also hwMemoryDevSize.0.0.0, hwCpuDevDuty.0.0.0) , but on version 2.2.6 this OID is 'Not supported'
Could you share your solution for similar problems?

Comment by Vladislavs Sokurenko [ 2016 Sep 02 ]

Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-7595
version 2.2

Fix for OID higher than MAX_INT to be accepted.
noRangeCheck yes disables the validation of varbind values against the MIB definition for the relevant OID. This is equivalent to the -Ir option.

Tested SNMP OID: "ifInOctets.4194304000"

Before fix:
Error not supported.

After fix:
Works.

Comment by Andris Mednis [ 2016 Sep 21 ]

(1) In zbx_snmp_print_oid() there is a check for netsnmp_ds_set_boolean() return code. In modified zbx_snmp_open_session() return code from netsnmp_ds_set_boolean() is not checked. I would recommend to add the check.

vso RESOLVED in r62653.

andris Reviewed. Please look into small changes r62679.

vso Reviewed. Please look into small changes r62684.

andris Thanks, reviewed.

Comment by Vladislavs Sokurenko [ 2016 Sep 22 ]

Merged in:
2.2.15rc1 r62698
3.0.5rc1 r62699
3.2.1rc1 r62700
3.3.0 (trunk) r62706

Generated at Wed Apr 30 06:21:46 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.