NAV 3.8.1 is now available for download at Launchpad:
https://launchpad.net/nav/3.8/3.8.1
This is a maintenance release, which includes fixes for the following issues:
* Various problems with the 3.8 build/install system, discovered during
Debian packaging.
* LP#618555 (alert addresses are not validated by alert profiles ui)
* LP#646708 (ipdevpoll fails to shutdown)
* LP#667771 (LDAP fallback to local password authentication regression)
* LP#715801 (Wrong gwcount in prefix report)
* LP#715807 (Prefix net types are wrongly classified when single router has
multiple addresses)
* LP#715851 (Missing config files during 3.8.0 install)
* LP#717144 (problem adding position cords on room)
* LP#719232 (AlertEngine crash error: filter() argument after ** must be a
dictionary)
* LP#720024 (logengine crashes when message contains : characters)
Please report bugs at https://launchpad.net/nav/+filebug :-)
A binary package for Debian 5 (Lenny) will be made available as soon as
possible. The Debian package is maintained by Morten Werner Forsbring, on
commission From UNINETT.
Happy NAVing everyone!
--
Morten Brekkevold
UNINETT
Hello there,
After reading the release notes of NAV 3.8.0 I was thrilled to see that PortAdmin/vlanAdmin had finally been merged with NAV in this release, and swiftly upgraded our production NAV server to the 3.8.0. Now what I don't get, is the relation required between the netbox you want to "operate" with PortAdmin/vlanAdmin, the user and the VLAN. I have already tested with several switches with the same organization membership as my own account (who also is a NAV administrator) but no matter what I do, I never get any available VLANs on my PortAdmin tab on any switch or port (as you can see here: http://dl.dropbox.com/u/9962750/portadmin.png)
Am I missing something fundamental in terms of relations required between the netbox, user and vlans?
Best regards,
Vidar Stokkenes
NAV 3.8.0 is now available for download at Launchpad:
https://launchpad.net/nav/3.8/3.8.0
This is a feature release, which includes the following changes:
User-visible features and improvements:
* The database schema can now be kept updated automatically using the new
`syncdb.py` program. Please see the `NOTES` file, and run the program as
soon as you've upgraded.
* NAV can now configure descriptions and access VLANs on your switch ports
when an SNMP write community is set for a switch. This functionality is
accessible through the IP Device Info tool.
* SeedDB has been rewritten to use the Django framework (and has
subsequently been reduced from nearly 5000 lines of spaghetti code to just
below 2000 maintainable lines).
* The number of concurrent ipdevpoll jobs can now be limited on a per-job
basis, to ease the load on your system if so desired. See the annotated
`ipdevpoll.conf` file.
Bugfixes:
* LP#643550 (Include ipdevinfo links in switch search in machine tracker)
* LP#545029 (SmbChecker runs out of available file descriptors)
Please report bugs at https://launchpad.net/nav/+filebug :-)
A binary package for Debian 5 (Lenny) will be made available as soon as
possible. The Debian package is maintained by Morten Werner Forsbring, on
commission From UNINETT.
Happy NAVing everyone!
--
Morten Brekkevold
UNINETT
NAV 3.7.4 is now available for download at Launchpad:
https://launchpad.net/nav/3.7/3.7.4
This is a maintenance release, which includes fixes for the following issues:
* LP#645892 (report: csv export does not export full report)
This wasn't properly fixed in 3.6.0.
* LP#702796 (Syntax error in HttpChecker.py)
Please report bugs at https://launchpad.net/nav/+filebug :-)
A binary package for Debian 5 (Lenny) will be made available as soon as
possible. The Debian package is maintained by Morten Werner Forsbring, on
commission From UNINETT.
Happy NAVing everyone!
--
Morten Brekkevold
UNINETT