Nav-users Juni 2015

nav-users@lister.sikt.no

4 participants
4 discussions

Some beginners questions
by Per Andersson 26 Jun '15

26 Jun '15

Hello! I have just started trying NAV, and is running it on a small part of our network at the moment, and have some questions: It finds our vlans and matches them with the correct prefixes but since we don't follow the convention for naming router interfaces the net ident and description fields is either empty (most common) or a bit confusing. Is there a way to edit them manually (directly in the database?)? Any other suggestions? If I want to enter cabling, in which "direction" is it supposed to be, should I enter the wiring closet as "Room" and the office as "Target" or the other way around? /Per Andersson Chalmers IT-department

2 3

Announcement: NAV 4.3.0 released
by Morten Brekkevold 19 Jun '15

19 Jun '15

The initial 4.3 series release of NAV is now out, with only minor changes and some bugfixes since the release candidate. A big thanks to those who helped test the release candidate! The source code is available for download at Launchpad [1]. A new package for Debian Wheezy has been published in our APT repository [2] as usual (We have no packages for Debian Jessie yet, due to dependency problems and our own resource constraints). The virtual appliance download has also been updated. Changes ======= This release makes some fundamental changes to NAV's data model to improve support for non-physical devices (like Cisco VSS and Cisco VDC). Please read the release notes [3] for further information. User-visible features and improvements: * LP#744943 (Add switch to toggle display of traffic lines in Geomap) * LP#961212 (Show planned/active maintenance tasks for device in IP Device Info) * LP#1149160 (Auto-recognize HTTP URLs in reports and hyperlink them) * LP#1166695 (PortAdmin available from the toolbox) * LP#1169550 (NAV's data model should reflect modern reality, with virtual device support) * LP#1242872 (Option to turn off traffic stats in Geomap) * LP#1248081 (New interface/tool to browse unrecognized neighbors) * LP#1366895 (Report widget) * LP#1421644 (Support Weathergoose traps from external temperature sensors) Bugfixes: * LP#1233093 (Report pages crash under psycopg2 >= 2.5) * LP#1397257 (Port Admin may not work properly for any non-HP and non-Cisco device) * LP#1447973 (CDP/LLDP neighbor matching fails when multiple ports match the identification) * LP#1447999 (Existing adjacency candidate data in db is not deleted if a device's CDP cache or LLDP remote table becomes empty) * LP#1448086 (Unable to identify LLDP neighbor's port in some instances) * LP#1458826 (1minstats job crashes on invalid ENTITY-MIB references from CISCO-PROCESS-MIB) * LP#1459138 (Ignore Cisco reserved VLANs when collecting BRIDGE-MIB data) * LP#1463724 (Increase frequency of module status verification) Happy NAVing everyone! Links ===== [1] https://launchpad.net/nav/4.3/4.3.0 [2] https://nav.uninett.no/wiki/nav_on_debian [3] https://nav.uninett.no/doc/4.3/release-notes.html#nav-4-3 -- Morten Brekkevold UNINETT AS

1 1

Failed to sending mail
by nicolas.biselx＠epfl.ch 15 Jun '15

15 Jun '15

Hello, When I do an alarm, the file eventengine.log receive the alert but with the following errors and I don't receive a mail: [2015-06-12 14:08:55,014] [INFO] [pid=26242 nav.alertengine.handle_new_alerts] alert 55 queued for admin due to subscription 1 [2015-06-12 14:09:21,098] [ERROR] [pid=26242 nav.alertengine.alertaddress.send] Email raised a DispatcherException indicating that an alert could not be sent at this time: Could not send email: Connection unexpectedly closed" Traceback (most recent call last): File "/usr/lib/python2.7/logging/handlers.py", line 926, in emit smtp.sendmail(self.fromaddr, self.toaddrs, msg) File "/usr/lib/python2.7/smtplib.py", line 722, in sendmail raise SMTPSenderRefused(code, resp, from_addr) SMTPSenderRefused: (553, 'sender domain must exist', 'navcron@navappliance') Logged from file profiles.py, line 377 [2015-06-12 14:09:21,655] [INFO] [pid=26242 nav.alertengine.check_alerts] 1 new alert(s), sent 0 alert(s), 1 queued alert(s), 0 alert(s) deleted, 1 failed send(s), 0 ignored [2015-06-12 14:09:21,656] [WARNING] [pid=26242 nav.alertengine.check_alerts] Send 1 alerts failed. I configured Exim with the following parameters: dc_eximconfig_configtype='satellite' dc_other_hostnames='exinfrserv1.epfl.ch' dc_local_interfaces='127.0.0.1 ; ::1' dc_readhost='exinfrserv1.epfl.ch' dc_relay_domains='' dc_minimaldns='false' dc_relay_nets='' dc_smarthost='mail.epfl.ch' CFILEMODE='644' dc_use_split_config='false' dc_hide_mailname='' dc_mailname_in_oh='true' dc_localdelivery='mail_spool' When I test with the command 'echo "hello world" | mail -vv -s test nicolas.biselx(a)epfl.ch' The mail is sent and receive In nav.conf, I also configured DEFAULT_FROM_EMAIL=nicolas.biselx(a)epfl.ch EMAIL_HOST=mail.epfl.ch EMAIL_PORT=465 EMAIL_HOST_USER=biselx EMAIL_HOST_PASSWORD=******** EMAIL_USE_SSL=True I don't know what's wrong, Is it fair to configure Exim and nav.conf ? Is what I missed part of the configuration ? Regards, Biselx Nicolas

3 2

Django and Debian 8
by stutavares＠unirn.edu.br 08 Jun '15

08 Jun '15

Hi guys, I have a newly installed version of Debian Jessie and it doesn't install nav with the simple 'apt-get install nav'. One of the reason is the dependancy on Django, which is in version 1.7 in the packages repository. I read a post that says you are still working on this compatibility issue. Meanwhile what should I do? Wait for a new version of nav? Try and install an older verion of Debian? What are my options now to install a new nav in my network? All the best, Studart

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Nav-users Juni 2015