Replies: 1 comment
-
@SuperQ It's unclear to me why this one was put in Q&A since it looks like there is some sort of limitation in the exporter or the generator that is affecting its ability to correctly read/parse the data that snmpwalk can successfully get. If there is any clear indicator that there might be any errors on my end, please let me know so I can further investigate |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Host operating system: output of
uname -a
Linux 5.15.0-67-generic #74-Ubuntu SMP Wed Feb 22 14:14:39 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
snmp_exporter version: output of
snmp_exporter -version
0.26.0
What device/snmpwalk OID are you using?
Juniper MX204 - OID 1.3.6.1.4.1.2636.3.45.1.1.1.1.5
snmp.yaml entry added by the generator:
If this is a new device, please link to the MIB(s).
Junos-OS/20.4R2/mib-jnx-bfd.txt
What did you do that produced an error?
I configured snmp_exporter to collect some metrics from different Juniper devices (switches and routers) and the whole process has been working fine, except if I add OID 1.3.6.1.4.1.2636.3.45.1.1.1.1.5 - jnxBfdSessIntfName to the Juniper MX204 router module, where SNMP walk executed by the exporter starts to timeout.
What did you expect to see?
The interface names associated with the BFD sessions. Output of a snmpwalk:
The same OID is also walked by Nagios without problems.
What did you see instead?
The whole snmp request for that module fails with a timeout:
Debug log:
The walk hangs exactly once the exporter reaches OID 1.3.6.1.4.1.2636.3.45.1.1.1.1.5, and the whole scrape process is back to green once it is removed from the configuration.
Beta Was this translation helpful? Give feedback.
All reactions