- Nav-users - lister.unit.no

GeoMap without Vlan interfaces
by Marcos Tadeu 17 Mai '23

17 Mai '23

Hello Can I config Geomap do not use the VLANs interfaces to trace links on map? I need only physical interfaces connections on GeoMap. Tia, -- Marcos Tadeu

2 2

Where does the DNS-button collect its data?
by Ingeborg Hellemo 12 Mai '23

12 Mai '23

/ipdevinfo contains a button named "DNS" which shows all the IP-addresses connected to the device and their hostnames. I have one device which is correctly registered i DNS. Even so, the DNS info says "No addresses found". Why? Where to start debugging? ipdevpolld -J dns -n <ip-address> runs as expected. --Ingeborg -- Ingeborg Østrem Hellemo -- ingeborg.hellemo(a)uit.no Dep. of Information Technology --- Univ. of Tromsø

2 8

VLANs on netmap
by Marcos Tadeu 09 Mai '23

09 Mai '23

Hello, The same VLAN appears several time on netmat. When click in one, different links are highlighted. Dispist commentary, how to do to appear one time? Regards, -- Marcos

2 2

spam VENDOR TENDA - MIB
by Marcos Tadeu 08 Mai '23

08 Mai '23

Hi, Thanks for the amazing software! We need to use with SW Tenda G5328P, with proprietary MIB. The MIB is on this email How we can include an new MIB? TIA, -- Marcos Tadeu

3 3

Error 500 when upgrading to nav 5.6
by FOUR Ludovic (EXT) 30 Mar '23

30 Mar '23

Hello, I've updated recently Nav on debian from 5.5.2-1 to 5.6 I have an error 500 when I try to reach the nav gui website Here is some errors on /var/log/apache2/error.log [Tue Jan 24 11:18:16.723757 2023] [mpm_prefork:notice] [pid 22855] AH00169: caught SIGTERM, shutting down [Tue Jan 24 11:23:07.716778 2023] [mpm_prefork:notice] [pid 1600] AH00163: Apache/(version removed) (Debian) mod_fcgid/(version removed) OpenSSL/1.1.1n mod_wsgi/(version removed) Python/3.7 configured -- resuming normal operations [Tue Jan 24 11:23:07.881160 2023] [core:notice] [pid 1600] AH00094: Command line: '/usr/sbin/apache2' [Tue Jan 24 11:27:21.186436 2023] [wsgi:error] [pid 1602] [remote <IP removed>:55041] mod_wsgi (pid=1602): Exception occurred processing WSGI script '/opt/venvs/nav/lib/python3.7/site-packages/nav/wsgi.py'. [Tue Jan 24 11:27:21.187713 2023] [wsgi:error] [pid 1603] [remote <IP removed>:55043] mod_wsgi (pid=1603): Exception occurred processing WSGI script '/opt/venvs/nav/lib/python3.7/site-packages/nav/wsgi.py'. [Tue Jan 24 11:27:21.212539 2023] [wsgi:error] [pid 1602] [remote <IP removed>:55041] Traceback (most recent call last): [Tue Jan 24 11:27:21.212543 2023] [wsgi:error] [pid 1603] [remote <IP removed>:55043] Traceback (most recent call last): [Tue Jan 24 11:27:21.212725 2023] [wsgi:error] [pid 1602] [remote <IP removed>:55041] File "/opt/venvs/nav/lib/python3.7/site-packages/django/core/handlers/wsgi.py", line 133, in __call__ [Tue Jan 24 11:27:21.212731 2023] [wsgi:error] [pid 1603] [remote <IP removed>:55043] File "/opt/venvs/nav/lib/python3.7/site-packages/django/core/handlers/wsgi.py", line 133, in __call__ [Tue Jan 24 11:27:21.212737 2023] [wsgi:error] [pid 1602] [remote <IP removed>:55041] response = self.get_response(request)one Apparently, uwsgi Proxy is only used by graphite. No WSGI or uwsgi error found in /var/log/apache2/graphite-web_error.log The uwsgi configuration has not been touched since installation of nav and the other vhosts are working. When I downgrade nav to previous version, nav is working again and I can see updated traffic graphs (no gaps or missing graphs since the error) Regards, Ludovic F. Faculty of pharmacy - Strasbourg FRANCE

2 4

Announcement: NAV 5.6.1 released
by Morten Brekkevold 23 Mar '23

23 Mar '23

The first maintenance release of the 5.6 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. Fixes ===== - Ensure event variables are always posted in transactions, so the event engine does not accidentally end up processing incomplete event information (#2594) - Report broken cache configuration as an error in Ranked Statistics tool, rather than taking down the whole NAV site (#2561, #2563) - Show error message on invalid ip address in ipdevinfo (#2590, #2589) - Link to correct room in room report if room has a space in its name (#2593, #2592) - Work around duplicate internal serial numbers in Juniper equipment by trusting data only from the device with t he lowest entity index (#2583, #2493) - Make save function in AlertHistory, EventHistory and AlertQueue atomic (#2594) - Ignore LDAP server referral responses, rather then erroring out during the login process (#2576, #1166) - Include the new_version variable in alert message templates for device hw/fw/sw upgrades (#2565) - Update NAV blog widget to use the new blog URL (#2585) - Handle invalid IP address input in ipdevinfo device searches gracefully, rather then crashing with a 500 error (#2589, #2590) - Fix broken links to room details from room report for rooms with spaces in their names (#2592, #2593) 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-6 -- Sincerely, Morten Brekkevold Sikt – Norwegian Agency for Shared Services in Education and Research

1 0

deviceNotice/None - no message template is defined
by Ingeborg Hellemo 23 Mar '23

23 Mar '23

NAV 5.5.2 An upgrade of a router generated several "Device SomeModule at router.domain had a software upgrade" (as expected), but also several Subject: deviceNotice/None on router.domain from NAV, but no message template is defined. Variable dump: {'_messages': None, 'alert_type': None, 'device': <Device: VB13030631>, 'event': <EventQueue: id=101132957, event_type_id='deviceNotice', source_id='ipdevpoll', target_id='eventEngine', netbox=<Netbox: router.domain> , subid='', state='x', time=datetime.datetime(2022, 12, 13, 13, 50, 53, 897695)>, 'event_type': <EventType: deviceNotice>, 'history_vars': {}, 'language': 'en', 'msgtype': 'email', 'netbox': <Netbox: router.domain>, 'severity': 3, 'source': <Subsystem: ipdevpoll>, 'state': 'x', 'subid': '', 'time': datetime.datetime(2022, 12, 13, 13, 50, 53, 897695), 'value': 100} --Ingeborg -- Ingeborg Østrem Hellemo -- ingeborg.hellemo(a)uit.no Dep. of Information Technology --- Univ. of Tromsø

2 7

Re: Error 500 when upgrading to nav 5.6
by Davide Miccone 08 Mar '23

08 Mar '23

Hello Ludovic, I have your some problem. Have you resolved? Any suggestion will be appreciated. Regards, Davide

3 2

Netmap is empty
by onygaard＠tryggheim.no 24 Feb '23

24 Feb '23

Hi, We are running NAV 5.6.0 (from av Debian package) on a local Debian 11 machine, set up with postgresql and apache2. Initially we had some problem with the error message "Graphite unreachable", but followed the solution suggested by datagutten: https://github.com/Uninett/nav/discussions/2535 Now, a lot looks nice. Graphs display fine, but we have problems with Netmap, which is empty. For the router e.g. the "Ports" tab is missing info about "To Device" and "To Port". "Port details" do not provide any options for "Two IP device". Regards, Ole Harald

3 5

Re: Netmap is empty
by Ole Harald Nygård 21 Feb '23

21 Feb '23

1 0

Alert Profiles, filters and options
by BERGELIN SABADELL, IVAR-ERIC 16 Feb '23

16 Feb '23

Hello, My name is Ivar and I work at Universitat Pompeu Fabra of Barcelona. I sent an email a few days ago asking about the API's options of NAV (no responses yet). Now I'm trying to get the link status of a switch using filters, but I have three questions. - Is it possible to get this information using filters? My idea is to send a daily email with a list of the ports of a specific switch which has link status down through NAV's "Alert Profiles" tool. - What is the difference between these two tabs? [image: image.png] [image: image.png] - Is this second option checking if a port has an ethernet cable plugged to the ethernet card of a computer at that moment? Thanks again -- *Ivar Bergelin* Tècnic de suport informàtic Unitat d'Informàtica del Campus del Poblenou Roc Boronat 138 | 08018 - Barcelona [Tel.] (+34) 93 542 23 58 http://www.upf.edu

2 1

Fwd: A question about computers connectivity
by BERGELIN SABADELL, IVAR-ERIC 16 Feb '23

16 Feb '23

Hello, My name is Ivar, I work at Universitat Pompeu Fabra of Barcelona and we use NAV 4.5.2. I have a question about the NAV's API functionalities. We are looking to see if it's possible to check whether a group of computers connected to a specific switch have "link signal status" even when they are turned off (all the computers have WOL enabled as well). I found an example to get the state (active) of a computer. Here in this following link of your documentation URL: http://navscc-upf.x.upf.edu/doc/howto/using_the_api.html You show a specific scenario titled: We want to know the interface a computer is connected to right now. We have the ip-address of the computer. So, when it says "We want to know the interface a computer *is connected to right now*" means the computer is turned on or it works even if the computer is off? it would help us a lot. Thank you. -- *Ivar Bergelin* Tècnic de suport informàtic Unitat d'Informàtica del Campus del Poblenou Roc Boronat 138 | 08018 - Barcelona [Tel.] (+34) 93 542 23 58 http://www.upf.edu

2 1

How to filter reports on Attributes
by Ingeborg Hellemo 08 Feb '23

08 Feb '23

Filter reports gives you the option to filter on "Attributes". What is the correct incantation to fill in that will give something else than "There was an unhandled SQL error!"? --Ingeborg -- Ingeborg Østrem Hellemo -- ingeborg.hellemo(a)uit.no Dep. of Information Technology --- Univ. of Tromsø

3 5

Re: Fortigate firewall
by Morten Brekkevold 23 Jan '23

23 Jan '23

On Tue, 10 Jan 2023 17:23:08 +0100 Biselx Nicolas <nicolas.biselx(a)epfl.ch> wrote: > I'm not sure but I think that's what you asked me... > See in attachement Yes, the attachment is perfect, showing an snmpwalk of the `ipAddressTable` :) > D:\>snmpwalk.exe -v 2c -c XXXXX forti-noc.epfl.ch 1.3.6.1.2.1.4.34 > iso.3.6.1.2.1.4.34.1.3.1.10.0.2.49.143 = INTEGER: 143 All the responses seem to show the same problem, but we only need this one response for me to claim that the Fortigate device has an incorrect implementation of the IP-MIB. This is the definition of an entry in the ipAddressTable: > IP-MIB::ipAddressEntry > ipAddressEntry OBJECT-TYPE > -- FROM IP-MIB > MAX-ACCESS not-accessible > STATUS current > INDEX { ipAddressAddrType, ipAddressAddr } > DESCRIPTION "An address mapping for a particular interface." > ::= { iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) ip(4) ipAddressTable(34) 1 } `iso.3.6.1.2.1.4.34.1.3` from above is a result from the `ipAddressIfIndex` column (column no. 3). The row index is given as `.1.10.0.2.49.143`. The `.1` indicates an address type of IPv4, which according to spec should occupy 4 octets. However, the remaining row index contains 5 octets - An invalid IPv4 address: `10.0.2.49.143`. This is the type definition: > InetAddressIPv4 ::= TEXTUAL-CONVENTION > DISPLAY-HINT "1d.1d.1d.1d" > STATUS current > DESCRIPTION > "Represents an IPv4 network address: > > Octets Contents Encoding > 1-4 IPv4 address network-byte order > > The corresponding InetAddressType value is ipv4(1). > > This textual convention SHOULD NOT be used directly in object > definitions, as it restricts addresses to a specific format. > However, if it is used, it MAY be used either on its own or in > conjunction with InetAddressType, as a pair." > SYNTAX OCTET STRING (SIZE (4)) This response perfectly explains the warning/error given by ipdevpoll: > device has strange SNMP implementation of IP-MIB; ignoring retrieved IP > address data: IPv4 address length is not 4: OID('.1.10.0.2.49.143') It seems to me like the Fortigate device appends an actual `ifIndex` value (143, in this case) to all the IP addresses, and is therefore in violation of the MIB definition. We could potentially work around this in NAV by ignoring the extra data and just interpret the first four octets, but this might cause problems with other devices that have faulty IP-MIB implementations, or it could cause potential problems if the same IP address appears multiple times with different ifIndex values attached to it. I would at the very least report this as a bug to Fortigate. -- Sincerely, Morten Brekkevold Sikt – Norwegian Agency for Shared Services in Education and Research

4 4

Re: Fortigate firewall
by Morten Brekkevold 10 Jan '23

10 Jan '23

On Mon, 9 Jan 2023 11:42:42 +0100 Biselx Nicolas <nicolas.biselx(a)epfl.ch> wrote: > In attachement, the debug with the list of ports It did find some 118 interfaces on the Fortigate, but no IP address information. Apparently, if found nothing useful in the IP-MIB: > 2023-01-09 11:27:03,353 [DEBUG plugins.prefix.prefix] [inventory fortigate] Trying address tables from IP-MIB > 2023-01-09 11:27:03,371 [WARNING plugins.prefix.prefix] [inventory fortigate] device has strange SNMP implementation of IP-MIB; ignoring retrieved IP address data: IPv4 address length is not 4: OID('.1.10.0.2.49.143') > 2023-01-09 11:27:03,371 [DEBUG plugins.prefix.prefix] [inventory fortigate] Found 0 addresses in IP-MIB: set() That is, it seems to have found *something*, but it didn't quite conform to that is expected in the MIB (the 1.10.0.2.49.143 value is invalid, as it is marked as a 4-octet IP address, but it contains 5 octets). Do you have the NET-SNMP command line tools and basic MIBs available on your system? Might be interesting to get a raw view of that the device presents, using something like these two commands: snmptable -v2c <community> <fortigate-ip-addr> IP-MIB::ipAddrTable snmptable -v2c <community> <fortigate-ip-addr> IP-MIB::ipAddressTable -- Sincerely, Morten Brekkevold Sikt – Norwegian Agency for Shared Services in Education and Research

1 0

Fortigate firewall
by Biselx Nicolas 02 Jan '23

02 Jan '23

Hi, We have a Fortigate firewall that I introduced with the GW category (routers layer 3 device), all information seems ok according to the capture. But when I look at the tools > watchdog there is a problem with the routing interfaces not being recognized ? It's a same with GSW Is there a solution to fix this? Regards, Nicolas

2 3

Correcting NAV topology after a physical reconfiguration
by tom.daae＠lom.kommune.no 21 Des '22

21 Des '22

Hi, I'm a new user of NAV and have found it to be a very useful tool. Among other things, it has helped us discover and plan improvements to our network topology. After implementing said improvements however, I find myself in a bit of a predicament. Two of my switches were previously connected via a link (in practice a daisy-chain), which is no longer physically present. NAV, of course, does not know the difference between a link that is temporarily down and one that is never coming back up, so the link remains in our netmap. I have not found a way of removing this link from NAV, short of deleting and re-registering the switches on either end of the link. This would of course mean losing a lot of traffic stats, so I'm wondering if there is any way to tell NAV do forget this specific link? Am I just misunderstanding something fundamental here?

2 1

Fortigate firewall
by Biselx Nicolas 20 Des '22

20 Des '22

Hi, We have a Fortigate firewall that I introduced with the GW category (routers layer 3 device), all information seems ok according to the capture. But when I look at the tools > watchdog there is a problem with the routing interfaces not being recognized ? It's a same with GSW Is there a solution to fix this? Regards, Nicolas

1 0

Any documentation about contrib/isc_dhpcd_graphite.py ?
by Ingeborg Hellemo 21 Nov '22

21 Nov '22

FreeBSD 12.3 python38-3.8.15 isc-dhcp44-server-4.4.3P1 dhcpd-pools-3.1 I try to use isc_dhpcd_graphite.py but stumble quite early: ./isc_dhpcd_graphite.py -n <graphiteserver> Traceback (most recent call last): File "/root/bin/isc_dhpcd_graphite.py", line 205, in <module> main() File "/root/bin/isc_dhpcd_graphite.py", line 194, in main output = render(jsonblob, args.actual_prefix, args.protocol) File "/root/bin/isc_dhpcd_graphite.py", line 134, in render return _render_text(jsonblob, prefix) File "/root/bin/isc_dhpcd_graphite.py", line 139, in _render_text input = _tuplify(jsonblob, prefix) File "/root/bin/isc_dhpcd_graphite.py", line 163, in _tuplify vlan = _clean_vlan(vlan_stat["location"]) File "/root/bin/isc_dhpcd_graphite.py", line 173, in _clean_vlan return regex.group() AttributeError: 'NoneType' object has no attribute 'group' Where to begin debugging? Any flags to dhcpd-pools that are implicit to Linux and I am missing? If I get this to work, examples of how to display the results via NAV are welcome. --Ingeborg -- Ingeborg Østrem Hellemo -- ingeborg.hellemo(a)uit.no Dep. of Information Technology --- Univ. of Tromsø

3 4

how to export cabling table ?
by FOUR Ludovic (EXT) 11 Nov '22

11 Nov '22

Hello, Sorry if the question was already asked. Can we export cabling into dump file or csv ? Best regards, Ludovic FOUR Faculté de Pharmacie - Support Informatique Université de Strasbourg / CNRS France

2 1

NAV 5.5.2: ipdevpoll will not start
by Ingeborg Hellemo 10 Nov '22

10 Nov '22

FreeBSD 12.3 python38-3.8.15 The error is not specific til 5.5.2 since I am upgrading from NAV 5.2.1. ipdevpoll will not start: Traceback (most recent call last): File "/usr/local/bin/ipdevpolld", line 19, in <module> from nav.ipdevpoll.epollreactor2 import install File "/usr/local/lib/python3.8/site-packages/nav/ipdevpoll/epollreactor2.py", line 24, in <module> from twisted.internet import epollreactor File "/usr/local/lib/python3.8/site-packages/twisted/internet/epollreactor.py ", line 16, in <module> from select import epoll, EPOLLHUP, EPOLLERR, EPOLLIN, EPOLLOUT ImportError: cannot import name 'epoll' from 'select' (/usr/local/lib/python3.8/lib-dynload/select.cpython-38.so) Am I missing a library or a module? This is a bit urgent since I really don't want to downgrade... --Ingeborg -- Ingeborg Østrem Hellemo -- ingeborg.hellemo(a)uit.no Dep. of Information Technology --- Univ. of Tromsø

2 2

Announcement: NAV 5.5.2 released
by Morten Brekkevold 10 Nov '22

10 Nov '22

The second maintenance release of the 5.5 series of NAV is now out, fixing a couple of serious collection and trap processing issues! 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, but currently, the automated GitHub workflows aren't working due to changes at GitHub. Fixes ===== - Fix serious collection breakdown in ipdevpoll by re-generating a valid Python representation of CISCO-ENHANCED-MEMPOOL-MIB (#2494, #2495) - Fix broken trap processing in snmptrapd (#2497, #2498) 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-5 -- Sincerely, Morten Brekkevold Sikt – Norwegian Agency for Shared Services in Education and Research

1 0

Announcement: NAV 5.5.1 released
by Morten Brekkevold 09 Nov '22

09 Nov '22

The first maintenance release of the 5.5 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, but currently, the automated GitHub workflows aren't working due to changes at GitHub. Fixes ===== - Delete and ignore module devices with fake serial number `BUILTIN`, as reported by Juniper equipment, in order to avoid spamming with `device[SFH]wUpgrade` alerts (#2491, #2492) Release notes ============= We always advise you to have a look at NAV's accompanying release notes [3] before upgrading. This maintenance release was made to fix an ugly issue for those who monitor Juniper equipment using NAV (of which there are quite a few). We've added the following note: Juniper ``BUILTIN`` devices --------------------------- Juniper equipment tends to report soldered-on linecards as field-replaceable modules through their implementation of ``ENTITY-MIB::entPhysicalTable``. These modules are also all reported as having the same serial number: ``BUILTIN``. NAV versions prior to 5.5.1 did not safeguard against this Juniper bug. This would cause NAV installations that monitor Juniper equipment to have a single device with the ``BUILTIN`` serial number, which was shared between all monitored Juniper netboxes. The attributes of ``BUILTIN`` devices (such as software or firmware revision) would be different across most Juniper netboxes, causing them to compete for updates of the attributes in the NAV database. This went under the radar until NAV 5.5.0 re-introduced the ``device*Upgrade`` set of alerts. Now, every time a Juniper netbox is polleed and the shared ``BUILTIN`` device's software/hardware/firmware revision was changed, an alert would be generated. For those unfortunate enough to subscribe to all NAV alerts, this would lead to a storm of alerts. Subsequently, NAV 5.5.1 deletes this shared ``BUILTIN`` device from the database, and adds functionality to ignore any module or entity that reports this as its serial number. 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-5 -- Sincerely, Morten Brekkevold Sikt – Norwegian Agency for Shared Services in Education and Research

1 0

Announcement: NAV 5.5.0 released
by Morten Brekkevold 04 Nov '22

04 Nov '22

The initial feature release of the 5.5 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 ======= - Bump lxml from 4.6.5 to 4.9.1 in /tests (#2443) - Links and documented references to the NAV mailing lists have changed to the lister.sikt.no domain. Added ===== - Add link to #nav irc channel on Libera.Chat to README file (#2475) - Add mac_addresses attribute to /netbox/ API endpoint (#2487, #2490) - Add ability to filter by alert severity in the status tool (#2467) - Support for fetching ARP cache entries from all Arista VRF instances (#2262, #2454)) - Link aggregation information added to NAV API (#1765, #2440) - Support fetching memory stats from CISCO-ENHANCED-MEMPOOL-MIB (#2236, #2439) - Added a flag to navcheckservice that shows all available handler plugins (#2378, #2437) - Post deviceHwUpgrade/deviceSwUpgrade/deviceFwUpgrade events when changes are detected to devices' hardware, software or firmware revisions (#2393, #2413) - Call a cleanup() method for individual container objects after ipdevpoll save stage (#2421) - Added Device methods to resolve and return related objects/entities (chassis, modules, fans, power supplied) and extended device descriptions (#2428) Fixed ===== - Avoid potential resource leaks by properly closing configuration files after reading them (#2451) - Geomap "link to this configuration" now actually opens the correct location at the correct zoom level (#2412, #2488) - snmptrapd can now identify an SNMP agent from any of its interface addresses (#2387, #2461) - PortAdmin now ignores incorrectly configured VLAN tags (tagged as NA) on Juniper switches, instead of crashing (#2452, #2453) - Fix potential ipdevpoll crashes due to database fetches in wrong thread (#2478, #2480) - Handle Graphite connection issues gracefully in ranked statistics page (#2459) - Handle Graphite connection issues gracefully in device group detail page (#2345, #2434) - Removed needless carbon data chunking from activeipcollector (#1696, #2462) - Evaluate 0.0 as a valid numeric metric value during threshold rule evaluations (#2447) - Updated dead links in Geomap documentation (#2419) - Link from IPAM to reserve prefixed in SeedDB now works again (#2410, #2422) - Improved inefficient database queries in Arnold (#2425) - Updated tox examples in hacking documentation (#2427, #2430) - Fixed an AttributeError crash bug in the naventity command line program (#2433, #2444) 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-5 -- Sincerely, Morten Brekkevold Sikt – Norwegian Agency for Shared Services in Education and Research

1 0

Nav - LLDP Missing on some FS model
by Marco Valerio Bifolco 03 Nov '22

03 Nov '22

Hello, First of all thanks for your job, we really appreciate nav solution. We noticed that some of our FS.COM switch, (we got, cisco, hp, dlink, fs) does not work as expected. Nav doesn't get LLDP information, and for this it is wrongly populating the net map. The FS model working properly are s3900, s5850; But not so lucky with s2800, s1400, s3400 . It's possible to force nav to choose a neighbor from cam candidate? Or set it manually? Or is it possible to make these switch works with nav? Maybe passing mib somehow? Many Thanks in advance Best Regards [cid:image001.png@01D8D356.6C245C00] Marco V. Bifolco System Engineer Office (+39) 0694320122 | Mobile (+39) 3519666252 marco.bifolco(a)sferanet.net<mailto:marco.bifolco@sferanet.net> assistenza(a)sferanet.net<mailto:assistenza@sferanet.net> [cid:image002.png@01D8D356.6C245C00] sferanet.net<http://www.sferanet.net/>

3 7

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Nav-users