[collectd] help with collecting # of accepted BGP routes

L. Gabriel Somlo gsomlo at gmail.com
Fri Oct 23 22:11:38 CEST 2009


On Sat, Oct 17, 2009 at 10:35:53PM -0400, matthew sporleder wrote:
> On Wed, Oct 14, 2009 at 2:24 PM, L. Gabriel Somlo <gsomlo at gmail.com> wrote:
> > Hi,
> >
> > I'm trying to graph the number of accepted bgp prefixes for
> > each peer of my border router. Using snmpwalk, I can retrieve
> > counts for all applicable BGP neighbors and protocols
> > (e.g. unicast, multicast) by running:
> >
> >
> > # snmpwalk -v2c -c comstr router CISCO-BGP4-MIB::cbgpPeerAcceptedPrefixes
> > ...
> > CISCO-BGP4-MIB::cbgpPeerAcceptedPrefixes.192.168.16.106.ipv4.unicast = Counter32: 190837
> > CISCO-BGP4-MIB::cbgpPeerAcceptedPrefixes.192.168.16.106.ipv4.multicast = Counter32: 4477
> > ...
> >
> 
> You may need an instance or instanceprefix to convince it to iterate
> and store everything.

I tried to use 'Instance "BGP4-MIB::bgpPeerIdentifier"' which returns
this:

# snmpwalk -v2c -c comstr router BGP4-MIB::bgpPeerIdentifier
...
BGP4-MIB::bgpPeerIdentifier.192.168.16.106 = IpAddress: 192.168.16.106
BGP4-MIB::bgpPeerIdentifier.192.168.16.107 = IpAddress: 192.168.16.107
...

That however generated a flood of errors like this one:

collectd[13493]: snmp plugin: I don't know the ASN type `64'

Anyhow, I thought Instance was optional, and simply made for more
human-readable rrd file names. Also, it seems that collectd doesn't
like to use anything that won't return a STRING for an Instance.


Seems to me the bigger issue is why I'm not getting any rrd files to
begin with. A secondary issue is whether to allow non-STRING
Instances.


--Gabriel




More information about the collectd mailing list