Is it possible to run auto discovery on a network segment and use multiple SNMP credentials? For example, our network printers use different SNMP credentials than our Cisco network equipment.

Right now I run autodiscovery with one set of credentials then go back and manually set the credentials on the printers.

Article Comments

Hello,

this is not possible at the moment, sorry.


Jan, 2013 - Permalink

You could create a new group for Network Printers, modify the SNMP credentials for this group by breaking inheritance, then run auto-discover out of this group.


Jan, 2013 - Permalink

Hello,

creating different groups where each is using a different SNMP community string is of course possible.

What is not possible to create a group that uses two or more SNMP Community strings and then run an auto discovery.


Jan, 2013 - Permalink

When is the ability to auto-discover with multiple SNMP community strings going to be added? WhatsUp has had this capability for years. (Unfortunately, we didn't realise that PRTG didn't when we decided to review our monitoring system, otherwise we may have gone with WUG instead.)


Mar, 2015 - Permalink

Hello,

we do understand that this is an important feature to you, but the overall demand from our users for this is almost not existing.

Therefore the priority to put time into this is very, very low.

It is unlikely that this will be available any time soon, sorry.


Mar, 2015 - Permalink

Thanks for the prompt response ... disappointing, esp. as it should be very easy (and quick) to implement, probably only take a few minutes to code.


Mar, 2015 - Permalink

Hi,

unfortunately it is not that easy.


Mar, 2015 - Permalink

We would like the product to allow multiple unique community names. PCI-DSS requires multiple unique credentials. The community string equals a password for v1 and v2. I would guess there is more need for multiple community names.


Sep, 2016 - Permalink

You'll have to use multiple groups configured with different credentials / communities. No way around that, sorry.


Sep, 2016 - Permalink

In my many years of using PRTG I have discovered several basic features most other network monitoring programs have that's missing from PRTG and this is one of them. Discovery isn't something that PRTG is good at, as in it's not very versatile.

Scanning a subnet with multiple SNMP community strings should be part of basic monitoring. There also should be an option to only add devices being discovered that has one or more specified SNMP community strings configured.

I've gotten the same response before like, "Well we add features based off of requests and including yours we only have 1".

Might I suggest you add features based on a different and more strategic plan.


Feb, 2018 - Permalink

Hi Will,

Thanks for your feedback regarding the matter. Just to put another light on it, as in why we probably won't implement a feature like that:

  1. Most of our customers (existing and new) don't ask for that feature.
  2. Using multiple credentials (assume you have ten sets) will potentially prolong the autodiscovery, whereas we thrive to make this as quick as possible without hammering the target device.
  3. As of today, we have five credential sets within each group you can define. Adding multiple sets of those credentials will most likely just clutter the interface of PRTG, which we're not a fan of.

Rest assured that I get you here - feature requests one might consider very useful getting turned down can sure be frustrating. However, if we'd implement every feature request we get, we sure won't be doing anything else. However, we are currently evaluating other options of gathering and evaluating feature requests, but I don't know the outcome of that yet.

Kind regards,
Stephan Linke, Tech Support Team


Feb, 2018 - Permalink