How To Fix Snmp Error # 223 Prtg (Solved)

Home > Snmp Error > Snmp Error # 223 Prtg

Snmp Error # 223 Prtg

The problem can be also fixed by resetting the IDrac. I am opening a ticket with Cisco to see what they think. Use at your own risk. 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. navigate here

The No such instance (SNMP error 223) message is directly related to changing SNMP Indexes. It is the ESX host itself that I am trying to monitor. You are invited to get involved by asking and answering questions! Add comment Created on Apr 23, 2012 11:18:53 PM by helixstorm (0) ●1 Permalink Please log in or register to enter your reply.

The next time you get error #223(no such instance) in PRTG, run the SNMP Tester but this time run the Custom OID test entering the following OID: 1.3.6.1.4.1.9.9.473.1.3.6.1.4.0.1.1. Find out how you can reduce cost, increase QoS and ease planning, as well. Before applying any instructions please exercise proper system administrator housekeeping.

  • According to the documentation, the OID should be 1.3.6.1.4.1.3375.2.6.1.4.3.
  • Does that work?
  • I have now reconfigured them via the OS interface.
  • How do I upload the document?
  • Add comment Created on Sep 22, 2014 3:35:12 PM by Patrick Hutter [Paessler Support] (7,144) ●3 ●3 Permalink Votes:0 Your Vote: Up Down As mentioned in the original post, doing a
  • Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind.
  • Before applying any instructions please exercise proper system administrator housekeeping.
  • What results do you get?
  • Free PRTG Download >> What is this?
  • Any suggestions?

This could have been caused by a device reboot or configuration change on the device. Sometimes problem can be forced by rebooting the server but not always. Free PRTG Download >> What is this? Please refer to this thread in order to understand where the query stems from.

Free PRTG Download >> What is this? Had written a post requesting help when I spotted the solution: Turned out I had to add ".0" to the end of the OID. Tested it so far with one sensor and it seems to work fine. https://kb.paessler.com/en/topic/61528-no-such-instance-snmp-error-223 Please contact us via a support ticket, this will allow us to troubleshoot the actual data expected by the sensor and returned by your iDrac's to check out what's causing the

SNMP works properly on about 150 switchports, but around 20 ports cant be monitored since the 29th of march. Add comment Created on Apr 18, 2012 3:49:05 PM by helixstorm (0) ●1 Permalink Accepted Answer Votes:0 Your Vote: Up Down What precise OID are you using? Add comment Created on Dec 16, 2013 4:08:28 PM by NextNav (0) ●1 Last change on Sep 23, 2015 4:50:42 AM by Luciano Lingnau [Paessler Support] Permalink Votes:0 Your Vote: Up Can you please re-add the sensors for a test?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. Add comment Created on Apr 22, 2016 10:05:13 AM by Torsten Lindner [Paessler Support] Permalink Votes:0 Your Vote: Up Down Hey, thx for replying! Essentially "The disk with serial number could not be found" means that the unique serial number used to identify this disk is no longer present. Thanks, Swami probe prtg snmp Created on Oct 25, 2010 10:37:16 PM by Swami V (0) ●1 Last change on Jun 5, 2015 7:25:28 AM by Luciano Lingnau [Paessler Support] Permalink

Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. check over here Best Regards, Luciano Lingnau [Paessler Support] Add comment Created on Jun 27, 2016 8:41:44 AM by Luciano Lingnau [Paessler Support] Permalink Please log in or register to enter your reply. I am using the SNMP Library Sensor. I create the sensors manualy.

Learn more Top Tags 5804× prtg 1858× snmp 1476× sensor 948× wmi 628× notifications 478× maps View all Tags Trouble with SNMP traffic sensors Votes:0 Your Vote: Up Down This Free PRTG Download >> What is this? Add comment Created on Sep 22, 2014 3:44:51 PM by kkunzler (0) ●1 Permalink Votes:0 Your Vote: Up Down Could you please forward us the results of both tests, including detailed his comment is here Are you able to access the OID using a different program using a get request (e.g.

You are invited to get involved by asking and answering questions! Use at your own risk. I hope this clears it up, but please let me know if there are any further questions.

If I walk the value, it returns ok: snmpwalk -v 2c -c public 192.168.40.2 1.3.6.1.4.1.232.22.2.3.1.1.1.5 iso.3.6.1.4.1.232.22.2.3.1.1.1.5.1 = STRING: "458032-B21" When I search for the value in SNMP Tester or add a

Learn more Top Tags 5804× prtg 1858× snmp 1476× sensor 948× wmi 628× notifications 478× maps View all Tags Fixing SNMP error # 223 by extending OID Votes:0 Your Vote: For the current already "broken" sensors, you can manually edit the interface number field (just use the new sensors and copy it from them), to get them working again. Find out how you can reduce cost, increase QoS and ease planning, as well. When I conduct a Walk on 1.3.6.1.4.1.9.9.473.1.3.6.1.4 for either a host that is in error or not I get the proper response: Paessler SNMP Tester 5.2.3 Computername: PRTGPROBENWAE01 Interface: (10.76.224.84) 6/17/2016

Does it have a different number in it? You are invited to get involved by asking and answering questions! All objects in this table are read-only to the management station. weblink You must make sure that a proper backup of all your data is available. © 1998 - 2016 Paessler AG Solutions • Imprint • Contact • Sitemap • Privacy Policy •

Will keep you informed if this solves the problem. You are invited to get involved by asking and answering questions! Thank you for your help, this seems to work fine :) Add comment Created on Apr 25, 2016 9:01:05 AM by Fraggles (0) ●1 Permalink Please log in or register to Free PRTG Download >> What is this?