01-17-2018 10:56 AM - edited 03-12-2019 07:38 AM
I am seeing this issue in the new 2.7.2 version.
We have several credential profiles, some SNMPv3, some SNMPv2, about 5 in total. All my devices were discovered in a previous version, and every week when the discovery ran no issues. Not sure under which version of the software this started but now when the discovery runs it will not use the different credentials for the different devices.
In my Discovery job, the 3rd page in, the Management Protocol is set to snmpv3. All devices using snmpv3 are rediscovered but all other devices go under the unreachable nodes. If I change the Management Protocol to snmpv2, all those devices are rediscovered but my snmpv3 devices are marked as unreachable.
One of the replies says that the software will remember which credentials to use during the inventory job but it seems that it is not the case because when checking on the web portal at services.cisco.com the devices are not appearing.
01-17-2018 04:00 PM
Hello trapasso,
Can you please check to see if your Collection Profile settings have the option enabled to run discovery and DAV when the profile starts? When the Collection job runs, it will verify all protocols to allow you to collect data from both SNMPv2 and V3 devices. You can view these settings in the Settings -> Manage Data Collection Profile settings window.
Thank you,
Jarrett
01-17-2018 07:28 PM
01-18-2018 11:46 AM
01-18-2018 12:17 PM
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