- Nav-users - lister.unit.no

Announcement: NAV 5.0.1 released
by Morten Brekkevold 05 Des '19

05 Des '19

The first maintenance release of the 5.0 series of NAV is now out! The source code is available for download at GitHub [1]. New packages for Debian 9/10 (Stretch/Buster) are available in our APT repository [2] as usual. Please also be extra aware of config file changes. Look out for `*.dpkg-dist` files in /etc/nav and make sure to update your running config. The virtual appliance will be updated shortly. Deprecation warning =================== Python 2 reaches its end-of-life on **January 1, 2020**. NAV 5.0 therefore moves to Python 3, and as such, you will need at least Python 3.5 to run NAV. Most of NAV will still run on Python 2 as of the 5.0 release, but from this point, Python 2 will be deprecated and we will start removing code that exists solely to keep compatibility with Python 2. Changes ======= Fixed GitHub issues in this release: * #2016 (ipdevpoll inventory job crashes when processing manufacturing dates from ENTITY-MIB under Python 3) * #2019 (IP Device info "Neighbor" tab is blank) * #2023 (Netmap layer 3 crashing) * #2025 (SeedDB bulk import file upload crashes) * #2030 (Ensure internal snmp agent check state stays in sync with global snmpAgentState) * #2031 (Fix PortAdmin crash on invalid IP search) * #2032 (Replace SNMP community columns in SeedDB netbox listing with management profile lists) * #2033 (Don't crash when logging in users with old-style password hashes) Please see the release notes [3] for more details. Happy NAVing everyone! Links ===== [1] https://github.com/UNINETT/nav/releases [2] https://nav.uninett.no/install-instructions/#debian [3] https://nav.uninett.no/doc/latest/release-notes.html#nav-5.0 -- Sincerely, Morten Brekkevold Uninett

1 0

Upgrade Debian to Buster and NAV to 4.9.8
by René Romijn 02 Des '19

02 Des '19

Hi, We did an upgrade to a new VM, we installed Debian Buster and we installed NAV 4.9.8. After that we did a restore of the postgress db with navsyncdb, and we also restored the /var/lib/graphite directory to have the history of the graphs. But now if i reboot the new NAV server, the graphs are resetted tot he point we did the restore. In the console log we see this error: 16/09/2019 08:02:28 :: Unhandled Error Traceback (most recent call last): File "/usr/lib/python3/dist-packages/twisted/python/threadpool.py", line 250, in inContext result = inContext.theWork() File "/usr/lib/python3/dist-packages/twisted/python/threadpool.py", line 266, in <lambda> inContext.theWork = lambda: context.call(ctx, func, *args, **kw) File "/usr/lib/python3/dist-packages/twisted/python/context.py", line 122, in callWithContext return self.currentContext().callWithContext(ctx, func, *args, **kw) File "/usr/lib/python3/dist-packages/twisted/python/context.py", line 85, in callWithContext return func(*args,**kw) --- <exception caught here> --- File "/usr/lib/python3/dist-packages/carbon/writer.py", line 189, in writeForever writeCachedDataPoints() File "/usr/lib/python3/dist-packages/carbon/writer.py", line 98, in writeCachedDataPoints (metric, datapoints) = cache.drain_metric() File "/usr/lib/python3/dist-packages/carbon/cache.py", line 187, in drain_metric metric = self.strategy.choose_item() File "/usr/lib/python3/dist-packages/carbon/cache.py", line 116, in choose_item return next(self.queue) builtins.StopIteration: Is this easy to fix? Kind regards, René.

2 11

Downgrade back to 4.9.8?
by Steve Kersley 14 Nov '19

14 Nov '19

Afternoon all, Is there a way to downgrade a Nav install to 4.9.8? Or will I need to blow away the database and start from scratch (no huge deal to be honest). Confession: I'm running it on Ubuntu rather than the recommended Debian. It got upgraded to 5.0.0, but as the Ubuntu LTS releases don't have a version of graphite-web that works with wsgi-python3 it's become an either/or, and I use graphite for storing other metrics as well as those from Nav. On attempting to pin the older version of Nav, it's failing to install because the database update script failed. Which I presume is because it had already upgraded the database for 5.0.0. I'm also toying after this to look at options of having Nav (and graphite and other services on this machine) as Docker containers simply to avoid version clashes in future. I see that Docker is listed as experimental, are there any particular issues to be aware of? Steve.

2 1

NAV netmap
by Erik 14 Nov '19

14 Nov '19

Hello, two questions on this part of NAV. 1. I have rooms which are in nested locations like "Address > Town > Country" but when I select "town" nothing shows in Netmap? Only selecting a room will show anything. I would have expected to show all which are below the nested set? 2 Is it possible to have a URL which wiil show a selected View in Full Screen directly so I can show it on a Dashboard monitor without manually having to select Full View? Cheers Erik

2 1

NAV 5.0.0
by Erik 08 Nov '19

08 Nov '19

Hi, After upgrading from 4.9.8 to 5.0.0 all works fine, except the "neighbors" tab. It worked fine in 4.9.8, but after upgrading it is blank? Cheers Erik

3 2

Announcement: NAV 5.0.0 released
by Morten Brekkevold 08 Nov '19

08 Nov '19

The first feature release of the 5.0 series of NAV is now out! The source code is available for download at GitHub [1]. New packages for Debian 9/10 (Stretch/Buster) are available in our APT repository [2] as usual. Please also be extra aware of config file changes. Look out for `*.dpkg-dist` files in /etc/nav and make sure to update your running config. The virtual appliance will be updated shortly. Deprecation warning =================== Python 2 reaches its end-of-life on **January 1, 2020**. NAV 5.0 therefore moves to Python 3, and as such, you will need at least Python 3.5 to run NAV. Most of NAV will still run on Python 2 as of the 5.0 release, but from this point, Python 2 will be deprecated and we will start removing code that exists solely to keep compatibility with Python 2. Changes ======= User-visible features and improvements: * #1793 (Add maintenance filter option to netbox API endpoint) + #1995 (Add maintenance filter to Netbox API endpoint) * #1859 (Improve portadmin support for dot1x) * #1905 (Add support for alcatel DDM-sensors) * #1908 (Add display widget for binary/boolean sensors to "racks") * #1919 (Add support for external sensors from newer Watchdog products) + #1926 (Add support for most external sensors on newer watchdog products) * #1930 (Refactor IT-WATCHDOGS-MIB MibRetriever implementations) * #1943 (Improve support for boolean sensors in racks) * #1947 (Management profiles) * #1969 (Store local chassis ids from LLDP-MIB and use for neighbor lookups) * #1970 (Add API for management profiles) * #1971 (Provide option to automatically enable CDP on voice ports) + #1974 (enabling CDP when a voice port is set using portadmin) * #1987 (Refactor power supply and fan monitoring functionality) * #1988 (Add status monitoring for Juniper PSUs and FANs) * #1989 (Collect optical sensor measurements from Coriant Groove devices) * #1998 (Remove support for alert dispatching over Jabber) * #2002 (Refactor installation documentation.) * #2005 (Export stream of serialized alerts from the event engine) * #2007 (Support REMOTE_USER header for web authentication) * #2008 (Add more database stats to Watchdog's "NAV by the numbers") Fixed GitHub issues in this release: * #1978 (Netmap layer 2 traffic data requests to Graphite are too slow and too large) * #1979 (Location alerts widget crashes intermittently) * #1980 (Using the wrong Radius dictionary file can cause servicemon to eat all available system memory and hang) * #1984 (Blank sysnames should not be allowed) + #1985 (Disallow blank sysnames) * #1990 (Make type changes immediately when unknown types are encountered) * #2004 ([BUG] Interface browser shows wrong "last used" date) * #2009 (Ensure rooms require a location attribute also in the SQL schema) Please see the release notes [3] for more details. Happy NAVing everyone! Links ===== [1] https://github.com/UNINETT/nav/releases [2] https://nav.uninett.no/install-instructions/#debian [3] https://nav.uninett.no/doc/latest/release-notes.html#nav-5.0 -- Sincerely, Morten Brekkevold Uninett

2 1

Napalm
by Erik 31 Okt '19

31 Okt '19

Hi, I build a new NAV server based on 4.98 on Debian 10. I would love to have Napalm back under the hood, but can't find a working manual for it? This one does not work (anymore?): https://netbox.readthedocs.io/en/stable/installation/2-netbox/#napalm-autom… Help? Cheers Erik

2 1

DNS service check, UDP or TCP?
by Ingeborg Hellemo 24 Okt '19

24 Okt '19

The NAV service monitor lets you monitor DNS. You then get graphs for availability and response time. Does this measure UDP or TCP response time? --Ingeborg -- Ingeborg Østrem Hellemo -- ingeborg.hellemo(a)uit.no Dep. of Information Technology --- Univ. of Tromsø

2 1

Re: copy all data and settings to new NAV install
by Morten Brekkevold 09 Sep '19

09 Sep '19

On Thu, 5 Sep 2019 08:51:05 +0200 (CEST) <kempere(a)quakerchem.com> wrote: > Is there a good way to move all settings and data to a fresh NAV installation? Hi Erik, This sounds more like a user question than something relevant for the developer's list. Therefore, I'm copying the user's list. This is in the documentation [1]. You may also simply want to use PostgreSQL's `pg_dumpall` program, as mentioned on that page. [1] https://nav.uninett.no/doc/latest/howto/migrate-data.html -- Morten Brekkevold Uninett

1 0

Announcement: NAV 4.9.8 released
by Morten Brekkevold 22 Aug '19

22 Aug '19

The eighth maintenance release of the 4.9 series of NAV is now out! The source code is available for download at GitHub [1]. New packages for Debian 9/10 (Stretch/Buster) are available in our APT repository [2] as usual. The Debian packages for NAV 4.9 have been rebuilt using dh-virtualenv, which means that most of the Python dependencies are now embedded into the packages themselves. If you have previously added a priority apt pin for packages from apt.uninett.no, you may now remove it, as there are no longer any other packages needed from that repository to run NAV. Please also be extra aware of config file changes. Look out for `*.dpkg-dist` files in /etc/nav and make sure to update your running config. The virtual appliance is currently being updated at the time of this writing, and will be uploaded soon. Changes ======= Fixed GitHub issues in this release: * #1753 (SNMP-less servers are no longer connected in the NAV topology) * #1941 (Interface information pop-ups in the status widget tends to hang) * #1942 (get_mib() should be able to load MIB modules from outside the nav.smidumps package) * #1962 (Environment rack widget edit mode crashes if there are racks in rooms with non-ascii characters in their name) * #1964 (smsd crashes when discarding non-dispatchable messages with non-ASCII chars (or for users with non-ASCII chars in their name)) * #1972 (Ensure PostgreSQL unique constraints are consistently named) * #1973 (Stop explicitly installing pl/pgSQL during db init.) * #1975 (Unhandled ValueError in eventengine when snmptrapd posts invalid linkState events) * #1976 (Properly display sensor data scale on sensor details page.) * #1977 (Use Juniper 802.1X VLAN workaround in default configuration) Please see the release notes [3] for more details. Happy NAVing everyone! Links ===== [1] https://github.com/UNINETT/nav/releases [2] https://nav.uninett.no/install-instructions/#debian [3] https://nav.uninett.no/doc/latest/release-notes.html#nav-4-9 -- Sincerely, Morten Brekkevold Uninett

1 0

Changing VLAN / ports on Juniper EX
by Jean Benoit 20 Aug '19

20 Aug '19

Hello, We are looking for a solution to manage local networks. Our goal is to recommend a tool to local net admins. Most of our switches are Juniper EX, as cisco and HP switches are phased out. Our current tool, Netmagis, is slow to evolve on the network configuration side (we have not enough time to develop it). The network admin in one of our Faculty is currently testing Nav. He seems satisfied so far, except for one thing : the impossibility to set a VLAN on a port on Juniper through the "Port Admin" feature. Do you have any plan to allow VLAN modification on Juniper ? Thanks for your answer. -- Jean

2 1

Announcement: NAV 4.9.7 packaged for Debian 10 (Buster)
by Morten Brekkevold 01 Aug '19

01 Aug '19

Hi everyone, this is a two-fold announcement: 1. We have, as of today, published a NAV 4.9.7 package for Debian 10 (Buster) in our regular APT repository [1]. 2. As previously mentioned, we are now discontinuing support for the Debian 8 (Jessie) line of NAV packages. There will be no new updates for this outdated platform from our side. There is, however, one caveat to using the NAV package on Debian 10: If you want to serve both the NAV web UI and Graphite-web from the same server, you cannot achieve this on Debian 10 using the regular Apache + mod_wsgi method for both applications. Debian 10 ships with a graphite-web package that runs on Python 3, while NAV 4.9 does not support Python 3 (we expect the next feature release to run on Python 3). mod_wsgi cannot be made to serve both Python versions on the same Apache server - you will have to select a Python-version specific mod_wsgi package. For this reason, the virtual appliance has not yet been updated to Debian 10. For our production deployments, we serve up NAV and Graphite-web using a uWSGI application server, and use Apache + *mod_uwsgi* as a front to provide TLS and serving of static file resources. This works fine on Debian 10, as each uWSGI application instance is an independent process. I suspect I'll be working on updating the appliance based on our production deployment configs of uWSGI. Hopefully, we can hopefully provide some config examples soon, for those who are interested in building their own deployments (of course, if you are already deploying Graphite on a separate server, this is a non-issue for you). [1] https://nav.uninett.no/install-instructions/#debian -- mvh Morten Brekkevold Uninett

1 1

New Install Issues
by Brian Mock 31 Jul '19

31 Jul '19

Hello, We are currently trying to set up a new installation of NAV (4.9.7). I have imported all of our devices and locations but am experiencing some issues. Some of our devices have interfaces that are showing wildly inaccurate data. It's mostly on any ten gig interfaces but also on a few gig interfaces but they're showing up to 15Tbps of traffic when in reality they're pushing far less than that and the graphs are very broken (see attached screenshots). Most ports on the same devices report properly so it's just a few isolated interfaces. The other issue we're running into is devices not showing linked to their neighbors. I tried working through the troubleshooting steps in the docs but the devices don't show up under unrecognized neighbors. On the devices however they show up in the ARP/CAM tables. We do have some links that don't support CDP but NAV should still be building these neighbor relationships through the ARP/CAM tables correct? Thanks for any assistance that you can provide! Regards, Brian Mock Unwired Broadband

2 3

Getting the ARP/Neighbors from Cisco ASA to NAV?
by Martin Burman 24 Jul '19

24 Jul '19

Hi We successfully use NAV for keeping track of devices but more often to find out which switchport a specific computer is attached to, either by searching for an IP address or a MAC address and it works great. We also have a lot of users directly attached to Cisco ASAs and these boxes does not give away their ARP/Neighbor cache via SNMP. The obvious first question is: has anyone successfully solved this already? Otherwise a "sh arp/sh ipv6 neigh" gives a parseable output and I assume this is the way to go via Expect or similar: Asa> sh ipv6 neighbor IPv6 Address Age Link-layer Addr State Interface fe80::6db1:8675:5895:8db1 423 001d.d8b7.1ce3 STALE ifname Is there a safe way to import this kind of data to NAV? Or any documentation hints that kicks me into the appropriate direction? I assume there are logic that updates existing mac addresses and creating new ones when needed and such and I don't want to ruin our installation. The second idea is to run some homebrewed snmp server that runs the "sh arp" in the back end and formats the output like a L3 switch would do, if that's the suggested way to go I would appreciate a decent oneliner with snmpwalk or similar that runs against a Cisco L3 switch (6500 or 6800) so I can compare the output I need to create. Thanks in advance and thanks a lot for a great piece of software! Martin Burman ---------- Göteborgs universitet IT-enheten +46 766-18 5982

2 1

NAV and Juniper virtual chassis
by Djuro Garvanovic 24 Jul '19

24 Jul '19

Hi I recently stumbled on your product while I was searching for a good network monitoring tool. So I started a POC with Debian package but got some problems with Graphite, and had to reverted to the appliance. Now that its running, I’m impressed over functions built in, especially the network auto mapping. But there is one thing I don’t know how to handle. We are mainly using Juniper EX4200, EX 3200 and EX2200 switches. Our Juniper EX4200 switches are set up as virtual chassis (stacked switches), and they all have the same ip address. The problem is that the switches, although they are in the same chassis, they are placed in different “rooms” a ring around our campus acting as distribution switches. Se config: dgc@MMACOR01> show virtual-chassis Virtual Chassis ID: b0c6.9a6f.7500 Virtual Chassis Mode: Enabled Mstr Mixed Neighbor List Member ID Status Serial No Model prio Role Mode ID Interface 0 (FPC 0) Prsnt BM0209493141 ex4200-24t 250 Master* N 1 vcp-0 7 vcp-255/1/1 1 vcp-1 1 (FPC 1) Prsnt BM0209505602 ex4200-24t 140 Linecard N 0 vcp-0 4 vcp-255/1/1 0 vcp-1 2 (FPC 2) Prsnt BR0218490227 ex4200-24f 130 Linecard N 3 vcp-0 5 vcp-255/1/2 3 vcp-1 3 (FPC 3) Prsnt BR0218490131 ex4200-24f 120 Linecard N 2 vcp-0 9 vcp-255/1/2 2 vcp-1 4 (FPC 4) Prsnt BM0209493198 ex4200-24t 210 Backup N 5 vcp-0 1 vcp-255/1/1 5 vcp-1 5 (FPC 5) Prsnt BM0209485774 ex4200-24t 200 Linecard N 4 vcp-0 2 vcp-255/1/1 4 vcp-1 6 (FPC 6) Prsnt BR0209485019 ex4200-24f 190 Linecard N 7 vcp-0 8 vcp-255/1/1 7 vcp-1 7 (FPC 7) Prsnt BR0209484982 ex4200-24f 180 Linecard N 6 vcp-0 0 vcp-255/1/1 6 vcp-1 8 (FPC 8) Prsnt BR0213155003 ex4200-24f 170 Linecard N 9 vcp-0 6 vcp-255/1/1 9 vcp-1 9 (FPC 9) Prsnt BR0214421949 ex4200-24f 160 Linecard N 8 vcp-0 3 vcp-255/1/1 8 vcp-1 Member ID for next new member: None {master:0} dgc@MMACOR01> And picture [cid:image002.png@01D52A71.D4537D10] It looks like I only can add a ip address once Is there a way to add the other MMACOR01 switches so I can see them, even if they have the same IP? Vänliga hälsningar / Best regards Djuro Garvanovic IT Infrastruktur Nätverk och kommunikation +46 40 323710 djuro.garvanovic(a)pagen.se<mailto:dgc@pagen.se> http://www.linkedin.com/in/djuro Pågen AB, Box 8143, SE-200 41 Malmö Besöksadress: Kopparbergsgatan 19, Grind G5 www.pagen.se<http://www.pagen.se/> www.facebook.com/pagensverige<http://www.facebook.com/pagensverige> [cid:image001.png@01D0B4AF.B24D9610]

2 1

Announcement: NAV 4.9.7 released
by Morten Brekkevold 07 Jun '19

07 Jun '19

The seventh maintenance release of the 4.9 series of NAV is now out! The source code is available for download at GitHub [1]. New packages for Debian 8/9 (Jessie/Stretch) are available in our APT repository [2] as usual. Please be advised that the Debian 8 package will be discontinued soon The Debian packages for NAV 4.9 have been rebuilt using dh-virtualenv, which means that most of the Python dependencies are now embedded into the packages themselves. If you have previously added a priority apt pin for packages from apt.uninett.no, you may now remove it, as there are no longer any other packages needed from that repository to run NAV. Please also be extra aware of config file changes. Look out for `*.dpkg-dist` files in /etc/nav and make sure to update your running config. The virtual appliance is currently being updated at the time of this writing, and will be uploaded soon. Changes ======= Fixed GitHub issues in this release: * #1882 (Invalid VLANs are generated from Juniper switches) * #1920 (Provide a hook for adding extra information in the What-If tab in the IP Device Info page) * #1946 (Vlans are categorized as linknets on Cisco Nexus with HSRP) * #1953 (Adding new public filter in Alert Profiles fails) * #1958 (NAV creates Graphite metrics with illegal characters in name) * #1960 (Add option to control user administrator privileges from LDAP) Please see the release notes [3] for more details. Happy NAVing everyone! Links ===== [1] https://github.com/UNINETT/nav/releases [2] https://nav.uninett.no/install-instructions/#debian [3] https://nav.uninett.no/doc/latest/release-notes.html#nav-4-9 -- mvh Morten Brekkevold Uninett

1 0

Announcement: NAV 4.9.6 released
by Morten Brekkevold 23 Mai '19

23 Mai '19

The sixth maintenance release of the 4.9 series of NAV is now out! The source code is available for download at GitHub [1]. New packages for Debian 8/9 (Jessie/Stretch) are available in our APT repository [2] as usual. The Debian packages for NAV 4.9 have been rebuilt using dh-virtualenv, which means that most of the Python dependencies are now embedded into the packages themselves. If you have previously added a priority apt pin for packages from apt.uninett.no, you may now remove it, as there are no longer any other packages needed from that repository to run NAV. Please also be extra aware of config file changes. Look out for `*.dpkg-dist` files in /etc/nav and make sure to update your running config. The virtual appliance is currently being updated at the time of this writing, and will be uploaded soon. Changes ======= Fixed GitHub issues in this release: * #1782 (ipdevpoll snmpcheck algorithm no longer works as expected) + #1952 ((snmpcheck) Store up/down state in NetboxInfo, so we can properly sen…) * #1931 (Support for HPE Metered PDUs) + #1933 (Add support for HPE metered PDUs) * #1935 (The VLAN dropdowns in PortAdmin needs to show the description in addition to the id, if any) + #1955 (Show net ident for vlans in the portadmin vlan dropdown box) * #1944 (Sensor links in Environment Rack navlet does not work) * #1948 (Verify LDAP entitlements) Please see the release notes [3] for more details. Happy NAVing everyone! Links ===== [1] https://github.com/UNINETT/nav/releases [2] https://nav.uninett.no/install-instructions/#debian [3] https://nav.uninett.no/doc/latest/release-notes.html#nav-4-9 -- mvh Morten Brekkevold Uninett

1 0

Power supply unknown
by Ingeborg Hellemo 14 Mai '19

14 Mai '19

NAV 4.8.6 We have a Cisco catalyst switch with a broken power supply. After changing the power supply NAV shows Status "Unknown" in the /#!sensors page. The ipdevpoll jobs runs without errors. Where shall I look? --Ingeborg -- Ingeborg Østrem Hellemo -- ingeborg.hellemo(a)uit.no Dep. of Information Technology --- Univ. of Tromsø

3 4

Announcement: NAV 4.9.5 released
by Morten Brekkevold 02 Mai '19

02 Mai '19

The fifth maintenance release of the 4.9 series of NAV is now out! The source code is available for download at GitHub [1]. New packages for Debian 8/9 (Jessie/Stretch) are available in our APT repository [2] as usual. The Debian packages for NAV 4.9 have been rebuilt using dh-virtualenv, which means that most of the Python dependencies are now embedded into the packages themselves. If you have previously added a priority apt pin for packages from apt.uninett.no, you may now remove it, as there are no longer any other packages needed from that repository to run NAV. Please also be extra aware of config file changes. Look out for `*.dpkg-dist` files in /etc/nav and make sure to update your running config. The virtual appliance is currently being updated at the time of this writing, and will be uploaded soon. Changes ======= Fixed GitHub issues in this release: * #1890 (Temperature gauges do not render if multiple threshold rules apply to it) + #1921 (Handle arbitrary number of thresholds for a given sensor) * #1902 (Sensor widgets should hyperlink to sensor's page view, not IP Device's page view) * #1903 (Topology missing for LLDP-enabled Alcatel switches) * #1906 ("Cisco chassis/module serial numbers decoded" report crashes when filtering) * #1907 (servicemon DnsChecker fails when DNS server doesn't have a matching record) * #1916 (UninettMailDispatcher does not work under NAV 4.9) * #1917 (snmptrapd needs to log more details about received traps) * #1923 (ENTITY-MIB implementation can no longer resolve physical device classes properly) + #1924 (Support cross-MIB type definitions in MibRetrievers) Please see the release notes [3] for more details. Happy NAVing everyone! Links ===== [1] https://github.com/UNINETT/nav/releases [2] https://nav.uninett.no/install-instructions/#debian [3] https://nav.uninett.no/doc/latest/release-notes.html#nav-4-9 -- mvh Morten Brekkevold Uninett

1 0

Fwd: Network Interfaces Search parameters
by BERGELIN SABADELL, IVAR-ERIC 05 Apr '19

05 Apr '19

Hello, This is Ivar Bergelin and I work at the IT department of Pompeu Fabra University in Barcelona. We use your software NAV to manage the whole network. I write to you because I have a question about the search parameters in the Netbox interfaces tab. [image: imagen.png] There is a button called "About the search" which contains the following information about search parameters: [image: imagen.png] [image: imagen.png] Is there's a place where I can find all the search parameters? In the image shows only few search examples but I would like to know all of them. I could'n find anything in the NAV's documentation. Thanks in advance. -- *Ivar Bergelin* Tècnic de suport a la docència Unitat d'Informàtica del Campus del Poblenou Roc Boronat 138 | 08018 - Barcelona [Tel.] (+34) 93 542 23 58 http://www.upf.edu

2 1

VM or Appliance forcasting
by ken.livesey＠subzero.com 28 Mar '19

28 Mar '19

Greetings, I am looking for assistance in determining respective NAV VM system parameters for managing 800-1000 Network devices across two data centers and 30 sites. Most of the network devices are Cisco and all sites are connected with high- speed and low latent connections. Please let me know if any additional information would be helpful. Thanks for your help, Ken...

3 3

Re: VM or Appliance forcasting
by Morten Brekkevold 28 Mar '19

28 Mar '19

On Wed, 27 Mar 2019 14:20:11 +0100 <ken.livesey(a)subzero.com> wrote: > Thanks for your feedback! Thanks for yours. I'm Cc-ing the mailing list once again, but leaving out most of your response here. > P.S. Any idea when SNMP V3 might be supported? No, but we're making progress on replacing the SNMP configuration attributes that are hardwired into the Netbox (IP Device) model with a more flexible management profile system. This will be useful when implementing NETCONF and/or RESTCONF, which is our current goal, but this can also be used to implement proper SNMPv3 support (since you will be able to store more than just community strings). I'm given to understand that the University of Linköping may be interested in developing support for SNMPv3, once management profiles hit the master branch. I'm also copying Pär Stolpe from LiU, so that he might comment (if he wants to) :-) -- mvh Morten Brekkevold Uninett

1 0

Announcement: NAV 4.9.4 released
by Morten Brekkevold 28 Mar '19

28 Mar '19

The fourth maintenance release of the 4.9 series of NAV is now out! The source code is available for download at GitHub [1]. New packages for Debian 8/9 (Jessie/Stretch) are available in our APT repository [2] as usual. The Debian packages for NAV 4.9 have been rebuilt using dh-virtualenv, which means that most of the Python dependencies are now embedded into the packages themselves. If you have previously added a priority apt pin for packages from apt.uninett.no, you may now remove it, as there are no longer any other packages needed from that repository to run NAV. Please also be extra aware of config file changes. Look out for `*.dpkg-dist` files in /etc/nav and make sure to update your running config. The virtual appliance is currently being updated at the time of this writing, and will be uploaded soon. Changes ======= NB: This release introduces a new dependency to py2-ipaddress==3.4.1 Fixed GitHub issues in this release: * #1639 (Not all NAV programs respect TIME_ZONE from nav.conf) * #1762 (navdump drops function-data) * #1788 (Deleting an alert profile subscription that has queued alerts will cause alertengine to process all those alerts as if they were new ones on the queue. ) * #1885 (LDAP authentication against Microsoft AD using suffix bind is broken in NAV 4.9) * #1894 (Terminals that don't support colors cause nav start/stop commands to crash) * #1895 (Verify nav.conf values as part of nav start) * #1896 (UnicodeEncodeError when LDAP user with non-ASCII characters in DN logs in) Please see the release notes [4] for more details. Happy NAVing everyone! Links ===== [1] https://github.com/UNINETT/nav/releases [2] https://nav.uninett.no/install-instructions/#debian [3] https://github.com/UNINETT/nav/issues [4] https://nav.uninett.no/doc/latest/release-notes.html#nav-4-9 -- mvh Morten Brekkevold Uninett

1 0

Re: Re: NAV docs and papers
by Eduardo Hartmann 26 Mar '19

26 Mar '19

1 0

FW: Unused port tracking / alert
by Daniel Gryzbon 25 Mar '19

25 Mar '19

Good day, We are now testing your product and we want to know, if is possible to track or be informed if some interface is not used for some time - e.q. no MAC address visible for long time or interface is down and not administrative down for long time. For example i try to configure alert profile with matchfield value.id cam.end_time with filter not equals 9999-12-31 23:59:59.999999 and added to filter group G01:All alerts with Add operation but no alert appeared on status tab. Is possible to somehow monitor it? Thank for your help Best regards [Hyundai Autoever_Ma_07012017] Daniel Gryžbon [New motto Hyundai blue] Network Specialist Hyundai AutoEver Europe GmbH, organizační složka Hyundai 700/1, 739 51 Nižní Lhoty Tel: +420 596 14 1755 E-Mail: daniel.gryzbon(a)hyundai-motor.cz<mailto:daniel.gryzbon@hyundai-motor.cz> Website: www.hyundai-autoever.eu<http://www.hyundai-autoever.eu/>

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Nav-users