Nav-users

nav-users@lister.sikt.no

1373 discussions

Re: Possible to include columns in status widget?
by Ingeborg Hellemo 13 Des '16

13 Des '16

> > john.m.bredal(a)uninett.no said: > > Having more columns in the widget makes it very crowded. > > We realize that will be an issue, especially on mobile devices. > > > john.m.bredal(a)uninett.no said: > > The only way I think we can do that is to make it configurable what columns > > you show in the widget (and in the status-page). That is absolutely possible. > > That would be perfect. We need organization to show, others could need > something else. Got my hands on NAV 4.6.0, found the "Extra columns" in the status widget. And could only choose between Location and Room. What happened to Organization? Seriøst!! --Ingeborg -- Ingeborg Østrem Hellemo -- ingeborg.hellemo(a)uit.no Dep. of Information Technology --- Univ. of Tromsø

2 1

NAV : add port activity graphs
by Orzakiewicz Cedric 07 Des '16

07 Des '16

Hi, Can anyone explain how to get activity graph of a switch port in NAV 4.6.0 ? Thanks.

2 6

Update device name
by Orzakiewicz Cedric 06 Des '16

06 Des '16

Hi, I am running NAV 4.6.0 I successfully added some devices. Then I noticed that they had no name, only their IP as device name. So I added the corresponding entries to my DNS server. Unfortunately, NAV has kept the IP as name and does not update the device name field automatically. Can anyone help me on this issue ? Thank you.

2 2

Announcement: NAV 4.6.0 released
by Morten Brekkevold 01 Des '16

01 Des '16

The initial 4.6 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. The virtual appliance will be updated shortly. Changes ======= As always, we recommend you read the release notes [3] for a fuller description of the new features and significant changes. NAV 4.6 introduces the following user-visible features and improvements: * LP#1248086 (alert on loss of redundancy in an aggregated (portchannel) link) * LP#1531850 (more flexible system for location of equipment) * LP#1634874 (choose columns in status widget) * LP#1646405 (Improve functions for IP Address Management [IPAM]) * LP#1646408 (prefix details page) * LP#1646411 (Collect and store static routes) * LP#1646413 (Work around buggy Q-BRIDGE-MIB implementation in Juniper EX switches) * LP#1646416 (Add a command line program to manipulate NAV users) These reported bugs have been fixed: * LP#1626856 (ipdevpoll inventory job crashes if a device reports multiple modules with the same name) * LP#1629823 (prefix usage api endpoint lists empty results) * LP#1630506 (Arnold detention crashes when switch reports SNMP agent error) * LP#1634903 (LLDP topology bug when two devices share the same initial sysname) * LP#1638568 (Incomplete topology information causes eventengine to post boxShadow alerts instead of boxDown alerts) * LP#1640714 (Erroneous interpretation of LLDP-MIB port numbers may cause wrong topology to be detected) * LP#1641522 (Chart Widget unresponsive) Happy NAVing everyone! Links ===== [1] https://launchpad.net/nav/4.6/4.6.0 [2] https://nav.uninett.no/install-instructions/#debian [3] https://nav.uninett.no/doc/4.6/release-notes.html#nav-4-6 -- Morten Brekkevold UNINETT AS

1 0

api alert severity level
by Biselx Nicolas 28 Nov '16

28 Nov '16

Hi, In the API alert, all results come with the same severity, 50. Is there a way to have different values, depending on the alerts ? Thanks Nicolas { "subject": "Power Supply 1 at ca-test4503e-8", "subject_url": "/ipdevinfo/ca-test4503e-8.epfl.ch/#!powerfans", "subject_type": "PowerSupplyOrFan", "on_maintenance": false, "acknowledgement": null, "event_history_url": "/devicehistory/history/?eventtype=e_psuState", "netbox_history_url": null, "device_groups": [ "TEST" ], "alert_type": { "name": "psuNotOK", "description": "A PSU has entered a non-OK state" }, "event_type": { "id": "psuState", "description": "Reports state changes in power supply units" }, "start_time": "2016-11-25T14:05:44.858", "end_time": "infinity", "id": 19198, "source": "powersupplywatch", "device": 2292, "netbox": 237, "subid": "237", "value": 100, "severity": 50 }, { "subject": "ca-test3850", "subject_url": "/ipdevinfo/ca-test3850.epfl.ch/", "subject_type": "Netbox", "on_maintenance": false, "acknowledgement": null, "event_history_url": "/devicehistory/history/?eventtype=e_boxState", "netbox_history_url": "/devicehistory/history/?netbox=1873", "device_groups": [], "alert_type": { "name": "boxDown", "description": "Box declared down." }, "event_type": { "id": "boxState", "description": "Tells us whether a network-unit is down or up." }, "start_time": "2016-11-25T11:06:58.413", "end_time": "infinity", "id": 19197, "source": "pping", "device": null, "netbox": 1873, "subid": "", "value": 1, "severity": 50 }

2 1

NAV Migration
by a.anderson＠tees.ac.uk 24 Nov '16

24 Nov '16

Hi We recently upgraded from 4.4.3 to 4.5.3 by building a new server with the supplied ovf file, and migrated the database using the procedure referenced in the following link. https://nav.uninett.no/doc/4.5/howto/migrate-data.html The cli command we used to restore used the --drop-database --create --restore switches on the new server. We now not the directory structure seems for the cam, arp folders is now / api/1/arp, whereas on the 4.4.3 box it was /api/arp. Is this due to the restore method we have used or has the directory structure changed Many thanks

2 1

Upgrade Debian and NAV from 4.4.4 to latest
by Espen Lorentzen 23 Nov '16

23 Nov '16

Hi, we are running NAV 4.4.4 on a dedicated Debian Wheezy box with backports enabled. AFAIK we have to upgrade Debian from Wheezy to Jessie to get the latest NAV release. Can I just replace wheezy to jessie in sources.list and nav.list and do an upgrade/dist-upgrade? -- MVH / REGARDS: Espen Lorentzen esplor(a)gmail.com

2 1

Re: SNMPv3 support
by Morten Brekkevold 26 Okt '16

26 Okt '16

On Wed, 26 Oct 2016 08:33:25 +0100 Matthew Seymour <matthew.seymour(a)york.ac.uk> wrote: > Thanks for the quick response Morten, I'll keep an eye on the project and > see how things develop. We wouldn't be in a position to sponsor a project > that we don't currently use, and without snmpv3 we can't evaluate use > unfortunately. Fully understandable, Matthew. We will get SNMPv3 support, so keep your eyes open :-) -- mvh Morten Brekkevold UNINETT

1 0

SNMPv3 support
by Matthew Seymour 26 Okt '16

26 Okt '16

Hello. A fellow UK university colleague recommended NAV, and having just taken a look I've fallen at the first hurdle of SNMPv3 support. I've noticed some references to this being in worked on, is there a rough timescale for when this might be available in a release or for beta testing? Regards -- Matthew Seymour Network Technician University of York

3 2

Possible to include columns in status widget?
by Ingeborg Hellemo 06 Okt '16

06 Okt '16

We have a need to include an Organization column in the Status widget (and Status page). Is this possible? --Ingeborg

2 3

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