MetaNAV

alertprofiles

2009-01-28T15:44:17+02:00

Alert Profiles was rewritten for NAV 3.5 and now resembles the look and feel found elsewhere in NAV. The functionality is with few exceptions the same as pre-3.5, so the general description given below is still representative. For reference though, you can browse through the [manual of the old Alert Profiles]. Please keep in mind that the GUI has changed. We will in due time make an updated manual.

arnold

2010-04-16T20:58:22+02:00

This documentation is for Arnold in NAV 3.4 and newer. For previous NAV versions, see an older revision of this page (dated 2008/04/01). Arnold is a subsystem to NAV 3, first released in NAV 3.1. Version 2 of Arnold was released in NAV 3.4. Arnold is a port-blocker and vlan changer, and was originally made to be able to easier remove mischievers from the campus-internet.

arnoldv2

2008-04-03T09:09:22+02:00

This document is under construction. Arnold is a subsystem to NAV 3, first released in NAV 3.1. Arnold is a port-blocker and vlan changer, and was originally made to be able to easier remove mischievers from the campus-internet. This document will give you information about how Arnold works and how to use and configure it. A FAQ-section will be added as questions are received.

backendprocesses

2010-05-18T12:15:05+02:00

NAV has a number of back-end processes. This document gives an overview, listing key information and detailed description for each process. We also give references to documentation found elsewhere on metaNAV. The following figure complements this document (the NAV 3.3 snmptrapd is not included in the figure):

bugtracker

2008-07-03T15:45:46+02:00

In later times NAV developers and users have been complaining about the speed and feel of Sourceforge.net as a tool in the development. Reporting bugs and issues should be extremly easy and fast, as this causes _more_ reports, and more information is allways good.

categoriesandtypes

2007-05-11T12:53:42+02:00

In NAV equipment is classified in categories. The categories are predefined by NAV and cannot be altered. When you add new equipment for NAV to monitor, you classify the equipment according to these categories. There are 7 categories: CATEGORY DESCRIPTION SNMP required? GW A router. Operates on layer 3 (IP layer) yes GSW A router and switch in one device. Operates on layer 2 and 3. A given port may configured for switching or for routing. An example is Catalyst 6500 (in na…

certifyequipment

2007-09-16T09:46:17+02:00

FIXME This page is not finished (and may not ever be) - please ignore it for the time being We have put a lot of effort into making the SNMP collection system as general as possible. All SNMP OIDs are i.e. structured in a separate OID database. Whenever possible we have chosen standard MIBs for our collection. In certain circumstances however, this is not possible and proprietary vendor MIBs are used. There may also be cases when a proprietary MIB is used even when not neccessary. If so, we s…

commandlinetools

2007-10-01T15:41:13+02:00

NAV has some useful command lines tools. We document the most important ones here. navclean.py Machine tracker data, i.e. ARP and CAM data, are never deleted from NAV. To delete old data run navclean.py. It behaves as the help option explains: % ./navclean.py -h Delete old arp and cam records from the NAV database. Usage: navclean.py [options...] Unless options are given, the number of expired ARP/CAM records will be printed. The default expiry limit is 6 months. To actually delete th…

contribsandthirdparty

2007-05-11T12:53:42+02:00

NAV contributions * The autodiscovery addon to the collections system is on the release notes of 3.1 said to be a contrib. The autodicsovery is not a contrib it is a part of NAV. It is of cource not compulsary to use. * UiT has made a radius module to NAV for their own purpuses. This is running at their NAV installation. They are planning to submit the radius module to contrib for the NAV 3.2 release.

debianpackage

2009-11-12T17:08:35+02:00

A Debian package of NAV is maintained by Morten Werner Forsbring on commission from UNINETT. This package has not yet been entered into the official Debian archives, but is available at . * See also DebianPackage/Todo - An official TODO-list for the Debian package

debianpackage_2ftodo

2007-05-11T12:53:42+02:00

This is the TODO list for the Debian packaging of NAV: * A recommended virtualhost configuration for the NAV server should be dropped into the /etc/apache2/sites-available/ directory. * The NAV webroot should be put in /usr/share/nav/htdocs/ instead of /var/www/nav/. * Package should actually purge database on removal (purging), not just asking about it. :) * Move cricket-config/ from /etc/nav/ to /var/lib/nav/ and create a symlink from /etc/nav/cricket-config -> /var/lib/nav/cricket-c…

devicemanagement

2007-10-06T08:22:33+02:00

The device management tool lets you view device history, register error events, delete outdated modules and more. It also has a ordering system, but... Ignore the ordering system - it is leaving NAV The device management tool consists of six tabs, where we recommend that you ignore three of them.

devvertofreebsd

2008-04-03T15:07:08+02:00

FIXME: Can someone who knows their way around the FreeBSD ports system add info on how to get a Mercurial client for FreeBSD? - Make a directory, example : /usr/local/src/nav - cd /usr/local/src/nav - hg clone http://metanav.uninett.no/hg/default/ (You need a Mercural client package) A directory /usr/local/src/nav/default is created - Some Mercurial commands : hg pull hg update hg log 01) nav stop /usr/local/etc/rc.d/apache2.sh stop /usr/local/etc/rc.d/020.jakarta-tomcat50…

equipmenttypes

2009-07-07T16:46:31+02:00

This page contains a list of types that may be unknown to NAV (we say may because they may have been included in a later patch/version). You can use this list directly and bulk in the types in your NAV installation using the “Edit database tool”.

eventandalertsystem

2007-10-08T16:24:43+02:00

This diagram gives an overview: [A diagram of NAV's event- and alert system.] More documentation * For a brief explanation of the background processes, event engine, alert engine and smsd, have a look at BackEndProcesses. Further references to NAV project reports are also given!

faq

2009-01-20T07:58:27+02:00

frontendtools

2007-10-03T10:14:54+02:00

An overview of the NAV front-end tools in terms of programming language and lines of code is given. For a further description of how the tools work, see our user guide. This list is updated as of NAV version 3.3.0. Tool Language Lines of Code Webfront (incl. User Admin) Python Approx 2600 + templates Status Python Approx 1900 + templates Network Explorer Java Approx 4200 Traffic Map Java Approx 4500 (applet) …

frontpage

2007-05-11T13:35:56+02:00

geomap

2009-08-14T14:19:52+02:00

Geomap shows network information on a geographical map. The map data comes from OpenStreetMap The network is shown as colored points and lines. Each point represents a collection of netboxes; each line represents the set of connections between the netboxes in the points at either end of the line. What the colors and sizes of points/lines represent is shown below the map (this depends on the chosen and on the ).

gettingstarted

2007-11-08T21:11:26+02:00

Let's get started! We guide you through the process from installing to getting NAV up and running, monitoring your network. NAV in eight steps Follow these 8 steps: * * * * * * * * * Happy NAV'ing! :-) 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. Several distribution packages are available or you can install NAV from source if you like.

hacking

2009-02-09T15:19:03+02:00

historyofnav

2009-01-29T14:20:57+02:00

1999 The development of NAV started in 1999. Prior to that NTNU, like so many others, had acquired a traditional network management system (HP Openview) that hopefully would fulfill our needs. After thorough investigation and adjustment of the system we found however that it lacked functionality in many areas. We decided to implement a basic system ourself.

howtoconfigurecricket

2007-10-03T09:35:56+02:00

Introduction The information assume that you have installed nav in /usr/local/nav. The information here is under construction. It is possibly erroneous and for a fact incomplete. The default installation of Cricket in NAV-v3 gives you statistics for your routers and switches and their interfaces. However, it may be desirable to add local statistics to the installation of Cricket. This document will lead you through a detailed way to do this without installing a new instance of Cricket. This d…

installing_from_source_on_debian

2010-02-10T13:15:18+02:00

This is an attempt at a guide and a few helpful pointers for those who don't care to use the prepackaged NAV for Debian. Versions used: Debian 5.0 (Lenny) NAV 3.5.2 Installing dependencies Make sure you have the non-free archive present in your sources.list:

installingoncentos5

2010-02-25T12:01:45+02:00

* Maintained by Roger Aas at Atea AS. ### ### NAV 3 installation ### ### for CentOS 5 ### ### Roger Aas, Atea AS ### ### ### 25.02.2010: ### - Fixed a lot of dependency problems, removed unneeded packages, upgraded others ### 22.02.2010: ### - NAV version is 3.5.5 ### - Fixed some minor problems ### 26.01.2010: ### - Tested on CentOS 5.4 i386 DVD ### - NAV version is 3.5.4 ### - FCGI-0.68, CGI.pm-3.48, psycopg2-2.0.13, IPy-0.70, setuptools-0.6c11, pyrad-1.2, Django-1.1.1 ### 10.09…

installingonrhel4

2007-07-30T15:39:39+02:00

* Mostly maintained by Roger Aas at Stord/Haugesund University College. ### ### NAV 3 installation ### ### for CentOS 4 or Red Hat Enterprise Linux 4 Advanced Server ### ### Roger Aas, Stord/Haugesund University College ### ### ### 27.07.2007: ### - Tested for RHEL4 Update 5 ### - No need to make ~/.gnupg anymore ### - Included a patch for forgetSQL-0.5.1 ### - Fixed smsd.py setup, now sends SMSes again ### - Big rewrite mainly because of this fix ### 12.07.2007: ### - Updated for…

installingonsles

2010-02-24T08:40:13+02:00

:!::!::!: This page is REALLY outdated :!::!::!: Installing the prerequisites RPM and SuSE Apart from what seemed to be installed by default, these packages were installed using yast2 (some of these packages might not make sense in a NAV context, but were installed as extra tools during the server preparation):

ipdeviceinfo

2009-01-28T15:58:32+02:00

[ ] The IP device info tool is a “dashboard” for a given IP device showing relevant information. It presents recent events for the device, if any. If the device is a switch or router a switch port and/or router interface view is given. [IP device center ]

layer2trace

2007-09-28T15:19:05+02:00

Use this tool to trace layer 2 network paths between hosts. Usage is: * Enter a hostname or IP address and trace up to its router. * Optionally enter a destination hostname or IP address and trace between the two. The result shows layer 2 (switch) hops as “level L2” and router hops as “level L3”. For each hop incoming and outgoing interface is displayed.

ldapauthentication

2009-03-04T10:55:18+02:00

NAV can authenticate web users externally via a LDAP server. This article describes how this feature works, and how to configure it. :!: This information is for NAV 3.4 and newer. :!: How to configure Configuration for LDAP authentication is stored in the config file etc/webfront/webfront.conf, in the [ldap] section. You should restart Apache to make sure any config changes take effect.

machinetracker

2007-11-01T15:03:04+02:00

NAV has historic data on the whereabouts of all machines (IP adresses / mac adresses) in the network. You can locate a machine down to the switch port the machine is directly attached to. The machine tracker tool allows you to search for the location of a given machine, or a set of machines. An example is given:

mailinglists

2008-04-03T15:18:39+02:00

There are two mailing lists relevant for NAV. They are: * nav-users: General NAV user discussion and help (see archive). * nav-dev: NAV development discussions (see archive). :!: We recommend that anyone who has or wants a NAV installation should subscribe subscribe to the nav-users list.

maintenancetasks

2007-10-04T14:35:30+02:00

Maintenance tasks is where you create and edit equipment maintenance schedules. Equipment on maintenance does not cause alerts when down or unavailable. IP devices or services can be set on maintenance. You may also set a whole room or location on maintanance.

messagestool

2007-09-19T11:19:43+02:00

The messages tool is where you can publish operational messages. The messages will be visable on the home page of NAV. The messages tool has four tabs, where the three first display messages (and let you edit them), the last tab is for adding new messages:

navappliance

2009-06-26T12:00:21+02:00

Several users have requested an appliance with NAV preinstalled. Thats why this appliance have been made. :) Debian GNU/Linux 4.0 (aka. etch) The appliance can be downloaded from here: i386: (cooming soon) x86_64 / amd64:

navconfiguration

2007-10-04T23:24:24+02:00

Here you can find a number of documents that give you necessary information on how to use and tune NAV. Getting started Getting Started guides through the initial steps of installing, configuring and seeding NAV Other essential information to get you started with NAV:

navdownload

2010-05-21T17:24:41+02:00

NAV is freely available under the GNU GPLv2 license. Latest version The latest stable version of NAV is 3.5.6. A beta of NAV 3.6 can also be downloaded at Launchpad, for those who crave the unstable bleeding edge. Smoothest install We recommend the Debian package. The package is currently the most comrehensive as it takes care of all dependencies. It also includes a short and well documented cook book of things you need to do after installation. Your procedure will be this;

navfaq

2010-02-24T13:47:12+02:00

What is NAV? NAV is an acronym for Network Administration Visualized. It is an advanced software suite to monitor large computer networks. It automatically discovers network topology, monitors network load and outages, and can send alerts on network events by e-mail and SMS, allowing for flexible configuration of alert profiles.

navfeatures

2007-09-29T15:41:53+02:00

Introduction Network Administration Visualized is an advanced software suite to monitor large computer networks. It automatically discovers network topology, monitors network load and outages, and can send alerts on network events by e-mail and SMS, allowing for flexible configuration of alert profiles.

navhome

2008-06-02T11:46:52+02:00

The main view The home page of NAV consists of the following elements; * A welcome message to anonymous and logged in NAV users. Edit the files webfront/welcome-anonymous.txt and webfront/welcome-registered.txt. * A display of operational messages, if any. You add or modifiy messages using the messages tool. * An overview of boxes that are down, if any. A link to the Status tool is provided for further details. * A NAV link box. Edit the file webfront/nav-links.conf. If the con…

navinstallation

2008-08-22T14:37:39+02:00

NAV is primarily aimed at Linux users, although most *NIXes should do. Successful installations of NAV have taken place on the following Linux distributions: Debian * UNINETT maintains a packaged version of NAV for Debian. More information can be found on this page. * If you prefer installing from source on Debian, follow this cookbook

navprojects

2007-09-16T09:44:37+02:00

So far there have been five NAV development projects at NTNU, all partly funded by UNINETT. Project reports are available from the links below (the three first projects only have Norwegian documentation): * NAVMe: Pilot project to install NAV at the University of Tromsø (fall 2001). (In Norwegian). * NAVRun: Create an installation package of NAV 2 for easy distribution/installation among Uninett members (2002). (In Norwegian). * NAVMore: Initial development of functionality that would e…

navscreenshots

2007-11-01T14:58:41+02:00

This document complements the NAVFeatures document. We here show a number of screenshots taken from running NAV version 3 installations (NTNU and UNINETT). Each screenshot is accompanied by text explaining the basic functionality. We do not go in detail, and not every aspect of NAV is covered.

navtechdoc

2007-10-01T19:00:50+02:00

Her you can find documents giving technical information on design etc. Lines of Code a summary of the number of lines of code in NAV. Database doc detailed information on the NAV database Back-end processes an overview of the background processes of NAV (daemons and cron jobs). Front-end code lines an overview of code lines in the front-end tools of NAV Command line tools an overview of the various command line tools that follow NAV Event and Alert System an overview of the …

navusers

2010-07-07T09:13:16+02:00

This page presents an alphabetical list of organizations using NAV, sorted by country. We know the list should be longer, so: :!: If your organization is using NAV - please add yourself to this list! Italy * UniMoRe - University of Modena e Reggio Emilia, Italy.

netmap

2008-06-11T08:42:27+02:00

Netmap is new in NAV 3.5 and replaces the old TrafficMap (vlanplot). Netmap is based on the prefuse library, and uses its ForceBasedLayout-engine for finding the optimal graphical layout for the network. The netmap itself is an Java Applet, and should run on both Java 5 and Java 6. Java 5 is required to build the Netmap-applet.

networkexplorer

2007-09-27T19:53:53+02:00

The network explorer tool presents the network in a tree structured manner. [Netowork explorer ] Navigation The initial view lists all the routers (GW and GSW). The user may explore a router by clicking on the plus sign (+). This will open a router interface listing for this router. If the tag “show detailed information” is checked details on IP addresses and router interface descriptions is also shown.

oldgettingstarted

2007-09-30T11:51:09+02:00

:!: This is the old document, that i out of date. Kept so we can import what's useful to the new document. FIXME This information is outdated Getting started with NAV 3.0 ============================ (This guide assumes NAV is installed in /usr/local/nav) NAV 3.0 assumes a simpler directory structure than previous NAV versions. Below /usr/local/nav/ you will find the following directories: ======= ====================================================================== apache/ Web related …

postcard

2007-05-11T12:53:42+02:00

NAV is free - no strings attached - apart from these two; * If you are using NAV please add yourself to this list (yes, we know it is far from complete). * If NAV makes you happy - make us happy! Send us a postcard, preferably with a picture from your location / city. No electronic postcards - use snail mail - send the postcard to:

productssupported

2007-05-11T12:53:42+02:00

TableOfContents(2) List of products Cisco Box attributes Router port attributes Switch port attributes Module attributes Product serial sw mem cpu temp cdp ports descr hsrp metric static arp stat ports duplex descr vlan cam stp stat serial sw p2mod Tested by Example <#FF8080> <#80FF80> NA NT Legend || NA || Not available / not relevant || || NT || Not Tested || ||<#FF8080> 0 || No support || ||<#80FF80> 1 || Mo…

projectsin2006

2007-05-11T12:53:42+02:00

This page is deprecated. See TaskList instead.

radius

2010-05-01T23:57:43+02:00

Radius is a NAV-tool that collects accounting-data from a Freeradius-server and makes them available to the user through a web-frontend. The goal is to make a more accessible and userfriendly interface to the accounting data instead of having to manually look through logfiles. The frontend is divided into three tabs where you can browse different sets of data from the radius-server.

readmedebian

2007-05-11T12:53:42+02:00

Outdated, see the official packaging NAV for Debian site.

reporttool

2009-03-04T08:45:55+02:00

[ ] The report tool presents a number of reports with information from your network. The report tool also links to the “IP address scope - graphical view” and the services matrix. Each NAV report is in essence an SQL query to the database. It shown its data in a number of columns. The data is in many cases also hyperlinks to other reports or other tools in NAV. The whole report system is highly configurable, the basis for the system is the configuration file report.conf. Details on the configu…

roadmap

2010-08-31T09:26:54+02:00

For a complete history of NAV, see HistoryOfNAV. The first official open source version of NAV was NAV 3.0. Where is NAV going? NAV has a long history and a lot of code to maintain. Our current strategy is this: * Let there be no doubt; our focus is on network management * NAV's key strength is on detecting network topology, tracking machines and visualizing the network. * We will focus on supporting commonly deployed network equipment. * Better wireless support is on our roadmap *…

seedessentials

2007-10-07T09:57:38+02:00

After NAV is installed and started (with ´nav start´) NAV does absolutely nothing ;-) Put differently, NAV does not autodiscover your network, you have to seed the database with key information. This document explains the requirements (minimum and recommended) that need to be followed in order to get NAV going.

servicemon

2010-05-28T12:33:38+02:00

Setting up a checker Checkers are managed in the SeedDB tool. (Servicemon currently doesn't have its own tool.) To add a checker, click “Add” under “Services”. This leads to a three-panel box where you can select the IP device and service you want to check. When you have selected a service, you'll get a some boxes to fill in arguments (see Checker arguments below). When you're done, just hit “Add service”

snmptrapd

2007-05-11T12:53:43+02:00

Introduction This file contains instructions on how to use the snmptrapd in NAV and how to add traphandlers to it. What is the snmptrapd? The snmptrapd is a program written in python designed to receive traps sent to NAV and process them by sending them to traphandlers. Traphandlers are independent and may be written by whoever wants to. snmptrapd is based on the pysnmp-library and the example on Python@SourceForge

sortedstats

2007-09-30T08:43:49+02:00

NAV maintains traffic statistics for all “intersections” in the network; i.e. all router and switch ports. Octet, packet and error counters are collected, along with CPU and memory statistics (and more). NAV also gathers statistics on servers, i.e. disk usage, memory, load etc.

start

2010-06-10T14:23:36+02:00

[(NAV logo)] Network Administration Visualized is an advanced software suite to monitor large computer networks. It automatically discovers network topology, monitors network load and outages, and can send alerts on network events by e-mail and SMS, allowing for flexible configuration of alert profiles.

statustool

2007-11-01T15:01:43+02:00

The status tool gives an overview on operations; i.e. that all the network components and services are up and running. Back-end processes NAV has four background processes that monitors the operational status of the network. It is the events triggered from these monitors that are displayed in the status tool. The four monitors are:

subnetsandvlans

2007-09-30T17:41:13+02:00

This document discusses natural attributes that describe a subnet (or vlan) and introduces NAV's guidelines for router interface descriptions. Vlan attributes The NAV database models subnets and vlans as they are set up in the production network. A vlan defines a broadcast domain that may consist of zero, one or more IP subnets, one being the most “normal” case. zero subnets means that this is a private network (i.e. a sunray vlan). By using secondary IP addresses (Cisco terminology) it is al…

sysloganalyzer

2009-03-25T15:00:31+02:00

The syslog analyzer lets you browse Cisco syslog messages that are collected by the syslog deamon. Only Cisco syslog messages are supported. The back-end A requirement for this tool is that a syslog daemon is running on your NAV machine collecting syslog messages from your Cisco gear. Unfortunately the NAV Syslog Analyzer only supports Cisco syslog messages, other messages will be ignored (an improvement is on our road map).

task

2008-05-08T14:37:10+02:00

Attempt at reorganizing the devel:tasklist page into a task namespace, using the DokuWiki task plugin. Unassigned tasks Open tasks Completed tasks My tasks

thresholdmonitor

2007-05-11T12:53:43+02:00

The threshold monitor in NAV 3 uses data from NAV's RRD database, and the RRD files generated by Cricket, to check for and report interfaces with high load, high CPU and related events. At the moment there is no interface to easily adjust the threshold values. However, this is under development.

toolbox

2007-05-11T12:53:43+02:00

tools

2007-05-11T12:53:43+02:00

These tools are available in the web interface of a standard NAV installation: * StatusTool * NetworkExplorer * TrafficMap * MessagesTool * ReportTool * Arnold * Layer2Traceroute * MachineTracker * CricketStatistics * EditDatabase * AlertProfiles * DeviceManagement * SyslogAnalyzer * UserAdmin * IpInfoCenter

trafficmap

2009-01-28T16:19:10+02:00

The traffic map is entirely rewritten for NAV 3.5. The old traffic map is no longer available, that is you may manually install it, if you want to keep it. Please refere to the Netmap page for more info on the 3.5 netmap. This page is kept for those running pre 3.5 or have manually installed the old traffic map.

upgrade_to_nav_3.6_documentation

2010-03-26T10:02:35+02:00

This document contains information about upgrading from previous version of NAV to 3.6. Cricket A brand new solution is in place for making cricket config files automatically. To ensure a smooth transition make sure to read this documentation carefully.

user_guide

2007-06-21T14:49:20+02:00

Network Administration Visualized can be divided into two parts: A set of back-end processes and a web-based user interface. The back-end processes are responsible for collecting and analyzing data from your monitored equipment and for performing various background maintenance and administrative tasks. The web-based user interface's main task is to present the collected and analyzed information to the network administrators and other users, and also to allow the administrators to perform admin…

useradminpanel

2010-05-01T23:58:10+02:00

This is where NAV administrator can control NAV user accounts, group memberships and access privileges. Account list The main view of the user administration panel shows the account list. Each user has a login (username) and a real name. If the user is authenticated externally via LDAP, the external column will indicate this. The final column lists the number of groups the user belongs to.

versionthreetwo

2007-05-11T12:53:43+02:00

NAV 3.2.0 was released on 2nd February 2007. The following features were planned (follow the links for details), but not all made it into the release. They will be re-scheduled for the 3.3 release (this page will soon disappear). * T1: Improve snmp data collection (Morten Brekkevold) * T3: Rewrite the message and maintenance tool (Stein Magnus Jodal) * T4: Enhance the status tool (Stein Magnus Jodal) * T5: Enhance the report tool (Morten / Stein Magnus) * T6: Improve IP device cente…