Nav-users March 2022

nav-users@lister.sikt.no

5 participants
5 discussions

NAV with Cisco 3850
by Mischa Diehm 15 Sep '23

15 Sep '23

Hi, we have a 3850 Stack with 3x ES-C3850-48T-S and 5x WS-C3850-12X48U. When we try to PortAdmin and edit a Port we get (see also attached Jpg): „IP device found but has no type“ Any ideas? Cheers, Mischa -- Mischa Diehm | Network Team (NINS) UniBasel | IT-Services (ITS) Klingebergstr. 70 | CH-4056 Basel Tel. +41 61 267 1574 | https://its.unibas.ch

4 4

nav 5.3 - alertengine not sending alert / blacklisted and connection timeout (error 110)
by Andrea Verni 26 Aug '22

26 Aug '22

Hi, I'm running NAV 5.3 and have issue with alertengine and email notifications. Email seems to remain stuck in the queue until I force a reboot of the VM. The error message I see in /var/log/nav/alertengine.log is: 2022-03-08 08:35:10,707 [WARNING] [nav.alertengine.alertaddress.send] Not sending alert 5824 ****** as handler Email is blacklisted: [Errno 110] Connection timed out 2022-03-08 08:35:10,716 [WARNING] [nav.alertengine.alertaddress.send] Not sending alert 5825 to ****** as handler Email is blacklisted: [Errno 110] Connection timed out 2022-03-08 08:35:10,720 [INFO] [nav.alertengine.check_alerts] 0 new alert(s), sent 0 alert(s), 910 queued alert(s), 0 alert(s) deleted, 910 failed send(s), 0 ignored However, by running a tcpdump I do not see any outbound/inbound connection to the configured email server. After the reboot it seems messages are going through (and I do see outbound connections to the configured mail server) 2022-03-08 08:39:38,277 [INFO] [nav.alertengine.alertaddress.send] alert 5367 sent by Email to ****** due to immediately subscription 2 2022-03-08 08:39:38,500 [INFO] [nav.alertengine.alertaddress.send] alert 5320 sent by Email to ****** due to immediately subscription 2 2022-03-08 08:41:34,963 [INFO] [nav.alertengine.check_alerts] 0 new alert(s), sent 910 alert(s), 0 queued alert(s), 0 alert(s) deleted, 0 failed send(s), 0 ignored I'm running Debian 10 and not have iptables/fail2ban on it. Any help? Thanks! Andrea

2 3

wrong Port configuration status for juniper device if port manually disabled
by FOUR Ludovic (EXT) 30 Mar '22

30 Mar '22

Hello, I found a problem wih NAV portadmin configuration page for Juniper EX series I ran wildcard changes to unused interfaces, and I disabled them manually with junos set command [ set interfaces <port number> disable ] However, in the NAV portadmin page configuration, the port status of those interfaces is still enabled. (checkbox checked) Interface => NAV: enabled / JunOS: disabled When I uncheck the enable checkbox, and save changes, the NAV portadmin page show disabled, and the port is still disabled in junos console. Interface => NAV: disabled / JunOS: disabled If enable and save changes again into NAV, and the port is next enabled in console. Interface => NAV: enabled / JunOS: enabled If I manually update the interface description with junos set command, and update NAV portadmin page, the description field is updated. Does NAV run netconf or snmp checkings before showing the portadmin page, or it does only rely on last database readings for portadmin state ? It makes some confusion, because we think the interface is enabled and working into NAV portadmin page, but it's not in reality. Regards, Ludovic FOUR SSI DR10 CNRS - Support Infoprox Pharma FRANCE

2 1

NAV (Network Administration Visualized) user discussions, questions and help
by Robert2 Wu 鄔忠慈 #8051 15 Mar '22

15 Mar '22

Hi We are use HPE Aruba 6300 switch in our company. When I use standard SNMP port 161 to query it will unsuccessful. I check device snmp agent port is 162. Where/How can I make a management profile and use port 162. Thanks Robert Wu robert2.wu(a)mpi.com.tw<mailto:robert2.wu@mpi.com.tw> ********************************************************************************************************** 本郵件及其附件(下稱本郵件)可能包含有旺矽公司機密資訊，非指定之收件者。請勿使用或揭露本信件內容，請立即通知寄件人並請銷毀此信件。 ************************************** Email Confidentiality Notice ************************************** This email may contain confidential information. Please do not use or disclose it in any way it if you are not the intended recipient. If you have received the e-mail in error, please notify us immediately by returning it to the sender and then delete it . **********************************************************************************************************

2 1

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

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Nav-users March 2022