[collectd] collectd 5.1.0 - "ASN type" error via snmp plugin

[ryanL]

hi,

i've seen discussion on this in the archive, particularly well documented
by Mark (gajillion), but haven't seen a subsequent solution. hoping someone
can point me in the right direction.

the error:

collectd[12476]: snmp plugin: I don't know the ASN type #130 (OID:
"SNMP-VIEW-BASED-ACM-MIB::vacmViewTreeFamilyStatus."_none_".1.2", data
block "bgp_updates", host block "iad1-er1")
rsyslogd-2177: imuxsock begins to drop messages from pid 12476 due to
rate-limiting

in my case, i'm querying for bgp message updates received from peers. the
oid "peeridentifier" i thought would be useful for my instance ID, as it
generates a nice string which i believe is what the plugin requires. but
this is throwing the "i don't know the ASN type" error. i'm simply writing
out to graphite, but no whisper files are generated. as i'm not querying
for "SNMP-VIEW-BASED-ACM-MIB::vacmViewTreeFamilyStatus", and because of the
rate-limiting notification, my belief is that the plugin is looping like
mad.

an example walk of of the oid's in question, which obviously stop correctly.

root at test-app-1 ~ # snmpwalk -v 2c -c <commstring> iad1-er1
BGP4-V2-MIB-JUNIPER::jnxBgpM2PeerIdentifier 2>/dev/null
BGP4-V2-MIB-JUNIPER::jnxBgpM2PeerIdentifier.0.ipv4.<3 octets
removed>.74.1.<3 octets removed>.73 = STRING: <3 octets removed>.69
BGP4-V2-MIB-JUNIPER::jnxBgpM2PeerIdentifier.0.ipv4.<3 octets
removed>.90.1.<3 octets removed>.89 = STRING: <3 octets removed>.69
BGP4-V2-MIB-JUNIPER::jnxBgpM2PeerIdentifier.0.ipv4.<3 octets
removed>.0.1.<3 octets removed>.1 = STRING: <3 octets removed>.1
BGP4-V2-MIB-JUNIPER::jnxBgpM2PeerIdentifier.0.ipv4.<3 octets
removed>.34.1.<3 octets removed>.33 = STRING: <3 octets removed>.78

root at test-app-1 ~ # snmpwalk -v 2c -c <commstring> iad1-er1
BGP4-V2-MIB-JUNIPER::jnxBgpM2PeerInUpdates 2>/dev/null
BGP4-V2-MIB-JUNIPER::jnxBgpM2PeerInUpdates.0.ipv4.<3 octets
removed>.62.1.<3 octets removed>.61 = Counter32: 8
BGP4-V2-MIB-JUNIPER::jnxBgpM2PeerInUpdates.0.ipv4.<3 octets
removed>.74.1.<3 octets removed>.73 = Counter32: 4
BGP4-V2-MIB-JUNIPER::jnxBgpM2PeerInUpdates.0.ipv4.<3 octets
removed>.90.1.<3 octets removed>.89 = Counter32: 2
BGP4-V2-MIB-JUNIPER::jnxBgpM2PeerInUpdates.0.ipv4.<3 octets removed>.0.1.<3
octets removed>.1 = Counter32: 13102293
BGP4-V2-MIB-JUNIPER::jnxBgpM2PeerInUpdates.0.ipv4.<3 octets
removed>.34.1.<3 octets removed>.33 = Counter32: 12665852

my associated types.db entry:

root at test-app-1 ~ # grep bgp_update /opt/collectd/share/collectd/types.db
bgp_updates in:COUNTER:0:U

my collectd.conf (within snmp plugin):

  </Data>
   <Data "bgp_updates">
       Type "bgp_updates"
       Table true
       Instance "BGP4-V2-MIB-JUNIPER::jnxBgpM2PeerIdentifier"
       Values "BGP4-V2-MIB-JUNIPER::jnxBgpM2PeerInUpdates"
   </Data>
   <Host "iad1-er1">
        Address "[removed]"
        Version 2
        Community "[removed]"
        Collect "bgp_updates"
        Interval 60
   </Host>

any insight would be greatly appreciated. for what it's worth, this works
perfectly:

       Type "if_octets"
       Table true
       Instance "IF-MIB::ifDescr"
       Values "IF-MIB::ifHCInOctets" "IF-MIB::ifHCOutOctets"

cheers!

ryan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.verplant.org/pipermail/collectd/attachments/20121030/e7934307/attachment.html>