Nav-users

nav-users@lister.sikt.no

1 participants
1378 discussions

Netmap question
by etiennel＠cos.flag.org 12 Sep '16

12 Sep '16

Hello, Very nice piece of software - most useful network monitoring tool I have seen in the open-source world. I have a question on the Netmap tool - I'm trying to have external links show and I wasn't able to. The scenarios are: - Edge router connected to the ISP. I can't add the ISP as a netbox as I don't have SNMP query access. So I added it as a server. How can I show on Netmap the edge router, the ISP end-device with a link between the two so I can see the bandwidth utilization and status? - A similar scenario, but with VPNs. I have a VPN router with multiple Tunnel interfaces (Csico) establishing a VPN with remote offices. I don't have SNMP of the remote offices' routers. How can I show this in Netmap tool - showing my VPN router with links to remove devices. I was able to do a similar thing with computers plugged into my switches, but in this case, I guess NAV uses the MAC address to match the device (in this case environment monitoring) with the switch port. Thank you. Etienne

3 2

ipdevpolld down
by Zhi-Wei Lu 12 Sep '16

12 Sep '16

Hi all, We are test driving NAV. I just have nav-4.5.3 installed on our CentOS7 test box. I can now log into the web console and start to add devices. But when I launch the daemon, the ipdevpolld will never stay up, I just wonder I can debug this problem, ipdevpoll does not have any information about why ipdevpolld won't stay up. Thank you very much for your help. Zhi-Wei Lu IET-CR-Network Operations Center University of California, Davis (530) 752-0155

2 1

Weird LLDP discovery
by Sylvain Desbureaux 01 Sep '16

01 Sep '16

Hello, I'm using nav in a "simple" lab environment. I have a firewall (Juniper SRX3400) acting as GW/Router between Vlans that are distributed in some rooms thanks to switches (Cisco and Juniper). In particuler I have a direct fiber link between a Cisco 4948 (named 4948-Datacenter) and a Juniper QFX3500 (named QFX3500-DC). Port of Cisco is Te1/49 and port of QFX is xe-0/0/43 On the map and on the report, I see this on Direct neighborship candidates for 4948-datacenter: Sysname Interface source Candidate neighbor Candidate neighbor port control 4948-datacenter.sdn.lab Te1/49 lldp 3750-core.sdn.lab Gi1/0/24 4948-datacenter.sdn.lab Te1/50 lldp qfx3500-dc.sdn.lab xe-0/0/43.0 I see also this for qfx3500-dc: qfx3500-dc.sdn.lab xe-0/0/43.0 lldp 4948-datacenter.sdn.lab Te1/49 and this: 3750-core.sdn.lab lldp 4948-datacenter.sdn.lab Gi1/45 3750-core.sdn.lab lldp 4948-datacenter.sdn.lab Gi1/46 3750-core.sdn.lab lldp 4948-datacenter.sdn.lab Gi1/47 3750-core.sdn.lab lldp 4948-datacenter.sdn.lab Gi1/48 3750-core.sdn.lab Gi1/0/25 lldp 3750-ucs.sdn.lab Gi1/0/25 On the devices, I have not that (see end of messages). I suspect a mis interpretation of snmp get on the 4948 but cannot be sure :/ I've put everything in a file in case it's hard to see on the mail. How can we proceed to have the correct information? Thanks in advance, Sylvain view from devices 4948: 4948-Datacenter>show lldp neighbors 4948-Datacenter>show lldp neighbors Capability codes: (R) Router, (B) Bridge, (T) Telephone, (C) DOCSIS Cable Device (W) WLAN Access Point, (P) Repeater, (S) Station, (O) Other Device ID Local Intf Hold-time Capability Port ID 3750-CORE Gi1/48 120 B Gi1/0/24 3750-CORE Gi1/47 120 B Gi1/0/23 3750-CORE Gi1/46 120 B Gi1/0/22 3750-CORE Gi1/45 120 B Gi1/0/21 3750-DMZ Gi1/25 120 B Gi1/0/21 3750-DMZ Gi1/27 120 B Gi1/0/23 3750-DMZ Gi1/26 120 B Gi1/0/22 3750-DMZ Gi1/28 120 B Gi1/0/24 4948-Datacenter2 Gi1/43 120 B Interco vers 4948-Datacenter QFX 4948-Datacenter2 Gi1/44 120 B Interco vers 4948-Datacenter 4948-Datacenter2 Gi1/41 120 B Interco vers 4948-Datacenter 4948-Datacenter2 Gi1/42 120 B Interco vers 4948-Datacenter nas Gi1/32 120 S 0015.17bb.0c81 nas Gi1/31 120 S 0015.17bb.0c80 nas Gi1/30 120 S 0015.17bb.0c83 nas Gi1/29 120 S 0015.17bb.0c82 nas Gi1/34 120 S 0015.17bb.0edf nas Gi1/33 120 S 0015.17bb.0ede nas Gi1/36 120 S 0015.17bb.0edd nas Gi1/35 120 S 0015.17bb.0edc QFX3500-DC Te1/49 120 B,R 589 nas Gi1/17 120 S 0021.5e75.094c Total entries displayed: 22 QFX3500: admin@QFX3500-DC> show lldp neighbors Local Interface Parent Interface Chassis Id Port info System Name ge-0/0/16.0 - 00:50:56:9d:1e:92 ens192 dns-server-1.infra.sdn.bizz.lab ge-0/0/16.0 - 00:50:56:9d:6f:f6 ens192 ntp-server.infra.sdn.bizz.lab xe-0/0/2.0 - 24:6e:96:02:3c:dc eth2 ceph-pf-2 xe-0/0/3.0 - 24:6e:96:02:42:bc eth2 ceph-pf-3 xe-0/0/1.0 - 24:6e:96:03:07:58 eth2 ceph-pf-1 ge-0/0/8.0 ae0.0 28:c0:da:3a:a9:80 ge-0/0/44.0 EX4200-LF ge-0/0/9.0 ae0.0 28:c0:da:3a:a9:80 ge-0/0/45.0 EX4200-LF xe-0/0/22.0 - 40:a8:f0:31:a8:f0 eth2 openstack-pf-compute-1 xe-0/0/26.0 - ac:4b:c8:f7:9c:64 xe-0/0/25.0 QFX3500-DC xe-0/0/25.0 - ac:4b:c8:f7:9c:64 xe-0/0/26.0 QFX3500-DC xe-0/0/4.0 - c8:1f:66:ec:e8:d3 c8:1f:66:ec:e8:d3 xe-0/0/21.0 - e4:1f:13:62:79:00 eth4 ceph-pf-frontend xe-0/0/43.0 - f8:66:f2:82:ec:70 vers QFX3500 xe-/0/0/43 4948-Datacenter 3750: 3750-CORE>show lldp neighbors Capability codes: (R) Router, (B) Bridge, (T) Telephone, (C) DOCSIS Cable Device (W) WLAN Access Point, (P) Repeater, (S) Station, (O) Other Device ID Local Intf Hold-time Capability Port ID 4948-Datacenter Gi1/0/23 120 B Gi1/47 4948-Datacenter Gi1/0/21 120 B Gi1/45 4948-Datacenter Gi1/0/22 120 B Gi1/46 4948-Datacenter Gi1/0/24 120 B Gi1/48 3750-UCS Gi1/0/25 120 B Gi1/0/25 Total entries displayed: 5 Thanks again! Sylvain

2 1

Announcement: NAV 4.5.3 released
by Morten Brekkevold 01 Sep '16

01 Sep '16

The third maintenance release of the NAV 4.5 series is now out. The source code is available for download at Launchpad [1]. A new package for Debian Jessie has been published in our APT repository [2] as usual (and the virtual appliance is being updated). Changes ======= The following reported bugs have been fixed: * LP#1592747 (Cisco chassis serial number decoding report should include modules as well) * LP#1597666 (No data collected on some Comet web probes) * LP#1608869 (graph widget does not update) * LP#1608920 (make graph widget time controls optional) * LP#1619136 (Specifying both starttime and endtime values crashes the arp API endpoint) * LP#1619138 (Searching for IP addresses in the arp API endpoint is horribly inefficient) The fix for LP#1619138 also entails that searching for IP prefixes is also possible on the `arp` API endpoint. Happy NAVing everyone! Links ===== [1] https://launchpad.net/nav/4.5/4.5.3 [2] https://nav.uninett.no/install-instructions/#debian -- Morten Brekkevold UNINETT AS

1 0

SNMPv3
by Jeff Stone 08 Aug '16

08 Aug '16

Hello All, New to NAV and really liking the product but we use SNMPv3 on our switches and we cannot see any support for v3. Is this supported or how do I get this working ? Thanks Jeff

3 2

NAV and API exports
by Mischa Diehm 22 Jul '16

22 Jul '16

Hi, We are programming an inventory tool that uses NAV as one of its main datasources. We are now trying to get the Serial (lots of cisco here) for a given device. In the ipdevinfo overview we see the serial (for stacks there are even the stackmembers with serials listed). My questions is if we there is a way to get this information through the API and if yes how we could retrieve it? My second questions is if there is an easy documented way to extend the API with stuff like that or e.g. Status info like „is the box currently online“? Is there a roadmap towards what should and will be implemented regarding the exporsure through the API (maybe even write stuff?) Thanks a lot, Mischa -- Mischa Diehm | Network Team (NINS) UniBasel | IT-Services (ITS) Klingebergstr. 70 | CH-4056 Basel Tel. +41 61 267 1574 | https://its.unibas.ch

2 1

Announcement: NAV 4.5.2 released
by Morten Brekkevold 30 Jun '16

30 Jun '16

The second maintenance release of the NAV 4.5 series is now out. The source code is available for download at Launchpad [1]. A new package Debian Jessie has been published in our APT repository [2] as usual (and the virtual appliance is being updated). Changes ======= The following reported bugs have been fixed: * LP#1567939 (add buttons to change time period in statistics widget) * LP#1575112 (Missing switch ports and CAM data from Aruba switches (S2500)) * LP#1594271 (Sensors with non-ASCII names or descriptions may cause errors in status widget and status page) * LP#1595445 (Some or all enabled VLANs are sometimes missing from Cisco trunk ports) * LP#1595835 (Collect binary inputs of Comet web sensors) Happy NAVing everyone! Links ===== [1] https://launchpad.net/nav/4.5/4.5.2 [2] https://nav.uninett.no/install-instructions/#debian -- Morten Brekkevold UNINETT AS

1 0

How patch points works?
by Davide Miccone 27 Jun '16

27 Jun '16

Release notes for 4.5 states that "Information about patch points is now also displayed on each port's ipdevinfo page". I created in Seed DB a new cabling and than a patch to connected to device port but in ipdevinfo page I can't see nothing. Please how patch points works? Tahnk you

2 1

Announcement: NAV 4.5.1 released
by Morten Brekkevold 16 Jun '16

16 Jun '16

The first maintenance release of the NAV 4.5 series is now out. The source code is available for download at Launchpad [1]. A new package Debian Jessie has been published in our APT repository [2] as usual (and the virtual appliance is being updated). Changes ======= The following reported bugs have been fixed: * LP#1591973 (navstats binary is not installed in NAV 4.5.0) * LP#1592281 (ipdevpoll statuscheck errors out on some Aruba switches) * LP#1593193 (Race condition may make eventengine ignore events at random) Happy NAVing everyone! Links ===== [1] https://launchpad.net/nav/4.5/4.5.1 [2] https://nav.uninett.no/install-instructions/#debian -- Morten Brekkevold UNINETT AS

1 0

Announcement: NAV 4.5.0 released
by Morten Brekkevold 09 Jun '16

09 Jun '16

The initial 4.5 series release of NAV is now out. The source code is available for download at Launchpad [1]. A new package for Debian Jessie is published in our APT repository [2], as usual. With this release, we discontinue our packaging support for the old Debian Wheezy release. If you wish to package for Wheezy yourself, you can fork the packaging code located at [3]. The virtual appliance will be updated shortly. Changes ======= NAV 4.5 introduces the following user-visible features and improvements: * LP#1321249 (A new tool for generating Graphite metrics from PostgreSQL queries) * LP#1531851 (Trend comparison in graphs) * LP#1531853 (API: more flexible authorization and administration) * LP#1534481 (Maintenance task selection based on device group) * LP#1546434 (Add bulk upload of images in room view) * LP#1577318 (Add timestamp filtering to cam and arp API) * LP#1588187 (Cabling/patch registration and presentation in need of serious usability improvements) These reported bugs have been fixed: * LP#1551217 (Alert from 3rd party - maintenance mode not respected) [the 4.4.4 release did not fix the eventengine part of this issue, this release does] * LP#1590654 (Lost ipdevpoll database connections aren't properly reset under Django 1.7) Happy NAVing everyone! Links ===== [1] https://launchpad.net/nav/4.5/4.5.0 [2] https://nav.uninett.no/install-instructions/#debian [3] https://bitbucket.org/mbrekkevold/nav-debian/ -- Morten Brekkevold UNINETT AS

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