Nav-users

nav-users@lister.sikt.no

3 participants
1384 discussions

Ordering of links in widget
by Ingeborg Hellemo 30 Nov '20

30 Nov '20

The Links widget shows links from the file webfront/nav-links.conf How are these links ordered in the widget? They are neither shown on the order they appear in the config file nor alphabetically. --Ingeborg -- Ingeborg Østrem Hellemo -- ingeborg.hellemo(a)uit.no Dep. of Information Technology --- Univ. of Tromsø

2 1

Adding a new device to NAV
by Simon Brown 23 Nov '20

23 Nov '20

Hi, I've added a few devices to a test NAV instance and I'm wondering how I add support for them. At Home / IP Device info / Device instance Only the basic device info is there. I have the MIBs for the devices, what should my next step be? Simon

3 3

No switch Type Name when using RW SNMP Profile
by Tal Bar-Or 17 Nov '20

17 Nov '20

Hello, We have issues with NAV , using same system for several years already , since SNMP profile introduced the switch losse its Switch Type result we cannot manage it . and any new switch added with RW profile is not able to be scanned for ports and config and etc... as soon as we uncheck the RW checkbox , switch is scanned for its ports and config Please advice Thanks -- Tal Bar-or

2 1

Announcement: NAV 5.0.8 released
by Morten Brekkevold 23 Okt '20

23 Okt '20

The eighth 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 reached 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 ======= This release fixes a single regression introduced by NAV 5.0.7: * #2196 ([BUG] ipdevpoll topo job crashes with a PostgreSQL operational error, due to an index size error) 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

Announcement: NAV 5.0.7 released
by Morten Brekkevold 15 Okt '20

15 Okt '20

The seventh 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 reached 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: * #2106 ([BUG] Cached LLDP/CDP records are never re-evaluated) * #2182 ([BUG] Delayed delivery alert subscriptions crash Alert Engine with a NameError) * #2184 ([BUG] Unrecognized Neighbors are never removed when all neighbors have been identified) * #2187 ([BUG] Locked accounts with a NULL value for a password cannot be edited) * #2188 ([BUG] Useradmin user listing becomes excruciatingly slow when many users have password issues) * #2189 ([BUG] Regression - ftp service check in 5.X does not work) 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

RE: Extra info in alertmails
by René Romijn 15 Sep '20

15 Sep '20

Oeps.. you are right 😊 Question still stands though. Is it possible to add more information in the alertsmails. -----Oorspronkelijk bericht----- Van: Morten Brekkevold <morten.brekkevold(a)uninett.no> Verzonden: dinsdag 15 september 2020 15:15 Aan: René Romijn <Rene.Romijn(a)tabsholland.nl> Onderwerp: Re: Extra info in alertmails On Mon, 14 Sep 2020 07:32:05 +0000 René Romijn <Rene.Romijn(a)tabsholland.nl> wrote: > Is it possible to add some more information in the alertmails? For example add Room? Hi René, I suspect you meant to send this to nav-users(a)uninett.no, not nav-users-request(a)uninett.no? -- sincerely, Morten Brekkevold Uninett

2 2

PoE graphs aren't display
by Biselx Nicolas 15 Sep '20

15 Sep '20

Hello, I can't understand why the gauges stay at 0 on the PoE page of a device: For example, If I click on PoE Group 2, I see port with the message delivering power in class4 But nothing appears in the graph either. Do the graphs have to be activated somewhere? Thank you in advance for your help Nicolas Biselx

2 7

Re: Seed Database IP having issues detect device
by Morten Brekkevold 28 Aug '20

28 Aug '20

On Sat, 22 Aug 2020 13:49:22 +0300 Tal Bar-Or <tbaror(a)gmail.com> wrote: > we added devices one by one manually , using a complete new installation. > Thanks > [image: 2020-08-22_13-40-06.jpg] > [image: 2020-08-22_13-48-00.jpg] Ok. I would prefer it if you kept the discussion on-list (unless you wish to post sensitive information in private), so I'm copying the list again in my reply. So, you background processes appear to be running. 1. Has NAV registered any alerts on your affected devices? 2. What are the job statuses of the affected devices (see their ipdevinfo pages)? 3. What does ipdevpoll.log have to say about the affected devices? -- sincerely, Morten Brekkevold Uninett

1 0

Announcement: NAV 5.0.6 released
by Morten Brekkevold 27 Aug '20

27 Aug '20

The sixth 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 reached 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: * #2144 (Prevent ipdevinfo from crashing on weird device names) * #2149 (Inventory failing on DLink DGS-1100 : 'TypeError: argument of type 'int' is not iterable') * #2150 ([BUG] Interface down is causing widget 'status' to display 'Could not load widget' due to HTTP 500) * #2165 ([BUG] Delayed delivery alert subscriptions in single time period alert profiles are never sent) * #2167 (Fix potential typecast issue with SQL migration to NAV 5.0) * #2169 ([BUG] macwatch.py crashes when logging notifications about found MAC addresses) * #2170 ([BUG] Alertengine stops dispatching Slack notifications indefinitely if Slack complains of too many requests) * #2171 (Warn about user accounts that have issues with their passwords) * #2172 (Prevent login/password changes to default account) * #2177 ([BUG] Attempting to move IP devices to another room crashes SeedDB) * #2178 ([BUG] PDU widget stops displaying properly if room is deleted) * #2179 ([BUG] UPS widget does not display properly if UPS is deleted from NAV) * #2180 ([BUG] Entering invalid dates in Device History search form causes crash) 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

Routerports?
by Jan Astrup 19 Aug '20

19 Aug '20

Hello, I'm new to the nav-system, but i must say i like it alot. However, I'm having issues with a few devices, primarily ubiquiti and cambium wireless access points and CPE's. None of their ports come up as router ports, which in my case i think would be needed in order to get all my links visible on the geomap(?). Also, none of the ports are "patchable", so I can't create patches and assign them to those devices. Any pointers in where i should start looking in order to get this issue fixed? Best regards, Jan Astrup

2 1

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