Hi,

I have started using the new Telegraf SNMP plugin, and so far working well 
but I have hit an issue that I am trying to work out a solution to.

I am using the mib cbgpPeer2Table to get BGP session information from a 
Cisco router.  Most of the stats are collected fine, but the number of 
prefixes for each peer is kept in a seleparate table with a suffix on the 
mapping.

For example if I snmpwalk cbgpPeer2RemoteIdentifier I see:

SNMPv2-SMI::enterprises.9.9.187.1.2.5.1.12.1.4.192.168.0.1 = IpAddress: 
119.168.0.1

SNMPv2-SMI::enterprises.9.9.187.1.2.5.1.12.1.4.192.168.0.2 = IpAddress: 
119.168.0.2

SNMPv2-SMI::enterprises.9.9.187.1.2.5.1.12.1.4.192.168.0.4 = IpAddress: 
119.168.0.4


If I then fetch cbgpPeer2State I get:


SNMPv2-SMI::enterprises.9.9.187.1.2.5.1.3.1.4.192.168.0.1 = INTEGER: 6

SNMPv2-SMI::enterprises.9.9.187.1.2.5.1.3.1.4.192.168.0.2 = INTEGER: 6

SNMPv2-SMI::enterprises.9.9.187.1.2.5.1.3.1.4.192.168.0.4 = INTEGER: 6


The following telegraf config works as expected:


[[inputs.snmp.table]]

name = "BGP"

inherit_tags = [ "hostname" ]

  [[inputs.snmp.table.field]]

name = "remoteAS"

oid = ".1.3.6.1.4.1.9.9.187.1.2.5.1.11"

is_tag = true


  [[inputs.snmp.table.field]]

name = "remoteID"

oid = ".1.3.6.1.4.1.9.9.187.1.2.5.1.12"

is_tag = true


  [[inputs.snmp.table.field]]

name = "state"

oid = ".1.3.6.1.4.1.9.9.187.1.2.5.1.3"



My problem occurs when I try to include data from 
cbgpPeer2AcceptedPrefixes. The results from an snmpwalk looks like:


SNMPv2-SMI::enterprises.9.9.187.1.2.8.1.1.1.4.192.168.0.1.1.1 = Counter32: 0

SNMPv2-SMI::enterprises.9.9.187.1.2.8.1.1.1.4.192.168.0.2.1.1 = Counter32: 
15464

SNMPv2-SMI::enterprises.9.9.187.1.2.8.1.1.1.4.192.168.0.4.1.1 = Counter32: 
11



There is a suffix of ".1.1" on these results, so telegraf is just ignoring 
the entries as they don't match any tag.



Is there some way to "map" this data?   I have tried just creating a new 
table to just collect the prefixes.  This works however I then have no 
identifier other than the hostname to know what the entry is for.


-- 
Remember to include the InfluxDB version number with all issue reports
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/influxdb.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/influxdb/57be82ab-506f-473a-9f45-4516a0cf8805%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to