navfeatures
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
navfeatures [2011/04/10 12:42] faltin [NAV answers your questions] |
navfeatures [2012/05/08 07:38] morten typo |
||
|---|---|---|---|
| Line 32: | Line 32: | ||
| * A postgreSQL database, [[/devel:database|NAVdb]], (1) modelling the running network. An [[backendprocesses#ipdevpoll|SNMP collector]] (3) collects data from the network. The physical interconnection of devices is auto detected, as well as the vlan topology. | * A postgreSQL database, [[/devel:database|NAVdb]], (1) modelling the running network. An [[backendprocesses#ipdevpoll|SNMP collector]] (3) collects data from the network. The physical interconnection of devices is auto detected, as well as the vlan topology. | ||
| - | * A [[/backendprocesses#pping|status monitor]] (3) that detects network outages. For severe cases where many devices are down NAV will try to pinpoint the root cause of the problem (i.e. distinguishing between devices down and devices in shadow) | + | * A [[/backendprocesses#pping|status monitor]] (3) that detects network outages. Both IPv4 and IPv6 are supported. For severe cases where many devices are down NAV will try to pinpoint the root cause of the problem (i.e. distinguishing between devices down and devices in shadow) |
| - | * [[sortedstats|Traffic statistics]] (2,20) 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). Use the "ranked statistics" option 19) to present a list of interfaces with most traffic, the highest error counts, etc. The traffic statistics collection uses [[http://people.ee.ethz.ch/~oetiker/webtools/rrdtool/|RRDTool]] and [[http://cricket.sourceforge.net/|Cricket]]. NAV automatically builds the Cricket configuration tree for you. | + | * [[sortedstats|Traffic statistics]] (2,20) 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, temperature sensors (and more). Use the [[sortedstats#ranked_statistics|"ranked statistics"]] (19) to present a list of interfaces with most traffic, the highest error counts, etc. The traffic statistics collection uses [[http://people.ee.ethz.ch/~oetiker/webtools/rrdtool/|RRDTool]] and [[http://cricket.sourceforge.net/|Cricket]]. NAV automatically builds the Cricket configuration tree for you. |
| - | * A [[machinetracker|machine tracker]] (12) where you can search for machines and where they currently are connected in the network, or where they have been connected earlier. Search for mac addresses, IPv4 or [[ipv6|IPv6]] addresses. If you use 802.1X authentication in the wired or wireless network, use NAV's radius-base [[radius|usertracker]] (12) to search for authenticated users. | + | * A [[machinetracker|machine tracker]] (12) where you can search for machines and where they currently are connected in the network, or where they have been connected earlier. Search for mac addresses, IPv4 or [[ipv6|IPv6]] addresses. |
| + | * A [[macwatch|Mac Watch tool]] that let you set up a watch list for mac addresses that will trigger alarms if watched mac addresses appear on the network. | ||
| + | * If you use 802.1X authentication in the wired or wireless network (i.e. eduroam), use NAV's radius-base [[radius|usertracker]] (12) to search for authenticated users. | ||
| * A machine detention tool (11: [[arnold|Arnold]]) lets you detain machines from the network, either by blocking the access switch port, or change the vlan to a quarantine vlan. A back-end script that easily integrates with external system can run automated detention jobs. | * A machine detention tool (11: [[arnold|Arnold]]) lets you detain machines from the network, either by blocking the access switch port, or change the vlan to a quarantine vlan. A back-end script that easily integrates with external system can run automated detention jobs. | ||
| Line 48: | Line 50: | ||
| * A [[layer2trace|layer 2 traceroute tool]] (16) that traces the physical path between two machines in the network. | * A [[layer2trace|layer 2 traceroute tool]] (16) that traces the physical path between two machines in the network. | ||
| - | * [[reporttool|Reports]] (13) that lists the inventory of routers and switches in the network. 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. Includes a subnet matrix that gives a good overview of your allocated IPv4 and IPv6 prefixes. | + | * [[reporttool|Reports]] (13) that lists the inventory of routers and switches in the network. 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 LLDP, discovery). |
| - | * An [[ipdeviceinfo|IP device info tool]] (15) that serves as a dashboard presenting all collected information about a device. For switches and routers 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. | + | * An [[ipdeviceinfo|IP Device Info tool]] (15) that serves as a dashboard presenting all collected information about a device. For switches and routers 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. |
| - | * A [[devicemanagement|device histoy tool]] (14) that displays all occurred events for a physical device (a given serial number). | + | * A [[devicemanagement|device history tool]] (14) that displays all occurred events for a physical device (a given serial number). |
| - | * A [[backendprocesses#thresholdmon|threshold monitor]] (7) that gives alarms based on high load / high error rates or severe CPU load etc. The threshold monitor is highly configurable through an administrative web interface. The monitor understand states and will prevent alarm flapping by using hysteresis. | + | * A [[backendprocesses#thresholdmon|threshold monitor]] (7) that gives alarms based on high load / high error rates or severe CPU load etc. The threshold monitor is highly configurable through [[thresholdmanager|the Threshold Manager web interface]]. The monitor understand states and will prevent alarm flapping by using hysteresis. |
| * A module monitor (5) that detects outage of switch or router components, i.e. individual switches in a switch stack or modules in a chassis. | * A module monitor (5) that detects outage of switch or router components, i.e. individual switches in a switch stack or modules in a chassis. | ||
| Line 60: | Line 62: | ||
| * A [[backendprocesses#servicemon|service monitor]] (6) that reports on service outages. Support the most important services; ssh, http(s), imap(s), pop, smtp, smb, rpc, dns, smb, dc, rpc, dhcp, ftp, smb, mysql, postresql, oracle, radius. Can easily be expanded to support more services. | * A [[backendprocesses#servicemon|service monitor]] (6) that reports on service outages. Support the most important services; ssh, http(s), imap(s), pop, smtp, smb, rpc, dns, smb, dc, rpc, dhcp, ftp, smb, mysql, postresql, oracle, radius. Can easily be expanded to support more services. | ||
| - | * A general [[backendprocesses#eventengine|event system]] (8) that processes all events, including alarms from external systems. | + | * A general [[backendprocesses#eventengine|event system]] (8) that processes all events, including alarms from external systems. Alarms from external systems are either sent as snmptrap to the NAV [[snmptrapd|snmp trap daemon]] or as email to NAV's [[devel:blueprints:mailin|mailin system]]. |
| * A flexible [[backendprocesses#alertengine|alert system]] (9), where each NAV user can adjust his own profile (using [[alertprofiles|the tool alert profiles]], 21) with fine-grained control options. Currently support for sending email, SMS and jabber alerts. The profiles can be made to adjust the volume and types/severities of alarms wanted, this as a function of time and day of the week. | * A flexible [[backendprocesses#alertengine|alert system]] (9), where each NAV user can adjust his own profile (using [[alertprofiles|the tool alert profiles]], 21) with fine-grained control options. Currently support for sending email, SMS and jabber alerts. The profiles can be made to adjust the volume and types/severities of alarms wanted, this as a function of time and day of the week. | ||
| Line 69: | Line 71: | ||
| In addition: | In addition: | ||
| - | |||
| - | * A [[sysloganalyzer|Cisco Syslog Analyzer]] that structures and lets you search syslog messeges from Cisco devices. | ||
| * A [[messagestool|message system]] that displays operational messages to IT support staff and end users. | * A [[messagestool|message system]] that displays operational messages to IT support staff and end users. | ||
| Line 76: | Line 76: | ||
| * A [[maintenancetasks|maintenance tool]] to put devices on maintenance for a planned time period and thus suppress alarms. | * A [[maintenancetasks|maintenance tool]] to put devices on maintenance for a planned time period and thus suppress alarms. | ||
| - | * A general mechanism for authentication and authorization of NAV users. Use the [[useradminpanel|user adminstration tool]] to manage users and on a group level set the appropriate authorization level. | + | * A [[sysloganalyzer|Cisco Syslog Analyzer]] that structures and lets you search syslog messeges from Cisco devices. |
| + | |||
| + | * A general mechanism for authentication and authorization of NAV users. Supports LDAP and Active Directory. Use the [[useradminpanel|user adminstration tool]] to manage users and on a group level set the appropriate authorization level. NAV administrator can "sudo" to other users to see/adjust their setup. | ||
| Line 90: | Line 92: | ||
| * What traffic volumes do we have? Are there any bottlenecks, if so, where? What are the traffic trends? Where should we upgrade first? | * What traffic volumes do we have? Are there any bottlenecks, if so, where? What are the traffic trends? Where should we upgrade first? | ||
| - | * What does the network look like? How is it interconnected? What is the scope of the various vlans / subnets? Where is server X connected again? | + | * What does the network look like? How is it interconnected? What is the scope of the various vlans / subnets? Where is server X connected? |
| * Do we see any traffic storms? In what direction does traffic flow? | * Do we see any traffic storms? In what direction does traffic flow? | ||
| Line 98: | Line 100: | ||
| * How many computers are connected totally? How many of these are student PCs? How many are staff computers? | * How many computers are connected totally? How many of these are student PCs? How many are staff computers? | ||
| - | * What are the movements in the network of laptop Y that seems to be compromised. Where has he been the last 90 days? Where is he now? | + | * What are the movements in the network of laptop Y that seems to be compromised. Where has he been the last 90 days? Where is it now? |
| * What type of network equipment do we have in our network? What kind of switches and routers, how many of each, where are they located? What software and hardware versions are they running? How many modules are there in the various stacked and chassis based switches? Are there any free, or almost free, modules? Help me get the overall picture, I need to expand switch Z and are looking for spare parts... | * What type of network equipment do we have in our network? What kind of switches and routers, how many of each, where are they located? What software and hardware versions are they running? How many modules are there in the various stacked and chassis based switches? Are there any free, or almost free, modules? Help me get the overall picture, I need to expand switch Z and are looking for spare parts... | ||
| Line 113: | Line 115: | ||
| Here are some areas where NAV does //not// help you: | Here are some areas where NAV does //not// help you: | ||
| - | * NAV is primarily a **monitoring** tool NAV and is **not** used for configuring your network equipment. There are however two important exceptions (NAV uses SNMP write in these two cases): | + | * NAV is primarily a monitoring tool NAV and is not used for configuring your network equipment. There are however two important exceptions (NAV uses SNMP write in these two cases): |
| * The port blocking tool [[Arnold]] | * The port blocking tool [[Arnold]] | ||
| - | * The PortAdmin component of IP Device Center that lets you configure vlan values and port descriptions of switchports. | + | * The [[portadmin|PortAdmin]] component of [[ipdeviceinfo|IP Device Info]] that lets you configure vlan values and port descriptions of switch ports. |
| * NAV is not the Oracle in Delphi that will pinpoint all errors in your network. NAV tries to discover serious errors, but is by no means perfect. There are still things that need to be discovered by other means than NAV. | * NAV is not the Oracle in Delphi that will pinpoint all errors in your network. NAV tries to discover serious errors, but is by no means perfect. There are still things that need to be discovered by other means than NAV. | ||
navfeatures.txt · Last modified: 2012/05/08 07:38 by morten
Page Tools
