02-25-2019 12:46 PM
We have a customer with newly installed collector that is not picking up several switches. We have verified the IP's are within the ranges we loaded and the SNMP community strings are correct. Yesterday's discovery still did not find them.
Solved! Go to Solution.
02-25-2019 02:53 PM
02-25-2019 02:53 PM
03-08-2019 07:01 AM
Thank you! Seems like this fixed, will know for sure on Monday
03-11-2019 08:30 AM
The customer was able to manually walk the devices from the collector to verify the collector could connect to them.
Does the collector skip devices that it failed to read before? Would think not. The ACL was preventing the collector from reading snmp from the device, but that has been fixed. None of them were picked up on yesterday's discovery.
03-11-2019 09:10 AM
03-11-2019 10:22 AM
Guess you didn't see my reply to my own post? None of the devices were discovered.
03-11-2019 10:29 AM - edited 03-11-2019 10:44 AM
You can confirm SNMP access to these devices by running an snmpwalk from the CLI (login to collectorlogin, then su to root)
Ex.
[root@localhost ~]# snmpwalk -v 2c -c community_string ip_address
[root@localhost ~]# snmpwalk -v 3 -u v3User -l AuthPriv -a SHA -A authPassword -x DES -X privPasword
If they are successful, please run a discovery with those IPs or IP ranges specified.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide