This is an old revision of the document!
Let's get started! We guide you through the process from installing to getting NAV up and running, monitoring your network.
Follow these 8 steps:
In principle, NAV can run on any Unix-like platform, as long as Apache, postgresql, Python and Java are supported. Several distribution packages are available or you can install NAV from source if you like.
If you are looking for the smoothest install - go for the Debian package. Your procedure will then be:
All the NAV configuration files are gathered in the
etc directory of NAV.
ADMIN_MAILto the email account of your NAV administrator.
DOMAIN_SUFFIXto your domain.
userpw_nav. NAV will use this password to access the NAV database. For debugging purposes you use it yourself to access the database from the shell with
psql manage nav.
A number of configuration files adjust how your NAV home page looks. They are all located in the
For details on how to configure what, see the navhome-document.
Start the NAV back-end processes (daemons and cron jobs) with
nav start. Verify that the NAV processes are running with
Here is an example that shows that
smsd is down and the rest is up and running:
$/usr/sbin/nav status Up: alertengine cricket eventengine getDeviceData iptrace logengine mactrace maintengine networkDiscovery pping servicemon thresholdMon Down: smsd
If some of the processes are down use
nav start <processname> to start it. Verify with
nav status. For more information on the back-end processes, see here.
When you first direct your browser to the NAV page served by your Apache, you are unauthenticated and will have the access privileges of an anonymous user.
You may log in to the web interface as the user “admin”, using “admin” as your password. It is of course extremely recommended that you immediately change this password to something harder to guess.
The user “admin” is a member of the group “NAV Administrators”, and will therefore have access to absolutely everything in the web interface.
For this task you use the user adminstration panel. The task typically covers:
Adjust existing groups privileges or add new groups as you like.
NAV does not autodiscover your network, you need to seed the database with key information. Seeding is covered in this document.
After you have registered your equipment in NAV, the background processes starts collecting information with snmp:
Cricket statistics collection will not start before your Cricket configuration tree is built.
The cricket config builder runs nightly, as a consequence you have to wait till the next morning to see statistics. You may however kick start this process by manually running
Put simply; allow some time for your network to be fully discovered and managed