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 name (ifalias/x.x.x.x) (SNMPerror #2)

Votes:

0

Hi,

We recently just upgraded our Cisco 6509 and so far after the upgrade some interfaces are showing down eventhough it is up and running. The errors are "no such name (ifalias/x.x.x.x) (SNMPerror #2)" and "no such instance (SNMP error #223).

Other interfaces are showing up and being monitored fine.

Anything that you can recommend doing? Prior the upgrade we do not see this issue. So far the cisco IOS version was also applied on our other identical routers and it is working fine.

cisco error error-#2 error-223 prtg

Created on Aug 28, 2015 7:52:16 AM



4 Replies

Votes:

0

Dear raidfanatic

Which sensor type are you using? Is it the SNMP Traffic sensor?

Created on Aug 28, 2015 12:02:33 PM by  Arne Seifert [Paessler Support]



Votes:

0

Yes.

bandwidthsensor smtptrafficsensor

Created on Sep 1, 2015 3:19:50 AM



Votes:

0

Dear raidfanatic

It looks like the Cisco update also changed some interface names. You can unlock the interface setting in the sensor configuration by clicking on the small lock item and enter a new interface name.

The alternative is to create the sensors for the updated interfaces anew. If only a handful of interfaces was changed, the first method is usually preferable as it keeps the historic data for that interface in a single sensor.

Created on Sep 1, 2015 8:15:49 AM by  Arne Seifert [Paessler Support]

Last change on Sep 1, 2015 8:16:36 AM by  Arne Seifert [Paessler Support]



Votes:

0

Hi,

That worked! :) thank you Arne!

Created on Sep 1, 2015 9:36:54 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.