User Tools

Site Tools


historyofnav

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
historyofnav [2012/01/29 20:57]
faltin [2006]
historyofnav [2012/09/18 09:48] (current)
bredal [2012 - NAV 3.11, 3.12]
Line 1: Line 1:
  
 ====== The history of NAV ====== ====== The history of NAV ======
- 
- 
- 
  
  
Line 260: Line 257:
 tested on an increasingly set of Norwegian universities and colleges. tested on an increasingly set of Norwegian universities and colleges.
  
-Documentation was improved and translated to English, and a new [[http://​metanav.ntnu.no|wiki web site]] +Documentation was improved and translated to English, and a new wiki web site
 (based on MoinMoin) was established,​ also allowing for a more distributed contribution (based on MoinMoin) was established,​ also allowing for a more distributed contribution
 of documentation. of documentation.
Line 278: Line 275:
 In June we finally announced our first release candidate (rc1), followed by a second in July.  In June we finally announced our first release candidate (rc1), followed by a second in July. 
  
-NAV 3.0.0 was finally released on September 16 2005.+NAV 3.0.0 was finally released on September 16 2005 with the following highlights:
  
-For details on the improvements made in the 2005 releases, we refer to the +  * Completely new web interface - new look 
 +  * New authentication and authorization system 
 +  * New Java based snmp collector: getDeviceData 
 +  * New database design 
 +  * New event- and alarm system (event engine, alert engine, alert profiles) 
 +  * Module monitor 
 +  * New message system 
 +  * New tool Network discovery, improved vlanplot (the network map) 
 + 
 +For further ​details on the improvements made in the 2005 releases, we refer to the 
 [[http://​svn.itea.ntnu.no/​repos/​nav/​navme/​tags/​3.0.0/​CHANGES|3.0 change log with its history]]. [[http://​svn.itea.ntnu.no/​repos/​nav/​navme/​tags/​3.0.0/​CHANGES|3.0 change log with its history]].
    
Line 287: Line 293:
  
  
-===== 2006 =====+===== 2006 - NAV v3.1 =====
  
 2006 has been a definite upswing for NAV. Project development is now 2006 has been a definite upswing for NAV. Project development is now
Line 317: Line 323:
 reduce the Cricket collector frequency for gigabit switch ports from reduce the Cricket collector frequency for gigabit switch ports from
 every 1 minute to every 5 minutes, thus removing the need to have a every 1 minute to every 5 minutes, thus removing the need to have a
-separate configuration tree for gigabit ports.+separate configuration tree for gigabit ports. The IP Device Center (later renamed to IP Device Info) was introduced.
  
 We established a project page for NAV at SourceForge. ​ This was used We established a project page for NAV at SourceForge. ​ This was used
Line 329: Line 335:
  
  
-===== 2007 =====+===== 2007 - NAV 3.2/​3.3 ​=====
  
 The NAV year of 2007 opened with the belated 3.2 release in February. The NAV year of 2007 opened with the belated 3.2 release in February.
Line 339: Line 345:
 and message systems, rewritten from scratch, after many usability and message systems, rewritten from scratch, after many usability
 complaints from users. ​ The Perl SMS daemon was rewritten in Python, complaints from users. ​ The Perl SMS daemon was rewritten in Python,
-adding support for SMS dispatcher plugins. ​ Much of the+adding support for SMS dispatcher plugins.  ​The Ranked Statisdtics feature 
 +was introduced. ​Much of the
 behind-the-scenes HTML and CSS was cleaned up and restructured. The behind-the-scenes HTML and CSS was cleaned up and restructured. The
 release also brought numerous small improvements to NAV overall. release also brought numerous small improvements to NAV overall.
Line 348: Line 355:
 device history was greatly improved. ​ The web interface received a device history was greatly improved. ​ The web interface received a
 major facelift. ​ Switch/​router interface names replaced port numbers major facelift. ​ Switch/​router interface names replaced port numbers
-as identifiers in most parts of the web interface.+as identifiers in most parts of the web interface. A router port 
 +view was added to IP Device Center (Info).
  
 The 2007 development project saw Morten Brekkevold take over as the The 2007 development project saw Morten Brekkevold take over as the
Line 356: Line 364:
  
 Project participants in 2007: John Magne Bredal, Vidar Faltinsen, Project participants in 2007: John Magne Bredal, Vidar Faltinsen,
-Stein Magnus Jodal, Kristian Klette, Morten Brekkevold (project+Stein Magnus Jodal, Kristian Klette, Jostein Gogstad, Morten Brekkevold (project
 leader). leader).
  
 +===== 2008 - NAV 3.4 =====
 +
 +In May 2008 NAV 3.4 was released. IPv6 support was added for the machine
 +tracker, subnet collection and subnet matrix. The LDAP authentication
 +was improved.
 +
 +In the summer and autumn there was ongoing development for v3.5.
 +
 +===== 2009 - NAV 3.5 =====
 +
 +In January NAV 3.5 was released:
 +  * A new and improved IP Device Info now replaced IP Device Center.
 +  * Alert Profiles and Alert Engine were rewritten in Python. ​
 +  * vlanplot was replaced by netmap. ​
 +  * Network explorer was rewritten in Python. ​
 +  * A new Radius tool was introduced that was able to track 802.1X authenticated users on the network
 +  * Report was improved and local reports were allowed
 +  * HP switch switch stack support was report do to many problems
 +
 +===== 2010 - NAV 3.6/3.7 =====
 +
 +NAV 3.6 was a major release for NAV as it introduced the forth generation SNMP collection system - ipdevpoll.
 +ipdevpoll would thus replace getDeviceData. The firs beta version of 3.6 came in May and the final release (after 6 beta version) ​
 +was launched in October. NAV 3.6 included:
 +
 +  * New SNMP collector: ipdevpoll ​
 +  * Major changes to the dataves with a new common interface table (leaving the separate router interface and switxh port tables behind)
 +  * New backend daemon mailin: For receiving external alarms as email, parsing them and posting events on the event queue
 +  * Enhancements to report system: CSV export, monthly availability report and more
 +  * Several subsystems rewritten: machine tracker, dev history, makecricketconfig (from perl to python)
 +  * Support ​ “ignore resolved alerts” in Alert Profiles
 +
 +NAV 3.7 came just a month after 3.6, in November, introducing more results from summer students:
 +
 +  * Geomap -  a geographical map using OpenStreetMap data.
 +  * A sudo (mechaism allowing NAV administrators to manage user’s alert profiles and other setup
 +  * Introducing AD LDAP support
 +
 +===== 2011 - NAV 3.8/​3.9/​3.10 =====
 +
 +In February NAV 3.8 was out with:
 +
 +  * New tool portAdmin that allows for configuring vlan value and port descriptions for switch ports.
 +  * The seedDB tool was rewritten
 +  * A report for inactive devices was included
 +
 +In May 3.9 came with:
 +
 +  * Threshold manager: New GUI to set threshold alarms - finally in place  ​
 +  * New tool Mac Watch: Generate alarm when a mac address appears on the network
 +  * Improved the physical topology detection ("​topology"​ replaces "​networkdiscovery topology"​)
 +  * Support for Extreme Switches
 +  * pynetsmp/​NetSNMP support for ipdevpoll - significant performance impact
 +
 +
 +In December 3.10 came with:
 +
 +  * Port link status monitoring with ipdevpoll - limit to topology ports if you like
 +  * Cricket statistics for environmental sensors in network equipment and Weathergoose
 +  * Generate alarm when a redundant power or fan in a switch fails (Cisco and HP)
 +  * Manage alarms from UPS: supports UPS-MIB (RFC 1628), APC, Eaton and MGE
 +  * Improved vlan topology detection ("​topology"​ now entirely replaces "​networkdiscovery"​)
 +  * Parallel DNS lookups increases performance ​
 +  * The status monitor (pping) now supports IPv6
 +  * Alerts when SNMP agent stops responding
 +
 +In November 2011 a NAV reference committee was established. The reference committee consists
 +of NAV power users from dominant Norwegian universities and university colleges. The reference
 +committee will give advice to future developments in NAV and help UNINETT in making our priorities.
 +The committee has members from these institutions:​ NTNU, UiT, UiO, UiA, HiVolda.
 +
 +
 +
 + ===== 2012 - NAV 3.11/3.12 =====
 +
 +In March NAV 3.11 was released with the following improvements:​
 +
 +  * LLDP support for improved topology detection.
 +  * getBoksMacs replaced by ipdevpoll plugins in `topo` job.
 +  * Q-BRIDGE-MIB now also used when collecting switch forwarding tables,
 +    meaning improved machine tracking data for switch vendors like HP, Juniper
 +    and Alcatel.
 +  * The Machine Tracker'​s IP search form has consolidated the `To` and `From`
 +    IP address search fields into a single `IP Range` search field with
 +    extended search syntax for ranges of IP addresses. ​ See LP#643544 for
 +    details.
 +  * ipdevpoll can now be made to run single job configurations from
 +    ipdevpoll.conf,​ to run in the foreground, and to log to stderr instead of
 +    its log file.
 +  * ipdevpoll will reset its log levels from logging.conf upon receiving a
 +    SIGHUP signal.
 +  * ipdevpoll will log the currently active polling jobs upon receiving a
 +    SIGUSR1 signal.
 +
 +
 +In June 2012 the number of full time NAV-developers doubled! ​
 +
 +
 +In September NAV 3.12 was out with:
 +
 +  * Rewrite of new Netmap using open standards as HTML5, Javascript (D3JS) and SVG (Scalable vector graphics) ​
 +  * A cleaner and more responsive Ip Device Info
 +  * An improved navbar search
 +  * Room information including devices and a powerful netbox interface overview
 +  * IPv6 traffic counters
 +  * An improved device poller
 +  * Greater use of django in favor of mod_python
 +
 + 
historyofnav.1327867059.txt.gz · Last modified: 2012/01/29 20:57 by faltin