BGP polling is empty with snmp-exporter but ok with snmpwalk

[boogie777]

Hello,
i meet a pb while trying to poll BGP info using snmp-exporter. Everything is OK while trying to retrieve other data from this network equipment ( extreme router ) using snmp-exporter ( able to get hw info, lacp , interfaces ....)
The result of BGP polling is "empty" when setting a minimalist conf ( only one oid ) using snmp-exporter while ok with a walk .

I surely made something wrong ..but unable to fix after hours of troubleshooting

Host operating system: output of uname -a

Linux workersops 3.10.0-1160.25.1.el7.x86_64 #1 SMP Wed Apr 28 21:49:45 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Kubernetes: 1.24.8
kube-prometheus-stack: 32.2.0
helm chart snmp-exporter: 1.4.0
snmp-exporter: 0.21
snmp v3

snmp_exporter version: output of snmp_exporter -version

snmp_exporter, version 0.21.0 (branch: HEAD, revision: 0d8c3527cac0c26f1d6005b84b74413d14264c37)
  build user:       root@51dfd4b1f59b
  build date:       20221122-15:14:18
  go version:       go1.19.3
  platform:         linux/amd64

What device/snmpwalk OID are you using?

BGP4-MIB / OID : 1.3.6.1.2.1.15.3.1.7

If this is a new device, please link to the MIB(s).

What did you do that produced an error?

With the following config of the snmp config :

bgp:
  walk:
  - 1.3.6.1.2.1.15.3.1.7
  metrics:
  - name: bgpPeerRemoteAddr
    oid: 1.3.6.1.2.1.15.3.1.7
    type: InetAddressIPv4
    help: The remote IP address of this entry's BGP peer. - 1.3.6.1.2.1.15.3.1.7
    indexes:
    - labelname: bgpPeerRemoteAddr
      type: InetAddressIPv4
  version: 3
  max_repetitions: 10
  retries: 3
  timeout: 5s
  auth:    
    security_level: authPriv
    username: bob
    password: <secret>
    auth_protocol: SHA
    priv_protocol: AES
    priv_password: <secret>
    context_name: k8s

Nb: the snmp config has been made using the generator tool

the BGP scrape result is empty :

# HELP snmp_scrape_duration_seconds Total SNMP time scrape took (walk and processing).`
 # TYPE snmp_scrape_duration_seconds gauge
 snmp_scrape_duration_seconds 0.023077785
 # HELP snmp_scrape_packets_retried Packets retried for get, bulkget, and walk.
 # TYPE snmp_scrape_packets_retried gauge
 snmp_scrape_packets_retried 0
 # HELP snmp_scrape_packets_sent Packets sent for get, bulkget, and walk; including retries.
 # TYPE snmp_scrape_packets_sent gauge
 snmp_scrape_packets_sent 3
 # HELP snmp_scrape_pdus_returned PDUs returned from get, bulkget, and walk.
 # TYPE snmp_scrape_pdus_returned gauge
 snmp_scrape_pdus_returned 0
 # HELP snmp_scrape_walk_duration_seconds Time SNMP walk/bulkwalk took.
 # TYPE snmp_scrape_walk_duration_seconds gauge
 snmp_scrape_walk_duration_seconds 0.023050813 

No error produced in snmp-exporter

snmp-exporter ts=2023-05-23T14:46:27.623Z caller=collector.go:231 level=debug module=extreme target=10.10.100.96 msg="Walk of subtree completed" oid=1.3.6.1.2.1.15.3.1.7 duration_seconds=422.814336ms                                                             
snmp-exporter ts=2023-05-23T14:46:27.623Z caller=main.go:108 level=debug module=extreme target=10.10.100.96 msg="Finished scrape" duration_seconds=0.423456631                                                                                                      
snmp-exporter ts=2023-05-23T14:46:37.744Z caller=main.go:97 level=debug module=extreme target=10.10.0.94 msg="Starting scrape"    
snmp-exporter ts=2023-05-23T14:46:37.745Z caller=collector.go:218 level=debug module=extreme target=10.10.0.94 msg="Walking subtree" oid=1.3.6.1.2.1.15.3.1.7                                                                                                        
snmp-exporter ts=2023-05-23T14:46:37.766Z caller=collector.go:231 level=debug module=extreme target=10.10.0.94 msg="Walk of subtree completed" oid=1.3.6.1.2.1.15.3.1.7 duration_seconds=21.544222ms                                                                 
snmp-exporter ts=2023-05-23T14:46:37.767Z caller=main.go:108 level=debug module=extreme target=10.10.0.94 msg="Finished scrape" duration_seconds=0.02246272 

What did you expect to see?

I would like to be able to retrieve simple info as snmpwalk did

[root@poll01 ~] # MIBS=BGP4-MIB snmpwalk 10.10.100.96 -v3 -l authPriv -u bob -a SHA -A xx -x AES -X xx 1.3.6.1.2.1.15.3.1.7
BGP4-MIB::bgpPeerRemoteAddr.10.121.232.1 = IpAddress: 10.121.232.1
BGP4-MIB::bgpPeerRemoteAddr.10.121.232.2 = IpAddress: 10.121.232.2
BGP4-MIB::bgpPeerRemoteAddr.10.121.232.3 = IpAddress: 10.121.232.3
BGP4-MIB::bgpPeerRemoteAddr.10.121.232.4 = IpAddress: 10.121.232.4
BGP4-MIB::bgpPeerRemoteAddr.10.121.232.5 = IpAddress: 10.121.232.5
BGP4-MIB::bgpPeerRemoteAddr.10.121.232.6 = IpAddress: 10.121.232.6
BGP4-MIB::bgpPeerRemoteAddr.10.121.232.7 = IpAddress: 10.121.232.7
...

What did you see instead?

the BGP scrape result is empty :

 # HELP snmp_scrape_duration_seconds Total SNMP time scrape took (walk and processing).
  # TYPE snmp_scrape_duration_seconds gauge
 snmp_scrape_duration_seconds 0.023077785
 # HELP snmp_scrape_packets_retried Packets retried for get, bulkget, and walk.
 # TYPE snmp_scrape_packets_retried gauge
 snmp_scrape_packets_retried 0
 # HELP snmp_scrape_packets_sent Packets sent for get, bulkget, and walk; including retries.
 # TYPE snmp_scrape_packets_sent gauge
 snmp_scrape_packets_sent 3
 # HELP snmp_scrape_pdus_returned PDUs returned from get, bulkget, and walk.
 # TYPE snmp_scrape_pdus_returned gauge
 snmp_scrape_pdus_returned 0
 # HELP snmp_scrape_walk_duration_seconds Time SNMP walk/bulkwalk took.
 # TYPE snmp_scrape_walk_duration_seconds gauge
 snmp_scrape_walk_duration_seconds 0.023050813 

Any clue is welcome :)
Thx

[billbongo]

hello,
is there any idea of what's wrong ?
Need more info ?

[caiospessoa]

Did you ever find a fix for this one, @boogie777?
I'm trying to set up BGP with Arista devices, but the scrape only gets LocalAS, BGP identifier, and version.

[candlerb]

I think you're going about this the wrong way. You need to start with the generator, give it the BGP4-MIB file (in addition to all the dependent mib files, which make mibs fetches for you), and the following generator.yml:

modules:
  BGP4-MIB:
    walk:
      - bgpPeerTable

Then the generator outputs the following snmp.yml:

# WARNING: This file was auto-generated using snmp_exporter generator, manual changes will be lost.
modules:
  BGP4-MIB:
    walk:
    - 1.3.6.1.2.1.15.3
    metrics:
    - name: bgpPeerIdentifier
      oid: 1.3.6.1.2.1.15.3.1.1
      type: InetAddressIPv4
      help: The BGP Identifier of this entry's BGP peer - 1.3.6.1.2.1.15.3.1.1
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerState
      oid: 1.3.6.1.2.1.15.3.1.2
      type: gauge
      help: The BGP peer connection state. - 1.3.6.1.2.1.15.3.1.2
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
      enum_values:
        1: idle
        2: connect
        3: active
        4: opensent
        5: openconfirm
        6: established
    - name: bgpPeerAdminStatus
      oid: 1.3.6.1.2.1.15.3.1.3
      type: gauge
      help: The desired state of the BGP connection - 1.3.6.1.2.1.15.3.1.3
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
      enum_values:
        1: stop
        2: start
    - name: bgpPeerNegotiatedVersion
      oid: 1.3.6.1.2.1.15.3.1.4
      type: gauge
      help: The negotiated version of BGP running between the two peers - 1.3.6.1.2.1.15.3.1.4
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerLocalAddr
      oid: 1.3.6.1.2.1.15.3.1.5
      type: InetAddressIPv4
      help: The local IP address of this entry's BGP connection. - 1.3.6.1.2.1.15.3.1.5
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerLocalPort
      oid: 1.3.6.1.2.1.15.3.1.6
      type: gauge
      help: The local port for the TCP connection between the BGP peers. - 1.3.6.1.2.1.15.3.1.6
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerRemoteAddr
      oid: 1.3.6.1.2.1.15.3.1.7
      type: InetAddressIPv4
      help: The remote IP address of this entry's BGP peer. - 1.3.6.1.2.1.15.3.1.7
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerRemotePort
      oid: 1.3.6.1.2.1.15.3.1.8
      type: gauge
      help: The remote port for the TCP connection between the BGP peers - 1.3.6.1.2.1.15.3.1.8
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerRemoteAs
      oid: 1.3.6.1.2.1.15.3.1.9
      type: gauge
      help: The remote autonomous system number received in the BGP OPEN message.
        - 1.3.6.1.2.1.15.3.1.9
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerInUpdates
      oid: 1.3.6.1.2.1.15.3.1.10
      type: counter
      help: The number of BGP UPDATE messages received on this connection. - 1.3.6.1.2.1.15.3.1.10
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerOutUpdates
      oid: 1.3.6.1.2.1.15.3.1.11
      type: counter
      help: The number of BGP UPDATE messages transmitted on this connection. - 1.3.6.1.2.1.15.3.1.11
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerInTotalMessages
      oid: 1.3.6.1.2.1.15.3.1.12
      type: counter
      help: The total number of messages received from the remote peer on this connection.
        - 1.3.6.1.2.1.15.3.1.12
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerOutTotalMessages
      oid: 1.3.6.1.2.1.15.3.1.13
      type: counter
      help: The total number of messages transmitted to the remote peer on this connection.
        - 1.3.6.1.2.1.15.3.1.13
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerLastError
      oid: 1.3.6.1.2.1.15.3.1.14
      type: OctetString
      help: The last error code and subcode seen by this peer on this connection -
        1.3.6.1.2.1.15.3.1.14
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerFsmEstablishedTransitions
      oid: 1.3.6.1.2.1.15.3.1.15
      type: counter
      help: The total number of times the BGP FSM transitioned into the established
        state for this peer. - 1.3.6.1.2.1.15.3.1.15
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerFsmEstablishedTime
      oid: 1.3.6.1.2.1.15.3.1.16
      type: gauge
      help: This timer indicates how long (in seconds) this peer has been in the established
        state or how long since this peer was last in the established state - 1.3.6.1.2.1.15.3.1.16
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerConnectRetryInterval
      oid: 1.3.6.1.2.1.15.3.1.17
      type: gauge
      help: Time interval (in seconds) for the ConnectRetry timer - 1.3.6.1.2.1.15.3.1.17
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerHoldTime
      oid: 1.3.6.1.2.1.15.3.1.18
      type: gauge
      help: Time interval (in seconds) for the Hold Timer established with the peer
        - 1.3.6.1.2.1.15.3.1.18
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerKeepAlive
      oid: 1.3.6.1.2.1.15.3.1.19
      type: gauge
      help: Time interval (in seconds) for the KeepAlive timer established with the
        peer - 1.3.6.1.2.1.15.3.1.19
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerHoldTimeConfigured
      oid: 1.3.6.1.2.1.15.3.1.20
      type: gauge
      help: Time interval (in seconds) for the Hold Time configured for this BGP speaker
        with this peer - 1.3.6.1.2.1.15.3.1.20
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerKeepAliveConfigured
      oid: 1.3.6.1.2.1.15.3.1.21
      type: gauge
      help: Time interval (in seconds) for the KeepAlive timer configured for this
        BGP speaker with this peer - 1.3.6.1.2.1.15.3.1.21
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerMinASOriginationInterval
      oid: 1.3.6.1.2.1.15.3.1.22
      type: gauge
      help: Time interval (in seconds) for the MinASOriginationInterval timer - 1.3.6.1.2.1.15.3.1.22
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerMinRouteAdvertisementInterval
      oid: 1.3.6.1.2.1.15.3.1.23
      type: gauge
      help: Time interval (in seconds) for the MinRouteAdvertisementInterval timer
        - 1.3.6.1.2.1.15.3.1.23
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerInUpdateElapsedTime
      oid: 1.3.6.1.2.1.15.3.1.24
      type: gauge
      help: Elapsed time (in seconds) since the last BGP UPDATE message was received
        from the peer - 1.3.6.1.2.1.15.3.1.24
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4

This works for me, e.g. if I point it at a Cisco Nexus 9K:

# HELP bgpPeerRemoteAs The remote autonomous system number received in the BGP OPEN message. - 1.3.6.1.2.1.15.3.1.9
# TYPE bgpPeerRemoteAs gauge
bgpPeerRemoteAs{bgpPeerRemoteAddr="10.9.1.82"} 65002
bgpPeerRemoteAs{bgpPeerRemoteAddr="192.168.127.2"} 65000
bgpPeerRemoteAs{bgpPeerRemoteAddr="192.168.14.1"} 65000
...

I'm testing this on an old system with snmp-exporter 0.20.0, so I had to change the config a little to get the old form (with module and auth combined).

If this still doesn't work on your target device, then I suggest you try reducing max_repetitions as some targets don't like the large default value (25). If that still doesn't work, then look at tcpdump to see if there's any clue (although the authPriv means that the content will be encrypted)

---

Aside: you might want to tweak it a bit, e.g. to use enums for the status. Currently I get:

# HELP bgpPeerAdminStatus The desired state of the BGP connection - 1.3.6.1.2.1.15.3.1.3
# TYPE bgpPeerAdminStatus gauge
bgpPeerAdminStatus{bgpPeerRemoteAddr="10.9.1.82"} 2
bgpPeerAdminStatus{bgpPeerRemoteAddr="192.168.127.2"} 2
bgpPeerAdminStatus{bgpPeerRemoteAddr="192.168.14.1"} 2
...
# HELP bgpPeerState The BGP peer connection state. - 1.3.6.1.2.1.15.3.1.2
# TYPE bgpPeerState gauge
bgpPeerState{bgpPeerRemoteAddr="10.9.1.82"} 6
bgpPeerState{bgpPeerRemoteAddr="192.168.127.2"} 6
bgpPeerState{bgpPeerRemoteAddr="192.168.14.1"} 6

With a slight tweak to generator.yml:

modules:
  BGP4-MIB:
    walk:
      - bgpPeerTable
    overrides:
      bgpPeerAdminStatus:
        type: EnumAsStateSet
      bgpPeerState:
        type: EnumAsStateSet
      bgpPeerRemoteAddr:
        ignore: true

Now we get the following snmp.yml:

# WARNING: This file was auto-generated using snmp_exporter generator, manual changes will be lost.
modules:
  BGP4-MIB:
    walk:
    - 1.3.6.1.2.1.15.3
    metrics:
    - name: bgpPeerIdentifier
      oid: 1.3.6.1.2.1.15.3.1.1
      type: InetAddressIPv4
      help: The BGP Identifier of this entry's BGP peer - 1.3.6.1.2.1.15.3.1.1
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerState
      oid: 1.3.6.1.2.1.15.3.1.2
      type: EnumAsStateSet
      help: The BGP peer connection state. - 1.3.6.1.2.1.15.3.1.2
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
      enum_values:
        1: idle
        2: connect
        3: active
        4: opensent
        5: openconfirm
        6: established
    - name: bgpPeerAdminStatus
      oid: 1.3.6.1.2.1.15.3.1.3
      type: EnumAsStateSet
      help: The desired state of the BGP connection - 1.3.6.1.2.1.15.3.1.3
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
      enum_values:
        1: stop
        2: start
    - name: bgpPeerNegotiatedVersion
      oid: 1.3.6.1.2.1.15.3.1.4
      type: gauge
      help: The negotiated version of BGP running between the two peers - 1.3.6.1.2.1.15.3.1.4
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerLocalAddr
      oid: 1.3.6.1.2.1.15.3.1.5
      type: InetAddressIPv4
      help: The local IP address of this entry's BGP connection. - 1.3.6.1.2.1.15.3.1.5
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerLocalPort
      oid: 1.3.6.1.2.1.15.3.1.6
      type: gauge
      help: The local port for the TCP connection between the BGP peers. - 1.3.6.1.2.1.15.3.1.6
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerRemotePort
      oid: 1.3.6.1.2.1.15.3.1.8
      type: gauge
      help: The remote port for the TCP connection between the BGP peers - 1.3.6.1.2.1.15.3.1.8
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerRemoteAs
      oid: 1.3.6.1.2.1.15.3.1.9
      type: gauge
      help: The remote autonomous system number received in the BGP OPEN message.
        - 1.3.6.1.2.1.15.3.1.9
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerInUpdates
      oid: 1.3.6.1.2.1.15.3.1.10
      type: counter
      help: The number of BGP UPDATE messages received on this connection. - 1.3.6.1.2.1.15.3.1.10
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerOutUpdates
      oid: 1.3.6.1.2.1.15.3.1.11
      type: counter
      help: The number of BGP UPDATE messages transmitted on this connection. - 1.3.6.1.2.1.15.3.1.11
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerInTotalMessages
      oid: 1.3.6.1.2.1.15.3.1.12
      type: counter
      help: The total number of messages received from the remote peer on this connection.
        - 1.3.6.1.2.1.15.3.1.12
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerOutTotalMessages
      oid: 1.3.6.1.2.1.15.3.1.13
      type: counter
      help: The total number of messages transmitted to the remote peer on this connection.
        - 1.3.6.1.2.1.15.3.1.13
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerLastError
      oid: 1.3.6.1.2.1.15.3.1.14
      type: OctetString
      help: The last error code and subcode seen by this peer on this connection -
        1.3.6.1.2.1.15.3.1.14
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerFsmEstablishedTransitions
      oid: 1.3.6.1.2.1.15.3.1.15
      type: counter
      help: The total number of times the BGP FSM transitioned into the established
        state for this peer. - 1.3.6.1.2.1.15.3.1.15
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerFsmEstablishedTime
      oid: 1.3.6.1.2.1.15.3.1.16
      type: gauge
      help: This timer indicates how long (in seconds) this peer has been in the established
        state or how long since this peer was last in the established state - 1.3.6.1.2.1.15.3.1.16
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerConnectRetryInterval
      oid: 1.3.6.1.2.1.15.3.1.17
      type: gauge
      help: Time interval (in seconds) for the ConnectRetry timer - 1.3.6.1.2.1.15.3.1.17
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerHoldTime
      oid: 1.3.6.1.2.1.15.3.1.18
      type: gauge
      help: Time interval (in seconds) for the Hold Timer established with the peer
        - 1.3.6.1.2.1.15.3.1.18
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerKeepAlive
      oid: 1.3.6.1.2.1.15.3.1.19
      type: gauge
      help: Time interval (in seconds) for the KeepAlive timer established with the
        peer - 1.3.6.1.2.1.15.3.1.19
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerHoldTimeConfigured
      oid: 1.3.6.1.2.1.15.3.1.20
      type: gauge
      help: Time interval (in seconds) for the Hold Time configured for this BGP speaker
        with this peer - 1.3.6.1.2.1.15.3.1.20
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerKeepAliveConfigured
      oid: 1.3.6.1.2.1.15.3.1.21
      type: gauge
      help: Time interval (in seconds) for the KeepAlive timer configured for this
        BGP speaker with this peer - 1.3.6.1.2.1.15.3.1.21
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerMinASOriginationInterval
      oid: 1.3.6.1.2.1.15.3.1.22
      type: gauge
      help: Time interval (in seconds) for the MinASOriginationInterval timer - 1.3.6.1.2.1.15.3.1.22
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerMinRouteAdvertisementInterval
      oid: 1.3.6.1.2.1.15.3.1.23
      type: gauge
      help: Time interval (in seconds) for the MinRouteAdvertisementInterval timer
        - 1.3.6.1.2.1.15.3.1.23
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4
    - name: bgpPeerInUpdateElapsedTime
      oid: 1.3.6.1.2.1.15.3.1.24
      type: gauge
      help: Elapsed time (in seconds) since the last BGP UPDATE message was received
        from the peer - 1.3.6.1.2.1.15.3.1.24
      indexes:
      - labelname: bgpPeerRemoteAddr
        type: InetAddressIPv4

Now we get:

# HELP bgpPeerState The BGP peer connection state. - 1.3.6.1.2.1.15.3.1.2 (EnumAsStateSet)
# TYPE bgpPeerState gauge
bgpPeerState{bgpPeerRemoteAddr="10.9.1.82",bgpPeerState="active"} 0
bgpPeerState{bgpPeerRemoteAddr="10.9.1.82",bgpPeerState="connect"} 0
bgpPeerState{bgpPeerRemoteAddr="10.9.1.82",bgpPeerState="established"} 1
bgpPeerState{bgpPeerRemoteAddr="10.9.1.82",bgpPeerState="idle"} 0
bgpPeerState{bgpPeerRemoteAddr="10.9.1.82",bgpPeerState="openconfirm"} 0
bgpPeerState{bgpPeerRemoteAddr="10.9.1.82",bgpPeerState="opensent"} 0
bgpPeerState{bgpPeerRemoteAddr="192.168.127.2",bgpPeerState="active"} 0
bgpPeerState{bgpPeerRemoteAddr="192.168.127.2",bgpPeerState="connect"} 0
bgpPeerState{bgpPeerRemoteAddr="192.168.127.2",bgpPeerState="established"} 1
bgpPeerState{bgpPeerRemoteAddr="192.168.127.2",bgpPeerState="idle"} 0
bgpPeerState{bgpPeerRemoteAddr="192.168.127.2",bgpPeerState="openconfirm"} 0
bgpPeerState{bgpPeerRemoteAddr="192.168.127.2",bgpPeerState="opensent"} 0
bgpPeerState{bgpPeerRemoteAddr="192.168.14.1",bgpPeerState="active"} 0
bgpPeerState{bgpPeerRemoteAddr="192.168.14.1",bgpPeerState="connect"} 0
bgpPeerState{bgpPeerRemoteAddr="192.168.14.1",bgpPeerState="established"} 1
bgpPeerState{bgpPeerRemoteAddr="192.168.14.1",bgpPeerState="idle"} 0
bgpPeerState{bgpPeerRemoteAddr="192.168.14.1",bgpPeerState="openconfirm"} 0
bgpPeerState{bgpPeerRemoteAddr="192.168.14.1",bgpPeerState="opensent"} 0

But to be honest, I'm not sure that's actually necessary, e.g. ifOperStatus and ifAdminStatus just give a number as well. I suppose some queries are easier with the EnumAsStateSet form (e.g. "what percentage of time was the connection in 'established' state?")