User Tools

Site Tools


gettingstarted

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
gettingstarted [2007/10/05 07:20]
faltin
gettingstarted [2011/04/11 08:30]
morten fix various stale details
Line 17: Line 17:
    - [[#Verify that your network is discovered]]    - [[#Verify that your network is discovered]]
    - Happy NAV'​ing! :-)    - Happy NAV'​ing! :-)
 +
  
  
Line 22: Line 23:
 ===== Install NAV and dependencies ===== ===== Install NAV and dependencies =====
  
-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, ​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 34: Line 36:
    - 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.    - 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.
    - Install [[http://​www.debian.org/​|Debian]]    - Install [[http://​www.debian.org/​|Debian]]
-   - ''​apt-get ​install nav''​ (first add a line to your sources.list,​ see [[http://​pkg-nav.alioth.debian.org/​|the package doc]]).+   - ''​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
  
  
 +==== Even easier install ====
  
 +  * Use our available [[navappliance|virtual appliance]] with NAV preinstalled!
 ===== Adjust NAV configuration files ===== ===== Adjust NAV configuration files =====
  
Line 49: 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 75: 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 145: Line 149:
 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 157: 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#​getdevicedata|getDeviceData]] should notice the new IP device within ​minutesand 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 ​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 ''​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, 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''​. [[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 and managed :-) Put simply; allow some time for your network to be fully discovered and managed :-)
  
gettingstarted.txt · Last modified: 2011/04/11 08:30 by morten