I have created a simple web application for monitoring routers running Mikrotik RouterOS.
It's been running on our network with eighty routers for about a year and it proved sometimes quite helpful so I decided to share it with you and release it under GPL.
Main functions:
- Signal, CPU load, uptime, latency graphing,
- Traffic monitoring
Screenshots:
Routers list
Signal graphs
Traffic monitoring
Download:
Direct link http://phill.gotdns.org/rosinfo.php
or somewhere on my homepage http://phill.gotdns.org/
Installation:
All information regarding installation is in the file docs/INSTALL.
Part of the README file
Introduction
============
ROSInfo is a simple tool for monitoring signal levels, traffic and network
latency of x86 machines, RouterBoards and other devices running Mikrotik
RouterOS. It was designed to be used with Mikrotik RouterOS v 2.9 and is being
developed and tested on a large network with many Mikrotik routers.
Environment
===========
Hardware
--------
Currently supported and tested are all versions of Mikrotik RouterOS 2.9.
Software requirements
---------------------
- Linux
- Apache
- PHP5 with support for snmp
- RRDTool 1.2
- php-rrdtool (not mandatory)
- SNMP utilities
- Cron or another scheduling daemon
Instalation
===========
- Unpack the tarball to a directory accessible by Apache.
- Make sure, that the ./rrd directory and it's subdirectories are writable by
Apache. Use chown and chmod to achieve this.
- Open file ./include/config.inc and change the contents to fit your needs.
- Setup cron to start the fetchexec.php file every 5 minutes.
Cron setup
----------
You can use the following statement placed in /etc/crontab. Make sure you
correct the path to the file fetchexec.php and php binary.
*/5 * * * * www-data /usr/bin/php /path/to/rosinfo/fetchexec.php > /dev/null 2>&1
Recomendations
==============
Do not start the fetchexec.php file manualy unless you are logged in as a user
under which Apache is running. You can use something like su www-data and then
start the fetchexec.php.
If you want to see some debug information from the fetchexec process, uncomment
the line $debug=1; in file config.inc. The output will be saved in a few
logfiles.
Phill