version is 3.4.1rc1
|
Documentation
Releases
Knowledge base
Sample configurations |
InstallationThere is an "INSTALL" file shipped with the distribution, briefly describing the installation procedures. Detailed description follows. For the NeTAMS system to be working successfully, it is necessary:
a) will you use the UNIX router for the traffic forwarding, and NeTAMS will be set up on the same computer, or there will be a separate router (PC or Cisco) sending traffic data towards. b) do you want to perform the traffic accounting only, or it is necessary for you to limit an access for some of the clients (for example, when one exceed its quota or balance zeroes) In case of UNIX router doing traffic limiting the Linux or FreeBSD operating system are working well. For Linux, IPQ module will be required, which exist in majority of distributions as the part of 2.4..x and 2.6..x kernels, and iptables package. You can verify its presence within the system by looking for netfilter/ip_queue.o file. For FreeBSD, it is necessary to work through IPFW/divert socket mechanism, when kernel must be configured to support "options IPFIREWALL" and "options IPDIVERT". To be convinced of the presence of the modules, look into the /.var/log/dmesg.today file and search for "ipfw initialized, divert enabled..." line. NeTAMS works under FreeBSD versions from 4.x up to CURRENT. If the traffic collector is another device (Cisco or PC-router), it is necessary to separately install this collector (flowprobe, fprobe, ipfw2netflow for Linux/FreeBSD/Solaris, possibly it will wokr under OpenBSD/NetBSD) and to install NeTAMS on the different server. In that case the hardware requirements are lower. On the server where NeTAMS is running it is desirable to establish a database server (MySQL or PostgresSQL) and a Web server (Apache). From the best practices, for 100-node network there will be gigabyte of disk space for database, and ~200 megebaytes for static HTML report pages are required. The list of the packets is given below (example is for ALTLinux Master 2.2):
For the FreeBSD everything which necessary (except for Apache and MySQL) goes in standard set. You should not create the databases and tables for NeTAMS - program will do it automatically on demand. Now you should download the NeTAMS distribution, unpack, compile and install it. At the current moment you can use NeTAMS-STABLE version , accessible from here: http://www.netams.com/download.html, or NeTAMS-CURRENT also (containing new functions and possible unstable), which is accessible through anonymous CVS:
cvs -d :pserver:netams@netams.netams.com:/netams/cvs checkout netams
In the majority of the cases NeTAMS-STABLE will be fine for you.Archive name has the following format: netams-3.2.10.tar.gz where 3 is version number, 2 is subversion number and 10 is the build number. Unpack: tar zxvf netams-3.2.XXXX.tar.gz cd netams-3.2.XXXX Start the bulid: make Configuration script, configure.sh, will try to fing the installed libraries and tune up other parameters, resulting with Makefile file. You can later edit it and do rebuild. Compile errors are usually caused by one Linux distribution keping its installed library or header files in unusual place. You should modify first lines of the script to put neccessary paths and do the full rebuild: make distclean && make. As a result you should obtain executable files netams, netamsctl, flowprobe, ulog2netflow and ipfw2netflow in src/ directory . Run "make install" to put them onto the right place, among man pages and sample configs. Please note you have to play with the CGI folder and startup script yourself. Command line keys are following: -l to log all netams activity onto the log-file (default is /var/log/netams.log) -d do not detach from the terminal and stay in debug mode, foreground -q not to write anyting but "NeTAMS" word upon startup -f configuration file name follows, default is /etc/netams.cfg for Linux and Solaris and /usr/local/etc/netams.cfg for FreeBSD. |