Welcome, Guest. Please login or register.

Author Topic: SNMP errors with multiple community strings  (Read 4186 times)


  • Newbie
  • *
  • Posts: 7
    • View Profile
SNMP errors with multiple community strings
« on: January 19, 2011, 06:39:11 PM »
I am getting complaints from our network team that NeDi is causing SNMP errors on our devices.  From what I can tell, it's because we have multiple communities defined in our nedi.conf file.  For example, I have:
Code: [Select]
comm            mycommstring
comm            public
The first is the community string in use on most of our network devices, the second is for non-network devices and a handful of older devices.

Our monitoring system is generating messages like:
Alarm Relation Report
Device neworkswich(192.168.##.##) receives an SNMP message with an erroneous community string

I'm assuming this is because it is NeDi is querying the device with the "public" community string even though it has already successfully used "mycommstring".  Is there a way to have it not query with a second string if the first is successful and/or make NeDi use the stings in the order they are in the file?



  • Administrator
  • Hero Member
  • *****
  • Posts: 2785
    • View Profile
    • NeDi
Re: SNMP errors with multiple community strings
« Reply #1 on: January 21, 2011, 08:11:50 PM »
It actually should prefer the working (stored in DB) community. Can you doublecheck with -v?
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!