This is an old revision of the document!
Here you can find a number of documents that give you necessary information on how to use and tune NAV.
|Getting Started||guides through the initial steps of installing, configuring and seeding NAV|
Other essential information to get you started with NAV:
Not everything in NAV is self explanatory. Unfortunately some features may stay unknown and hidden to the NAV user. We hope this user guide will help! The outline for the user guide follows the NAV toolbox and explains the usage of the various tools.
The home page is where you start. The home page gives an overview of status, displays operational messages and links to other tools.
The status tool gives an overview on operations; i.e. that all the network components and services are up and running.
The Network explorer displays the network resources in tree structured manner. You can drill down for details or use the search utility to locate what you are interested in.
The network weather map displays the layer 3 and layer 2 topology and current traffic conditions. Dropdown menues give detailed information and links to the traffic statistics.
The report tool is a highly customizable report generator that displays information from the NAV database. Information on software version, equipment type, location etc. Also detailed information of router and switch ports with data on IP address / prefixes, vlans, port speed and duplex etc. CSV export supported. Includes a subnet matrix that gives a good overview of your allocated IPv4 and IPv6 prefixes. Also includes an overall downtime report for last month and a report that list unregistered network gear (based on CDP, soon LLPD, discovery).
the IP Device Info tool displays all information NAV has collected for a device. For routers and switches this includes a graphical layout of all ports showing link speed, duplex, vlan and status. A separate view displays the link history of switch ports thus giving an overview of the switch port utilization ratio.
NAV uses Cricket to collect statistical data such as interface counters, CPU load, memory usage, temperature and more. See howtoconfigurecricket for information on how to expand the set of cricket statistics that is collected.
The statistics tool also includes a ranked statistics feature that displays tabular reports on the interfaces with heaviest load, the router with highest CPU usage and so forth.
The machine tracker lets you find IPv4, IPv6 or MAC addresses that are or have been in operation. Mac addresses are tracked down to their connected switch port.
Mac watch lets you set up a list of mac addresses that you want to track. When one of these mac addresses appear on the network, an alarm is triggered.
Layer 2 trace gives you the layer 2 trace of a machine to its default router. Alternatively the tool can give you the complete layer 2 trce between two machines.
The syslog analyzer lets you browse Cisco syslog messages that are collected by the syslog deamon.
Arnold is a switchport blocking tool. Use it to manually block switch ports or change the vlan of the port (to quarantine machines). Use the back end feature of Arnold and run automated blocking/quarantine raids.
Edit Database is the tool for seeding you NAV database with essential informations.
The messages tool is where you can publish operational messages. The messages will be visable on the home page of NAV.
AlertProfiles is where you set up your personal alert profiles; i.e. which alerts you would like to receive as email or sms.
Maintenance tasks is where you create and edit equipment maintenance schedules. Equipment on maintenance does not cause alerts when down or unavailable.
The threshold manager is the user interface for configuring and managing threshold values for all collected (RRD-based) statistics in NAV.
The user administration panel lets you control NAV user accounts, group memberships and access privileges.
The Radius accounting tool lets you search for users that has logged in using a radius server (i.e. eduroam users)
The device history tool lets you view device history, register error events, or delete modules that are down and no longer are in operation