Differences

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

--- historyofnav [2007/09/16 07:46] – faltin
+++ historyofnav [2012/09/18 07:48] (current) – [2012 - NAV 3.11, 3.12] bredal
@@ Line 3: / Line 3: @@
+===== 1999 - NAV v1 =====
-===== 1999 =====
+The development of NAV started  at [[http://www.ntnu.no|NTNU]] in 1999. Prior to that NTNU, like so
-The development of NAV started in 1999. Prior to that NTNU, like so
 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
 lacked functionality in many areas. We decided to implement a basic
@@ Line 14: / Line 13: @@
 The name NAV came about later, in the initial stages we called our
-system **NettInfo**. The first tasks we solved were:
+system //NettInfo//. The first tasks we solved were:
   * A rudimentary collection system that gathered router port data using SNMP.
@@ Line 38: / Line 37: @@
 Trygve Lunheim, Tor-Arne Kvaløy, Eric Sandnes,
 Stig Venås, Gro-Anita Vindheim, Knut-Helge Vindheim.
 ===== 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:
@@ Line 61: / Line 59: @@
-===== 2001 =====
+===== 2001 - NAV v2 =====
 In early 2001 UNINETT gained interest in our system. They asked
@@ Line 198: / Line 196: @@
 new equipment types:
-  * An OID database is introduced containing information on all SNMP OIDs NAV used in the collection process.  The new collection engine, getDeviceData, uses the OID datebase. When new equipment is added to NAV it is tested against all the OIDs and classified accordingly.
+  * An OID database is introduced containing information on all SNMP OIDs NAV used in the collection process.  The new collection engine, getDeviceData, uses the OID database. When new equipment is added to NAV it is tested against all the OIDs and classified accordingly.
 The new collection system (getDeviceData) uses a plug in-based architecture, working
@@ Line 220: / Line 218: @@
   * Device management with the ability to track milestone events of physical devices from order and arrival through the operational stages.
-Also worth mentioning; NAV has so far been presented on numerous occations/
+Also worth mentioning; NAV has so far been presented on numerous occasions/
 conferences in Norway. In 2003 NAV is for the first time
 presented internationally:
@@ Line 235: / Line 233: @@
 Magnus Thanem Nordseth, Andreas Åkre Solberg, Magnar Sveen,
 Stian Søiland, Gro-Anita Vindheim, Morten Vold, Arne Øslebø.
@@ Line 242: / Line 241: @@
 was to finish off unfinished work, fixing bugs and testing the
 system thoroughly. In terms of new functionality, a conservative model was followed.
-Our focus was on completing NAV3 and thus permanantly leaving NAV2 behind.
+Our focus was on completing NAV3 and thus permanently leaving NAV2 behind.
 Many hours were put into further
@@ Line 258: / Line 257: @@
 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.
-A total of 8 NAV 3.0 beta releases was relased in 2004, beta4  (May 11) being the first GPL release
+A total of 8 NAV 3.0 beta releases was released in 2004, beta4  (May 11) being the first GPL release
 and beta7 (July 27) being the first with a changelog (which has been updated since).
@@ Line 270: / Line 269: @@
 Stian Søiland, Gro-Anita Vindheim, Morten Vold (project leader), Arne Øslebø.
-===== 2005 =====
+===== 2005 - NAV v3.0 =====
 was a relatively slow year for NAV. NTNU and UNINETT did not have so much resources to put into the
@@ Line 276: / Line 275: @@
 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]].
@@ Line 284: / Line 292: @@
 Faltinsen, Gro-Anita Vindheim, Morten Vold (project leader).
-===== 2006 =====
- has been a definite upswing for NAV. Project development is now supported by the UNINETT
+===== 2006 - NAV v3.1 =====
-[[http://www.gigacampus.no/om.en.html|GigaCampus programme]] with an overall goal
-of getting NAV up and running at most major universities and university colleges in Norway within 2008. Morten Vold is devoted full time
-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
-also recruited a new student during the summer months; Stein Magnus Jodal.
-The university of Tromsø is making contributions to NAV. Together with the University of Bergen they are sponsoring a FreeBSD ports of NAV.
+has been a definite upswing for NAV. Project development is now
-University of Oslo is maintaining the NAV debian package. A Suse package is maintained by NTNU and a Centos RPM is contributed by
+supported by the UNINETT
-Alexander Krapivin at MSU, Moscow, Russia. We are in dialogue with others as well.
+[[https://openwiki.uninett.no/gigacampus:about|GigaCampus programme]] with an
+overall goal 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 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.
-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.
+The Universities of Tromsø and Bergen began sponsoring a FreeBSD port
-  * See [[http://svn.itea.ntnu.no/repos/nav/navme/tags/3.1.0/CHANGES|change log for 3.1]]
+of NAV, while Tromsø offered to contribute their own code to NAV.  The
-  * See plans for 3.2 at the [[roadmap]].
+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.
-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
+A strategy of targeting new feature releases twice a year was
-using the !SourceForge bug tracker system for bugs. We see a lot of traffic on the
+established (with bugfix releases in between).  NAV 3.1 was released
-[[http://desperados.itea.ntnu.no/pipermail/nav-users/|nav-users mailing list]]. A month after the 3.1 release we have seen
+in June and 3.2, with an original schedule of October, was released in
-approximately 160 downloads from around the world (the 3.0 version is downloaded 674 times as of 20 July 2006).
+February 2007.
-Project praticipants in 2006: John Magne Bredal, Vidar Faltinsen (project leader), Stein Magnus Jodal, Morten Vold.
+NAV gained the capability to actively block switch ports through the
+addition of the NTNU-contributed Arnold tool.  Adding the ability to
+collect high speed traffic counters (64 bits) made it possible to
+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.
+We established a project page for NAV at SourceForge.  This was used
+for bug tracking and hosting source code releases.  A month after the
+.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.
+ ===== 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