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

Custom OID problem (No such name Error # 2)

Votes:

0

Recently added device for APC Inrow Air Conditioner When I add a SNMP Custom OID the sensor shows 'No such name (Error #2)'

I have previously added an APC Environment manager devices and sensors, as well as a UPS, just by specifying OID's.

custom oid prtg snmp

Created on Apr 20, 2010 5:41:18 AM

Last change on Apr 20, 2010 7:54:54 AM by Daniel Zobel [Product Manager]



6 Replies

Accepted Answer

Votes:

0

The "No such name" error means that the specified SNMP object was not found. This can have various reasons - changed OID, network connection problems, etc.

As a first step, please use our SNMP Tester to check if you can properly connect to your device. With this tool, check if you can "Read Device Uptime" and if there are any results when you "Scan Available Standard Interfaces".

For more information about SNMP Tester, please see How can I test the functionality of my SNMP device?

In addition, please see the article My SNMP sensors don’t work. What can I do?

Created on Apr 20, 2010 7:54:16 AM by Daniel Zobel [Product Manager]

Last change on Sep 10, 2013 2:12:59 PM by Gerald Schoch [Paessler Support]



Votes:

0

Hi,

I run the test tool and can get the uptime or available standard interfaces, but I still get the same error : "No Such Name (SNMP error # 2).

Do you have other idea.

Thanks

Created on Sep 21, 2010 1:33:51 PM



Votes:

0

Hello,

that means, given the assumption that the SNMP Settings (port, version, community string, potential authentication credentials, etc.) are correctly set, the target device does not have a counter for this OID.

Best Regards.

Created on Sep 21, 2010 3:10:15 PM by Torsten Lindner [Paessler Support]



Votes:

0

Actually the MIB needed to be imported for this particular OID, so your diagnosis is incorrect.

Interestingly other APC devices did not need the MIB to be imported, to reference the OID.

Created on Sep 24, 2010 4:40:42 AM



Votes:

0

I just discovered that the APC OIDs work properly if you add a zero to the end of the OID. For example the InRow RC value "airIRRCUnitStatusAirFlowMetric" has an OID of 1.3.6.1.4.1.318.1.1.13.3.2.2.2.5 according to the APC MIB file, but works properly in PRTG if you enter the OID as 1.3.6.1.4.1.318.1.1.13.3.2.2.2.5.0.

Created on May 25, 2011 1:04:58 PM



Votes:

0

Hello, I have a similar problem, I already tried to add a [b].0[/b] to the end of the OID but in my case, doesn't work.

If I try to Walk to those OIDs, I can get a result:

SnmpWalk v1.01 - Copyright (C) 2009 SnmpSoft Company [ More useful network tools on http://www.snmpsoft.com ]

OID=.1.3.6.1.4.1.318.1.1.1.9.3.3.1.10.1.1.1, Type=Integer, Value=17
OID=.1.3.6.1.4.1.318.1.1.1.9.3.3.1.10.1.1.2, Type=Integer, Value=58
OID=.1.3.6.1.4.1.318.1.1.1.9.3.3.1.10.1.1.3, Type=Integer, Value=23

but if I try to create a sensor I got error [b]No Such Name (SNMP error # 2)[/b]

Created on Oct 25, 2019 9:46:08 AM

Last change on Oct 25, 2019 1:09:15 PM by Birk Guttmann [Paessler Support]




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.