Nav-users

nav-users@lister.sikt.no

1376 discussions

Power supply unknown
by Ingeborg Hellemo 14 Mai '19

14 Mai '19

NAV 4.8.6 We have a Cisco catalyst switch with a broken power supply. After changing the power supply NAV shows Status "Unknown" in the /#!sensors page. The ipdevpoll jobs runs without errors. Where shall I look? --Ingeborg -- Ingeborg Østrem Hellemo -- ingeborg.hellemo(a)uit.no Dep. of Information Technology --- Univ. of Tromsø

3 4

Announcement: NAV 4.9.5 released
by Morten Brekkevold 02 Mai '19

02 Mai '19

The fifth maintenance release of the 4.9 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 available in our APT repository [2] as usual. The Debian packages for NAV 4.9 have been rebuilt using dh-virtualenv, which means that most of the Python dependencies are now embedded into the packages themselves. If you have previously added a priority apt pin for packages from apt.uninett.no, you may now remove it, as there are no longer any other packages needed from that repository to run NAV. Please also 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 is currently being updated at the time of this writing, and will be uploaded soon. Changes ======= Fixed GitHub issues in this release: * #1890 (Temperature gauges do not render if multiple threshold rules apply to it) + #1921 (Handle arbitrary number of thresholds for a given sensor) * #1902 (Sensor widgets should hyperlink to sensor's page view, not IP Device's page view) * #1903 (Topology missing for LLDP-enabled Alcatel switches) * #1906 ("Cisco chassis/module serial numbers decoded" report crashes when filtering) * #1907 (servicemon DnsChecker fails when DNS server doesn't have a matching record) * #1916 (UninettMailDispatcher does not work under NAV 4.9) * #1917 (snmptrapd needs to log more details about received traps) * #1923 (ENTITY-MIB implementation can no longer resolve physical device classes properly) + #1924 (Support cross-MIB type definitions in MibRetrievers) Please see the release notes [3] for more details. Happy NAVing everyone! Links ===== [1] https://github.com/UNINETT/nav/releases [2] https://nav.uninett.no/install-instructions/#debian [3] https://nav.uninett.no/doc/latest/release-notes.html#nav-4-9 -- mvh Morten Brekkevold Uninett

1 0

Fwd: Network Interfaces Search parameters
by BERGELIN SABADELL, IVAR-ERIC 05 Apr '19

05 Apr '19

Hello, This is Ivar Bergelin and I work at the IT department of Pompeu Fabra University in Barcelona. We use your software NAV to manage the whole network. I write to you because I have a question about the search parameters in the Netbox interfaces tab. [image: imagen.png] There is a button called "About the search" which contains the following information about search parameters: [image: imagen.png] [image: imagen.png] Is there's a place where I can find all the search parameters? In the image shows only few search examples but I would like to know all of them. I could'n find anything in the NAV's documentation. Thanks in advance. -- *Ivar Bergelin* Tècnic de suport a la docència 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

VM or Appliance forcasting
by ken.livesey＠subzero.com 28 Mar '19

28 Mar '19

Greetings, I am looking for assistance in determining respective NAV VM system parameters for managing 800-1000 Network devices across two data centers and 30 sites. Most of the network devices are Cisco and all sites are connected with high- speed and low latent connections. Please let me know if any additional information would be helpful. Thanks for your help, Ken...

3 3

Re: VM or Appliance forcasting
by Morten Brekkevold 28 Mar '19

28 Mar '19

On Wed, 27 Mar 2019 14:20:11 +0100 <ken.livesey(a)subzero.com> wrote: > Thanks for your feedback! Thanks for yours. I'm Cc-ing the mailing list once again, but leaving out most of your response here. > P.S. Any idea when SNMP V3 might be supported? No, but we're making progress on replacing the SNMP configuration attributes that are hardwired into the Netbox (IP Device) model with a more flexible management profile system. This will be useful when implementing NETCONF and/or RESTCONF, which is our current goal, but this can also be used to implement proper SNMPv3 support (since you will be able to store more than just community strings). I'm given to understand that the University of Linköping may be interested in developing support for SNMPv3, once management profiles hit the master branch. I'm also copying Pär Stolpe from LiU, so that he might comment (if he wants to) :-) -- mvh Morten Brekkevold Uninett

1 0

Announcement: NAV 4.9.4 released
by Morten Brekkevold 28 Mar '19

28 Mar '19

The fourth maintenance release of the 4.9 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 available in our APT repository [2] as usual. The Debian packages for NAV 4.9 have been rebuilt using dh-virtualenv, which means that most of the Python dependencies are now embedded into the packages themselves. If you have previously added a priority apt pin for packages from apt.uninett.no, you may now remove it, as there are no longer any other packages needed from that repository to run NAV. Please also 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 is currently being updated at the time of this writing, and will be uploaded soon. Changes ======= NB: This release introduces a new dependency to py2-ipaddress==3.4.1 Fixed GitHub issues in this release: * #1639 (Not all NAV programs respect TIME_ZONE from nav.conf) * #1762 (navdump drops function-data) * #1788 (Deleting an alert profile subscription that has queued alerts will cause alertengine to process all those alerts as if they were new ones on the queue. ) * #1885 (LDAP authentication against Microsoft AD using suffix bind is broken in NAV 4.9) * #1894 (Terminals that don't support colors cause nav start/stop commands to crash) * #1895 (Verify nav.conf values as part of nav start) * #1896 (UnicodeEncodeError when LDAP user with non-ASCII characters in DN logs in) Please see the release notes [4] for more details. 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 [4] https://nav.uninett.no/doc/latest/release-notes.html#nav-4-9 -- mvh Morten Brekkevold Uninett

1 0

Re: Re: NAV docs and papers
by Eduardo Hartmann 26 Mar '19

26 Mar '19

1 0

FW: Unused port tracking / alert
by Daniel Gryzbon 25 Mar '19

25 Mar '19

Good day, We are now testing your product and we want to know, if is possible to track or be informed if some interface is not used for some time - e.q. no MAC address visible for long time or interface is down and not administrative down for long time. For example i try to configure alert profile with matchfield value.id cam.end_time with filter not equals 9999-12-31 23:59:59.999999 and added to filter group G01:All alerts with Add operation but no alert appeared on status tab. Is possible to somehow monitor it? Thank for your help Best regards [Hyundai Autoever_Ma_07012017] Daniel Gryžbon [New motto Hyundai blue] Network Specialist Hyundai AutoEver Europe GmbH, organizační složka Hyundai 700/1, 739 51 Nižní Lhoty Tel: +420 596 14 1755 E-Mail: daniel.gryzbon(a)hyundai-motor.cz<mailto:daniel.gryzbon@hyundai-motor.cz> Website: www.hyundai-autoever.eu<http://www.hyundai-autoever.eu/>

2 1

NAV docs and papers
by Eduardo Hartmann 25 Mar '19

25 Mar '19

2 1

How to limit historical data (trends)?
by c5244714＠gmail.com 20 Mar '19

20 Mar '19

Hello, I'm using NAV 4.9.3 and have a big issue with the trend of interface traffic historical data(trend). I configured to monitor over 100 cisco switches and +2000 interfaces and the trend is consuming lot of data and deplete my storage space. the historical is a great feature with a 1 year history but its too much for us with our limited resources. My question is if there is anyway to control or limit the period of the data , lets say only 2 weeks with retention Thanks Dan

2 1

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