Nav-users November 2009

nav-users@lister.sikt.no

6 participants
5 discussions

installation on ubuntu 9.04
by vvatikiotis＠gmail.com 07 Jan '10

07 Jan '10

Hello all, I'm trying to install nav on ubuntu 9.04 and this fails cause of 2 (only 2) dependency failures. a) python < 2.5. 9.04 has python 2.6. b) postgress = 8.1. Ubuntu has postgres 8.3 Is it necessary to pin these 2 dependency versions ? I have knowledge of python but I'd assume that 2.6 is good enough against 2.5 source code. Same goes for postgres Correct me if I'm wrong. In the mean time I'l try to force install nav. btw, seems VERY promising. thx all vassilis

4 4

Possible maintainers of a Redhat/EPEL NAV package
by Stokkenes Vidar 25 Nov '09

25 Nov '09

Hello everyone, This is probably a very delicate request, so I'll try to keep myself short. Due to our companys policies, we are trying to run everything in production on Redhat Linux servers. This is a problem when it comes to NAV, as the maintainer of the old Redhat RPM package is MIA, and no one else have really stepped forward to continue his work. I am aware of that compiling NAV from source is a viable option for someone, but considering I'm a repository maniac I would like to see Redhat on a somewhat "public" Redhat repository. We are currently undermanned and don't really have time to develop or maintain the package ourselves. However we do have resources to hire an external consulant to make the package for us. So therefor I am wondering. Lets say we hire someone to get NAV packed for Redhat Linux and submit it to EPEL, are there anyone more RPM/EPEL experienced than me who are interested in maintaining and committing new changes to the package? I've already contacted consulants at (Linpro) Redpill and gotten a time/cost estimate to develop the package. Now I just need someone volunteers to maintain the package once it's been initially set up (preferably people with commit access on EPEL) Any help or inputs would be appreciated! Best regards, ------------------------------------------------------ Vidar Stokkenes Networking Consulant Networking and telecom Department Helse Nord IKT - Tromsø Phone: (+47) 76 16 61 87 or (+47) 77 66 99 55 Cell: (+47) 95 87 99 42 e-mail: vidarst(a)hn-ikt.no

1 0

Cabling and patch data removed in NAV 3.6?
by Vidar Faltinsen 13 Nov '09

13 Nov '09

nav-users, As you might know there is ongoing work on preparing a NAV 3.6beta. In 3.6 there are some changes to the database, i.e the interfaces will now relate directly to the netbox (switch or router), not to a module. We will still keep module information, but the strict mapping from interface to module is changed. This effects a number of front end (and back end) tools and we are in the process of updating it all. One system that is effected is the seed database subtool where you can add data on your twisted pair cabling and your patches from switch to jack in the wiring closets. We are seriously considering _not_ to maintain/keep this tool from 3.6. Our feeling is that _not_ many people use this part of NAV. It has never given full effect since the machine tracker does not include these data in its search results (which has been our intention of course). We also argue that by using sensible interface description naming standards you will in effect document the same data. I.e. if you set the jack number and room number as description of the switch ports that are patched to your end users/offices you have these data. The "details" link under interface in the MAC search results in machine tracker give this information (it displays the interface view of ip device info). In my opinion you should in fact do this documentation as part of your interface description, because this is useful when working directly with the switch through the CLI. Should you then double the work and do it both in the seed database patch register in addition?... Another argument is that other systems do cabling documentation more comprehensive. NAV has i.e. no support for documenting your fibre cabling. A system like Telemator (http://www.mxdata.no/) or equivalent cabling information systems do this better. Looking at integration between these systems and NAV is of course interesting. I know the University of Tromsø has done some interesting work here. Yet another mishap with the NAV patch register is that when you replace your switch with a new one, you will in the process loose your patch data for the switch and will have to do this registering from scratch again. So people out there - who is going to miss the patch and cabling part of NAV? Best regards, - Vidar

1 0

Re: EdgeCore ES4612 no port info
by Morten Brekkevold 10 Nov '09

10 Nov '09

On Mon, 09 Nov 2009 14:49:55 +0200 Kostua <kostua(a)innkom.zp.ua> wrote: >> I hope I will find something useful from the getDeviceData.log that >> can tell me why this happens. >> >> > ok, done. sending attachment. [...] > Nov 08 10:34:57 2009 172.16.2.49_13 CGW_DEVHANDLER-4-PROCESS_CGW Oidkeys [ifDescr, ifSpeed] are required, but not supported by 172.16.2.49, type ES4612, unable to fetch data! This tells me that the OID profile of the device is lacking, for some unknown reason. Please browse to Toolbox -> Report and search for 172.16.2.49 in the "IP Device Report" search box. What is the number in the "snmp" column? What is the list of oidkeys reported when you click on the number in the snmp column? To make getDeviceData re-profile the device, browse to Toolbox -> SeedDB -> IP Devices Edit, find 172.16.2.49 and edit it. Don't change anything, just click the "Update" button and finish the procedure. To speed things up, you can then restart getDeviceData. Tail getDeviceData.log and verify that you get several log messages from OID_TESTER about 172.16.2.49. When the messages stop appearing, please check the snmp column in the IP device report again. -- mvh Morten Brekkevold UNINETT

1 0

Re: EdgeCore ES4612 no port info
by Kostua 06 Nov '09

06 Nov '09

Ok. I recently moved NAV from vmware to dedicated server, and Cricket began to draw traffic graph. In "IP Device Info" show right numbers of ports (8) but port status of all ports indicated "Not active"

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 November 2009