User Tools

Site Tools


howtoconfigurecricket

Differences

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

Link to this comparison view

Next revision
Previous revision
howtoconfigurecricket [2007/05/11 10:53]
faltin
howtoconfigurecricket [2015/10/14 13:42]
morten remove obsolete page
Line 1: Line 1:
  
-====== Howto configure local Cricket-additions in NAV-v3 ====== 
  
-[[TableOfContents(2)]]+ 
 +====== How to configure local Cricket-additions in NAV-v3 ====== 
  
 ===== Introduction ===== ===== Introduction =====
Line 136: Line 137:
  
 3. Make a new cron-fragment in /​usr/​local/​nav/​etc/​cron.d. This will ensure that you can start/stop collecting using the nav-script. Make sure that you create a fragment that is not likely to be overwritten,​ i.e. the name should reflect that this is a local addition. This because if a future release of NAV has a fragment with the same name, complications may occur. 3. Make a new cron-fragment in /​usr/​local/​nav/​etc/​cron.d. This will ensure that you can start/stop collecting using the nav-script. Make sure that you create a fragment that is not likely to be overwritten,​ i.e. the name should reflect that this is a local addition. This because if a future release of NAV has a fragment with the same name, complications may occur.
 +
  
  
 ===== Coming updates in NAV ===== ===== Coming updates in NAV =====
  
-The current directory-structure with giga-switch-ports and +makecricketconfig.pl ​is planned ​for a rewrite. It will be rewritten ​in pythonA list with planned changes ​will come during ​the year.
-giga-router-interfaces in addition to the other directories ​is not an +
-optimal structure. When you search ​for a graph you do not want to have +
-to search in multiple places to find what you are looking for.  +
- +
-A coming update in NAV plans to solve this problem. It will get rid of +
-the giga-directories and put all information ​in one directory for +
-switch-ports and one for router-interfaces +
- +
-The reason this has not been done before is that you need to use +
-SNMP-v2 to fulfill this, and the current set of network-equipment does +
-not always update the SNMP-v2 counters according to the standard. We +
-plan to develop a test for this and put the ones that follow the +
-standard in the "​normal"​ directories,​ and the others in another +
-directory. ​ Hopefully the number of ports/​interfaces that go in the +
-other directory ​will decrease as time goes by and they start to update +
-the counters correctly. +