- Nav-users - lister.unit.no

portadmin at CISCO switch is not working
by klaus.pantleon＠voith.com 29 Aug '22

29 Aug '22

Hello, I have a problem with portadmin and CISCO switches. The portadmin is not showing any changable entries when I connect nav-portadmin to a cisco switch. Other brands like netgear, tp-link, hirschmann are working good. Sorry If I post the question to the wrong place. Please help me to find the right place to post. Best Regards, Klaus

3 3

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

Announcement: NAV 5.4.0 released
by Morten Brekkevold 19 Mai '22

19 Mai '22

The initial feature release of the 5.4 series of NAV is now out! The source code is available for download at GitHub [1]. New packages for Debian 10 (Buster) and 11 (Bullseye) are available in our APT repository [2] as usual. 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 automatically. Changed ======= - The changelog format has changed from the legacy format into one based on Keep a Changelog. - Transceivers are no longer classed as modules (#1154) - Generate more secure API tokens (#2366) - Remaining instances of "Uninett" in footer FAQ have changed to Sikt (#2367) - Upgrade to napalm 3.4.1 (#2403) Added ===== - Support more recent AKCP environment probes (#2107 - Collect and graph temperature readings from JUNIPER-MIB (#2342) - Add support for wildcards in report IN operator (a.k.a. (,,)) (#2347) - Get VLAN tag from Juniper chassis cluster redundant ethernet interface ("RETH") names (#2357) - Collect and graph memory usage from JUNIPER-MIB (#2359) - Document NAV's various command line utilities (#2368) - Add a contrib script to ship ISC DHCP server lease stats to NAV's Graphite instance (#2371) Fixed ===== - Don't display JavaScript alert dialog box when generating links to the current Geomap configuration (#1016) - Optimize SeedDB prefix listing queries (#2156) - Fix broken deletion of quick links from "My stuff"-menu (#2334) - Display friendlier Juniper RPC error reports in Portadmin (#2362) - Get rid of warning: CacheKeyWarning: Cache key contains characters that will cause errors if used with memcached (#2379) - Get rid of warning: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated (#2381) - Get rid of warning: django.contrib.postgres.fields.JSONField is deprecated. Support for it (except in historical migrations) will be removed in Django 4.0. (#2382) - Rotate room image thumbnails correctly based on EXIF orientation tag (#2385) - Fix Django JSONField import deprecation warnings (#2396) - Fix broken documentation build environment in Read The Docs (#2399) - Optimize SeedDB room listing queries (#2400) - Optimize SeedDB netboxtype listing queries (#2401) - Optimize SeedDB vlan listing queries (#2402) - Fix broken deserialization of Rack data (#2407) - Remove unnecessary quotation marks in SeedDB (#2416) - Fix incorrect handling of stateless event posting in internal APIs (#2417) Removed ======= - Remaining Python 2 compatibility code (#2319) - Dependency on the six Python module 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-4 -- Sincerely, Morten Brekkevold Sikt – Norwegian Agency for Shared Services in Education and Research

1 0

Re: wrong Port configuration status for juniper device if port manually disabled
by FOUR Ludovic (EXT) 06 Apr '22

06 Apr '22

Hello, I just forgot to reply to all, my bad sorry I leave all the comments below I took a look into ipdevpoll.log When I'm updating a port, there is new [INFO schedule.netboxjobscheduler] line into ipdevpoll log, means that the scheduler is doing fine. I still have the same issue with portadmin enabled checkbox : if you uncheck enabled box, save, then reload page, the checkbox goes back to checked, and remains in this state. - but it updates the interface - (disabled) I've made some setup to portadmin.conf, and changed link_edit = false (better not cut the tree branch where you are sitting on) but I don't think it's related to. Regards, Ludovic ----- Mail original ----- De: "Morten Brekkevold" <morten.brekkevold(a)sikt.no> À: "FOUR Ludovic / PHA" <ludovic.four(a)unistra.fr> Envoyé: Vendredi 1 Avril 2022 14:39:19 Objet: Re: wrong Port configuration status for juniper device if port manually disabled On Thu, 31 Mar 2022 09:24:46 +0200 (CEST) "FOUR Ludovic (EXT)" <ludovic.four(a)unistra.fr> wrote: > I only disable the physical port in this case. Hi Ludovic, did you intentionally leave the mailing list out of your reply? > I did that, but there's no update even when I close Chrome or firefox > (did some tests on both). I tried by clearing firefox/chrome cache > too. The interface status still remains checked (enable) in portadmin > web page. Then I need to do some testing on our own equipment in an attempt to reproduce this. I'll have to get back to you. > I also have some update problem with aggregated interfaces (aeX) > created with Junos Console. NAV can detect the aeX interface when I > create it. But still remains when I remove it. I can't see the > physical interfaces that were previously members of the aggregated > interface in the physical ports list anymore. What ports NAV knows about is only updated by the inventory job, which runs every 6 hours. However, ipdevpoll does show some restraint from deleting any interface as soon as it appears missing (some devices can be wonky) - it actually marks it internally with a "missing since" timestamp, and removes it only when it remains missing after certain amount of time. I don't recall the exact amount, but I'm guessing 24 hours. > Maybe a SSL cache issue on server side ? > I'm using standard apache mod ssl settings > SSLSessionCache shmcb:${APACHE_RUN_DIR}/ssl_scache(512000) > SSLSessionCacheTimeout 300 No, this is unrelated to content caching. -- Sincerely, Morten Brekkevold Sikt – Norwegian Agency for Shared Services in Education and Research

2 1

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

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