- Nav-users - lister.unit.no

Announcement: NAV 4.3.1 released
by Morten Brekkevold 20 Aug '15

20 Aug '15

The first maintenance release of the NAV 4.3 series is now out. The source code is available for download at Launchpad [1]. New packages for Debian Wheezy and Jessie have been published in our APT repository [2] as usual. Changes ======= The following reported bugs have been fixed: * LP#1464660 (macwatch AttributeError when attempting to post events under NAV 4.3.0) * LP#1466734 (Portadmin should link back to ipdevinfo) * LP#1467508 (report export csv not working) * LP#1469620 (Ipdevinfo: switchport activity only show activity for last 30 days) * LP#1469988 (arnold does not reset autoenable date on manual detentions) * LP#1478827 (Include vendor and description in the netbox API endpoint) * LP#1478835 (portadmin snmp timeout while saving) * LP#1480262 (Rendering a port traffic graph results in a UnicodeEncodeError) * LP#1480814 (Non-ASCII characters in username will crash login page if authenticating against a Microsoft AD server) * LP#1483145 (seeddb invalid ip crashes check connectivity) * LP#1484386 (Floating graph control panel intermittently appears at top of page when selecting Port Metrics tab in ipdevinfo) * LP#1484423 (ipdevpoll inventory job fails with AttributeError: 'NoneType' object has no attribute 'strip') * LP#1484427 (ipdevpoll 5minstats job fails on some Cisco WLCs) * LP#1486415 (IntegrityError when posting chassis events from ipdevpoll) * LP#1486430 (Jobs "inventory" and "statuscheck" fails after switch OS upgrade) Happy NAVing everyone! Links ===== [1] https://launchpad.net/nav/4.3/4.3.1 [2] https://nav.uninett.no/wiki/nav_on_debian [3] https://nav.uninett.no/doc/4.3/release-notes.html#nav-4-3 -- Morten Brekkevold UNINETT AS

1 0

no interface graph
by Tal Bar-Or 14 Aug '15

14 Aug '15

Hello List, I have just installed NAV 4.3.1 along with Graphite on Debian according to instruction, all seems to went well. I have issue that Interface graph not appear at all on other hand CPU's and RTA metrics yes, looking on logs "/var/log/carbon/query.log" i see following below ,any idea how to fix it please advice Thanks > 12/08/2015 01:37:17 :: [127.0.0.1:59337] cache query for > "nav.devices.2xx_1xx_2xx_2ports.Te2_0_2.ifInOctets" returned 0 values > 12/08/2015 01:37:17 :: [127.0.0.1:59337] cache query for > "nav.devices.2xx_1xx_2xx_2ports.Te2_0_2.ifOutOctets" returned 0 values > 12/08/2015 01:37:17 :: [127.0.0.1:59337] cache query for > "nav.devices.2xx_1xx_2xx_2ports.Te2_0_3.ifInOctets" returned 0 values > 12/08/2015 01:37:17 :: [127.0.0.1:59337] cache query for > "nav.devices.2xx_1xx_2xx_2ports.Te2_0_3.ifOutOctets" returned 0 values > 12/08/2015 01:37:17 :: [127.0.0.1:59337] cache query for > "nav.devices.2xx_1xx_2xx_2ports.Te2_0_4.ifInOctets" returned 0 values > 12/08/2015 01:37:17 :: [127.0.0.1:59337] cache query for > "nav.devices.2xx_1xx_2xx_2ports.Te2_0_4.ifOutOctets" returned 0 values > 12/08/2015 01:37:17 :: [127.0.0.1:59337] cache query for > "nav.devices.2xx_1xx_2xx_2ports.Te2_0_5.ifInOctets" returned 0 values > 12/08/2015 01:37:17 :: [127.0.0.1:59337] cache query for > "nav.devices.2xx_1xx_2xx_2ports.Te2_0_5.ifOutOctets" returned 0 values > 12/08/2015 01:37:17 :: [127.0.0.1:59337] cache query for > "nav.devices.2xx_1xx_2xx_3.ports.9.ifInOctets" returned 0 values > 12/08/2015 01:37:17 :: [127.0.0.1:59337] cache query for > "nav.devices.2xx_1xx_2xx_3.ports.9.ifOutOctets" returned 0 values > 12/08/2015 01:37:17 :: [127.0.0.1:59337] cache query for > "nav.devices.2xx_1xx_2xx_3.ports.A1.ifInOctets" returned 0 values > 12/08/2015 01:37:17 :: [127.0.0.1:59337] cache query for > "nav.devices.2xx_1xx_2xx_3.ports.A1.ifOutOctets" returned 0 values > 12/08/2015 01:37:17 :: [127.0.0.1:59337] cache query for > "nav.devices.2xx_1xx_2xx_5.ports.A1.ifInOctets" returned 0 values > 12/08/2015 01:37:17 :: [127.0.0.1:59337] cache query for > "nav.devices.2xx_1xx_2xx_5.ports.A1.ifOutOctets" returned 0 values > 12/08/2015 01:37:17 :: [127.0.0.1:59337] cache query for > "nav.devices.2xx_1xx_2xx_6.ports.A1.ifInOctets" returned 0 values > 12/08/2015 01:37:17 :: [127.0.0.1:59337] cache query for > "nav.devices.2xx_1xx_2xx_6.ports.A1.ifOutOctets" returned 0 values > 12/08/2015 01:37:17 :: [127.0.0.1:59337] cache query for > "nav.devices.2xx_1xx_2xx_7.ports.A1.ifInOctets" returned 0 values > 12/08/2015 01:37:17 :: [127.0.0.1:59337] cache query for > "nav.devices.2xx_1xx_2xx_7.ports.A1.ifOutOctets" returned 0 values > 12/08/2015 01:37:17 :: [127.0.0.1:59337] cache query for > "nav.devices.2xx_1xx_2xx_8.ports.A1.ifInOctets" returned 0 values > 12/08/2015 01:37:17 :: [127.0.0.1:59337] cache query for > "nav.devices.2xx_1xx_2xx_8.ports.A1.ifOutOctets" returned 0 values > 12/08/2015 01:37:17 :: [127.0.0.1:59337] cache query for > "nav.devices.5_2xx_2x_1xx_rev_sfr_net.ports.1_44.ifInOctets" returned 0 > values > 12/08/2015 01:37:17 :: [127.0.0.1:59337] cache query for > "nav.devices.5_2xx_2x_1xx_rev_sfr_net.ports.1_44.ifOutOctets" returned 0 > values > 12/08/2015 01:37:17 :: [127.0.0.1:59337] cache query for > "nav.devices.sw-qa12-core_gef_local.ports.A1.ifInOctets" returned 0 values > 12/08/2015 01:37:17 :: [127.0.0.1:59337] cache query for > "nav.devices.sw-qa12-core_gef_local.ports.A1.ifOutOctets" returned 0 value > -- Tal Bar-or

2 1

NAV RAM Usage
by Studart UNI-RN 29 Jul '15

29 Jul '15

Hello guys, I'm running NAV 4.2 in a production environment here at the company I'm working for. I'm using Debian Wheezy (no graph interface installed) with 1GB of RAM and I have about 50 devices in the NAV seed database. I've noticed that almost all the the memory is already in use. It's no problem for me to increase it since it's in a virtual environment. But since I increase it I was just wondering if this is normal for NAV to use such amount of RAM memory. Thank you very much, -- Studart Tavares Analista de Redes Liga de Ensino do RN UNIRN - Centro Universitário do RN 55 84 3215-2917 (r 2818)

2 2

Some beginners questions
by Per Andersson 26 Jun '15

26 Jun '15

Hello! I have just started trying NAV, and is running it on a small part of our network at the moment, and have some questions: It finds our vlans and matches them with the correct prefixes but since we don't follow the convention for naming router interfaces the net ident and description fields is either empty (most common) or a bit confusing. Is there a way to edit them manually (directly in the database?)? Any other suggestions? If I want to enter cabling, in which "direction" is it supposed to be, should I enter the wiring closet as "Room" and the office as "Target" or the other way around? /Per Andersson Chalmers IT-department

2 3

Announcement: NAV 4.3.0 released
by Morten Brekkevold 19 Jun '15

19 Jun '15

The initial 4.3 series release of NAV is now out, with only minor changes and some bugfixes since the release candidate. A big thanks to those who helped test the release candidate! 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 (We have no packages for Debian Jessie yet, due to dependency problems and our own resource constraints). The virtual appliance download has also been updated. Changes ======= This release makes some fundamental changes to NAV's data model to improve support for non-physical devices (like Cisco VSS and Cisco VDC). Please read the release notes [3] for further information. User-visible features and improvements: * LP#744943 (Add switch to toggle display of traffic lines in Geomap) * LP#961212 (Show planned/active maintenance tasks for device in IP Device Info) * LP#1149160 (Auto-recognize HTTP URLs in reports and hyperlink them) * LP#1166695 (PortAdmin available from the toolbox) * LP#1169550 (NAV's data model should reflect modern reality, with virtual device support) * LP#1242872 (Option to turn off traffic stats in Geomap) * LP#1248081 (New interface/tool to browse unrecognized neighbors) * LP#1366895 (Report widget) * LP#1421644 (Support Weathergoose traps from external temperature sensors) Bugfixes: * LP#1233093 (Report pages crash under psycopg2 >= 2.5) * LP#1397257 (Port Admin may not work properly for any non-HP and non-Cisco device) * LP#1447973 (CDP/LLDP neighbor matching fails when multiple ports match the identification) * LP#1447999 (Existing adjacency candidate data in db is not deleted if a device's CDP cache or LLDP remote table becomes empty) * LP#1448086 (Unable to identify LLDP neighbor's port in some instances) * LP#1458826 (1minstats job crashes on invalid ENTITY-MIB references from CISCO-PROCESS-MIB) * LP#1459138 (Ignore Cisco reserved VLANs when collecting BRIDGE-MIB data) * LP#1463724 (Increase frequency of module status verification) Happy NAVing everyone! Links ===== [1] https://launchpad.net/nav/4.3/4.3.0 [2] https://nav.uninett.no/wiki/nav_on_debian [3] https://nav.uninett.no/doc/4.3/release-notes.html#nav-4-3 -- Morten Brekkevold UNINETT AS

1 1

Failed to sending mail
by nicolas.biselx＠epfl.ch 15 Jun '15

15 Jun '15

Hello, When I do an alarm, the file eventengine.log receive the alert but with the following errors and I don't receive a mail: [2015-06-12 14:08:55,014] [INFO] [pid=26242 nav.alertengine.handle_new_alerts] alert 55 queued for admin due to subscription 1 [2015-06-12 14:09:21,098] [ERROR] [pid=26242 nav.alertengine.alertaddress.send] Email raised a DispatcherException indicating that an alert could not be sent at this time: Could not send email: Connection unexpectedly closed" Traceback (most recent call last): File "/usr/lib/python2.7/logging/handlers.py", line 926, in emit smtp.sendmail(self.fromaddr, self.toaddrs, msg) File "/usr/lib/python2.7/smtplib.py", line 722, in sendmail raise SMTPSenderRefused(code, resp, from_addr) SMTPSenderRefused: (553, 'sender domain must exist', 'navcron@navappliance') Logged from file profiles.py, line 377 [2015-06-12 14:09:21,655] [INFO] [pid=26242 nav.alertengine.check_alerts] 1 new alert(s), sent 0 alert(s), 1 queued alert(s), 0 alert(s) deleted, 1 failed send(s), 0 ignored [2015-06-12 14:09:21,656] [WARNING] [pid=26242 nav.alertengine.check_alerts] Send 1 alerts failed. I configured Exim with the following parameters: dc_eximconfig_configtype='satellite' dc_other_hostnames='exinfrserv1.epfl.ch' dc_local_interfaces='127.0.0.1 ; ::1' dc_readhost='exinfrserv1.epfl.ch' dc_relay_domains='' dc_minimaldns='false' dc_relay_nets='' dc_smarthost='mail.epfl.ch' CFILEMODE='644' dc_use_split_config='false' dc_hide_mailname='' dc_mailname_in_oh='true' dc_localdelivery='mail_spool' When I test with the command 'echo "hello world" | mail -vv -s test nicolas.biselx(a)epfl.ch' The mail is sent and receive In nav.conf, I also configured DEFAULT_FROM_EMAIL=nicolas.biselx(a)epfl.ch EMAIL_HOST=mail.epfl.ch EMAIL_PORT=465 EMAIL_HOST_USER=biselx EMAIL_HOST_PASSWORD=******** EMAIL_USE_SSL=True I don't know what's wrong, Is it fair to configure Exim and nav.conf ? Is what I missed part of the configuration ? Regards, Biselx Nicolas

3 2

Django and Debian 8
by stutavares＠unirn.edu.br 08 Jun '15

08 Jun '15

Hi guys, I have a newly installed version of Debian Jessie and it doesn't install nav with the simple 'apt-get install nav'. One of the reason is the dependancy on Django, which is in version 1.7 in the packages repository. I read a post that says you are still working on this compatibility issue. Meanwhile what should I do? Wait for a new version of nav? Try and install an older verion of Debian? What are my options now to install a new nav in my network? All the best, Studart

2 1

change map on geomap
by nicolas.biselx＠epfl.ch 27 Mai '15

27 Mai '15

Hello, Is it possible to change the map in Geomap? In our campus we have additional layers of openstreetmap it would be nice to Integer. see: http://plan.epfl.ch/?zoom=20&recenter_y=5864085.12615&recenter_x=731137.442… thank you

3 4

Announcement: NAV 4.3.0 release candidate 1
by Morten Brekkevold 21 Mai '15

21 Mai '15

We have a release candidate for NAV 4.3.0 ready to download for those who want an early peek. The source code is available for download at Launchpad [1]. A new package for Debian Wheezy has been published in our APT repository, but in the "navbeta" archive instead of the regular "nav" archive - modify the instructions at [2] accordingly (We have no packages for Debian Jessie yet, due to dependency problems and our own resource constraints). We have also published a "beta" Virtual Appliance on our homepage, if you want to test the release candidate separately from your production install (remember, there is no downgrade path!) Changes ======= This release makes some fundamental changes to NAV's data model to improve support for non-physical devices (like Cisco VSS and Cisco VDC). Please read the release notes [3] for further information. User-visible features and improvements: * LP#744943 (Add switch to toggle display of traffic lines in Geomap) * LP#961212 (Show planned/active maintenance tasks for device in IP Device Info) * LP#1149160 (Auto-recognize HTTP URLs in reports and hyperlink them) * LP#1166695 (PortAdmin available from the toolbox) * LP#1169550 (NAV's data model should reflect modern reality, with virtual device support) * LP#1242872 (Option to turn off traffic stats in Geomap) * LP#1248081 (New interface/tool to browse unrecognized neighbors) * LP#1366895 (Report widget) * LP#1421644 (Support Weathergoose traps from external temperature sensors) Bugfixes: * LP#1397257 (Port Admin may not work properly for any non-HP and non-Cisco device) * LP#1447973 (CDP/LLDP neighbor matching fails when multiple ports match the identification) * LP#1447999 (Existing adjacency candidate data in db is not deleted if a device's CDP cache or LLDP remote table becomes empty) * LP#1448086 (Unable to identify LLDP neighbor's port in some instances) Happy NAVing everyone! Links ===== [1] https://launchpad.net/nav/4.3/4.3.0 [2] https://nav.uninett.no/wiki/nav_on_debian [3] https://nav.uninett.no/doc/4.3/release-notes.html#nav-4-3 -- Morten Brekkevold UNINETT AS

1 0

Announcement: NAV 4.2.6 released
by Morten Brekkevold 06 Mai '15

06 Mai '15

The sixth 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. Debian Jessie (the next stable release of Debian) is scheduled for release on Saturday 25th April, so we will start working on building a package for Jessie as well. Changes ======= The following 11 reported issues have been fixed: Bugfixes: * LP#1248083 (The ipdevinfo "Affected" tab should be renamed to "what if") * LP#1248085 (ipdevinfo "affected" tab needs to properly list the affected organizations) * LP#1338388 (Netmap link traffic does not always show) * LP#1435451 (Vendors report should only show Vendors in use) * LP#1436125 (No CPU graph from some Cisco CPUs) * LP#1436388 (VLAN number cannot be forced by router port description) * LP#1437318 (PostgreSQL load driven up by overzealous pruning of old ipdevpoll_job_log entries in NAV 4.2.5) * LP#1438930 (No negative values can be displayed in graphs) * LP#1442538 (Graphite-web doesn't support metric aliases with non-ASCII characters) * LP#1443775 (alert templates for climate humidity notifications does not exist) * LP#1444416 (netmap L3 crash in urlresolvers.py) Happy NAVing everyone! Links ===== [1] https://launchpad.net/nav/4.2/4.2.6 [2] https://nav.uninett.no/wiki/nav_on_debian -- Morten Brekkevold UNINETT AS

1 1

NAV and VLAN with Virtualized firewall
by Mattias Söderholm 13 Apr '15

13 Apr '15

Hi! I have a problem with VLAN auto discover. I have followed the guidelines with adding the router (firewall), but it won't get the VLAN info from it. The firewall is a software firewall (Sophos UTM) that's running in a Hyper-V cluster for HA . Could it be the software switch in the Hyper-V that's giving some problem or the firewall software? Before I also had some HP 2530 swithes added as an GWS. Then I got some VLAN info added to NAV, but NAV deletes the VLAN info in the SeedDB after a while and create it again with a new ID. So now I have changed the HP 2530 switches back to SW and hope the VLAN info will stay in SeedDB! But it would be great if I can get VLAN info to show up in Netmap. Is there some way to fix this if I can't get the info from the firewall? There is also a problem if you change a GWS to a SW, then ipdevpoll try to still collect ip2mac from the device but won't get the info and you end up with WatchDog reporting problems with ip2mac for that switch, The solution I have used is to go into the database and delete all post related to ip2mac for that device from ipdevpoll_log_job table. Is it a bug or am I doing something wrong here? Best regards Mattias

2 21

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

Announcement: NAV 4.2.1 released
by Morten Brekkevold 28 Nov '14

28 Nov '14

The first 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 reported issues have been fixed: * LP#1395710 (api token can not be refreshed from the api) * LP#1396514 (Status tool in NAV 4.2 shows no events if API call returns a 500 error) * LP#1396516 (Status API in NAV 4.2 crashes when there are old deviant alerts present) * LP#1396517 (Status tool makes hyperlinks out of alert subjects that have no defined URL) * LP#1396531 (logengine spams the error message "KeyError: 'LINK'") * LP#1396914 (netmap filter on location excludes links) In the NAV 4.2.0 release announcement and changelog, four bugfixes were omitted by accident, because they had originally been committed to the 4.1.x release branch. The changelog has been updated. These were the bugfixes in question: * LP#1385121 ("Add graph to dashboard" does nothing under certain Apache configurations) * LP#1386716 (Maintenance task with no end time displays incorrectly in edit form) * LP#1389121 (when searching for an ip-address with space in it, NAV crashes) * LP#1389145 (Netbiostracker crash on unparseable MAC Address) Please refer to the release notes [3] for further information on upgrading. Happy NAVing everyone! Links ===== [1] https://launchpad.net/nav/4.2/4.2.1 [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

2 4

logengine spams with INFO-messages
by Ingeborg Hellemo 27 Nov '14

27 Nov '14

I am aware of https://bugs.launchpad.net/nav/+bug/1396531 but I am not sure it is related. Since NAV 4.2 I receive email every minute with INFO:nav.logengine:Reading new log entries What am I missing? --Ingeborg -- Ingeborg Østrem Hellemo -- ingeborg.hellemo(a)uit.no Dep. of Information Technology --- Univ. of Tromsø

2 1

NAV 4.2 empty status page
by Ingeborg Hellemo 27 Nov '14

27 Nov '14

We have just moved our NAV 4.2-box from test to production and with real use the bugs start popping up. One user will not see any Events on his status page, even though he has chosen all possible Event types. The user is even "NAV administrator" How to debug this? We know there are events to be seen and the handful of other users I have tested as will see events as expected. --Ingeborg -- Ingeborg Østrem Hellemo -- ingeborg.hellemo(a)uit.no Dep. of Information Technology --- Univ. of Tromsø

2 1

Announcement: NAV 4.2.0 released
by Morten Brekkevold 27 Nov '14

27 Nov '14

The feature release of the new 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 new features and changes have been introduced: * LP#1063703 (The status page is becoming cluttered and should be redesigned) * LP#1374384 (Adding new devices to a room on maintenance does not put those devices on maintenance) * LP#1383624 (Machine Tracker should search uplink data as well) * LP#1383625 (Machine Tracker MAC search should also search physical port addresses) * LP#1384262 (Add unrecognized neighbor search to navbar) * LP#1388078 (Add IGMP Multicast group usage statistics to NAV) * LP#1389226 (Arbitrary attributes on netbox and location) * LP#1390073 (Add support for AKCP sensorProbe8) * LP#1388835 (Maintenance Engine needs a rewrite) * Netmap has been redesigned to fit better in the NAV 4 design. Please refer to the release notes [3] for further information on upgrading. Happy NAVing everyone! Links ===== [1] https://launchpad.net/nav/4.2/4.2.0 [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

2 3

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Nav-users