How to monitoring BGP on Mikrotik Device?

Article Comments

Hi there,

There are no already defined sensors here.

Maybe this article helps to create the needed sensors on your own.

Kind regards,
Birk Guttmann, Tech Support Team


Nov, 2019 - Permalink

I already try add bgp sensor with device template but there is no respon.

Thanks


Nov, 2019 - Permalink

Hi,

There are also other solutions provided.

Have you tried those?

Kind regards,
Birk Guttmann, Tech Support Team


Nov, 2019 - Permalink

For some reasons, second way (custom script via powershell) not possible to try at this time.

any advice?


Dec, 2019 - Permalink

Hi,

Please make sure that SNMP is enabled and works fine with the PRTG Probe Server. Have you already checked this?

Can you get results with the SNMP Tester that is also mentioned in the article?

Kind regards,
Birk Guttmann, Tech Support Team


Dec, 2019 - Permalink

SNMP already enabled and works, it shows with all sensor / interface (except BGP sensor) appears normally. This BGP monitoring issue only on mikrotik routerOS device.


Dec, 2019 - Permalink

Hi,

Sorry, I have to ask again.

Can you get results with the SNMP Tester that is also mentioned in the article?

Kind regards,
Birk Guttmann, Tech Support Team


Dec, 2019 - Permalink

Here is the results, I run two times test.

First test to show system uptime, Works.

Paessler SNMP Tester 5.2.3 Computername: EKOWA Interface: (x.x.x.x)
12/21/2019 8:40:36 PM (33 ms) : Device: 202.159.xx.xx
12/21/2019 8:40:36 PM (51 ms) : SNMP V2c
12/21/2019 8:40:36 PM (70 ms) : Uptime
12/21/2019 8:40:36 PM (331 ms) : SNMP Datatype: ASN_TIMETICKS
12/21/2019 8:40:36 PM (351 ms) : -------
12/21/2019 8:40:36 PM (372 ms) : DISMAN-EVENT-MIB::sysUpTimeInstance = 1131478900 ( 130 days )
12/21/2019 8:40:36 PM (682 ms) : SNMP Datatype: ASN_TIMETICKS
12/21/2019 8:40:36 PM (703 ms) : HOST-RESOURCES-MIB::hrSystemUptime.0 = 1131478900 ( 130 days )
12/21/2019 8:40:36 PM (720 ms) : Done

Second test with custom OID BGP, Null. 

Paessler SNMP Tester 5.2.3 Computername: EKOWA Interface: (x.x.x.x)
12/21/2019 8:41:13 PM (39 ms) : Device: 202.159.xx.xx
12/21/2019 8:41:13 PM (58 ms) : SNMP V2c
12/21/2019 8:41:13 PM (77 ms) : Custom OID 1.3.6.1.2.1.15.3
12/21/2019 8:41:14 PM (455 ms) : SNMP Datatype: ASN_NULL
12/21/2019 8:41:14 PM (473 ms) : -------
12/21/2019 8:41:14 PM (490 ms) : Value: NULL2
12/21/2019 8:41:14 PM (508 ms) : Done

Dec, 2019 - Permalink

Hi there,

Please try to use the walk option in the tester with the following OID.

1.3.6.1.2.1.15.3

What result do you get?

Kind regards,
Birk Guttmann, Tech Support Team


Dec, 2019 - Permalink

Here is the results, seems like not responding.

----------------------- New Test ----------------------- Paessler SNMP Tester 5.2.3 Computername: EKOWA Interface: (x.x.x.x) 12/24/2019 10:43:57 AM (6 ms) : Device: 202.159.xx.xx 12/24/2019 10:43:57 AM (9 ms) : SNMP V2c 12/24/2019 10:43:57 AM (11 ms) : Walk 1.3.6.1.2.1.15.3

----------------------- New Test ----------------------- Paessler SNMP Tester 5.2.3 Computername: EKOWA Interface: (x.x.x.x) 12/24/2019 10:48:08 AM (9 ms) : Device: 202.159.xx.xx 12/24/2019 10:48:08 AM (15 ms) : SNMP V2c 12/24/2019 10:48:08 AM (19 ms) : Walk 1.3.6.1.2.1.15.3


Dec, 2019 - Permalink

The Mikrotik might simply not support this. Please check Luciano Lingnau's reply on the matter. The following is basically all we have in terms of Mikrotik monitoring.


Dec, 2019 - Permalink