No Such Instance 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 nosuchinstance snmp and answering questions! Learn more Top Tags 5776× prtg 1852× snmp 1472× sensor prtg snmp error # -2003 946× wmi 622× notifications 473× maps View all Tags No such instance (SNMP error #223) Votes:0 Your Vote: Up Down Hello, since prtg snmperr_no_vars 23 days I get the SNMP error # 223 on some switchports on a Cisco Switch. SNMP works properly on about 150 switchports, but around 20 ports cant be monitored since the 29th of march.
Snmpget No Such Instance Currently Exists At This Oid
Before this date they also were scanned without any issues. Could you maybe help me with this issue? The 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 snmp error codes 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 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 Fr
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 snmp no such object asking and answering questions! Learn more Top Tags 5776× prtg 1852× snmp 1472×
"snmp Error # -2003"
sensor 946× wmi 622× notifications 473× maps View all Tags No such instance (SNMP error 223) after reboot of Dell Poweredge
Snmp Tester
Server Votes:0 Your Vote: Up Down Hello, We are running PRTG V15.1.15.2022 and recently started using PRTG to monitor some of our Dell PowerEdge servers. We can add the Dell PowerEdge Heath Monitor and PRTG correctly https://kb.paessler.com/en/topic/69283-no-such-instance-snmp-error-223 raises an alarm when a hardware issue arises. Howerver when rebooting the OS, most of the time the Sensor goes in "No Such Instance SNMP error # 223". Deleting the sensor and recreating the sensor solves the problem. The problem can be also fixed by resetting the IDrac. What can I do in PRTG to prevent the need to do one of the two workarounds ? Best regards, Sven dell poweredge https://kb.paessler.com/en/topic/69889-no-such-instance-snmp-error-223-after-reboot-of-dell-poweredge-server snmp Created on Jun 9, 2016 8:35:32 AM by SvenVR73 (0) ●1 Permalink 8 Replies Votes:0 Your Vote: Up Down Hello Sven, Since you use an older PRTG version please update first to the latest version of PRTG in order to see if the issue still remains, using the Auto-Update. Alternatively you can download the software from our Paessler Service Center using your registered email and password. Once you have downloaded the latest version, you can install it directly over the version currently running. The configuration and database will not be affected by installing the newer version over the old and the configuration is automatically backed up before this process. Add comment Created on Jun 10, 2016 12:20:01 PM by Jochen Greger [Paessler Support] Last change on Jun 10, 2016 12:20:25 PM by Jochen Greger [Paessler Support] Permalink Votes:0 Your Vote: Up Down I updated PRTG to version v16.2.24.4470 but still have the same problem. After a couple of dayes I get the status " No such instance (SNMP error 223)" in PRTG. When I remove the sensor and add it the problem is gone for a couple of days. Sometimes problem can be forced by rebooting the server but not always. I have this problem on several Dell PowerEdge Server
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 https://kb.paessler.com/en/topic/51403-trouble-with-snmp-traffic-sensors Tags 5776× prtg 1852× snmp 1472× sensor 946× wmi 622× notifications 473× 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 https://kb.paessler.com/en/topic/70048-no-such-instance-snmp-error-223-after-reboot-of-windows-server it is not exactly the same ... I have a problem with SNMPv2 traffic sensors on interfaces of a VMware server. I create the sensors manualy. When I get the list of interfaces, they are all there and I no such 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 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 no such instance 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 create SNMP traffic sensors, I can discover the interfaces OK. But after I create sensors on the actiove ones, they all go red ("Show alarm when disconnected") once PRTG starts trying to read the counters. But if I switch to SNMPv1, I can get the available interfaces, and I can read the 32-bit counters OK. Unfortunatel
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 5776× prtg 1852× snmp 1472× sensor 946× wmi 622× notifications 473× maps View all Tags No such instance (SNMP error 223) after reboot of Windows server Votes:0 Your Vote: Up Down We are running v16.2.23.3270+ and are experiencing the error for one element in a custom OIDLIB from Cisco. 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 8:19:59 AM (10 ms) : Device: 10.156.20.52 6/17/2016 8:19:59 AM (14 ms) : SNMP V2c 6/17/2016 8:19:59 AM (19 ms) : Walk 1.3.6.1.4.1.9.9.473.1.3.6.1.4 6/17/2016 8:19:59 AM (29 ms) : 1.3.6.1.4.1.9.9.473.1.3.6.1.4.0.1.1 = "6" [ASN_INTEGER] The act of Walking or Scanning the OIDLIB from the SNMP Tester clears the error. Thanks, Mark Knepper UC Engineer error oidlib snmp Created on Jun 17, 2016 3:33:25 PM by mtknepper (0) ●1 Last change on Jun 20, 2016 10:30:35 AM by Luciano Lingnau [Paessler Support] Permalink 5 Replies Votes:0 Your Vote: Up Down Hello Mark, thank you for your KB-Post. This is very unusual. As you're not running the latest PRTG version I must kindly ask that you begin by updating to the latest stable release to confirm whenever the issue persists. If the issue persists, please run a walk against the following OID: 1.3.6.1.4.1.9.9.473.1.3.6, this will allow us to check how this table looks like. How are you monitoring the sensor in PRTG? SNMP Library Sensor SNMP Custom Sensor SNMP Custom Advanced Sensor SNMP Custom Table Sensor Please share a screenshot from the sensor's settings. Please also note that you can contact us via a support ticket as it will allow you to easily share screenshots and other log-files. Best Regards, Luciano Lingnau [Paessler Support] Add comment Created on Jun 20, 2016 10:41:37 AM by Luciano Lingnau [Paessler Support] Permalink Votes:0 Your Vote: Up Down Thanks Luciano, I ha