Locate devices missing SNMP credentials or using public/private community string
Summary: Michael Williams, coming from Auvik, is trying to recreate functionality in LM to locate devices running SNMP without correct credentials and identify those using public/private strings. Patrick Rouse suggests using Resource Explorer to filter or group devices by specific metadata. However, Michael Williams explains this approach might not work as the auto.snmp.operational property only appears if communication via SNMP has occurred successfully. Michael Williams is setting SNMP credentials at a group level and notes the challenge of distinguishing between devices running SNMP with incorrect credentials and devices not running SNMP at all. The discussion highlights the need for more effective detection methods or properties to differentiate these scenarios.
Hi!
Very new to LM. Coming from Auvik.
Trying to re-create some of the things Auvik did OOB. Mainly trying to locate devices that are running SNMP but we have not yet supplied the correct credentials for. And also a means to locate devices running public or private community string.
With some help from ChatGPT, I tried to create my first logic module this morning but just couldn't quite get it figured out. Hoping someone here might.
It's also entirely possible that this info is already available by some means that I just don't know about.
Sorry if I dropped this in wrong section. Product Discussion seemed most appropriate.
Thanks!
Patrick Rouse
·5 months agoWhen looking for devices based on metadata, Resource Explorer is your friend because you can search for device including or excluding specific metadata.
So, you could start by grouping devices by this property, which will tell you which ones have operational snmp collection.
When the resource property auto.snmp.operational exists, the value should be true or false.
You can filter and/or group by any resource property.
Michael Williams
OP5 months agoThanks for the reply. From what i've seen, the auto.snmp.operational property doesn't exist unless the device has at some point been communicated with successfully via snmp. I'm looking for devices running snmp that LM hasn't communicated successfully with.
Patrick Rouse
·5 months agoThen filter for devices with SNMP credentials set and use an excludes filter for auto.snmp.operational
Michael Williams
OP5 months agoThanks,
Right now, we are setting up snmp credentials at a group level. We are running netscans to include all devices and dumping them in that group. I've not yet come across any property that would tell me that snmp is running on a device but the supplied creds we set at the group level did not work. It would be awesome if auto.snmp.operational got added to devices that are running SNMP but are not being supplied the correct credentials but it doesn't seem to do that. I haven't really found a property to work with to locate these devices. A device running SNMP, for which we have not supplied the correct creds for, appears to be indistinguishable from a device that doesn't have SNMP running at all.
Of course the devices that are running with the SNMP credentials set at group level do get properly recognized and the auto.snmp.operational property gets to true. And as an experiment if you go into the device property of that working device and set snmp credentials incorrectly on purpose, then auto.snmp.operational will flip to false.
Thanks again
Michael Williams
OP5 months agoThe drive to be able to do this comes from the idea of being able to onboard a new client and locate as many network devices as possible even if we don't have the correct creds. Obviously that requires that snmp was enabled on a device in the first place. It's usually a combination of physical inventory assessment, devices showing snmp is running, devices showing ssh as open, and then checking devices with http(s)