Nav-users

nav-users@lister.sikt.no

1376 discussions

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Nav-users