Support for Mikrotik?

[sevrinrobstad]

Mikrotiks devices should be fully supported by NAV. Basic support seems to already be there, but a whole lot more can be monitored on a Mikrotik. Latest MIB can be downloaded from here: https://wiki.mikrotik.com/wiki/Manual:SNMP#Management_information_base_.28MIB.29 (Direct link: https://box.mikrotik.com/f/0d2bf2e84c434e7a9754/?dl=1)

[lunkwill42]

Hi @pokemongomongo - it would be helpful if you would be more specific as to what is missing from NAV's support - especially since, AFAIK, we have no Mikrotik devices to test on.

[sevrinrobstad]

Hi, and thanx for the quick reply.

All Mikrotik devices (with RouterOS) can do full routing, queues, dhcp, be a wireless controller and much more. Not all of them have the CPU to do so efficiently though.

Basically I want full support for all the things Mikrotik lets you monitor.

In my particular case I want to monitor DHCP leases per dhcp server, wireless connection through the wireless controller capsman, wireless TX/RX quality (for P2P links), and registrations through Hotspot controller, but there might be more that could be nice to monitor.

If that’s not practical, I at least miss mtxrHotspot mtxrDHCP mtxrPOE mtxrWireless mtxrQueues mtxrHealth

From: Morten Brekkevold notifications@github.com Sent: Monday, May 6, 2019 8:22 To: Uninett/nav nav@noreply.github.com Cc: pokemongomongo sevrin@pixel.no; Mention mention@noreply.github.com Subject: Re: [Uninett/nav] Support for Mikrotik? (#1932)

Hi @pokemongomongo https://github.com/pokemongomongo - it would be helpful if you would be more specific as to what is missing from NAV's support - especially since, AFAIK, we have no Mikrotik devices to test on.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Uninett/nav/issues/1932#issuecomment-489511634 , or mute the thread https://github.com/notifications/unsubscribe-auth/AFP6XN2ZWUG4TZUSMF2OHFLPT7FAFANCNFSM4HK4AZXQ . http://www.mailscanner.tv/1x1spacer.gif

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/Uninett/nav/issues/1932#issuecomment-489511634", "url": "https://github.com/Uninett/nav/issues/1932#issuecomment-489511634", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

[lunkwill42]

You want to graph timeseries data from a Mikrotik router, or are you talking about modelling new inventory models that don't exist in NAV thus far? Or both? The former is much simpler than the latter.

[sevrinrobstad]

I’m not quite sure I understand the question, but I think it’s the former. I want to be able to log for example DHCP clients, Registered wireless users, Wireless link quality and such.

Its just a name and a number that should be graphed.. 😊

From: Morten Brekkevold notifications@github.com Sent: Monday, June 17, 2019 11:02 To: Uninett/nav nav@noreply.github.com Cc: pokemongomongo sevrin@pixel.no; Mention mention@noreply.github.com Subject: Re: [Uninett/nav] Support for Mikrotik? (#1932)

You want to graph timeseries data from a Mikrotik router, or are you talking about modelling new inventory models that don't exist in NAV thus far? Or both? The former is much simpler than the latter.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Uninett/nav/issues/1932?email_source=notifications&email_token=AFP6XN53U7T24ZEVLKCAZHTP25HHZA5CNFSM4HK4AZX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODX2QQZI#issuecomment-502597733 , or mute the thread https://github.com/notifications/unsubscribe-auth/AFP6XNZTARHE6XTNKFNS773P25HHZANCNFSM4HK4AZXQ . https://s3.amazonaws.com/msv5/images/spacer.gif

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/Uninett/nav/issues/1932?email_source=notifications\u0026email_token=AFP6XN53U7T24ZEVLKCAZHTP25HHZA5CNFSM4HK4AZX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODX2QQZI#issuecomment-502597733", "url": "https://github.com/Uninett/nav/issues/1932?email_source=notifications\u0026email_token=AFP6XN53U7T24ZEVLKCAZHTP25HHZA5CNFSM4HK4AZX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODX2QQZI#issuecomment-502597733", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ] -- This message has been scanned for viruses and dangerous content by http://www.mailscanner.info/ MailScanner, and is believed to be clean.

-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

[lunkwill42]

I’m not quite sure I understand the question, but I think it’s the former. I want to be able to log for example DHCP clients, Registered wireless users, Wireless link quality and such. Its just a name and a number that should be graphed..

As long as these are values that can be read directly from MIB objects, the simplest solution is to implement a new sensor plugin for ipdevpoll: https://nav.uninett.no/doc/4.9/hacking/adding-environment-probe-support.html (as long as one is comfortable with calling these readouts "sensors").

Otherwise, a bespoke Mikrotik plugin would be in order (like statsystem, which runs as part of the 1minstats job).

One bit that is missing from NAV, though, is a generic SNMP stats collector, that just collects SNMP data as configured in some config file, and ships it to Graphite, also as configured in that file. Users had that option when NAV integrated with Cricket, but since SNMP collection moved into NAV, Cricket was dropped.

At the very least, you would need to identify the exact MIB objects that should be collected and graphed.

[lunkwill42]

Closing due to lack of activity.