Nav-users October 2014

nav-users@lister.sikt.no

3 participants
4 discussions

NAV mac-search with Nexus and FabricPath
by Mischa Diehm 09 Apr '15

09 Apr '15

Hi, we have FP activated in our datacenter and use Cisco Nexus (5,6,7)k. I'm not sure what caused the problem but NAV can't find MAC-addresses on these devices and even on catalysts behind them anymore. I don't know what algorithm is used to figure out where a MAC-address is attached but maybe someone who knows can clarify what is needed for that to work? Thanks in advance, Mischa -- Mischa Diehm | Network Operations Center (NOC) UniBasel | UniRechenZentrum (URZ) Klingebergstr. 70 | CH-4056 Basel Tel. +41 61 267 1574 | http://urz.unibas.ch

2 7

Announcement: NAV 4.1.2 released
by Morten Brekkevold 30 Oct '14

30 Oct '14

The second maintenance release of the NAV 4.1 series is now available, version 4.1.2. The source code is available for download at Launchpad [1]. A new package for Debian Wheezy has been published in our APT repository [2]. Changes ======= The following reported issues have been fixed in the new release: * LP#1236387 (Netbiostracker doesn't handle MAC addresses with hyphens) * LP#1248084 (The heading "devices going down" in ipdevinfo affected tab should be changed to "devices unreachable") * LP#1359111 (Problem getting inventory for HP 5412R) * LP#1370051 (Whitespace in machinetracker widget causes stacktrace) * LP#1370517 (Several search views throw 500 exceptions where a 404 Not Found would be appropriate) * LP#1371026 (ipdevpoll topo job fails with AttributeError) * LP#1373841 (link from subnet matrix to machinetracker gives no results) * LP#1374391 (graph widget should have a target url attribute) * LP#1375749 (Maintenance calendar does not display task starting previous month) * LP#1380583 (Python requirements in install doc are out of sync with requirements.txt) * LP#1382460 (Ambiguous search input crashes l2trace) * LP#1382492 (Machine tracker searches crash when results include devices that haven't had any ipdevpoll jobs run against them) * LP#1382522 (Radius accounting search crashes when searching for hostname that cannot be found in DNS) * LP#1383624 (Machine Tracker should search uplink data as well) * LP#1383625 (Machine Tracker MAC search should also search physical port addresses) * LP#1384262 (Add unrecognized neighbor search to navbar) * LP#1387215 (Rubbish CDP neighboring port data crashes topo job) * LP#1387598 (ip2mac and inventory jobs crash with "IPv4 Address with more than 4 bytes" on some Cisco devices) Please refer to the release notes [3] for further information on upgrading from versions prior to 4.1. Happy NAVing everyone! Links ===== [1] https://launchpad.net/nav/4.1/4.1.2 [2] https://nav.uninett.no/wiki/nav_on_debian [3] https://nav.uninett.no/doc/4.1/release-notes.html -- Morten Brekkevold UNINETT AS

1 0

SNMP agent down
by Steve Kersley 13 Oct '14

13 Oct '14

I'm trying out the NAV virtual appliance (4.1.0), talking to 25 or so Cisco switches. It was working fine but after a few weeks, one of the switches is showing a problem, "SNMP agent down". The SNMP agent is not down. The switch is fine, its configuration hasn't changed. I can talk SNMP to it fine using the same credentials from other machines, and the NAV VM can talk SNMP fine to all of the other switches - all have the same SNMP credentials, and most are the same model of Cisco switch. (I was going to test from the NAV VM or watch the network traffic but the appliance doesn't come with the snmp tools or tcpdump, and is isolated from the Internet so not easily able to install them) Restarting the switch made no difference. I've had a rummage in the logs without seeing anything obvious. Any clues where to look to find why NAV is unable to talk SNMP to this one switch suddenly, after working fine for several weeks? Steve.

2 2

Unmanaged switches
by pentium100＠gmail.com 13 Oct '14

13 Oct '14

Hello, Is there a way to insert an unmanaged switch to the network map? I use some of them in my network and would like to mark them on the map. Right now I have real network topology something like this: Router -- managed switch -- unmanaged switch -- devices Only one devices on the unmanaged switch is shown, even though multiple MACs are detected on the relevant port of the managed switch. Is there a way to mark that there is an unmanaged switch so that those devices are drawn on the map (with link speed/usage pulled from the devices if possible)?

2 1

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Nav-users October 2014