New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and 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


View all Tags


Could not identify port number

Votes:

0

Your Vote:

Up

Down

I have an ASA 5505 that I am using SNMP Traffic sensor on and I am monitoring mulptile interfaces on that ASA. One of them is giving me an error that says Could not Identify Port Number. The other interfaces are working fine. I have no idea why this is doing this. Any ideas?

snmp snmp-sensor snmp-traffic

Created on May 22, 2015 12:50:58 PM by  Jon DeSalvatore (0) 1



7 Replies

Votes:

0

Your Vote:

Up

Down

Have you tried to recreate the sensor? Also, please try to scan the interfaces with the SNMP Tester and see if the port number looks correct. If not, you may want to restart SNMP on the Cisco.

Created on May 25, 2015 11:28:27 AM by  Greg Campion [Paessler Support]



Votes:

0

Your Vote:

Up

Down

I have rebooted the ASA already. I have also tried to recreate the sensor.

Whats weird is I am able to monitor 3 other interfaces on the ASA but the one I need to monitor the most is the one that gives the error.

Created on May 25, 2015 2:32:11 PM by  Jon DeSalvatore (0) 1



Votes:

0

Your Vote:

Up

Down

Please send us the results of the SNMP test to [email protected] and we can see what may be the issue. It could be the naming that is used for the interface.

Created on May 25, 2015 2:42:18 PM by  Greg Campion [Paessler Support]



Votes:

0

Your Vote:

Up

Down

So I just renamed the interface description and recreated the sensor and now it worked. Go figure.

Thanks.

Created on May 25, 2015 2:54:00 PM by  Jon DeSalvatore (0) 1



Votes:

0

Your Vote:

Up

Down

Would it be possible to post what the name was before and after for anyone who has a similar issue? Thanks!

Created on May 25, 2015 3:12:32 PM by  Greg Campion [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Not sure if the name has anything to do with it...

interface Ethernet0/0
 description ***CXN to ISP*** 
!
interface Ethernet0/1
 description ***CXN to 2821 Router G0/1***
 switchport trunk native vlan 2
 switchport mode trunk

Here is the config on 2 of the interfaces. E0/0 was the problem one while E0/1 has not had any issues.

I updated the E0/0 to be:

interface Ethernet0/0
 description Comcast ISP
!
interface Ethernet0/1
 description ***CXN to 2821 Router G0/1***
 switchport trunk native vlan 2
 switchport mode trunk

And left E0/1 the way it was. I recreated the sensor and then it worked without an issue.

Created on May 26, 2015 11:38:41 AM by  Jon DeSalvatore (0) 1

Last change on May 27, 2015 11:56:06 AM by  Greg Campion [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Thanks so much for the information! Hopefully it will help others if they have similar issues.

Created on May 27, 2015 11:56:35 AM by  Greg Campion [Paessler Support]



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.