When running the auto-discovery on a stack of 6 Cisco 3750's, several of the active ports were not recognized or added to the list of sensors for that device. Rerunning auto-discovery did not add the switch ports either.

How can I correct this and get the switches added.

Article Comments

Dear Mark,

just to check, can you add sensors for those ports manually? Please also check if the option "Skip Auto-Discovery for known devices/IPs" is enabled in the group where the Auto-Discovery takes places.

Best Regards.


Feb, 2011 - Permalink

Hello, I encounter maybe a similar issue for different models of Cisco switches ( 3560, 9300, 3850 ). When using auto-discovery , the ports are discovered but the port number is not displayed. Instead of Gi1/0/5 for example I see 10105. this feature used to work with previous versions of PRTG.


Oct, 2019 - Permalink

Hi there,

We have addressed this issue in the latest release:
https://www.paessler.com/prtg/history/stable
SNMP CISCO SYSTEM HEALTH
SNMP Cisco System Health sensors get correct names and units again after sensor creation. In previous versions, all channels except for the first one were only named by the index of the OID in certain cases.

Best regards.


Oct, 2019 - Permalink

Hello Dariusz,

Thank you for your advice. I am running PRTG Network Monitor 19.3.51.2830 x64. so auto-discovery does not work anymore for cisco switches ? I must use a specific sensor for each cisco device? kind regards, Felix.


Oct, 2019 - Permalink

Hello Dariusz, I have upgraded the PRTG server to version 19.4.52.3515 and still get the same problem: the port numbers are not displayed correctly when doing an auto-discovery on a Cisco switch. Instead of seeing interface Gi1/0/5 for example I see 10105. This feature is working fine on a very old version of PRTG ( version 9 ).

I would appreciate your help for this incident. thank you. Kind regards, Felix.


Oct, 2019 - Permalink

Hi Felix,

I'll contact you via mail, since it's easier to handle those cases there.

Kind regards,
Birk Guttmann, Tech Support Team


Oct, 2019 - Permalink