Error "error walking target x.x.x.x: request timeout (after 3 retries)" about grafana-mikrotik HOT 12 CLOSED

SNMPv2-SMI::enterprises.14988.1.1.20.2.1 = No more variables left in this MIB View (It is past the end of the MIB tree)

1.3.6.1.4.1.14988.1.1.20.2.1.* Is responsible for IKE security association. Should be displayed when ipsec is running, but I haven't tested that

Error scraping target" err="error walking target x.x.x.x: request timeout (after 3 retries)

never seen such a issue. I use SNMP v3 trap in my mikrotik and snmp_exporter 0.20.0
Try running snmp_exporter from my repository, he 100% work and open in you browser http://host.ip.address:9116/snmp?module=mikrotik&target=mikrotik.ip.address

from grafana-mikrotik.

yes, I tested 1.3.6.1.4.1.14988.1.1.20.2.1.* works if ipsec connect is active

from grafana-mikrotik.

I guess the problem may due to lack of IPsec conn in my setup. I have masked 1.3.6.1.4.1.14988 in snmp.yml and the rest works well.

from grafana-mikrotik.

this is not error
do not need to masked, 1.3.6.1.4.1.14988 does not interfere with the work even if there is no data in this OID

from grafana-mikrotik.

I have a same issue
http://localhost:9116/snmp?target=192.168.1.254&module=mikrotik

output: `An error has occurred while serving metrics:

error collecting metric Desc{fqName: "snmp_error", help: "Error scraping target", constLabels: {}, variableLabels: []}: error walking target 192.168.1.254: request timeout (after 3 retries)`

prometheus config:
`scrape_configs:

• job_name: 'prometheus'
  scrape_interval: 5s

  static_configs:

  • targets: ['localhost:9090']

• job_name: 'Mikrotik'
  static_configs:

  • targets:
    • 192.168.1.254 # SNMP device.
      metrics_path: /snmp
      params:
      module: [mikrotik]
      relabel_configs:
  • source_labels: [address]
    target_label: __param_target
  • source_labels: [__param_target]
    target_label: instance
  • target_label: address
    replacement: localhost:9116
    `
    Targets:
    

from grafana-mikrotik.

@auterpring
maybe you have 7.x version of rOS installed ?
In version 7, delays in the response to SNMP on weak models were noticed

from grafana-mikrotik.

@auterpring maybe you have 7.x version of rOS installed ? In version 7, delays in the response to SNMP on weak models were noticed

No, I have 6.48.3. RouterOS version.
BTW, when I use MIB Browser, I can get all information and OIDs

from grafana-mikrotik.

@auterpring maybe you have 7.x version of rOS installed ? In version 7, delays in the response to SNMP on weak models were noticed

in Mikrotik log I can see, that exporter is working

g

from grafana-mikrotik.

port 9116 open? could it be that the log is generated due to the MIB Browser ?
try opening exporter_ip:9116 and manually fill in the required fields

@auterpring maybe you have 7.x version of rOS installed ? In version 7, delays in the response to SNMP on weak models were noticed

in Mikrotik log I can see, that exporter is working g

from grafana-mikrotik.

port 9116 open? could it be that the log is generated due to the MIB Browser ? try opening exporter_ip:9116 and manually fill in the required fields

@auterpring maybe you have 7.x version of rOS installed ? In version 7, delays in the response to SNMP on weak models were noticed

in Mikrotik log I can see, that exporter is working g

port 9116 is open

I resolve this issue using base snmp.yml from prometheus/snmp_exporter.
Now I try to generate new snmp.yml file

from grafana-mikrotik.

@auterpring
The problem is not snmp.yml
Your problem is that Prometheus cannot reach port 9116 of the exporter
Try specifying a real (not localhost) exporter IP in prometheus.yml, like replacement: 192.168.1.5:9116

from grafana-mikrotik.

@auterpring The problem is not snmp.yml Your problem is that Prometheus cannot reach port 9116 of the exporter Try specifying a real (not localhost) exporter IP in prometheus.yml, like replacement: 192.168.1.5:9116

oh, it works with any other module

besides mikrotik

from grafana-mikrotik.