Hi,
first of all welcome to the list!
we (UniBasel) use NAV for quite some while now and are very pleased with the possibilities NAV gives us. We use Debian as OS with the following Setup:
root@urz-nav:~# uname -a
Linux urz-nav 2.6.32-5-amd64 #1 SMP Fri May 10 09:44:53 UTC 2013 x86_64 GNU/Linux
root@urz-nav:~# cat /etc/debian_version
6.0.7
root@urz-nav:~# dpkg -l | grep nav
ii nav 2+3.14.15-1 Network Administration Visualized
A problem we have since a while is that our system is permanently under a lot of load (mostly CPU bound) and we haven't really found a way to reduce the pressure. The hardware we use is a hp blade (ProLiant BL460c G6) with:
Intel(r) Xeon(r) Processor X5550 (4 Cores/ 8 Threats)
(8M Cache, 2.66 GHz, 6.40 GT/s Intel(r) QPI)
and:
root@urz-nav:~# free
total used free shared buffers cached
Mem: 12321700 11673596 648104 0 387768 9123748
At the moment we have 1460 active Devices (mainly Cisco Switches). Around 30 or 40 are OVERDUE in:
https://urz-nav/report/lastupdated
So my question is, do you have any good experience with HW-systems that are actually dealing with this amount of devices or is there any tuning possibility (without losing functionality) we could try to reduce the pressure on the system?
Thanks in advance,
Mischa Diehm
--
Mischa Diehm | Network Operation Center (NOC)
Universitaet Basel | Universitaetsrechenzentrum
Klingelbergstr. 70 | CH-4056 Basel | Switzerland
Tel. +41 61 267 15 74 | Fax +41 61 267 22 82 | http://urz.unibas.ch
Hi all,
we thought we should do as everybody else on the Internet, so this week
we launched our own NAV blog.
As NAV developers, we hope to blog about what we're working on behind
the scenes, be it either related to network management or software
development, but it will always be related to our work on NAV.
Our first entry is up on http://blog.nav.uninett.no/ - have a read :-)
--
Morten Brekkevold
UNINETT
The second beta release of the NAV 4.0 series is now available for
download at Launchpad: https://launchpad.net/nav/4.0/4.0b2
This release fixes three bugs reported against the first beta version,
as well as improving the UI of several of the tools:
* LP#1262644 (seeddb bulk import does not work)
* LP#1263040 (ipdevinfo should not crash when Graphite-web is not reachable)
* LP#1267464 (NAV 4 must provide a tool for migrating RRD data from NAV 3)
The most important of these changes is the addition of the conversion
tool to migrate data from NAV 3's RRD files into NAV 4's Graphite
metrics. This was held back from b1 due to license compatibility issues,
which should now be resolved.
Instructions for migrating RRD data has been added to the release notes,
but in short, they refer to the migration guide available at [1].
A Debian package has been uploaded to our APT repository. We have not
yet built a new virtual appliance, but upgrading your existing one
should be simple matter of "apt-get update && apt-get upgrade".
As usual, please report bugs at https://launchpad.net/nav/+filebug .
Happy NAVing everyone!
[1] https://nav.uninett.no/doc/4.0/howto/migrate-rrd-to-graphite.html
--
Morten Brekkevold
UNINETT AS
The fourth maintenance release of the NAV 3.15 series is now available
for download at Launchpad: https://launchpad.net/nav/3.15/3.15.4
This release fixes 4 reported issues:
* LP#1246684 (AttributeError crash in Machine Tracker when search results
include data from deleted IP devices)
* LP#1255958 (DHCP service-check failure)
* LP#1265753 (portadmin does not allow empty ifalias)
* LP#1265755 (portadmin fails to load template for ifalias format)
Please report further bugs at https://launchpad.net/nav/+filebug
A binary package for Debian Wheezy has been made available in our APT
repository.
Happy NAVing everyone!
--
Morten Brekkevold
UNINETT AS