There are several options for you. You’ll likely get the archive working on any Unix system, where you can satisfy the dependencies (amazingly enough, Windows too!).
You can get it running on Debian/Ubuntu within 5 minutes (more details in Generic Installation Procedure):
sudo apt-get install apache2 libapache2-mod-php5 mysql-server libnet-snmp-perl libcrypt-rijndael-perl libcrypt-hcesha-perl libcrypt-des-perl libdigest-hmac-perl libio-pty-perl libnet-telnet-perl libalgorithm-diff-perl librrds-perl php5-mysql php5-snmp php5-gd php5-mcrypt rrdtool libsocket6-perl
Optional (read below for details): libweb-simple-perl libnet-ntp-perl libnet-dns-perl
Then perform the following steps:
- create a /nedi folder somewhere (preferable in /var) and extract the tarball. Change permission to www-data
- In /etc edit apache2/sites-enabled/000-default.conf and adjust document root to /var/nedi/html
- edit apache2/apache2.conf and change /var/www to /var/nedi/html as well
- Optionally adjust php5/apache2/php.ini to increase max upload and post size
- run nedi -i and you should be able to login with admin/admin
- For security reasons, you should at least limit access to SSL and prohibit showing directory indexes…
The installation for Redhat/CentOS is similar (e.g. with postgres backend):
yum -y install perl-Net-Telnet perl-Socket6 perl-Algorithm-Diff perl-Net-Telnet perl-Net-SNMP net-snmp rrdtool perl-RRD-Simple.noarch perl-Time-HiRes-Value.noarch perl-Class-DBI-Pg.noarch perl-DBD-Pg perl-IO-Pty-Easy.noarch perl-libwww-perl.noarch postgresql php-pgsql php-process
Some faithful community members did a great job in documenting their installations with a lot more details:
Generic Installation Procedure
- Satisfy the dependencies listed below.
- Extract the NeDi archive (e.g. to /var/nedi). Move the files in html to your webserver’s document root (e.g. /var/www/htdocs) or adjust the document root.
- Edit nedi.conf to fit your needs (Please use the new one as copying your existing config may lead to errors, if new items are missing). If you get ‘Dude, where is nedi.conf?’ link it to /etc.
- Cd to /var/nedi (or whatever you chose) and type ./nedi.pl -i to initialize the backend. Starting with NeDi 1.4, you can use -i nodrop for updating an existing DB structure without the need for DB admin credentials. Alternatively -i updatedb will do just that without any loss of data.
- The monitoring daemon moni.pl can be started from commandline, startup script or the GUI.
- Since syslog.pl requires a priviledged port (514) a simple workaround (to avoid running it as root) would be to forward a high port via system’s FW. This means something like this for Linux: iptables -A PREROUTING -t nat -p udp –dport 514 -j REDIRECT –to-port 1514. Just set $port in syslog.pl to 1514 (or whatever you chose the port to be). Now you can even restart it from the GUI with System-Services.
- A similar setup can be implemented for snmptrapd: iptables -A PREROUTING -t nat -p udp –dport 162 -j REDIRECT –to-port 1162.
Head over to the Documentation pages once you’re done here…
The computer requirements depend on the size of your network (surprised?). A single 2GHz core and 1GB Ram will do fine for networks with 500 devices and 10’000 nodes. You may consider increasing this for larger networks…
The NeDi script itself uses up to 150MB of RAM on a discovery run. If you want to include Tobi’s RRDtool, you’ll need ~200KB disk storage per interface (can be adjusted with rrdsize in nedi.conf).
The discovery part is programmed in Perl and needs those additional modules:
- LWP::UserAgent (optional HTTP service monitoring and getting info from Cisco phones)
- Net::DNS::Resolver (optional DNS service monitoring)
- Net::NTP (optional NTP service monitoring, e.g monitor actual stratum)
- IO::Tty (optional SSH support)
- libnet (provides Net::SMTP for alerts)
The frontend requires a webserver providing PHP with the following addons:
- GD (for Topology-Map)
- MCRYPT for SHA256 password encryption