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 | ||
navscreenshots [2011/04/04 07:52] faltin [The traffic map] |
navscreenshots [2012/10/19 06:22] bredal [IP Device Info] |
||
---|---|---|---|
Line 16: | Line 16: | ||
- | ====== The traffic map ====== | + | ====== Traffic maps ====== |
There are two traffic maps tools in NAV; Netmap and Geomap. More info will follow later. | There are two traffic maps tools in NAV; Netmap and Geomap. More info will follow later. | ||
Line 58: | Line 58: | ||
- | ====== The device center ====== | + | ====== IP Device Info ====== |
- | The device center is basically an overview page showing lots of collected information regarding a particular IP device. | + | IP device info summarizes most of what NAV knows about a single IP device (or arbitrary IP address within your network) on a single page. |
- | In the case of switches | + | |
- | all switch ports with corresponding speed, duplex, link etc is also shown: | + | |
- | {{screenshot:3.3:devcenter.png|}} | + | {{:ipdevinfo-ss.png?600|}} |
+ | Switch ports and router ports on devices are displayed in a graphical fashion, grouped by modules. | ||
+ | {{:screenshot:swportstatus.png?300|}} | ||
+ | {{:screenshot:swportactivity.png?300|}} | ||
====== Reports ====== | ====== Reports ====== | ||
NAV has a number of reports (and with a little knowledge it is easy to make new reports). We give four report examples below. | NAV has a number of reports (and with a little knowledge it is easy to make new reports). We give four report examples below. | ||
Line 92: | Line 93: | ||
- | ====== IP address scope - graphical view ====== | + | ====== Subnet matrix ====== |
For large networks the task of maintaining the total IP address scope may be a challenge in itself. It is useful | For large networks the task of maintaining the total IP address scope may be a challenge in itself. It is useful | ||
- | to have an overview of all the subnets in operation, and whats more, how full they are, i.e. how many machines | + | to have an overview of all the subnets in operation, and what's more, how full they are, i.e. how many machines |
- | do they contain. NAV introduces a tabular view that gives an excellent overview on a single page: | + | do they contain. NAV introduces the subnet matrix that gives an excellent overview on a single page: |
+ | |||
+ | FIXME Old screenshot | ||
{{screenshot:3.3:prefixmatrix.png|}} | {{screenshot:3.3:prefixmatrix.png|}} | ||
Line 139: | Line 142: | ||
Note that alarms from external systems may be sent to NAV and thus included in the alert profile setup. | Note that alarms from external systems may be sent to NAV and thus included in the alert profile setup. | ||
+ | |||
+ | This is an old screenshot, please FIXME | ||
{{screenshot:3.3:alertprofiles.png|}} | {{screenshot:3.3:alertprofiles.png|}} | ||
- | ====== Device Management ====== | + | ====== Device History ====== |
- | The device management tool has a focus on the physical network devices identified by their unique | + | The device history tool has a focus on the physical network devices identified by their unique |
- | serial number (as opposed to the logical devices identified by IP addresses). By registering 'milestone events' | + | serial number (as opposed to the logical devices identified by IP addresses). The Device History tool lets you |
- | for the devices NAV maintains important historic information. Typical examples are ordering, arrival, on shelf, | + | see the history of devices, register error events or delete outdated modules. |
- | in operation, error events, end of operations. Some of these events are detected automatically by the system, | + | |
- | others require manual recordings. | + | |
The example shows the tab for registering a particular error event: | The example shows the tab for registering a particular error event: | ||
+ | |||
+ | The screenshot is outdated, please FIXME | ||
{{screenshot:3.3:devmngt.png|}} | {{screenshot:3.3:devmngt.png|}} | ||
- | We may for instance have repeating error occurance for a device, where fixes are done by different staff. Device | + | We may for instance have repeating error occurrence for a device, where fixes are done by different staff. Device |
- | management then serves as a place to get the overall picture. | + | history then serves as a place to get the overall picture. |
- | ====== Edit Database ====== | + | ====== Seed Database ====== |
NAV does not fully autodiscover the network. You need to seed the database with key information, the most important | NAV does not fully autodiscover the network. You need to seed the database with key information, the most important | ||
being the IP address and SNMP community string of the devices you would like NAV to manage. The home page og | being the IP address and SNMP community string of the devices you would like NAV to manage. The home page og | ||
- | the edit database tool looks like this: | + | the seed database tool looks like this: |
+ | |||
+ | The screenshots of Seed Database are outdated, please FIXME | ||
{{screenshot:3.3:editdb.png|}} | {{screenshot:3.3:editdb.png|}} | ||
Below follows an example of the form used to add a new box (ip device) to NAV. Note that we allow bulk import | Below follows an example of the form used to add a new box (ip device) to NAV. Note that we allow bulk import | ||
- | of seed data from a text file format. This is useful if you have a large number of devices in your network | + | of seed data from a text file format. This is useful if you have a large number of devices in your network. |
- | (or if you are migrating from a NAV v2 installation). | + | |
{{screenshot:3.3:addbox.png|}} | {{screenshot:3.3:addbox.png|}} |