Nav-users April 2018

nav-users@lister.sikt.no

2 participants
4 discussions

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

netmap and lag
by Zhi-Wei Lu 09 May '18

09 May '18

Hi NAV gurus, We have a very limited test envioronment for NAV, our environment are Foundry based (->Brocade-> Arris and Extreme now). We have enabled lldp on edge switches, but not on ALL upstream routers. Even on connections with lldp on, the map does not show LAG ports correctly, it seems. Is there a manual way to fix netmap problem for those it fails to correctly identify the connections? Thank you. Zhi-Wei Lu IET-CR-Network Operations Center University of California, Davis (530) 752-0155

3 7

Sizing the NAV server
by Zhi-Wei Lu 09 May '18

09 May '18

Hi NAV gurus, I have been testing NAV on and off for a while with a fraction of our devices on a small VM. I like it more and more as I am getting used to it. I would like to get recommendation of a NAV setup that can handle our environment. Our network is layered like the following: Border Router: 2 Core and Area Router: ~30 Building Router: ~100 Edge Switch: ~1500 Shall we use one big server or multiple servers, physical or virtual for various NAV management components? What CPU, MEMORY, DISK IO, and DISK size shall we plan for? Thank you very much for your help. Zhi-Wei Lu IET-CR-Network Operations Center University of California, Davis (530) 752-0155

2 1

Announcement: NAV 4.8.4 released
by Morten Brekkevold 05 Apr '18

05 Apr '18

The fourth maintenance release of the 4.8 series of NAV is now out! The source code is available for download at GitHub [1]. New packages for Debian 8/9 (Jessie/Stretch) are published in our APT repository [2], as usual. The virtual appliance will be updated shortly. Changes ======= Fixed GitHub issues: * #1638 ('array index out of range' when viewing a trunk port in PortAdmin) * #1643 (Location with active alerts - edit title) * #1650 (Submitting a threshold rule without a target crashes with a KeyError) * #1655 (Auditlog only displaying the first 100 entries in the log) + #1654 (Fix broken auditlog browsing and auditlog more things) * #1656 (Sensor widget crashes when sensor is missing) * #1660 (UninettMailDispatcher does not support non-ASCII characters and requires SMTP server on localhost) * #1661 (Business reports, link availability - want description) * #1664 (Remove bracket syntax for url parameters to Graphite) * #1665 (Interface details tries to get sensor data on empty sensorlist) * #1669 (Shouldn't use CAM to select topology for aggregated ports where LLDP is available on the physical ports) + #1685 (Do not consider CAM data from aggregator ports when there is LLDP/CDP topology available from its aggregated ports) * #1670 (Treshold editor doesn't work for metrics with hash characters in name) * #1673 (Repeated traceback e-mails for Internal Server Error: /netmap/traffic/layer2/) * #1676 (Audit log changes to API tokens) * #1677 (ipdevinfo should link to an IP Device's audit log) * #1678 (EventMixIn.get_subject() should never return a string) * #1680 (SeedDB patch editor only lists switch ports, not physical ports) Happy NAVing everyone! Links ===== [1] https://github.com/UNINETT/nav/releases [2] https://nav.uninett.no/install-instructions/#debian [3] https://github.com/UNINETT/nav/issues -- Morten Brekkevold UNINETT AS

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Nav-users April 2018