This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
gettingstarted [2007/10/03 18:22] faltin |
gettingstarted [2007/10/08 20:53] faltin |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Getting Started ====== | ====== Getting Started ====== | ||
- | This document covers the whole process from installing NAV to getting it up and running, monitoring your network. | + | Let's get started! We guide you through the process from installing to getting NAV up and running, monitoring your network. |
- | ===== Eight steps ===== | + | |
+ | ===== NAV in eight steps ===== | ||
Follow these 8 steps: | Follow these 8 steps: | ||
Line 16: | Line 17: | ||
- [[#Verify that your network is discovered]] | - [[#Verify that your network is discovered]] | ||
- Happy NAV'ing! :-) | - Happy NAV'ing! :-) | ||
+ | |||
Line 21: | Line 23: | ||
In principle, NAV can run on any Unix-like platform, as long as Apache, Perl, Python, PHP and Java are supported. | In principle, NAV can run on any Unix-like platform, as long as Apache, Perl, Python, PHP and Java are supported. | ||
- | Several distribution packages are available or you can install 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. | ||
+ | |||
+ | |||
+ | |||
==== Smoothest install ==== | ==== Smoothest install ==== | ||
Line 28: | Line 33: | ||
If you are looking for the smoothest install - go for the [[http://pkg-nav.alioth.debian.org/|Debian package]]. Your procedure will then be: | If you are looking for the smoothest install - go for the [[http://pkg-nav.alioth.debian.org/|Debian package]]. Your procedure will then be: | ||
- | - Install Debian | + | - Follow our [[navfaq#what_are_the_hardware_requirements|hardware requirements]]. Hook on a [[navfaq#any_requirements_for_the_cell_phone|cell phone]], if you like. |
- | - ''apt-get install nav'' (first add a line to your sources.list, see [[http://pkg-nav.alioth.debian.org/|the package doc]]). | + | - Install [[http://www.debian.org/|Debian]] |
+ | - ''aptitude install nav'' (first add a line to your sources.list, see [[http://pkg-nav.alioth.debian.org/|the package doc]]). | ||
- Follow the ''REAME.Debian'' cookbook | - Follow the ''REAME.Debian'' cookbook | ||
Line 51: | Line 57: | ||
A number of configuration files adjust how your NAV home page looks. They are all located in the ''etc/webfront''-directory. | 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. | For details on how to configure what, see the [[navhome]]-document. | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
===== Start NAV daemons and cron jobs ===== | ===== Start NAV daemons and cron jobs ===== | ||
- | Start the NAV daemons and cron jobs with ''nav start''. Verify that the NAV processes are running with | + | Start the NAV back-end processes (daemons and cron jobs) with ''nav start''. Verify that the NAV processes are running with |
- | ''nav status'' | + | ''nav status''. |
+ | Here is an example that shows that ''smsd'' is down and the rest is up and running: | ||
<code> | <code> | ||
- | $/etc/init.d/nav status | + | $/usr/sbin/nav status |
- | Up: alertengine cricket eventengine getDeviceData getvtpvlan iptrace logengine mactrace maintengine | + | Up: alertengine cricket eventengine getDeviceData iptrace logengine mactrace maintengine networkDiscovery pping servicemon thresholdMon |
- | networkDiscovery pping servicemon smsd thresholdMon | + | Down: smsd |
</code> | </code> | ||
- | If some of the processes are not running use ''nav start <processname>'' to start it. | + | 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 [[backendprocesses|here]]. |
Line 129: | Line 146: | ||
NAV does not autodiscover your network, you need to seed the database with key information. Seeding is covered in | NAV does not autodiscover your network, you need to seed the database with key information. Seeding is covered in | ||
[[seedessentials|this document]]. | [[seedessentials|this document]]. | ||
+ | |||
+ | |||
+ | |||
Line 142: | Line 162: | ||
* 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 ''getDevicedata.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 ''getDevicedata.log'' file. | ||
- | After the individual components has its collected data the [[backendprocesses#mac-to-switch_port_collector_mactrace_getboksmacs_cam_logger|mac-to-switchport collector]] 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 |
- | [[backendprocesses#physical_topology_builder_networkdiscovery_topology|physical topology builder]] that runs every hour. | + | [[backendprocesses#networkdiscovery_topology|physical topology builder]] that runs every hour. |
- | Cricket statistics collection will not start before your Cricket config tree is built. | + | Cricket statistics collection will not start before your Cricket configuration tree is built. |
- | [[backendprocesses#collecting_statistics|The cricket config builder]] runs nightly, which you have to wait till the next moring to see statistics. You may however kickstart this process by manually running ''makecricketconfig.pl''. | + | [[backendprocesses#collecting_statistics|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 ''makecricketconfig.pl''. |
- | Put simply; allow some time for your network to be fully discovered :-) | + | Put simply; allow some time for your network to be fully discovered and managed :-) |