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 | ||
historyofnav [2007/09/26 14:46] faltin |
historyofnav [2012/05/07 11:21] morten fix url |
||
---|---|---|---|
Line 3: | Line 3: | ||
+ | ===== 1999 - NAV v1 ===== | ||
- | + | The development of NAV started at [[http://www.ntnu.no|NTNU]] in 1999. Prior to that NTNU, like so | |
- | ===== 1999 ===== | + | |
- | + | ||
- | The development of NAV started in 1999. Prior to that NTNU, like so | + | |
many others, had acquired a traditional network management system (HP | many others, had acquired a traditional network management system (HP | ||
- | Openview) that hopefully would fulfill our needs. After thorough | + | Openview) that hopefully would fulfil our needs. After thorough |
investigation and adjustment of the system we found however that it | investigation and adjustment of the system we found however that it | ||
lacked functionality in many areas. We decided to implement a basic | lacked functionality in many areas. We decided to implement a basic | ||
Line 39: | Line 37: | ||
Trygve Lunheim, Tor-Arne Kvaløy, Eric Sandnes, | Trygve Lunheim, Tor-Arne Kvaløy, Eric Sandnes, | ||
Stig Venås, Gro-Anita Vindheim, Knut-Helge Vindheim. | Stig Venås, Gro-Anita Vindheim, Knut-Helge Vindheim. | ||
- | | ||
===== 2000 ===== | ===== 2000 ===== | ||
The development at the time was focused around perl and php. In 2000 | The development at the time was focused around perl and php. In 2000 | ||
- | we introduced java in an upgraded version of the traffic map. We | + | we introduced java in an upgraded version of the traffic map (vlanplot). We |
also introduced mySQL for our database. Further: | also introduced mySQL for our database. Further: | ||
Line 62: | Line 59: | ||
- | ===== 2001 ===== | + | ===== 2001 - NAV v2 ===== |
In early 2001 UNINETT gained interest in our system. They asked | In early 2001 UNINETT gained interest in our system. They asked | ||
Line 236: | Line 233: | ||
Magnus Thanem Nordseth, Andreas Åkre Solberg, Magnar Sveen, | Magnus Thanem Nordseth, Andreas Åkre Solberg, Magnar Sveen, | ||
Stian Søiland, Gro-Anita Vindheim, Morten Vold, Arne Øslebø. | Stian Søiland, Gro-Anita Vindheim, Morten Vold, Arne Øslebø. | ||
+ | |||
Line 259: | 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 271: | Line 269: | ||
Stian Søiland, Gro-Anita Vindheim, Morten Vold (project leader), Arne Øslebø. | Stian Søiland, Gro-Anita Vindheim, Morten Vold (project leader), Arne Øslebø. | ||
- | ===== 2005 ===== | + | ===== 2005 - NAV v3.0 ===== |
2005 was a relatively slow year for NAV. NTNU and UNINETT did not have so much resources to put into the | 2005 was a relatively slow year for NAV. NTNU and UNINETT did not have so much resources to put into the | ||
Line 277: | 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 286: | Line 293: | ||
- | ===== 2006 ===== | + | ===== 2006 - NAV v3.1 ===== |
- | 2006 has been a definite upswing for NAV. Project development is now supported by the UNINETT | + | 2006 has been a definite upswing for NAV. Project development is now |
- | [[http://www.gigacampus.no/om.en.html|GigaCampus programme]] with an overall goal | + | supported by the UNINETT |
- | of getting NAV up and running at most major universities and university colleges in Norway within 2008. Morten Brekkevold (previously Vold) is devoted full time | + | [[https://openwiki.uninett.no/gigacampus:about|GigaCampus programme]] with an |
- | to NAV (he is now employed by UNINETT). Vidar Faltinsen is back as project leader. From NTNU John Magne Bredal is working 40% with NAV. We have | + | overall goal of getting NAV up and running at most major universities |
- | also recruited a new student during the summer months; Stein Magnus Jodal. | + | and university colleges in Norway within 2008. Morten Brekkevold |
+ | (previously Vold) is devoted full time to NAV, now being employed by | ||
+ | UNINETT. Vidar Faltinsen made a comeback as project leader. John | ||
+ | Magne Bredal at NTNU devoted 40% of his time working with NAV. We | ||
+ | also recruited a student, Stein Magnus Jodal, to work on NAV as a | ||
+ | summer intern, and we kept him on for the fall. | ||
- | The university of Tromsø is making contributions to NAV. Together with the University of Bergen they are sponsoring a FreeBSD ports of NAV. | + | The Universities of Tromsø and Bergen began sponsoring a FreeBSD port |
- | University of Oslo is maintaining the NAV debian package. A Suse package is maintained by NTNU and a Centos RPM is contributed by | + | of NAV, while Tromsø offered to contribute their own code to NAV. The |
- | Alexander Krapivin at MSU, Moscow, Russia. We are in dialog with others as well. | + | Debian developer Morten Werner Olsen at The University of Oslo was |
+ | commisioned by UNINETT to maintain a Debian NAV package. A SuSE | ||
+ | package was maintained by NTNU and Centos RPMs were contributed by | ||
+ | Alexander Krapivin at MSU, Moscow, Russia. | ||
- | A strategy with feature releases twice a year is established (bug fixes in between). NAV 3.1 was released in June and 3.2 is scheduled for October. | + | A strategy of targeting new feature releases twice a year was |
- | * See [[http://svn.itea.ntnu.no/repos/nav/navme/tags/3.1.0/CHANGES|change log for 3.1]] | + | established (with bugfix releases in between). NAV 3.1 was released |
- | * See plans for 3.2 at the [[roadmap]]. | + | in June and 3.2, with an original schedule of October, was released in |
+ | February 2007. | ||
- | We have established a home page for NAV at [[http://sourceforge.net/projects/nav/|SourceForge]]. Releases and binaries are available from here. We are also | + | NAV gained the capability to actively block switch ports through the |
- | using the !SourceForge bug tracker system for bugs. We see a lot of traffic on the | + | addition of the NTNU-contributed Arnold tool. Adding the ability to |
- | [[http://desperados.itea.ntnu.no/pipermail/nav-users/|nav-users mailing list]]. A month after the 3.1 release we have seen | + | collect high speed traffic counters (64 bits) made it possible to |
- | approximately 160 downloads from around the world (the 3.0 version is downloaded 674 times as of 20 July 2006). | + | reduce the Cricket collector frequency for gigabit switch ports from |
+ | every 1 minute to every 5 minutes, thus removing the need to have a | ||
+ | separate configuration tree for gigabit ports. The IP Device Center (later renamed to IP Device Info) was introduced. | ||
- | Project participants in 2006: John Magne Bredal, Vidar Faltinsen (project leader), Stein Magnus Jodal, Morten Brekkevold. | + | We established a project page for NAV at SourceForge. This was used |
+ | for bug tracking and hosting source code releases. A month after the | ||
+ | 3.1 release, we had seen approximately 160 downloads from around the | ||
+ | world (at the same time, the 3.0 version had been downloaded 674 | ||
+ | times). | ||
+ | Project participants in 2006: John Magne Bredal, Vidar Faltinsen | ||
+ | (project leader), Stein Magnus Jodal, Morten Brekkevold. | ||
+ | |||
+ | ===== 2007 - NAV 3.2/3.3 ===== | ||
+ | |||
+ | The NAV year of 2007 opened with the belated 3.2 release in February. | ||
+ | The 3.2 release also marked our first step towards realizing a new | ||
+ | long-term goal: Reduce the number of dependencies and programming | ||
+ | languages utilized in NAV. | ||
+ | |||
+ | The 3.2 release replaced the messages system with separate maintenance | ||
+ | and message systems, rewritten from scratch, after many usability | ||
+ | complaints from users. The Perl SMS daemon was rewritten in Python, | ||
+ | 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 | ||
+ | release also brought numerous small improvements to NAV overall. | ||
+ | |||
+ | October 1st brought the NAV 3.3 feature release. This release added | ||
+ | the long-awaited plugin based SNMP trap daemon, which enabled NAV to | ||
+ | translate traps into NAV events and alerts. Browsing and searching of | ||
+ | device history was greatly improved. The web interface received a | ||
+ | major facelift. Switch/router interface names replaced port numbers | ||
+ | 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 | ||
+ | project leader. Kristian Klette was taken on as a new student intern, | ||
+ | and started working on a Traffic Map replacement, based on the Prefuse | ||
+ | visualization library. | ||
+ | |||
+ | Project participants in 2007: John Magne Bredal, Vidar Faltinsen, | ||
+ | Stein Magnus Jodal, Kristian Klette, Jostein Gogstad, Morten Brekkevold (project | ||
+ | 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. | ||
+ | |||
+ | |||
+ | |||
+ |