This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
gettingstarted [2010/11/18 13:56] morten replace gDD info with ipdevpoll |
gettingstarted [2011/04/11 06:30] (current) morten fix various stale details |
||
---|---|---|---|
Line 23: | Line 23: | ||
===== Install NAV and dependencies ===== | ===== Install NAV and dependencies ===== | ||
- | In principle, NAV can run on any Unix-like platform, as long as Apache, postgresql, Perl, Python, PHP and Java are supported. | + | 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. | Several distribution packages are available or you can install NAV from source if you like. | ||
* See our [[navdownload|download page]] for details. | * See our [[navdownload|download page]] for details. | ||
Line 40: | Line 40: | ||
+ | ==== Even easier install ==== | ||
+ | * Use our available [[navappliance|virtual appliance]] with NAV preinstalled! | ||
===== Adjust NAV configuration files ===== | ===== Adjust NAV configuration files ===== | ||
Line 51: | Line 53: | ||
- In ''nav.conf'' set ''ADMIN_MAIL'' to the email account of your NAV administrator. | - In ''nav.conf'' set ''ADMIN_MAIL'' to the email account of your NAV administrator. | ||
- In ''nav.conf'' set ''DOMAIN_SUFFIX'' to your domain. | - In ''nav.conf'' set ''DOMAIN_SUFFIX'' to your domain. | ||
- | - In ''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''. | + | - In ''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 nav nav''. |
Line 77: | Line 79: | ||
<code> | <code> | ||
$/usr/sbin/nav status | $/usr/sbin/nav status | ||
- | Up: alertengine cricket eventengine getDeviceData iptrace logengine mactrace maintengine networkDiscovery pping servicemon thresholdMon | + | Up: alertengine cricket eventengine ipdevpoll logengine mactrace maintengine networkDiscovery pping servicemon snmptrapd thresholdMon |
Down: smsd | Down: smsd | ||
</code> | </code> | ||
Line 160: | Line 162: | ||
After you have registered your equipment in NAV, the background processes starts collecting information with snmp: | After you have registered your equipment in NAV, the background processes starts collecting information with snmp: | ||
- | * [[backendprocesses#ipdevpoll|ipdevpoll]] should notice the new IP device within 2 minutes, and will then classify the new box in terms of OIDs supported. This can be seen from the IP device report from the [[reporttool|report tool]]. | + | * [[backendprocesses#ipdevpoll|ipdevpoll]] should notice the new IP device within 2 minutes and will start collecting switch/router port information and more. Verify the status using the report tool (or network explorer). You may also check the ''ipdevpoll.log'' file. |
- | * The next step for getDeviceData will be to gather switch/router port information and more. Verify the status using the report tool (or network explorer). You may also check the ''ipdevpoll.log'' file. | + | |
After the individual components has its collected data [[backendprocesses#mactrace|mactrace]] will every 15 minutes gather mac to switch port data. This will in turn be used by the | After the individual components has its collected data [[backendprocesses#mactrace|mactrace]] will every 15 minutes gather mac to switch port data. This will in turn be used by the |