Nav-users

nav-users@lister.sikt.no

1379 discussions

Announcement: NAV 5.3.0 released
by Morten Brekkevold 04 Mar '22

04 Mar '22

The initial feature release of the 5.3 series of NAV is now out! The source code is available for download at GitHub [1]. A new package for Debian 10 (Buster) is available in our APT repository [2] as usual. Packages for Debian 11 (Bullseye) have not been built yet. Please 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 as soon as possible. Changes ======= On January 1st 2022, Uninett, NSD and Unit (all entities owned by the Norwegian government) were merged into the new governmental agency *Sikt - Norwegian Agency for Shared Services in Education and Research*. This marks the first release of NAV under the new name. User-visible features and improvements: The main reason for this new feature release is to ensure NAV is compatible with Python 3.9 (which is the default Python version on the current Debian stable distro, Bullseye). Features that were already lurking in the pipeline are: * #2245 (Link to room details page from SeedDB room edit page) * #2274 (Hidden attributes for devices) * #2323 (Completely hide all attributes starting with "__") * #2309 (Support a report.conf.d/ style config directory for reports) * #2311 (Wishlist: Info about locations visible via /report/location) Other fixed GitHub issues in this release: * #2280 (Only ethernetCsmacd interfaces are shown in the room viewer) * #2310 ([BUG] snmptrapd plugins crash when posting events in NAV 5.2) * #2315 (Properly upgrade to Django 2.2) * #2316 (Upgrade dependencies that will need a newer version to run on Django 3.2 or later) * #2317 (Upgrade Django to 3.2) * #2321 (Also list local conf reports in report widget) * #2324 ([BUG] Example severity rules distributed with NAV 5.2.1 do not actually work) * #2328 (Remove "no access" message from login page during normal login) * #2329 (Upgrade to dnspython 2.1) * #2341 (Warn when database config isn't readable) * #2352 (Fix Python 3.9 compatibility) * #2353 (Document the name change from Uninett to Sikt) * #2355 (Add Sikt to About page, copyrights and graphical profile) 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.readthedocs.io/en/latest/release-notes.html#nav-5-3 -- Sincerely, Morten Brekkevold Sikt – Norwegian Agency for Shared Services in Education and Research

1 2

NAV - Palo Alto ARP table import for Machine Tracer
by Mehmet E. Şahin (BAŞKANLIK-BİDB) 28 Jan '22

28 Jan '22

Hi Everyone, We have NAV to monitor network switches and also Palo Alto Firewall. We can only use Palo Alto api to query its arp table as it does not support it over snmp. Could there be a way to import those ARP records from palo alto firewall to NAV periodically ? We are asking this because the machine tracer tool on NAV is very useful and would be great if those arp recods from palo alto to be imported to the NAV. Best Regards Mehmet Emin Şahin

4 6

Power Distribution MIBs
by Simon Brown 11 Jan '22

11 Jan '22

Hello, Nav has a Power distribution equipment category. Is there any guidance on what is supported by default? Is there a standard MIB lik IF-MIB or is this all vendor specific? Thanks, Simon -- Simon Brown System Engineer EISCAT Scientific Association P. O. Box 812, SE-981 28 Kiruna, Sweden simon.brown(a)eiscat.se

1 0

Snmp V3
by Marco BARBIERI 21 Des '21

21 Des '21

Hi, is there any news about snmp v3 support in NAV? I know it's something that has already been asked, but as far as i can see it isn't supported yet, i'm i wrong? Best regards, Marco Barbieri, -- -- Marco Barbieri - Si.RS Reti e Sistemi - 0592058003 - 3316213040

2 3

How to add sensorgateway probes to nav ?
by FOUR Ludovic (EXT) 17 Des '21

17 Des '21

Hello, I'm using NAV 5.2 and I would like to add a couple of Serverscheck temperature probes that monitor our network racks Product reference is detailed here : https://serverscheck.com/sensors/baseunit.asp I'm trying to add the probes by following the adding AKCP probe tutorial. I made this : 1/ Translate the sensorgateway.mib into SERVERSCHECK-MIB.py with smidump command 2/ Copy the python file to folder /opt/venvs/nav/lib/python3.7/site-packages/nav/smidumps There's a ServersCheck module used in MIB file, that i'm using to interrogate directly the probe I can get the temperature value with snmpwalk -c community -v1|2c <IP of the probe> ServersCheck:sensor1Name.0 If I translate into OID with snmptranslate command, I get this OID .1.3.6.1.4.1.17095.3.2.0 3/ Create the file serverscheck_mib.py with those lines to /opt/venvs/nav/lib/python3.7/site-packages/nav/mibs from twisted.internet import defer from nav.mibs import reduce_index from nav.mibs.mibretriever import MibRetriever from nav.smidumps import get_mib class ServerCheckMib(MibRetriever): mib = get_mib('SERVERSCHECK-MIB') @defer.inlineCallbacks def get_all_sensors(self): result = [ { 'oid': '.1.3.6.1.4.1.17095.3.2.0', 'unit_of_measurement': 'celsius', 'precision': 1, 'scale': None, 'description': "Ambient temperature", 'name': "Ambient temperature", 'internal_name': "Ambient temperature", 'mib': 'SERVERSCHECK-MIB', } ] defer.returnValue(result) - Add the following lines to /etc/nav/ipdevpoll.conf (note sure of iana code of serverscheck manufacturer. should be 25432) 25432 = ServersCheckMib SERVERSCHECK = SERVERSCHECK-MIB At this point i'm stuck (ipdevpoll log empty) and I still can't get sensors readings into NAV and it doesn't recognize the probe type into collected info of the seedDB probe page Any ideas of what I'm doing wrong ? Regards, Ludovic FOUR SSI DR10 CNRS - Support Infoprox Pharma 74, route du Rhin F-67401 Illkirch-Graffenstaden Tel: 03 68 85 43 11 Contact support: support-pharma(a)unistra.fr Tel: 03.68.85.42.50 - Mobile: 06.11.69.03.65

2 1

advice on upgrading nav 4.9.5 on debian 8.11 to nav 5.3 ideally debian 11
by Mischa Diehm 10 Des '21

10 Des '21

Hei all, we have a larger NAV setup with a bit more than 1000 Cisco Switches and use quite a lot of the features supported in NAV. Since our setup is a bit dusty we plan to upgrade (nav 4.9.5 on debian 8.11 to nav 5.3 ideally debian 11). I wanted to ask for your advice on the upgrade paths possible. We use a external db server that hosts the postgres db. Requirements/Whishes: - it would be great to keep the devices history and graphs so a simple dump.py and reinstall would be a bit lossy - it would be nice to start with a fresh installed debian 11. Is there a good/preferred path that we could follow? Thanks for any ideas and suggestions, Mischa p.s.: Any ideas / timeframe when nav will release debian 11 packages? -- narrowin.ch /\ network & security

3 2

wsgi throwing errors when talking with ldap-server
by Ingeborg Hellemo 04 Nov '21

04 Nov '21

NAV 5.1.2 I had to upgrade the OS on my NAV-box, and hence all the software depending on libraries. After this I have wsgi throwing errors on me. Not all the time. Users local to NAV can log in just fine, but users who authenticate via ldap gets the error. I have tried to reinstall psycopg2. I have also switched from installing mod_wsgi from an OS-package to using pip Apache/2.4.51 (FreeBSD) OpenSSL/1.1.1l mod_wsgi/4.9.0 Python/3.7 The error is not connected to communication with the ldap-server (AD) Output with debug=true in webfront.conf ldap_create ldap_url_parse_ext(ldaps://XXXX.ad.uit.no:636) ldap_sasl_bind ldap_send_initial_request ldap_new_connection 1 1 0 ldap_int_open_connection ldap_connect_to_host: TCP XXXX.ad.uit.no:636 ldap_new_socket: 18 ldap_prepare_socket: 18 ldap_connect_to_host: Trying 129.242.xx.zzz:636 ldap_pvt_connect: fd: 18 tm: -1 async: 0 attempting to connect: connect success [Tue Nov 02 08:53:35.941429 2021] [wsgi:error] [pid 34769] [client 129.242.14.106:49209] Truncated or oversized response headers received from daemon process 'NAV': /usr/local/lib/python3.7/site-packages/nav/wsgi.py, referer: https://nav.uit.no/index/login/?origin=/&noaccess [Tue Nov 02 08:53:35.977367 2021] [core:notice] [pid 34758] AH00052: child pid 34760 exit signal Segmentation fault (11) Any ideas? --Ingeborg -- Ingeborg Østrem Hellemo -- ingeborg.hellemo(a)uit.no Dep. of Information Technology --- Univ. of Tromsø

1 1

Announcement: NAV 5.2.1 released
by Morten Brekkevold 23 Sep '21

23 Sep '21

The first maintenance release of the 5.2 series of NAV is now out! This release fixes a particularly nasty regression bug in pping, which would prevent you from being alerted about boxDown events. If you are already running 5.2.0, we recommend that you upgrade as soon as possible. The source code is available for download at GitHub [1]. A new package for Debian 10 (Buster) is available in our APT repository [2] as usual. Packages for Debian 11 (Bullseye) have not been built yet. Please 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 has been updated. Changes ======= * #2304 (Display alert severity values in the event/alert details page) * #2306 ([BUG] pping is unable to report unreachable devices in NAV 5.2.0) * #2308 ([BUG] Alert Profile severity filters that ship with NAV are outdated) 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.readthedocs.io/en/latest/release-notes.html#nav-5-2 -- Sincerely, Morten Brekkevold Uninett

1 0

Announcement: NAV 5.2.0 released
by Morten Brekkevold 16 Sep '21

16 Sep '21

The initial feature release of the 5.2 series of NAV is now out! The source code is available for download at GitHub [1]. A new package for Debian 10 (Buster) is available in our APT repository [2] as usual. Packages for Debian 11 (Bullseye) have not been built yet. Please 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 has been updated. Changes ======= User-visible features and improvements: * #1928 (Document 802.1X support of PortAdmin for end users) * #2289 (Add config option to disallow editing of uplinks and downlinks in PortAdmin) * #2295 (Redefine alert severity levels and make them configurable) * #2297 (Document the event and alert type hierarchy) Fixed GitHub issues in this release: * #2296 ([BUG] Portadmin save API incorrectly returns 500 error where 400 is appropriate) * #2298 ([BUG] PortAdmin RpcError on JunOS 20 and newer) 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.readthedocs.io/en/latest/release-notes.html#nav-5-2 -- Sincerely, Morten Brekkevold Uninett

1 0

LDAP / ActiveDirectory issues
by Andrea Verni 02 Sep '21

02 Sep '21

Hi, I deployed NAV 5.14 on a debian 10 VM and configured LDAP authentication as from https://nav.readthedocs.io/en/latest/reference/ldap.html?highlight=ldap - however if using LDAP the login works randomly (need to try 2 to 5/6 time to login) while LDAPS never works. I did a test with ldapsearch on the same VM using both LDAP and LDAPS and both works so no issues with basedn or manager credentials nor with certificates. Is anyone else experiencing the same issue ? Other LDAPS based applications we use internally sucessfully connect to same AD servers. Anyone can help maybe? Thanks! Andrea

2 2

← Newer
1
...
7
8
9
10
11
12
13
...
138
Older →

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