Error Snmp 223
Contents |
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 5747×
Prtg Snmp Error # -2003
prtg 1842× snmp 1468× sensor 938× wmi 622× notifications 467× maps View all Tags No such nosuchinstance snmp instance (SNMP error #223) Votes:0 Your Vote: Up Down Hello, since 23 days I get the SNMP error # 223 on some switchports on a
Snmperr_no_vars
Cisco Switch. SNMP works properly on about 150 switchports, but around 20 ports cant be monitored since the 29th of march. Before this date they also were scanned without any issues. Could you maybe help me with this issue? The prtg snmperr_no_vars ports are connected and everything is fine, only the monitoring is broken. Its just annoying in the error overview to have all these ports (also on some other switches) shown up. greetings Fraggles prtg snmp snmp-error#223 Created on Apr 22, 2016 8:00:38 AM by Fraggles (0) ●1 Permalink Best Answer Accepted Answer Votes:0 Your Vote: Up Down It seems that the interface numbers did change. This could have been caused by a device reboot or configuration change on the device. You snmp error 2003 can set PRTG to try catch such changes in the future and adjust the sensors accordingly, so that they continue to work: Automatically update port name and number for SNMP Traffic sensors when the device changes them. 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. Add comment Created on Apr 25, 2016 8:03:30 AM by Torsten Lindner [Paessler Support] Permalink 6 Replies Votes:0 Your Vote: Up Down Hello, Thank you very much for your KB-Post. Can you please re-add the sensors for a test? Do the new ones then work for the same interfaces? best regards. 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! Tested it so far with one sensor and it seems to work fine. I will test it now on the other switchports and give feedback, if it works or not. :) best regards Fraggles Add comment Created on Apr 22, 2016 10:29:32 AM by Fraggles (0) ●1 Permalink Votes:0 Your Vote: Up Down Hello, please then check the "Interface number"-field for one old and new sensor (for the same interface) in the settings of the sensors. Does it have a different number in it? Add comment Created on Apr 22, 2016 11:04:07 AM by Torsten Lindner [Paessler Support] Permalink Votes:0 Yo
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!
Snmp Error Codes
Learn more Top Tags 5747× prtg 1842× snmp 1468× sensor 938× wmi 622× notifications snmpget no such instance currently exists at this oid 467× maps View all Tags snmpwalk shows valid oid, but prtg and snmp tester fail (error # 223) Votes:0 Your Vote: Up
Snmp No Such Object
Down I'm trying to monitor certain oids from our HP C3000 Blade. 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 https://kb.paessler.com/en/topic/69283-no-such-instance-snmp-error-223 in SNMP Tester or add a Custom OID sensor, I get the following error: No such instance (SNMP error # 223) Any ideas? We really need to monitor some of these OIDs... Thanks! c3000 hp snmp-error-223 Created on Apr 17, 2012 7:56:09 PM by helixstorm (0) ●1 Permalink Best Answer Accepted Answer Votes:0 Your Vote: Up Down What precise OID are you using? Please make sure it is 1.3.6.1.4.1.232.22.2.3.1.1.1.5.1. Add comment Created on Apr 23, https://kb.paessler.com/en/topic/34763-snmpwalk-shows-valid-oid-but-prtg-and-snmp-tester-fail-error-223 2012 10:56:03 AM by Patrick Hutter [Paessler Support] (7,144) ●3 ●3 Permalink 4 Replies Votes:0 Your Vote: Up Down Seeing as the result seems to be in a string format, have you tried using our SNMP Custom String sensor? Add comment Created on Apr 18, 2012 9:47:02 AM by Patrick Hutter [Paessler Support] (7,144) ●3 ●3 Permalink Votes:0 Your Vote: Up Down Yes, and that also gives the same snmp error 223. 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? Please make sure it is 1.3.6.1.4.1.232.22.2.3.1.1.1.5.1. Add comment Created on Apr 23, 2012 10:56:03 AM by Patrick Hutter [Paessler Support] (7,144) ●3 ●3 Permalink Votes:0 Your Vote: Up Down Ah doh, didn't even notice the .1 - Thanks! 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. 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. © 1998 - 2016 Paessler AG Solutions • Imprint • Contact • Sitemap • Privacy Policy • Uninstall • Terms
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 https://kb.paessler.com/en/topic/51403-trouble-with-snmp-traffic-sensors involved by asking and answering questions! Learn more Top Tags 5747× prtg 1842× snmp 1468× sensor 938× wmi 622× notifications 467× maps View all Tags Trouble with SNMP traffic sensors Votes:0 Your Vote: Up Down This is going to sound very much like something I posted before, but it is not exactly the same ... I have a problem with SNMPv2 traffic sensors on interfaces of a VMware server. snmp error I create the sensors manualy. When I get the list of interfaces, they are all there and I select the ones I am interested in. But as soon as PRTG starts polling them, it fails, giving "No Such Name (SNMP error #2)". If I create the sensors with SNMPv1, I do not get the problem. So I suspected that the server was doing SNMPv1 but not SNMPv2c. But, when error snmp 223 I try an SNMPv2c walk using MIBtools on my CA Spectrum, I can see all the version 2 interface MIB. The server guys insist they are running SNMPv2c OK, and that there is no IP access-list that would explian the difference in behaviour. Any suggestions? Thanks. Kevin DORRELL error-#2 snmp traffic-sensors Created on May 3, 2013 3:19:47 PM by dorreke (0) ●1 Permalink 4 Replies Votes:0 Your Vote: Up Down Hello, the host you are trying to monitor is the ESX host itself or a VM running on the ESX host? Did you already try to scan for available interfaces using our free SNMP tester http://www.paessler.com/tools/snmptester Add comment Created on May 6, 2013 7:26:42 AM by Aurelio Lombardi [Paessler Support] Last change on May 6, 2013 7:26:58 AM by Aurelio Lombardi [Paessler Support] Permalink Votes:0 Your Vote: Up Down Hi, and thanks for looking into this. It is the ESX host itself that I am trying to monitor. I have another 21 ESX hosts that seem to be behaving correctly, but the server team upgraded this one a couple of weeks ago, and since then I cannot read the SNMPv2 counters. The strangest thing is that if I set SNMPv2c for the device and try to crea