[html]
A release candidate of NAV 3.3.0 is now available for download at SourceForge,
see http://sourceforge.net/projects/nav
This is mainly a feature release, but many bugs have also been fixed. We
kindly ask you to give us feedback, both positive and negative, on the mailing
list if you decide to test the release candidate.
We will wait about 10 days to see what issues may arise concering this
candidate, before we release the final 3.3.0 version.
The Debian package maintainer, Morten Werner Olsen, is currently in the final
stages of testing a Debian Etch package of NAV 3.2.2, and will proceed to
package NAV 3.3.0 when this work is finished.–
mvh
Morten Brekkevold
UNINETT
Version 3.3.0_rc1
(released 18 September 2007)
#####################################################################
## WARNING WARNING WARNING WARNING WARNING WARNING WARNING ##
#####################################################################
## ##
## This release makes changes to the NAV database. If you are ##
## upgrading from a previous release you also need to upgrade your ##
## database schema. For information on how to upgrade the database ##
## schema, please take a look in doc/sql/upgrades for more ##
## information. ##
## ##
#####################################################################
New features and improvements:
* Plugin-based SNMP trap reception daemon. Comes ready with plugins
for LINKUP/LINKDOWN traps and association traps from Airespace
equipment (Cisco WLAN Controllers).
* Greatly improved browsing and searching of device history in
device management web tool.
* Redesigned web interface to make it more concise.
* Switch port numbers replaced by interface names as identifiers in
all parts of the interface, including the Machine Tracker.
* IP Device Center now has a tab to display router ports on modules,
and also has detail views for router ports.
* SF#1556369 (Support machine tracker switch searches by IP address).
* Status page automatically refreshes every 30 seconds.
* Logengine can now parse syslog files using a user defined
character set (whereas it would previously choke on non-ASCII
Latin-1 characters being inserted in the database).
Bugfixes:
* SF#1733239 (SQL character encoding errors in logengine)
* SF#1750311 (Status subsystem crashes under mod_python 3.3.1)
* SF#1733356 (Alert profile filters based on subcategory do not work)
* SF#1660467 (Status Page crashes when box is down/on maintenance)
* SF#1742713 (Messages retains db connections between browser requests)
* SF#1739532 (l2trace crashes with traceback when searching by dns name)
* SF#1702676 (EditDB assumes all SNMP devices can speak SNMPv1)
* SF#1724688 (Missing quotes in arnold.pl)
Also various other small bugfixes and improvements.
===========================
Release notes for NAV 3.3
===========================
Please report bugs at http://sourceforge.net/projects/nav
If you are upgrading from versions of NAV older than 3.2.2, please refer to the
release notes of the in-between versions before reading any further.
SNMP Trap daemon
================
NAV 3.3 features a new, plugin-based SNMP trap daemon. The process is called
snmptrapd, and will start by default along with the rest ov NAV when the “nav
start” command is issued.
The trap daemon currently comes with two plugins, or traphandlers (sic) as the
snmptrapd calls them. One handles LINKUP and LINKDOWN traps from equipment,
translating these into NAV linkState events. The resulting linkUp/linkDown
alerts can be subscribed to through the Alert Profiles subsystem. The second
plugin handles access point association/disassociation traps (sent when dumb
access points associate or disassociate with the controller, not when wireless
clients associate with access points) from a Cisco WLAN Controller, translating
these into NAV events which can also be subscribed to.
For further snmptrapd docs, see subsystem/snmptrapd/README .
Upgrading from NAV 3.2.2
========================
Database schema changes
-----------------------
NAV 3.3 makes various small changes to the database tables containing
historical machine tracker data. Measurements show that updating the schema
with these changes will run about 33 times slower on PostgreSQL 7.4 than on
PostgreSQL 8.1. No, this is not a typo, we literally mean thirty-three times
slower. The actual running time will vary with the number of records present
in the tables.
The provided upgrade script employs a schema change syntax that was first
introduced in PostgreSQL 8, and will consequently not work on a PostgreSQL 7.4
installation. While more complex, 7.4-compatible syntax is provided in the
script comments, it is highly recommended to upgrade to PostgreSQL 8 before
upgrading NAV to version 3.3, as this minimizes the amount of downtime.
Although NAV 3.3 will most certainly run fine on PostgreSQL 7.4 after an
upgrade, it is likely that future NAV releases will use non-backwards
compatible PostgreSQL 8 syntax. We therefore recommend upgrading as soon as
possible.
[/html]
—