Nav-users

nav-users@lister.sikt.no

2 participants
1380 discussions

NAV - Palo Alto Plugin: MAC Records Keep Expiring
by Mehmet E. Şahin (BAŞKANLIK-BİDB) 10 Des '24

10 Des '24

Hi Everyone, We started using the new Palo Alto plugin with excitement. It successfully retrieves the ARP table from the Palo Alto firewall as XML every 20 minutes. However, for some reason, while reading the ARP table from Palo Alto, the records are constantly expiring and being added again. This does not occur for the ARP records received via SNMP. Has anyone observed this situation? In the example below, the IP address 192.168.0.250 belongs to a server. There is no disconnection, but for some reason, the MAC tracker records show that a re-connection is happening every 20 minutes. (BTW - our nav version is the latest (5.10.2).) Best Regards Mehmet E. ŞAHİN

3 5

During upgrade I get "The automatic update script failed to update database"
by Davide Miccone 12 Nov '24

12 Nov '24

This is not the first time that happen. Upgrading to the latest 5.11 (from 5.9) I get error at the end. Inspecting nav DB it seems that DB has been updated. To check that DB has been updated I read the content of file cat sc.05.11.0001.sql, cat sc.05.11.0002.sql and check the DB for the presence of the table "manage.oui" and of the new records in the table "altertype". Below the error that I get: ===================== Automatic database update failed The automatic update script failed to update the database. Script output: could not connect to server: Connection refused Is the server running on host "localhost" (::1) and accepting TCP/IP connections on port 5432? could not connect to server: Connection refused Is the server running on host "localhost" (127.0.0.1) and accepting TCP/IP connections on port 5432?

2 1

Port description is not committed Cisco 3750X
by Davide Miccone 12 Nov '24

12 Nov '24

Cisco a C3750X-48. Cisco IOS Software, C3750E Software (C3750E-UNIVERSALK9-M), Version 15.2(4)E, RELEASE SOFTWARE (fc2) NAV 5.11.0 Port description is not written to switch configuration. Changes to vlan and enable/disable works Davide

2 1

Error in snmptrapd
by Ingeborg Hellemo 04 Nov '24

04 Nov '24

Was trying to use snmptrapd for the first time in years. Incoming traps generates this error: 2024-10-30 11:00:25,287 [ERROR] [zen.pynetsnmp.callback] Exception in _callback invalid input syntax for type inet: "None" LINE 1: ... LEFT JOIN gwportprefix USING (interfaceid) WHERE 'None' IN ... ^ Traceback (most recent call last): File "/usr/local/lib/python3.9/site-packages/pynetsnmp/netsnmp.py", line 464, in _callback sess.callback(pdu.contents) File "/usr/local/lib/python3.9/site-packages/nav/snmptrapd/agent_pynetsnmp.py ", line 221, in callback self._callback(addr, pdu) File "/usr/local/lib/python3.9/site-packages/nav/snmptrapd/agent_pynetsnmp.py ", line 130, in callback self._client_callback(trap) File "/usr/local/lib/python3.9/site-packages/nav/bin/snmptrapd.py", line 234, in trap_handler _log_trap_handle_result(handled_by, trap) File "/usr/local/lib/python3.9/site-packages/nav/bin/snmptrapd.py", line 239, in _log_trap_handle_result trap.netbox.sysname + ' ({})'.format(trap.agent) if trap.netbox else trap.agent File "/usr/local/lib/python3.9/site-packages/nav/snmptrapd/trap.py", line 87, in netbox setattr(self, '_netbox', self._lookup_agent()) File "/usr/local/lib/python3.9/site-packages/nav/snmptrapd/trap.py", line 67, in _lookup_agent cur.execute( psycopg2.errors.InvalidTextRepresentation: invalid input syntax for type inet: "None" LINE 1: ... LEFT JOIN gwportprefix USING (interfaceid) WHERE 'None' IN ... ^ 2024-10-30 11:02:07,171 [ERROR] [zen.pynetsnmp.callback] Exception in _callback current transaction is aborted, commands ignored until end of transaction block Traceback (most recent call last): File "/usr/local/lib/python3.9/site-packages/pynetsnmp/netsnmp.py", line 464, in _callback sess.callback(pdu.contents) File "/usr/local/lib/python3.9/site-packages/nav/snmptrapd/agent_pynetsnmp.py ", line 221, in callback self._callback(addr, pdu) File "/usr/local/lib/python3.9/site-packages/nav/snmptrapd/agent_pynetsnmp.py ", line 130, in callback self._client_callback(trap) File "/usr/local/lib/python3.9/site-packages/nav/bin/snmptrapd.py", line 207, in trap_handler connection = getConnection('default') File "/usr/local/lib/python3.9/site-packages/nav/db/__init__.py", line 170, in getConnection _connection_cache.invalidate() File "/usr/local/lib/python3.9/site-packages/nav/__init__.py", line 55, in invalidate if self[key].is_invalid(): File "/usr/local/lib/python3.9/site-packages/nav/db/__init__.py", line 57, in is_invalid if self.ping(): File "/usr/local/lib/python3.9/site-packages/nav/db/__init__.py", line 77, in ping cursor.execute('SELECT 1') psycopg2.errors.InFailedSqlTransaction: current transaction is aborted, commands ignored until end of transaction block The incoming traps does not have any corresponding handler (yet), but I was expecting the code to handle unknown traps without barfing. --Ingeborg -- Ingeborg Østrem Hellemo -- ingeborg.hellemo(a)uit.no Dep. of Information Technology --- Univ. of Tromsø

3 7

Re: Problem with build_sphinx
by Ingeborg Hellemo 04 Nov '24

04 Nov '24

(Morten forgot to Cc the list. I think he is struggling with som new shortcuts in his mailer.) > On Fri 01 Nov 2024 at 07:50, Ingeborg Hellemo <ingeborg.hellemo(a)uit.no> wrote: > > > I'm compiling NAV from source. Somehow I've messed up my environment and > > haven't been able to install the documentation for the last two versions. (No > > showstopper, but irritating). I guess I have the wrong version of setuptools > > or something. > ... > > /usr/local/src/nav-5.11.0/# python setup.py build_sphinx > ... > > error: invalid command 'build_sphinx' > > Nah, the old ways of setuptools are becoming deprecated in the Python > world, and I think maybe Sphinx no longer integrates with setuptools. > We should really update our install docs on this point: We already > updated the docs build routine for the latest Debian package: > > https://github.com/Uninett/nav-debian/commit/ee65417603ae2780c506443e398c1a… > > Sphinx should have provided its own `sphinx-build` command, but you > apparently need to give it an input directory and an output directory as > arguments, so for the Debian build we use something like > > `sphinx-build doc/ doc/_build` > *Gasp!* Install docs not updated!?! The new command worked as a charm. --Ingeborg -- Ingeborg Østrem Hellemo -- ingeborg.hellemo(a)uit.no Dep. of Information Technology --- Univ. of Tromsø

2 1

Problem with build_sphinx
by Ingeborg Hellemo 01 Nov '24

01 Nov '24

I'm compiling NAV from source. Somehow I've messed up my environment and haven't been able to install the documentation for the last two versions. (No showstopper, but irritating). I guess I have the wrong version of setuptools or something. FreeBSD 13.3-RELEASE-p7 python39-3.9.20 setuptools 63.1.0 Sphinx 7.4.7 sphinxcontrib-applehelp 2.0.0 sphinxcontrib-devhelp 2.0.0 sphinxcontrib-django 2.5 sphinxcontrib-htmlhelp 2.1.0 sphinxcontrib-jsmath 1.0.1 sphinxcontrib-programoutput 0.17 sphinxcontrib-qthelp 2.0.0 sphinxcontrib-serializinghtml 2.0.0 /usr/local/src/nav-5.11.0/# python setup.py build_sphinx /usr/local/lib/python3.9/site-packages/setuptools/installer.py:27: SetuptoolsDeprecationWarning: setuptools.installer is deprecated. Requirements should be satisfied by a PEP 517 installer. warnings.warn( WARNING: The wheel package is not available. /usr/local/lib/python3.9/site-packages/setuptools/config/pyprojecttoml.py:104: _BetaConfiguration: Support for `[tool.setuptools]` in `pyproject.toml` is still *beta*. warnings.warn(msg, _BetaConfiguration) usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: invalid command 'build_sphinx' --Ingeborg -- Ingeborg Østrem Hellemo -- ingeborg.hellemo(a)uit.no Dep. of Information Technology --- Univ. of Tromsø

1 0

Re: R: Disabling a device in Seed Database - there is a way to disable device polling without deleting?
by Morten Brekkevold 04 Okt '24

04 Okt '24

On Mon 30 Sep 2024 at 15:12, Davide Miccone <davide(a)wpweb.com> wrote: > the use case is really simple. > > One switch fail and needs to be replaced. (Or I need to replace an old > with a new one). > > I have the old switch configuration backup but NAV's representation is > more clear than the script, especially for those who are used to > managing the switch through NAV. > > So I replace the switch but I wish to leave the old switch inside NAV > because some configurations are not immediately migrated to the new > switch, so I need to see in NAV the configuration of the old switch. > > Continue to see the old switch in NAV is very useful for this > reason. But I don't want to see the switch has a failed switch in the > home page. NAV was never designed with this use-case in mind. Rather, the common approach would be to put the dead switch in maintenance mode in NAV. NAV will still attempt to monitor it, but any alarms about it will be suppressed. You can put a device on maintenance directly from the status tool by checking the checkbox next to the offending alert and selecting "Put on maintenance" from the actions drop-down menu. IIRC, this will create a maintenance task with no set end-time for that device. This also allows you to add a description/reason for why the device has been placed on maintenance. > Several Network Monitoring Tools (LibreNMS, CheckMK, Zabbix) let > disable a device. You're welcome to post a feature request in our tracker :-) -- Sincerely, Morten Brekkevold Sikt – Norwegian Agency for Shared Services in Education and Research

1 0

Announcement: NAV 5.11.0 released
by Morten Brekkevold 03 Okt '24

03 Okt '24

The first feature release of the 5.11 series of NAV is now out! The source code is available for download at GitHub [1]. New packages for 11 (Bullseye) are available in our APT repository as usual. We haven't started building packages for Debian 12 (Bookworm) yet, as NAV does not yet support running under Python 3.11. 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. Removed ======= - Dropped support for Python 3.7 (#2790) Added ===== - Post lifecycle event when power supplies or fans are removed (#2982) - Post lifecycle event when a module or chassis is deleted via the status or device history tools (#2983) - Database model for representing Organizationally Unique Identifiers (OUI) to identify vendors for MAC addresses - Script for populating database with OUIs and corresponding vendors from IEEE (#2945) - Module for generating JWTs (#2948) - Documentation for configuring and using JWT tokens in NAV API (#2618) Changed ======= - Upgraded dependencies after dropping support for Python 3.7 (#2790) - Changed Sphinx version to 7.4.7 (#2826) - Changed required PostgreSQL version to 13 (#2892) - Moved the test suite's web crawler complexity away from the test discovery phase to the test phase itself. This reduces the number of generated test cases from N to 2 (where N is the number of reachable NAV pages) (#2966) - Link to the doc for using docker for development from the README and mention what ports are used when using docker for development (#2978) - Many user-facing forms of the web user interface have been refactored in order to remove a dependency that keeps NAV incompatible with Python 3.11. This should not affect looks or functionality. This work is still ongoing in the master branch and we hope it will be complete by NAV version 5.12. Fixed ===== - Correctly delete an IP Device's existing function value when empty field value is submitted in the IP Device IP Device edit form (#2269) - Fixed crash bug when reordering filters within a filter group in Alert Profiles (#2979) - Fixed IPAM API crash bug that caused unnecessary error reports sent as e-mail to site admins (#2989) - Fixed bad tooltip grammar in ipdevinfo "degraded aggregate link" badge - Make the test suite easier to run under MacOS - Skip tests when 3rd party requirements are missing, instead of outright failing Security ======== - Ensure that CSRF token info is preserved when refactoring crispy forms to non-crispy equivalents. This means that flat_form.html and _form_content.html templates will include CSRF token info if form method is set to POST. (#3056) Release notes ============= We always advise you to have a look at NAV's accompanying release notes [3] before upgrading. 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-11 -- Sincerely, Morten Brekkevold Sikt – Norwegian Agency for Shared Services in Education and Research

1 0

Disabling a device in Seed Database - there is a way to disable device polling without deleting?
by Davide Miccone 25 Sep '24

25 Sep '24

I wish disable a configured device from polling, Is there a way from Seed Database to achieve this without deleting the device? Any suggestion will be appreciated. Thanks Davide

1 0

Performance questions and weathermap
by Manuel Marín 08 Jul '24

08 Jul '24

Dear NAV community We are looking for a network monitoring platform as a replacement to cacti/weathermap and I was wondering if there is information about performance/hardware requirement for a network with ~20K networks devices. Can NAV support this number of devices? It would be great if someone can share their experiences running NAV with large networks. Thank you! Regards -- Manuel Marín Engineering mmg(a)flo.net US +1 915 217 2232 MX +52 656 215 0906 flo.net Flō Networks was formerly known as Transtelco / Flō Networks era anteriormente conocido como Transtelco. CONFIDENTIALITY NOTICE: This message is intended only for the individual or entity to whom it is addressed. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. AVISO DE CONFIDENCIALIDAD:Esta comunicación es sólo para el uso de la persona o entidad a la que se dirige y puede contener información privilegiada, confidencial y exenta de divulgación bajo la legislación aplicable. Si no es el destinatario de esta información, se le notifica que cualquier uso, difusión, distribución o copia de la comunicación está estrictamente prohibido.

1 0

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