Cisco Discovery Issues - SNMP or SSH

ian_starr
Tera Contributor

yesterday

We have a number of Cisco Switches and WAPS which Discover fine via SNMP 1 day and then stop the next. When they stop they seem want to use SSH Credentials and not SNMP as the Probe dictates and SSH is needed.

Anyone else seen similar behaviour and understand how to stop it or why it happens ?

0 Helpfuls
  • 181 Views
4 REPLIES 4

Kieran Anson
Kilo Patron

yesterday

If you look at your discovery_port_probe table, what priority is set for ssh and snmp?

KieranAnson_0-1761661203289.png

 

0 Helpfuls

ian_starr
Tera Contributor

yesterday

Hi Kieran, it was as per your picture but I did change the order to SNMP before SSH but made no difference

0 Helpfuls

Kieran Anson
Kilo Patron
In response to ian_starr

yesterday

When you say 'stop' can you elaborate? Does the discovery schedule fail because it finds no accessible port? Or tries SSH first, fails, and isn't trying SNMP?

0 Helpfuls

ian_starr
Tera Contributor

yesterday

Yeh it didn't appear to attempt SNMP at all. If I looked back in the history strangely it was working a couple of weeks back.

Our Creds are CyberArk stored so I have just simply re-created the SNMP Community String Cred in the instance and its tested fine with the same key. So it appears solved or at least a work around for now.

Thanks for adding comment so quickly anyway.

0 Helpfuls