Hello,

on an embedded system we had problems with snmpd starting, which we
could track down to the mib_indexes folder/files. This is what
happened:

1) system has some MIB files in some folder which is known to
net-snmp, no mib_indexes yet
2) net-snmp creates mib_indexes
3) we add some MIB files to the folder from 1), mib_indexes stay the
same
4) snmpd won't startup properly with the following error in syslog:

May  8 08:42:55 XXX daemon.err snmpd[366]: MIB search path: 
/root/.snmp/mibs:/usr/share/snmp/mibs
May  8 08:42:55 XXX daemon.err snmpd[366]: Cannot find module (LLDP-MIB): At 
line 0 in (none)
May  8 08:42:55 XXX daemon.err snmpd[366]: /etc/snmp/snmpd.conf: line 30: 
Error: bad SUBTREE object id
May  8 08:42:55 XXX daemon.err snmpd[366]: net-snmp: 1 error(s) in config 
file(s)

The reported line in snmpd.conf is this:

    view    public_view     included    LLDP-MIB::lldpMIB

LLDP-MIB is one of the MIB files we added in 3) but there's no entry
for that in mib_indexes.

Now my question: what is the designated way to update those
mib_indexes? Can net-snmp scan by itself somehow? How can that be
triggered? Or is this to be done manually by administrator? 

I could not find any information on this topic in a web search or in
some manual. :-/

Greets
Alex

-- 
/"\ ASCII RIBBON | »With the first link, the chain is forged. The first
\ / CAMPAIGN     | speech censured, the first thought forbidden, the
 X  AGAINST      | first freedom denied, chains us all irrevocably.«
/ \ HTML MAIL    | (Jean-Luc Picard, quoting Judge Aaron Satie)

Attachment: signature.asc
Description: PGP signature

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Reply via email to