September 2016 - Nav-users

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

PortAdmin - save changes in HP 5130 switch?
by Mattias Söderholm 13 Feb '17

13 Feb '17

Hi. We have now inserted some HP 5130 EI (also HP 5700) switches in NAV and want to use PortAdmin. Everything works except saving to memory. The problem is the save command! For HP Procurve switches you use "save" or "write memory" commands to save changes and it's done. HP 5130 EI is a little bit different. There you must use "save force", if you only use "save" command you have to answer some questions. Can this be fixed? Regards Mattias

3 15

Additional equipment OID addition.
by tranimarc＠hotmail.com 03 Okt '16

03 Okt '16

Hi, I'm working on a project to replace all polled data collections we have running on Cacti for our network devices ( Cisco, F5, Brocade, Sanbox, ..... ) to graphite. Actually your tools is the only one using graphite out of the box and I was wondering how much work it would be to add unsupported monitoring MIBs and if there would be some example other than https://nav.uninett.no/doc/4.2/hacking/adding-environment-probe-support.html ? Actually all exotic devices are showing values for their network interfaces but most are not retrieving CPU/Memory and other specific data. Thanks Marc TRANI

2 1

Problem: NAV alerts not working
by Patricio, Oscar (Coriant - PT/Lisbon) 22 Sep '16

22 Sep '16

Hi all, I've been trying NAV out for the third time now, as I am experimenting with several similar tools. First of all, I really like NAV and it is the tool that shows the most potential from all I tried, in terms of network monitoring. BUT (there is always a but in theses emails), I am having trouble getting thresholds and their respective alerts to work. I have really kept my installation to the simples possible, so at the moment I only have one device and I have only setup one single threshold, purposefully so that it immediately is exceeded. But after I do that, there is no event and it is as though the threshold has not been exceeded. When I look into the thresholdmon.log this is what I see repeatedly: 2016-09-21 14:40:01,992 [INFO nav.thresholdmon] evaluating 1 rules 2016-09-21 14:40:02,513 [WARNING nav.thresholdmon] did not find any matching values for rule u'nav.devices.XXXXXXXXX.ports.Bridge-Aggregation1.ifInOctets' <50% 2016-09-21 14:40:02,513 [INFO nav.thresholdmon] done What does this mean? This interface has traffic and that traffic is beeing graphed without issues... So my question is: what am I missing? This is supposed to be very simple to configure but apparently does not work. Am I doing some basic error? Thank you for your attention. Best regards, Óscar

2 1

Re: ipdevpolld down
by Morten Brekkevold 19 Sep '16

19 Sep '16

On Mon, 12 Sep 2016 18:20:15 +0000 Zhi-Wei Lu <zwlu(a)ucdavis.edu> wrote: > Thank you Morten, > > The log file didn't contain much information why the ipdevpolld exits, > ... [snip] > > It appears that if I use the forward group mode (-f), ipdevpolld -f > > With the -f switch, the daemon would just exit. Is there any debug > mode on "ipdevpolld"? The `-f` switch is to run ipdevpoll in the foreground instead of the background. You will still need to add the `-s` switch if you want output to your terminal and not just to the log file. You can manipulate log levels of various parts of NAV using the `logging.conf` configuration file. There are some examples of level configuration in that file already, but you can add `nav.ipdevpoll = DEBUG` to debug-log everything ipdevpoll-related (which can be quite a lot of output). -- mvh Morten Brekkevold UNINETT

2 2

Netmap Filter
by Biselx Nicolas 13 Sep '16

13 Sep '16

Hello All, In Netmap we can filter by room or location, is there a way to filter by Device Group ? Thanks Biselx Nicolas

2 1

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