What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Fixing SNMP error # 223 by extending OID

Votes:

0

Hello,

I read all the posts here on error 223 and couldn't figure out why snmpwalk AND Paessler SNMP Tester 5.2.3 returned the same 223 error when SNMPTester was in "Custom OID" request mode.

Had written a post requesting help when I spotted the solution: Turned out I had to add ".0" to the end of the OID.

According to the documentation, the OID should be 1.3.6.1.4.1.3375.2.6.1.4.3. This works with snmp walk, but not when using "Custom OID" request type.

Then I spotted that the Walk type request returned a response where the OID had a .0 added to the end. The number could be different for other OIDs, I guess.

Problem 223:

----------------------- New Test -----------------------
Paessler SNMP Tester 5.2.3 
15.07.2016 09:46:30 (8 ms) : Device: x.x.x.x
15.07.2016 09:46:30 (12 ms) : SNMP V2c
15.07.2016 09:46:30 (16 ms) : Custom OID 1.3.6.1.4.1.3375.2.6.1.4.3
15.07.2016 09:46:30 (25 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHINSTANCE
15.07.2016 09:46:30 (30 ms) : -------
15.07.2016 09:46:30 (33 ms) : Value: 223 (No such instance (SNMP error # 223))
15.07.2016 09:46:30 (38 ms) : Done

But using Walk worked, request includes an altered OID.

----------------------- New Test -----------------------
Paessler SNMP Tester 5.2.3 
15.07.2016 09:46:26 (8 ms) : Device: x.x.x.x
15.07.2016 09:46:26 (12 ms) : SNMP V2c
15.07.2016 09:46:26 (16 ms) : Walk 1.3.6.1.4.1.3375.2.6.1.4.3
15.07.2016 09:46:26 (24 ms) : 1.3.6.1.4.1.3375.2.6.1.4.3.0 = "3" [ASN_APP_COUNTER64]

Simply adding a .0 to the end of the OID when I got the 223 error was the trick. I guess the ".0" has something to do with the data type returned.

----------------------- New Test -----------------------
Paessler SNMP Tester 5.2.3 
15.07.2016 09:57:04 (8 ms) : Device: x.x.x.x
15.07.2016 09:57:04 (11 ms) : SNMP V2c
15.07.2016 09:57:04 (15 ms) : Custom OID 1.3.6.1.4.1.3375.2.6.1.4.3.0
15.07.2016 09:57:04 (22 ms) : SNMP Datatype: ASN_APP_COUNTER64
15.07.2016 09:57:04 (26 ms) : -------
15.07.2016 09:57:04 (30 ms) : Value: 3 (OK)
15.07.2016 09:57:04 (34 ms) : Done

#223 prtg snmp solved walk

Created on Jul 15, 2016 8:08:13 AM

Last change on Jul 15, 2016 12:37:30 PM by Luciano Lingnau [Paessler]



1 Reply

Accepted Answer

Votes:

0

Please confirm, you're trying to monitor the following, correct?

apmAccessStatCurrentActiveSessionsSCALARCounter641.3.6.1.4.1.3375.2.6.1.4.3.0

This is a SCALAR OID, since it's not part of an SNMP Table, the convention is to append a 0 to specify the "lack of an index". The same is also valid for the following "standard" OID's:

sysUpTimeInstance1.3.6.1.2.1.1.3.0
hrSystemUptime1.3.6.1.2.1.25.1.1.0
sysDescr1.3.6.1.2.1.1.1.0

Please note that when you're issuing a Walk the SNMP Tester queries the device the device returns all valid sub-OID's. Which when querying such an index will only have a single result, the actual OID that you want to query appended with 0.

15/07/2016 14:41:57 (16 ms) : walk 1.3.6.1.2.1.25.1.1
15/07/2016 14:41:57 (18 ms) : 1.3.6.1.2.1.25.1.1.0 = "28716896" [ASN_TIMETICKS]

On contrast to the example above, the OID below is NOT a SCALAR but is part of a Table:

hrStorageDescr1.3.6.1.2.1.25.2.3.1.3

If you use the SNMP Tester and walk 1.3.6.1.2.1.25.2.3.1.3 the result will look like the following:

15/07/2016 14:41:57 (75 ms) : 1.3.6.1.2.1.25.2.3.1.3.1 = "C:\ Label:Windows  Serial Number xxxxx" [ASN_OCTET_STR]
15/07/2016 14:41:57 (78 ms) : 1.3.6.1.2.1.25.2.3.1.3.2 = "D:\ Label:DATA  Serial Number xxxxxxx" [ASN_OCTET_STR]
15/07/2016 14:41:57 (83 ms) : 1.3.6.1.2.1.25.2.3.1.3.3 = "E:\" [ASN_OCTET_STR]
15/07/2016 14:41:57 (86 ms) : 1.3.6.1.2.1.25.2.3.1.3.4 = "Virtual Memory" [ASN_OCTET_STR]
15/07/2016 14:41:57 (89 ms) : 1.3.6.1.2.1.25.2.3.1.3.5 = "Physical Memory" [ASN_OCTET_STR]

As for PRTG, it does only issue the equivalent of Custom OID queries from the tester, it can't do a walk, thus entering an OID missing the index or the .0 suffix will always result in an error.

I hope this clears it up, but please let me know if there are any further questions.

Created on Jul 15, 2016 12:48:57 PM by Luciano Lingnau [Paessler]




Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.