[html]
Version 3.1.0[/html]
(released 30 June 2006)
#####################################################################
## 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:
* Arnold, a subsystem to block users’ switch ports by using NAV’s
Machine Tracker data.
* IP Information Center web tool, displays any information NAV has on
single IP addresses.
* Extra tab on IP Device Center to illustrate switch port usage.
* The IP Device Center will now display a device’s software version,
and a timestamp of the last update made by getDeviceData.
* A “refresh” link on the IP Device Center allows the user to trigger
a new collection run to refresh the device data.
* l2trace web tool, enables users to trace network paths on layer
two.
* Autodiscovery command line tool added to contrib. This tool will
try to discover every managed network device within your network,
and add them to NAV.
* All logged in users are now considered members of the new system
group “Authenticated Users”. Minimum privileges for authenticated
users can be granted to this group.
* Password hashes stored in the account database are now salted, for
slightly enhanced security.
* NAV now supports reading interface speeds from the ifHighSpeed OID,
thus supporting speeds above 4.2Gbps.
* Initial db setup now suggests creating only one database user,
instead of the previous two.
Bugfixes:
* Dependency on pysnmp=3.3.5 (the unstable dev branch) has been
removed, please downgrade to pysnmp 2.
* EditDB no longer crashes when adding devices that report duplicate
serial numbers.
* AlertEngine would crash when concatenating several queued alerts
into one SMS message.
* AlertEngine would, under certain circumstances, not delete a user’s
queued alerts, resulting in constant retransmission of the same
queued alerts.
* Some improved debug logging in AlertEngine.
* DNS lookups in getDeviceData are slightly more robust.
* The cam logger now runs 4 times an hour, as opposed to once every
hour, which was not a very good default.
* Missing Traffic Map icons were added.
* Machine Tracker would crash when doing DNS lookups on inactive host
searches (#1509944).