Nav-users

nav-users@lister.sikt.no

3 participants
1372 discussions

Problem upgrading 4.0.0 -> 4.1.1
by Martin JABUREK 23 Sep '14

23 Sep '14

Hi, I just tried to upgrade, but now I have some issues: - I had 4.0.0 working -Then I downloaded 4.1.1 and do config and make - I pip installed django-hstore - then service nav stop, make install - service nav start Now It complains that ipdevpoll failed to start and I'm also unable to log in to web interface with 500 Error. I can see this error in apache error log: [Tue Sep 23 14:04:33 2014] [error]] mod_wsgi (pid=16795): Exception occurred processing WSGI script '/usr/local/nav/lib/python/nav/wsgi.py'. [Tue Sep 23 14:04:33 2014] [error] Traceback (most recent call last): [Tue Sep 23 14:04:33 2014] [error]] File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/wsgi.py", line 219, in __call__ [Tue Sep 23 14:04:33 2014] [error] self.load_middleware() [Tue Sep 23 14:04:33 2014] [error] File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 47, in load_middleware [Tue Sep 23 14:04:33 2014] [error] raise exceptions.ImproperlyConfigured('Error importing middleware %s: "%s"' % (mw_module, e)) [Tue Sep 23 14:04:33 2014] [error] ImproperlyConfigured: Error importing middleware nav.django.auth: "cannot import name force_str" I suppose, that I missed some steps in the upgrade process. Can you please suggest, what can be done? Brgds Mat ---------------------------------------------------------------- Tento e-mail včetně příloh obsahuje důvěrné informace a je určen výhradně jeho adresátovi. Pokud jste obdržel(a) tento e-mail omylem, informujte o tom prosím odesílatele a neprodleně jej vymažte ze systému. Neoprávněné šíření, kopírování, úpravy nebo zpřístupnění jeho obsahu je zakázáno. Odesílatel neodpovídá za chyby či ztráty obsahu této zprávy vzniklé v důsledku komunikace prostřednictvím e-mailu. This e-mail and any files attached to it are confidential and intended solely for the named addressee. If you have received this e-mail in error please contact the sender and delete it from your system immediately. Illegal distribution, copying, modification and disclosure of its content is prohibited. The sender of this e-mail shall not be held liable for any errors or loss of contents that may be caused by communication via e-mail.

1 0

navsyncdb, hstore extension and superuser
by Ingeborg Hellemo 19 Sep '14

19 Sep '14

Trying to upgrade my database from 3.15 to 4.1.1. I see that the script tries to connect as user 'root' while "Creating hstore extension": Creating hstore extension in database nav psql: FATAL: no pg_hba.conf entry for host "129.242.5.180", user "root", database "nav", SSL off Failed to install the hstore extension, maybe you need to run as the postgres superuser? I can of course edit my pg_hba.conf but it will not help since my postgres superuser is 'pgsql' not 'root'. How can I make the script connect as user 'pgsql'? or Can I instead run some sql by hand? --Ingeborg

1 1

NAV API
by Jarle Teigen 08 Sep '14

08 Sep '14

Hi, A couple of short questions about NAV API: I want to search NAV for a mac address in arp, and only get back last seen. Is that possible ? An how do I do that ? Is there a feature for sorting of the results ? -- Jarle Teigen

2 1

Switch inventory isn't updated
by Bruno Galindro da Costa 15 Aug '14

15 Aug '14

At http://nav.setic.ufsc.br/report/swport, I can view my interfaces with VLANs assignments. The problem is: the information for a given netbox isn't updated. All of the jobs are running fine for that netbox (green lights in jobs list). For example: I've a set of tagged VLANs in a trunk port on that switch that isn't reported by NAV. I'll sent to Morten DEBUG logs from ipdevpolld inventory job. -- Att. Bruno Galindro da Costa

2 6

Announcement: NAV 4.1.1 released
by Morten Brekkevold 14 Aug '14

14 Aug '14

The first maintenance release of the NAV 4.1 series is now available, version 4.1.1. 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#1052804 (NoReverseMatch error on multiple pages when adding IPv6 host with no DNS name) * LP#1316599 (NoReverseMatch exception when trying to load netmap) * LP#1333170 (Disused prefixes aren't properly deleted from the database) * LP#1338548 (Searching for an apparently "invalid" hostname crashes ipdevinfo) * LP#1339575 (Room and organization data keys cannot be added using SQL without first checking for NULL values) * LP#1340193 (NAV gets confused when re-using VLAN tags for multiple broadcast domains) * LP#1340576 (Virtual status of router addresses cycles back and forth, causing net type to swing back and forth between lan and link) * LP#1355693 (Interface names not present in linkState alert messages) * LP#1355923 (dump.py -t room crash) 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.1 [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

Graphite update frequency
by Bruno Galindro da Costa 14 Aug '14

14 Aug '14

How many times NAV input data into graphite per day for a given switch port? I need to know what is the graphite update frequency of collected data of my switch ports. Is each 1 min/ 5 min...? -- Att. Bruno Galindro da Costa

3 4

Netmap showing gray traffic
by Bruno Galindro da Costa 13 Aug '14

13 Aug '14

Why netmap is showing gray traffic of my interfaces? See this print (I've removed the net prefix for security reasons): [image: Imagem inline 1] In the above example, I've put in evidence the conection beetween 251.245 and 251.247. Here are those interface graphs: *251.245:* [image: Imagem inline 3] *251.247:* [image: Imagem inline 4] -- Att. Bruno Galindro da Costa

3 9

NAV not getting LLDP information from switches
by Bruno Galindro da Costa 13 Aug '14

13 Aug '14

I've two switches: xxx.xxx.251.245 and xxx.xxx.252.121. 250.121 is connected to GigabitEthernet 1/0/5 of 251.245 251.245 is connected to GigabitEthernet 1/48 of 250.121 251.245 is a 5500G-EI 24-Port (3Com Switch 5500G-EI 24-Port Software Version 3Com OS V3.03.02s168p22 from 3com) 250.121 is a DGS-3120-48TC (DGS-3120-48TC Gigabit Ethernet Switch from dlink) All of them has LLDP enabled. This is the neighbor information on switch port 1/48 of 250.121: Port ID : 1:48 ------------------------------------------------------------------------------- Remote Entities Count : 1 Entity 1 Chassis ID Subtype : MAC Address Chassis ID : 00-1E-C1-ED-78-80 Port ID Subtype : Interface Name Port ID : GigabitEthernet1/0/5 Port Description : GigabitEthernet1/0/5 System Name : xxxxxx System Description : Switch 5500G-EI 24-Port System Capabilities : Bridge, Router Management Address Count : 1 Port PVID : 1 PPVID Entries Count : 0 VLAN Name Entries Count : 1 Protocol ID Entries Count : 0 MAC/PHY Configuration/Status : (See Detail) Power Via MDI : (See Detail) Link Aggregation : (See Detail) Maximum Frame Size : 1522 Unknown TLVs Count : 0 This is the neighbor information on switch port 1/0/5 of 251.245: LLDP neighbor-information of port 5[GigabitEthernet1/0/5]: Neighbor index : 1 Update time : 80 days,21 hours,14 minutes,30 seconds Chassis type : MAC address Chassis ID : 2810-7B68-9D90 Port ID type : MAC address Port ID : 2810-7B68-9DC0 Port description : D-Link DGS-3120-48TC R2.00.010 Port 48 on Unit 1 System name : xxxxxx System description : Gigabit Ethernet Switch System capabilities supported : Repeater,Bridge System capabilities enabled : Repeater,Bridge Management address type : ipV4 Management address : xxx.xxx.252.121 Management address interface type : IfIndex Management address interface ID : 5121 Management address OID : In NAV, the DIRECT NEIGHBORSHIP CANDIDATES reports that *another.host* is a candidate neighbor to 1/0/5 of 251.245. BUT *another.host* is physically connected in switch port 1/2 of 252.121, as reported bellow: [image: Imagem inline 3] AFAIK, Nav will use LLDP over CAM to build the network topology. But, in this case, maybe is occurring something wrong, because seems that Nav isn't collecting LLDP informations from switches to build the network topology. Another strange thing is the UNRECOGNIZED NEIGHBORS report. It is reporting that 251.245 is an unrecognized neighbor of 252.121 with lldp as source. Why?? [image: Imagem inline 4] Morten, I'll send to you by e-mail the result of these commands: root@nav:~# ipdevpolld -J topo -n xxx.xxx.252.121 root@nav:~# snmpwalk -v2c -c 1brass12 xxx.xxx.252.121 .1.0.8802.1.1.2.1.4 root@nav:~# snmpwalk -v2c -c 1brass12 xxx.xxx.252.121 .1.0.8802.1.1.2.1.3 root@nav:~# ipdevpolld -J topo -n xxx.xxx.251.245 root@nav:~# snmpwalk -v2c -c 1brass12 xxx.xxx.251.245 .1.0.8802.1.1.2.1.4 root@nav:~# snmpwalk -v2c -c 1brass12 xxx.xxx.251.245 .1.0.8802.1.1.2.1.3 -- Att. Bruno Galindro da Costa

2 6

Sysname () is already in database
by jorr＠streamguys.com 12 Aug '14

12 Aug '14

Hello, I am demoing out the NAV appliance and we have a number of physical and virtual hosts that do not have reverse DNS entries available, resolution of the IPs belonging to the hosts results in unknown.domainname.tld. When attempting to add multiple hosts to the NAV seed database, I receive errors when NAV attempts to resolve the DNS name of the host, claiming that the host already exists, despite all unique information with the exception of the failed resolution of the fqdn. Is there a work-around so that NAV does not lookup the DNS name of said devices? Sincerely, Jesse

3 4

dump.py -t room error
by Sigurd Mytting 12 Aug '14

12 Aug '14

Hi! Trying to dump rooms I get this: # /usr/lib/nav/dump.py -t room #roomid[:locationid:descr:opt1:opt2:opt3:opt4:position] Traceback (most recent call last): File "/usr/lib/nav/dump.py", line 233, in <module> main() File "/usr/lib/nav/dump.py", line 229, in main handler() File "/usr/lib/nav/dump.py", line 102, in room line.extend(['%s=%s' % x for x in room.data.items()]) AttributeError: 'str' object has no attribute 'items' Can anyone verify the same problem with Debian and UNINETT 4.1 packages? Cheers, -Sigurd

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Nav-users