New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

300.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


SNMP error 222

Votes:

0

Your Vote:

Up

Down

Hello,

i am trying to monitor a Rittal lcp. I have a MIB File and converted it to oidlib. Now when I try to create a new snmp library sensor I am getting always the error No such Object error # 222. Can anyone tell me what I should do?

Here a sample from the oidlib file:
rittal-LCP-DX MODULE-IDENTITY

--
-- Node definitions
--

	-- 1.3.6.1.4.1.2606
	rittal OBJECT IDENTIFIER 		::= { enterprises 2606 }

	-- 1.3.6.1.4.1.2606.21
	lcp-dx OBJECT IDENTIFIER 		::= { rittal 21 }

	-- 1.3.6.1.4.1.2606.21.1
	system OBJECT IDENTIFIER		::= { lcp-dx 1 }

	-- 1.3.6.1.4.1.2606.21.1.1
	agentRelease OBJECT-TYPE
		SYNTAX Integer32
		UNITS "N/A"
		MAX-ACCESS read-only
		STATUS current
		DESCRIPTION "Release of the Agent."
		::= { system 1 }

	-- 1.3.6.1.4.1.2606.21.1.2
	agentCode OBJECT-TYPE
		SYNTAX Integer32
		UNITS "N/A"
		MAX-ACCESS read-only
		STATUS current
 		DESCRIPTION "Code of the Agent. 2=pCOWeb."
		::= { system 2 }

	-- 1.3.6.1.4.1.2606.21.2
	instruments OBJECT IDENTIFIER 		::= { lcp-dx 2 }

	-- 1.3.6.1.4.1.2606.21.2.0
 	pCOWebInfo OBJECT IDENTIFIER 		::= { instruments 0 }


	-- 1.3.6.1.4.1.2606.21.2.0.10
	pCOStatusgroup OBJECT IDENTIFIER 	::= { pCOWebInfo 10 }

	-- 1.3.6.1.4.1.2606.21.2.0.10.1
	pCOId1-Status OBJECT-TYPE
		SYNTAX Integer32
		UNITS "N/A"
		MAX-ACCESS read-only
		STATUS current
		DESCRIPTION "Status of pCOId1. 0=Offline, 1=Init, 2=Online"
		::= { pCOStatusgroup 1 }

	-- ... You will have how many pCOIdX-Status objects as the pCOs connected to pCOWeb.

	-- 1.3.6.1.4.1.2606.21.2.0.11
	pCOErrorsNumbergroup OBJECT IDENTIFIER	::= { pCOWebInfo 11 }

	-- 1.3.6.1.4.1.2606.21.2.0.11.1
	pCOId1-ErrorsNumber OBJECT-TYPE
		SYNTAX Integer32
		UNITS "N/A"
		MAX-ACCESS read-only
		STATUS current
		DESCRIPTION "Number of Communication Errors from pCOId1 to pCOWeb."
		::= { pCOErrorsNumbergroup 1 }

	-- ... You will have how many pCOIdX-ErrorsNumber objects as the pCOs connected to pCOWeb.
	

	-- 1.3.6.1.4.1.2606.21.2.1.1
	digitalObjects OBJECT IDENTIFIER	::= { rittal-LCP-DX 1 }

and so on...

error-#222 no-such-object snmp

Created on Jun 22, 2020 12:33:13 PM by  paul-sch (0) 1

Last change on Jun 22, 2020 1:10:01 PM by  Birk Guttmann [Paessler Support]



5 Replies

Votes:

0

Your Vote:

Up

Down

Hello there,

The error message indicate, there is no response to the requested OIDs on the target device here. I would start with a simple test to confirm that SNMP is working fine. Therefore, simply try to add a SNMP Uptime Sensor. This sensor type should work for all SNMP devices that are configured correctly.

Please let us know if this worked fine.


Kind regards,
Birk Guttmann, Tech Support Team

Created on Jun 22, 2020 1:18:41 PM by  Birk Guttmann [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hello,

the System-Uptime / System-Laufzeit Sensor is working fine and shows 6days0h41min.

IT looks like there is something wrong with the oidlib. I deleted all OIDs except one but i am getting still the error 222

This is how the oidlib now looking like:

<?xml version="1.0" encoding="UTF-8"?>
  <oidlist>
    <system>
      <version>
        2
      </version>
    </system>
    <list>
      <entry>
        <name>
          Rittal-LCP-DX-MIB|digital objects|high-pressure
        </name>
        <lookupname/>
        <oid>
          1.3.6.1.4.1.2606.21.2.1.1.3.0
        </oid>
        <type>
          vmAbsolute
        </type>
        <kind>
          mkDirect
        </kind>
        <unittype>
          sutCustom
        </unittype>
        <units>
          N/A
        </units>
        <indicator>
          high-pressure
        </indicator>
        <scale>
          1
        </scale>
        <multiply>
          no
        </multiply>
        <max>
          0
        </max>
        <usegetnext>
          no
        </usegetnext>
        <is64bit>
          no
        </is64bit>
        <isunsigned>
          no
        </isunsigned>
        <isfloat>
          no
        </isfloat>
        <description>
          High Pressure Switch Alarm
        </description>
        <OriginalOID>
          1.3.6.1.4.1.2606.21.2.1.1.3
        </OriginalOID>
        <OriginalLabel>
          high-pressure
        </OriginalLabel>
        <TableOID/>
        <DisplayHint/>
        <DataType>
          ASN_INTEGER
        </DataType>
        <DataSize>
          0
        </DataSize>
        <UnitSource/>
        <UnitNormalized/>
        <GroupMajor>
          Rittal-LCP-DX-MIB
        </GroupMajor>
        <GroupMinor>
          digital objects
        </GroupMinor>
        <GroupSub>
          high-pressure
        </GroupSub>
        <FormatType/>
        <FormatValue/>
      </entry>
    </list>
    <lookups/>
  </oidlist>

Is it looks "normal"?

kind regards Paul

Created on Jun 23, 2020 8:50:01 AM by  paul-sch (0) 1

Last change on Jun 24, 2020 7:32:31 AM by  Birk Guttmann [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi Paul,

Please use our SNMP Tester, run it on the PRTG Probe Server, and perform a "Walk" with the OID 1.3.6.1.4.1.2606.21.2.1.1 for the tester against the target device. Kindly configure the Device's IP/Port and SNMP Credentials accordingly.

Which results do you get in the Tester?


Kind regards,
Birk Guttmann, Tech Support Team

Created on Jun 24, 2020 7:34:57 AM by  Birk Guttmann [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi,

first I checked the uptime:

----------------------- New Test -----------------------
Paessler SNMP Tester - 20.2.4 Computername: MYPC Interface: MYIP
25.06.2020 14:23:04 (11 ms) : Device: TargetIP
25.06.2020 14:23:04 (13 ms) : SNMP v2c
25.06.2020 14:23:04 (16 ms) : Uptime
25.06.2020 14:23:04 (25 ms) : SNMP Datatype: ASN_TIMETICKS
25.06.2020 14:23:04 (28 ms) : -------
25.06.2020 14:23:04 (30 ms) : DISMAN-EVENT-MIB::sysUpTimeInstance = 70723190 ( 8 days 4 hours )
25.06.2020 14:23:04 (40 ms) : SNMP Datatype: ASN_TIMETICKS
25.06.2020 14:23:04 (44 ms) : HOST-RESOURCES-MIB::hrSystemUptime.0 = 70728115 ( 8 days 4 hours )
25.06.2020 14:23:04 (46 ms) : Done

looks good, now the walk with 1.3.6.1.4.1.2606.21.2.1.1:

----------------------- New Test -----------------------
Paessler SNMP Tester - 20.2.4 Computername: MYComputer Interface: MYIP
25.06.2020 14:21:18 (9 ms) : Device: TargetIP
25.06.2020 14:21:18 (15 ms) : SNMP v2c
25.06.2020 14:21:18 (18 ms) : Walk 1.3.6.1.4.1.2606.21.2.1.1

Thats it, nothing happen at all...

Then I started the scan with the OIDLIB:

---------------------- New Test -----------------------
Paessler SNMP Tester - 20.2.4 Computername: MyComputer Interface: MyIP
25.06.2020 14:20:39 (7 ms) : Device: TargetIP
25.06.2020 14:20:39 (10 ms) : SNMP v2c
25.06.2020 14:20:39 (12 ms) : Scan OIDLIB c:\...\Rittal.oidlib
Scanning OIDs
from library: "c:\...\Rittal.oidlib"
on device: TargetIP
25.06.2020 14:20:39 Oidscan: Start Scan
25.06.2020 14:20:39 Oidscan: Rittal-LCP-DX-MIB|system|agent release|| 1.3.6.1.4.1.2606.21.1.1.0
25.06.2020 14:20:39 Oidscan: Rittal-LCP-DX-MIB|system|agent code|| 1.3.6.1.4.1.2606.21.1.2.0

**Shortened by Birk Guttmann**

Found OIDs:
No OIDs found

grrr. It looks like the device don't answer to the oids... or do you have an other idea?

kind regards Paul

Created on Jun 25, 2020 12:51:27 PM by  paul-sch (0) 1

Last change on Jun 26, 2020 10:10:44 AM by  Birk Guttmann [Paessler Support]



Votes:

1

Your Vote:

Up

Down

Hello Paul,

I shortened your above response a bit. Yes, it seems that the OIDs from the MIB are not supported by the targeted device. I would recommend to directly ask the vendor for the correct MIB file.


Kind regards,
Birk Guttmann, Tech Support Team

Created on Jun 26, 2020 10:12:14 AM by  Birk Guttmann [Paessler Support]



Please log in or register to enter your reply.


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.