Nav-users

nav-users@lister.sikt.no

3 participants
1372 discussions

NAV mac-search with Nexus and FabricPath
by Mischa Diehm 09 Apr '15

09 Apr '15

Hi, we have FP activated in our datacenter and use Cisco Nexus (5,6,7)k. I'm not sure what caused the problem but NAV can't find MAC-addresses on these devices and even on catalysts behind them anymore. I don't know what algorithm is used to figure out where a MAC-address is attached but maybe someone who knows can clarify what is needed for that to work? Thanks in advance, Mischa -- Mischa Diehm | Network Operations Center (NOC) UniBasel | UniRechenZentrum (URZ) Klingebergstr. 70 | CH-4056 Basel Tel. +41 61 267 1574 | http://urz.unibas.ch

2 7

Announcement: NAV 4.2.5 released
by Morten Brekkevold 27 Mar '15

27 Mar '15

The fifth maintenance release of the NAV 4.2 series is now available. This replaces the 4.2.4 release, which broke the parallel pinger, and possibly other event-posting components. Again, to those who already upgraded to 4.2.4, we apologize for the inconvenience. More details at the bug report here: https://bugs.launchpad.net/nav/+bug/1434520 The source code is available for download at Launchpad [1]. A new package for Debian Wheezy has been published in our APT repository [2], as usual. Changes ======= The following 20 reported issues have been fixed: * LP#1403365 (offMaintenance alerts for same device every 5 minutes) * LP#1422298 (device history crashes when viewing weathergoose events) * LP#1422316 (thresholdmon AttributeError crash) * LP#1425536 (Status widget error when filtering on Device group) * LP#1425846 (alert profiles does not display without refresh) * LP#1427666 (watchdog is slow) * LP#1428071 (Portadmin crashes when searching by sysname or ip) * LP#1428578 (seeddb test for snmp version crashes if neither v1 or v2c is supported) * LP#1429868 (ipdevpoll jobs that are no longer supposed to run for a device as flagged as "overdue") * LP#1430795 (SeedDB room edit form asks for user's location, shows no map until permission is given) * LP#1430797 (Geomap shows no map at all when no room positions are defined) * LP#1430802 (SeedDB room edit insists on inserting a geoposition) * LP#1430803 (SeedDB room form position indicator icon is missing) * LP#1431780 (Trunk port status is never reset on non-Cisco equipment) * LP#1432056 (mod_wsgi option WSGIApplicationGroup should be %{GLOBAL} by default) * LP#1432057 ([appliance] missing python-dnspython) * LP#1432620 (Unable to load Netmap layer 3 map with ELINK peers) * LP#1432682 (Should be able to specify exact subnet prefixes to ignore) * LP#1433063 (netmap zoom and pan does not work for some views) * LP#1433120 (Shouldn't generate linkState alerts for intentionally shutdown interfaces) Happy NAVing everyone! Links ===== [1] https://launchpad.net/nav/4.2/4.2.5 [2] https://nav.uninett.no/wiki/nav_on_debian -- Morten Brekkevold UNINETT AS

2 6

Re: Hard Disk Full
by Morten Brekkevold 26 Mar '15

26 Mar '15

On Wed, 25 Mar 2015 14:31:44 +0000 "Anderson, Ally" <A.Anderson(a)tees.ac.uk> wrote: > Hi Morten > > Many thanks for the prompts response No problem. Please do remember do Cc: the nav-users list when responding, unless revealing private information. > We are running the 4.2.2 distribution. This was installed using the > package management system on a 10Gb disk with a single partition. This > has been running for almost two years now. I will assume this means you are using a stable version of Debian GNU/Linux as your OS. Is this a virtual machine? 10GB sounds awfully small compared to most modern physical drives, even looking two years back - I would not run NAV in production on such a small drive. Just the OS itself would take up a large chunk of those 10GB, so I would strongly suggest that you increase the drive size. > Not entirely sure what has filled the disk, but the ARP/CAM tables > would make sense. If you could point me in the right direction I will > check With only 10GB to go on, it could be anything. But I would typically guess log files or the PostgreSQL database. Use the `du` command to figure out where in the directory structure the disk space is being used: du -csh /* | sort -h To see how much space PostgreSQL takes up, run: du -csh /var/lib/postgresql > Any help you could offer in clearing these down after a specific > number of days has elapsed would be appreciated. Once PostgreSQL is taking up X amount of space, it doesn't help to delete records to help the OS reclaim that space. The unused space is still allocated to PostgreSQL, which will re-use it when it needs to. After deleting a bunch of records, a full vacuum (with downtime) of the database must usually be issued to let the OS reclaim the disk space: sudo -u postgres vacuumdb --full See http://www.postgresql.org/docs/9.1/static/sql-vacuum.html . Regular record deletion will, of course, help maintain the database at a reasonable size. NAV comes with the navclean command, which can delete old log records from NAV's database. See /usr/lib/nav/navclean.py -h for more details. If the default expiry limit of 6 months is OK for you, you could set up a daily cron job to run something like this: /usr/lib/nav/navclean.py -f --arp --cam > Thanks > > Ally Haha, apologies for the Mr. Anderson quip; With no first name to go by, I just couldn't resist a reference to the Matrix ;-) -- Morten Brekkevold UNINETT

2 1

Hard Disk Full
by a.anderson＠tees.ac.uk 25 Mar '15

25 Mar '15

Hi As an inexperienced NAV user - I need some assistance. Our instance of NAV has filled the hard disk and I wondered if there was a way to delete some records from it. I would also like to know if there was a way of limiting how much information was stored. Thanks

2 1

Cisco IOS 3.6.x / VTP
by kentobias＠wcn.co 25 Mar '15

25 Mar '15

Hello all, Great work on NAV, appreciate all the hard work. I've looked through the documentation and searched the archive and I haven't seen this issue. I can't seem to pin down the cause. NAV version is 4.1.2 on the Debian virtual appliance you offer. I've added a new group of Cisco 3850s to a network and now changes to port information aren't saved. Description information is not saved at all. VLAN information is changed, but only ephemerally, not in the actual port configuration. This means that the VLAN information isn't preserved across reloads. The only difference that I can find are the IOS version and VTP. The previous 3850s are running 3.3.x and the new 3850s are running 3.6.1. The new 3850s are using VTP v3 whereas the current 3850s are not. There are no error messages generated during the port configuration that I can find. Has anyone seen this before? Thanks.

4 20

activate more counters
by AlexDF 24 Mar '15

24 Mar '15

Hi all I'm using NAV in an Italian Hospital, where all networking switches are from Enterasys (now Extreme Networks). Regarding the following interface counters: ifInMulticastPkts ifInBroadcastPkts ifOutMulticastPkts ifOutBroadcastPkts is it possible to add the graphs of the above counters on switch port details ? At the moment I have traffic, unicast, errors and discarded. Thanks Alex

3 5

Announcement: NAV 4.2.4 released
by Morten Brekkevold 20 Mar '15

20 Mar '15

The fourth maintenance release of the NAV 4.2 series is now available. The source code is available for download at Launchpad [1]. A new package for Debian Wheezy has been published in our APT repository [2], as usual. Changes ======= The following 20 reported issues have been fixed: * LP#1403365 (offMaintenance alerts for same device every 5 minutes) * LP#1422298 (device history crashes when viewing weathergoose events) * LP#1422316 (thresholdmon AttributeError crash) * LP#1425536 (Status widget error when filtering on Device group) * LP#1425846 (alert profiles does not display without refresh) * LP#1427666 (watchdog is slow) * LP#1428071 (Portadmin crashes when searching by sysname or ip) * LP#1428578 (seeddb test for snmp version crashes if neither v1 or v2c is supported) * LP#1429868 (ipdevpoll jobs that are no longer supposed to run for a device as flagged as "overdue") * LP#1430795 (SeedDB room edit form asks for user's location, shows no map until permission is given) * LP#1430797 (Geomap shows no map at all when no room positions are defined) * LP#1430802 (SeedDB room edit insists on inserting a geoposition) * LP#1430803 (SeedDB room form position indicator icon is missing) * LP#1431780 (Trunk port status is never reset on non-Cisco equipment) * LP#1432056 (mod_wsgi option WSGIApplicationGroup should be %{GLOBAL} by default) * LP#1432057 ([appliance] missing python-dnspython) * LP#1432620 (Unable to load Netmap layer 3 map with ELINK peers) * LP#1432682 (Should be able to specify exact subnet prefixes to ignore) * LP#1433063 (netmap zoom and pan does not work for some views) * LP#1433120 (Shouldn't generate linkState alerts for intentionally shutdown interfaces) Happy NAVing everyone! Links ===== [1] https://launchpad.net/nav/4.2/4.2.4 [2] https://nav.uninett.no/wiki/nav_on_debian -- Morten Brekkevold UNINETT AS

2 2

Announcement: NAV 4.2.3 released
by Morten Brekkevold 12 Feb '15

12 Feb '15

The third maintenance release of the NAV 4.2 series is now available. The source code is available for download at Launchpad [1]. A new package for Debian Wheezy has been published in our APT repository [2], as usual. Changes ======= The following 15 reported issues have been fixed: * LP#392148 (Add microformats in maintenance module) * LP#1108736 (seeddb vlan page have checkbox but no delete selected) * LP#1242868 (device group improvements) * LP#1248095 (device groups should be searchable in the NAVbar) * LP#1316608 (Search in statistics gives stacktrace) * LP#1398382 (AssertionError prevents Netmap from loading any graph/map) * LP#1410687 (room netbox interfaces must indicate that topology exists) * LP#1411243 (Radius error log search: "could not convert string to float: hours") * LP#1412735 (arnold switching from exponential to normal duration gives wrong duration) * LP#1414934 (Expanding some switch ports makes Network Explorer hang) * LP#1414943 (No collected IPv6 prefixes on Cisco Nexus routers) * LP#1414975 (network explorer doesn't report backend failures to end user) * LP#1419746 (portadmin crashes when searching for a netbox that has no type) * LP#1420836 (Parsing of sensors with names that contains #) * LP#1421126 (snmpAgentDown blocks BoxDown event) Happy NAVing everyone! Links ===== [1] https://launchpad.net/nav/4.2/4.2.3 [2] https://nav.uninett.no/wiki/nav_on_debian -- Morten Brekkevold UNINETT AS

1 0

Announcement: NAV 4.2.2 released
by Morten Brekkevold 08 Jan '15

08 Jan '15

The second maintenance release of the NAV 4.2 series is now available. The source code is available for download at Launchpad [1]. A new package for Debian Wheezy has been published in our APT repository [2], as usual. Changes ======= Important note: This release adds commas to the list of characters escaped in Graphite metric names, which may change the name used for some of your existing metrics after an upgrade. If you want to keep your data, the underlying files need to be renamed manually in your Graphite installation. See the updated release notes [3] for more details. The following 23 reported issues have been fixed: * LP#1169559 (Print button for Netmap) * LP#1394522 (Netbox and Location bulk import formats must be changed to include data attributes) * LP#1396913 (Status page, filter on Device Group) * LP#1396920 (NAV 4, Internet Explorer Compatibility mode) * LP#1396924 (NAV 4.2 does not work with SASS 3.4 or newer, but the install docs do not specify this) * LP#1397255 (Subject text of psuDown alerts in status tool is non- descriptive) * LP#1397886 (device history script timeout on many results) * LP#1398382 (AssertionError prevents Netmap from loading any graph/map) * LP#1398791 (Maintenance system stops working when an IP device on maintenance is deleted) * LP#1398815 (Rooms, hyperlink inconsistensies between report and seeddb) * LP#1399558 (portadmin tries to write to memory for each change) * LP#1400307 (Need easier way to remove services) * LP#1401114 (dropdown for ipdevice when adding a service is fubar) * LP#1401470 (ipdevpoll TypeError: unsupported operand type(s) for +: 'NoneType' and 'float') * LP#1403066 (Some routers fail to expand in Network Explorer) * LP#1403432 (report.conf, wrong url for netboxinfo) * LP#1403797 (Geomap is insanely slow after migration to Graphite in NAV 4.0) * LP#1403803 (Geomap "loading data" indicator is missing) * LP#1403884 (geomap sends data request on every tiny movement) * LP#1404207 (Intermittent ValueErrors thrown from pynetsnmp causes ipdevpoll jobs to fail) * LP#1404222 (Conflicting sysnames cause ipdevpoll jobs to crash) * LP#1404225 (Multiple DNS PTR records for the same IP address causes sysname to swing back and forth in NAV) * LP#1407625 (/search/devicegroup takes too long) Happy NAVing everyone! Links ===== [1] https://launchpad.net/nav/4.2/4.2.2 [2] https://nav.uninett.no/wiki/nav_on_debian [3] https://nav.uninett.no/doc/4.2/release-notes.html#nav-4-2 -- Morten Brekkevold UNINETT AS

1 0

How to speed up Geomap?
by Ingeborg Hellemo 04 Des '14

04 Des '14

The transition from NAV 3.15 to 4.X has made Geomap incredibly slow. If I change zoom-level it takes several (four) minutes before new dots and lines show up. I guess this has to do with graphite's webserver not being able to deliver data fast enough (5000 lines of "POST /render/ HTTP/1.1" 200 XXX "-" "Python-urllib/2.7" in httpd-access.log) . The httpd process runs at 100% WCPU Is there something I can tune to make Geomap usable again? --Ingeborg -- Ingeborg Østrem Hellemo -- ingeborg.hellemo(a)uit.no Dep. of Information Technology --- Univ. of Tromsø

2 2

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Nav-users