NAV 3.2.0 released


#1

[html]

=============================
Release notes for NAV 3.2.0
=============================
Please report bugs at http://sourceforge.net/projects/nav

Upgrading from NAV 3.1.1
========================

New messages and maintenance subsystems
---------------------------------------
NAV 3.2 introduces new messages and maintenance systems, rewritten from
scratch. These also utilize new database tables. There is no migration
strategy for these systems, which means that any maintenance schedules and
messages you have in your old NAV installation will be lost during the database
upgrade.


Update Cricket configuration
----------------------------
NAV 3.2 finally configures Cricket to exclusively use 64-bit traffic counters
for SNMPv2-enabled devices. This also means you must update your Cricket
configuration tree with new Defaults- and .nav-files from NAV.

NAV’s initial Cricket configuration tree is found in the source code under the
subsystem/statTools/cricket/cricket-config/ subdirectory. Copy this
recursively to your active cricket-config directory (and make sure to also copy
the hidden .nav files as well). If your cricket-config directory is
/usr/local/cricket/cricket-config/ , you can do it like this:

cp -rv subsystem/statTools/cricket/cricket-config <br /> /usr/local/cricket/

Also, you can update your Cricket installation’s ‘subtree-sets’ file, which is
contained in the same directory as cricket-conf.pl. Remove the ‘giga’ subtree.
Nothing should break if you forget to, however.


Cricket data migration
----------------------
The switch to 64-bit traffic counters also means that the “giga” configuration
subtrees and data directories are now obsolete, and the cron process that ran
collection for the giga subtree once a minute has been removed. All Cricket
data collection is now done in 5 minute intervals.

After the upgrade, before you start NAV/Cricket again, you will need to move
your existing RRD-files in the giga directories to the corresponding "normal"
directories, if you want to keep historical statistical data for your gigabit
interfaces.

Go to your cricket-data directory, there you should typically find the
following subdirectories:

router-interfaces switches
router-interfaces-snmpv1-and-giga switch-ports
routers switch-ports-snmpv1-and-giga

Move the data files from the giga directories into the corresponding non-giga
directories, like so:

mv router-interfaces-snmpv1-and-giga/* router-interfaces
mv switch-ports-snmpv1-and-giga/* switch-ports

Be aware that if you are running an older version of NAV, your giga directories
might instead be named ‘giga-switch-ports’ and ‘giga-router-interfaces’.

When you’ve done this, you should run makecricketconfig.pl and cleanrrds.pl as
the navcron user, to create a new Cricket configuration tree and clean up NAV’s
RRD file database:

# su navcron
$ makecricketconfig.pl
$ cleanrrds.pl -r


You may notice discontinuities in your gigabit traffic graphs at the time of
the upgrade, due to the switch from 32-bit to 64-bit counters.



Version 3.2.0
(released 02 February 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:

* New messages and maintenance web tools, rewritten from scratch, replace the
old messages system. The maintenance tool features a calendar for ease of
use.

* SMS Daemon rewritten in Python, now extensible with dispatcher plugins.
Existing plugins for Gammu, Boost Communications (www.boostcom.no) and
e-mail gateways.

* New link from alert profiles enables users to see their own SMS queues.

* More information and links in the IP Device Browser. Among other things:
New color for 10gig ports, displays serial number, displays software
version and displays “first discovered by NAV” time.

* Full description (ifAlias) string now stored for gwports too.

* All reports have been revised. A new report lists unrecognized CDP
neighbours seen by NAV. Reports now display 1000 rows per page by default,
instead of 100.

* The status page now shows devices and services on maintenance.

* A new tool to show ranked statistical data collected by NAV/Cricket.
Useful for checking which routers/switches have the highest CPU
utilization, which interfaces have the most traffic, etc.

* NAV now configures Cricket to utilize 64-bit traffic counters where
applicable, preventing counter wrap-around problems for saturated links and
reducing collection frequency for gigabit interfaces from once a 1 minute
to once every 5 minutes.

* Room IDs can now be changed in EditDB

* The OID tester component of getDeviceData now runs faster, by not issuing
unnecessary indexed community snmp queries.

* New About-page in web interface.

* HTML templates restructured, much of the web interface will now validate as
XHTML 1.0 Transitional.

* NAV installation can now properly report its own version number.

* JVM options can now be configured individually for Java bases subsystems in
nav.conf. Java subsystems can now also be configured to use an alternate
JVM installation using the JAVA_HOME variable in nav.conf.

* Cleaned up output from nav start/stop/status commands, to increase
legibility.

* Removed gDD dependency on the system’s /usr/bin/host program.

* Arplogger now ignores routers that are known to be down, instead of spewing
SNMP query errors by e-mail.

* IP Devices can now be deleted directly from the Edit IP Device form in
EditDB.

* Nice, new icons for several web tools, now with SVG source files.

Bugfixes:

* Many SQL errors related to missing tables in FROM clauses fixed.

* Fixed bug #1551839 (Cannot change IP address in EditD:roll:

* Fixed bug #1602315 (EditDB crashes when attempting to delete rooms in use)

* Fixed bug #1643321 (EditDB crashes when entering invalid IP address)

* Fixed bug which crashed EditDB when devices returned SNMP Integer values as
serial numbers.

* Arnold now properly blocks switch ports on HP equipment.

* Changed inefficient hash indexes which caused the logengine (syslog
analyzer) to run extremely slowly and PostgreSQL to run up an insane server
load.

* Fixed bug that occurred spuriously, causing the Prefix Matrix to believe an
entire network scope was a subnet on its own.

* makecricketconfig.pl would set strange umask values when writing
cricket-config, which would cause permission problems and possibly make
graphs disappear from the Cricket web interface.

* … and various other small bugs.


Morten Vold
UNINETT

[/html]

#2

[html] It seems we pushed the 3.2.0 release out the door a little too fast. I’ve had a disturbing bug report today that indicates total breakage of NAV’s eventEngine.

NAV 3.2.0 introduces the new messages and maintenance subsystems, discarding the old combined messages/maintenance interface. In doing so, the old message/maintenance database tables are dropped. Apparently, though, the eventEngine erroneously uses the maintenance schedule tables to retrieve the maintenance status of devices, instead of the alert history tables, which are authoritative for these kinds of device states.

None of the active NAV developers were aware of this, and the result is that the eventEngine tries to use database tables that don’t exist, and therefore seems to fail to retrieve any meaningful data about devices.


/I would therefore advise everyone to delay upgrading to or installing NAV 3.2, while we are working on a bugfix for this problem./




For those really persistent souls among you, you can still have the eventEngine working decently if you modify the 3.2.0.sql script and comment out the following SQL statements before running it:

DROP VIEW maintenance_view;
DROP TABLE maintenance;
DROP TABLE emotd_related;
DROP TABLE emotd;

If the tables have already been dropped, or you have made a clean installation of NAV 3.2.0, you can install the missing tables in the manage database by locating their definitions in http://svn.itea.ntnu.no/repos/nav/navme/tags/3.1.1/doc/sql/manage.sql .

Please be aware that even with this “patch” in place, eventEngine will be unable to hold back alerts for devices on maintenance, since it is looking in the wrong place for maintenance status.


mvh
Morten Brekkevold
UNINETT [/html]