No such instance ошибка snmp 223

I am able to retrieve the SNMP information RFC1213-mib using the SnmpB tool but when I add these variables to the PRTG I get No such instance (SNMP error # 223) errors messages.

I have tried using auto discovery and manually adding the OIDs 1.3.6.1.2.1.2.2.1.8 and none of them work.

This is what is retrieved by the SnmpB tool.

1: sysDescr.0 Raven XE EV-DO
2: sysObjectID.0 airlink.12.20
3: sysUpTimeInstance 7:18:54.22
4: sysContact.0 
5: sysName.0 
6: sysLocation.0 
7: sysServices.0 76
8: ifNumber.0 1
9: ifIndex.1 1
10: ifDescr.1 Sierra Wireless Ethernet Port
11: ifType.1 ethernetCsmacd(6)
12: ifMtu.1 1500
13: ifSpeed.1 100000000
14: ifPhysAddress.1 00:14:3e:04:01:26
15: ifAdminStatus.1 up(1)
16: ifOperStatus.1 up(1)
17: ifInOctets.1 4000317
18: ifOutOctets.1 3394212

mib2
prtg
snmp

Вернуться в «Коммутаторы и маршрутизаторы Ethernet»

Hi,

I’m referring to an older question of another User in this Forum (http://www.lansweeper.com/Forum/yaf_postst11320findunread_Any-way-of-debugging-SNMP-v3-queries.aspx#post42246)

We encountered a similar problem, that our Alcatel Switches are not able to be scanned via SNMP v3 through Lansweeper. Even the device-Tester is not able to get a reply from those devices. We double-checked everything, authentication, connection and even with a secondary tool (Paessler) to check if anything is possible.

First thing we found with Paessler:

1.3.6.1.2.1.1.2.0 works
1.3.6.1.2.1.1.2 not

———————— New Test ————————
Paessler SNMP Tester 5.2.3 Computername: xxxxxx Interface: (10.XX.X.50)
04.01.2017 14:27:20 (22 ms) : Device: 10.XX.XXX.11
04.01.2017 14:27:20 (49 ms) : SNMP V3
04.01.2017 14:27:20 (54 ms) : Custom OID 1.3.6.1.2.1.1.2
04.01.2017 14:27:20 (183 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHINSTANCE
04.01.2017 14:27:20 (193 ms) : ——-
04.01.2017 14:27:20 (216 ms) : Value: No such instance (SNMP error # 223)
04.01.2017 14:27:20 (220 ms) : Done

———————— New Test ————————
Paessler SNMP Tester 5.2.3 Computername: xxxxxx Interface: (10.XX.X.50)
04.01.2017 14:27:25 (19 ms) : Device: 10.XX.XXX.11
04.01.2017 14:27:25 (29 ms) : SNMP V3
04.01.2017 14:27:25 (39 ms) : Custom OID 1.3.6.1.2.1.1.2.0
04.01.2017 14:27:25 (151 ms) : SNMP Datatype: ASN_OBJECT_ID
04.01.2017 14:27:25 (157 ms) : ——-
04.01.2017 14:27:25 (163 ms) : Value: 1.3.6.1.4.1.6486.800.1.1.2.1.10.1.6
04.01.2017 14:27:25 (169 ms) : Done

Paessler shows that the Custom OID used by Lansweeper device-tester seems to be incorrect / not showing a result. The same OID added with a «.0» gives the result desired.

We already had contact via EMail to Lansweeper support but ended in «Please monitor the traffic between Lansweeper and the device with Wireshark» that then has been too much hassle for us. As shown above the main thing might be the OID.

Would someone be able to assist us in this matter? Could it be that the device-tester needs to be changed / fixed?

Another, second problem:
When those switches are stacked they will be recognized as ONE Element only (we did this with SNMPv2) and if you try to enter the stacks manually they will be merged to the master (without adding hardware-information / serial-no., etc.) to the lansweeper database afterwards.

Is there a chance to get at least the details of the merged element(s) to the entry of the stack?

Thanks in advance for any help,
Martin!

Hi,

I try it, but i have some errors. I’m trying to query data from my fortigate.
I get these errors:

/opt/splunk/etc/apps/snmp_ta/bin/snmp.py" Traceback (most recent call last):
/opt/splunk/etc/apps/snmp_ta/bin/snmp.py"   File "/opt/splunk/etc/apps/snmp_ta/bin/snmp.py", line 492, in <module>
/opt/splunk/etc/apps/snmp_ta/bin/snmp.py"     do_run()
/opt/splunk/etc/apps/snmp_ta/bin/snmp.py"   File "/opt/splunk/etc/apps/snmp_ta/bin/snmp.py", line 316, in do_run
/opt/splunk/etc/apps/snmp_ta/bin/snmp.py"     lookupNames=True, lookupValues=True)
/opt/splunk/etc/apps/snmp_ta/bin/snmp.py" UnboundLocalError: local variable 'oid_args' referenced before assignment

In my splunk index:

FORTINET-FORTIGATE-MIB::fgSysCpuUsage."" = "No Such Instance currently exists at this OID" 
FORTINET-CORE-MIB::fnSysSerial."" = "No Such Instance currently exists at this OID"

With MibViewer I have received the snmp reply:

Send snmp get request to x.x.x.x:161
.1.3.6.1.4.1.12356.100.1.1.1.0 (not in loaded mib files) --> FG600C3912801998

Send snmp get request to x.x.x.x1:161
.1.3.6.1.4.1.12356.101.4.1.3.0 (not in loaded mib files) --> 0