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

No such instance (SNMP error #223)

Votes:

0

Hello,

since 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. 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



Best Answer

Accepted Answer

Votes:

0

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.

Created on Apr 25, 2016 8:03:30 AM by Torsten Lindner [Paessler Support]



6 Replies

Votes:

0

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.

Created on Apr 22, 2016 10:05:13 AM by Torsten Lindner [Paessler Support]



Votes:

0

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

Created on Apr 22, 2016 10:29:32 AM



Votes:

0

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?

Created on Apr 22, 2016 11:04:07 AM by Torsten Lindner [Paessler Support]



Votes:

0

hello again,

I checked the interfacenumbers and the re-added sensor has an other interface number then the sensor had before. Is this a problem? After re-adding the sensors work fine again.

Created on Apr 22, 2016 12:38:39 PM



Accepted Answer

Votes:

0

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.

Created on Apr 25, 2016 8:03:30 AM by Torsten Lindner [Paessler Support]



Votes:

0

Perfect! Thank you for your help, this seems to work fine :)

Created on Apr 25, 2016 9:01:05 AM




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.