This is an old revision of the document!
Note: The old gettingstarted-document is out of date - if you want - have a look anyway
This document covers the whole process from installing the basic system to seeding your NAV database so that your NAV is up and running. For covered topics, see table of content.
A good reference for this first task is the cookbook for installing NAV on RHEL4 / CentOS4. Your procedure should cover:
The NAV postgres databases need to be initialized. Tell me how…
This section should cover:
All the NAV configuration files are gathered in the etc
directory of NAV.
nav.conf
set ADMIN_MAIL
to the email account of your NAV administrator.nav.conf
set DOMAIN_SUFFIX
to your domain.db.conf
set 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 etc/webfront
-directory.
For details on how to configure what, see the navhome-document.
Start the NAV daemons and cron jobs with nav start
. Verify that the NAV processes are running with
nav status
$/etc/init.d/nav status Up: alertengine cricket eventengine getDeviceData getvtpvlan iptrace logengine mactrace maintengine networkDiscovery pping servicemon smsd thresholdMon
If some of the processes are not running use nav start <processname>
to start it.
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. See this document for details. 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:
the status using the report tool (or network explorer). You may also check the getDevicedata.log
file.
After the individual components has its collected data the mac-to-switchport collector will every 15 minutes gather mac to switch port data. This will in turn be used by the physical topology builder that runs every hour.
Put simply; allow some time for your network to be fully discovered :)