Nav-users

nav-users@lister.sikt.no

1 participants
1378 discussions

Problem with Network explorer after upgrading to 3.4/3.4.2 and an issue with c6509-E
by Rikard Stemland Skjelsvik 01 Aug '08

01 Aug '08

Dear all, I have a small issue with Nav after upgrading to 3.4 When i click on the link to Network explorer, i get the following error: HTTP Status 404 - /navAdmin/servlet/navAdmin type Status report message /navAdmin/servlet/navAdmin description The requested resource (/navAdmin/servlet/navAdmin) is not available. Apache Tomcat/5.5 The catalog /var/www/nav/navAdmin only includes .htaccess and an index file that is zero bytes. I am running Debian and i upgraded from a previous version(where network explorer worked) with the apt-get dist-upgrade command. My google-fu came up with a previous poster where Morten Brekkevold replied: NAV contains two Java servlets, vPServer.war and navAdmin.war . These are usually installed in the apache/webapps/ directory, and should be symlinked into Tomcat's webapps directory (wherever your Tomcat installation may be, you don't mention which distro you are using). The catalog /var/www/nav/vPServer, as /var/www/nav/navAdmin, includes only .htaccess and index. A find reveals that both vPServer.war and navAdmin.war is installed in /var/lib/tomcat5.5/webapps/ I would apreciate any help or pointers that could help me solve this problem. As a side note: When adding a Cisco 6509 running s72033_rp-ADVIPSERVICESK9_WAN-M), Version 12.2(33)SXH1, RELEASE SOFTWARE (fc3) to NAV, the cpu on the 6500 went through the roof. This could be a bug, though, i have seen CiscoWorks doing the same before. Any ideas? Is there a way to "nice" NAV on some types of equipment? Regards, Rikard

2 4

questions on MetaNAV about ipv6
by yongkai Jiang 01 Aug '08

01 Aug '08

hi all, I am writing this letter to ask some questions about ipv6 support on MetaNAV. We are investigating into MetaNAV3.4 to manage ipv6 networks. In MetaNAV3.4.0 release note, it says that the system supports ipv6 now. I am a new comer to MetaNAV and know little about SNMP and ipv6 at the moment. So I wonder what does it means by supporting ipv6? Does it means that it has full support on it? eg, can metanav discover an ipv6 device and query related information from it(cpu,load, etc.)? Does it auto-discover the topology in an ipv6 vlan? Can it deal with ipv6 addresses? ... Thanks in advance! Best regards! Sincerely, Richard July 30, 2008

2 1

no such checker: oracle ?
by Stokkenes Vidar 31 Jul '08

31 Jul '08

Hello, As I've recently managed to set up my Siemens SMS gateway properly with the latest gammu, I want to make a profile to monitor our Oracle cluster with NAV and send a notification when its down. While adding the premade "oracle" service to a server (SRV) object, "servicemon" gives me the following error in servicemon.log: [2008-07-31 15:06:38] db.py:getCheckers:226 [Critical] no such checker: oracle [2008-07-31 15:06:38] db.py:getCheckers:226 [Critical] no such checker: oracle [2008-07-31 15:06:38] db.py:getCheckers:226 [Critical] no such checker: oracle [2008-07-31 15:06:38] db.py:getCheckers:226 [Critical] no such checker: oracle [2008-07-31 15:06:38] db.py:getCheckers:226 [Critical] no such checker: oracle [2008-07-31 15:06:38] db.py:getCheckers:226 [Critical] no such checker: oracle [2008-07-31 15:06:38] db.py:getCheckers:226 [Critical] no such checker: oracle [2008-07-31 15:06:38] db.py:getCheckers:226 [Critical] no such checker: oracle [2008-07-31 15:06:38] db.py:getCheckers:226 [Critical] no such checker: oracle [2008-07-31 15:06:38] db.py:getCheckers:226 [Critical] no such checker: oracle [2008-07-31 15:06:38] db.py:getCheckers:226 [Critical] no such checker: oracle This kinda tells me that the premade service called "oracle" is either defunct or just a limbo... But why is it in the list when it doesn't seem to be working? And how can I "recreate" this service in NAV? (I know which ports to probe, etc) I tried to look around with"find" and "locate", but I can't seem to find the location where I can add/edit these premade services (http/https/ssh/dc/oracle/dns, etc) Any help would be appreciated! ------------------------------------------------------ Vidar Stokkenes Konsulent Nettverk Seksjon for nettverk og telekom HN IKT - Tromsø Tlf: 76 16 61 87 / 77 66 99 55 Mobil: 95 87 99 42 e-post: vidar.stokkenes(a)hn-ikt.no<mailto:vidar.stokkenes@hn-ikt.no> [cid:image001.png@01C8F31F.82A227E0]

1 0

NAV and firewalls
by Fredrik Holmberg 24 Jul '08

24 Jul '08

Hi everyone, Testing NAV (3.4.0) in a LAN environment where there are no internal/managed routers (managed by ISP), only firewalls (Check Point NGX R61) connecting the subnets. What is considered best practice when adding these devices in NAV? Can all the features be available in such a LAN setup (prefix matrix report, netmap/traffic map, "connected to" column in switch port report, machine tracker etc.)? The rest of the networking equipment (switches, servers) is up and running. Kind regards, Fredrik Holmberg

2 1

Some questions about Edit Database
by Christian Baensch 24 Jul '08

24 Jul '08

Hello, we´re actually testing your magnificant nms and we´ve some questions about "Edit Database" a) Is it possible to add/edit the default categories for the ip devices; e.g. "category=gsw" or "category=wlan" b) Is it possible to change the "Function" description of an aviable ip device; e.g. Funcion=Network Thanks in advance and with kind regards from germany!! Christian Baensch -- Christian Baensch, Kommunikationssysteme Friedrich-Alexander-Universitaet Erlangen-Nuernberg, Germany Regionales Rechenzentrum Erlangen (RRZE) christian.baensch(a)rrze.uni-erlangen.de www.rrze.uni-erlangen.de

2 1

SQL errors in NAV 3.4
by Morten Brekkevold 21 Jul '08

21 Jul '08

Hello everyone, While testing Werner's upcoming Debian package of NAV 3.4.1, we discovered some bugs in the SQL scripts that initialize the NAV database, see [1] for details. Two of the problems described in [1] will affect anyone who has initialized a new NAV database while installing NAV 3.4.0 or 3.4.1 from scratch. These two problems are potentially serious if you value the correctness of your machine tracker data. Whenever your delete an IP Device from NAV, there are two database rules making sure that every machine tracker entry related to this IP Device is closed. If you are affected, these rules will not have been defined, and all open records related to an IP Device will stay open as the device is deleted. The third problem is relatively minor. It only affects those who have initialized the NAV database on PostgreSQL 8.3 or newer. When a service check is deleted, a database rule removes NAV's knowledge of the service response time RRD file. Other parts of NAV will automatically remove this when it sees the file has gone 30 days without being updated. To summarize: If you upgraded to NAV 3.4 from an older version, and you do not run PostgreSQL 8.3 or newer, you do not need to take any action. If you are affected by the above problems, you can either wait for NAV 3.4.2, which we hope to release shortly, or you can apply the attached, short SQL script in your NAV manage database (using psql). [1] http://sourceforge.net/support/tracker.php?aid=2023345 -- mvh Morten Brekkevold UNINETT /* * * This SQL script is designed to upgrade your NAV database from * version 3.4.0 or 3.4.1 to 3.4.2. * * This script is only necessary if either: * * 1. You installed NAV 3.4 from scratch, creating a new database. * * or * * 2. You installed NAV on a PostgreSQL version 8.3 database. * * * NAV 3.4.1 and 3.4.1 were shipped with a manage.sql containing a * couple of errors in the order of which relations and rules were * created, and also a small typecasting error only present on * PostgreSQL 8.3 and newer (See SF#2023345 for more details). * * * Run the script as the nav database user like this: * * psql -f 3.4.2.sql manage nav * */ BEGIN; -- Redefine these two rules to make sure that they actually are -- present. CREATE OR REPLACE RULE netbox_close_arp AS ON DELETE TO netbox DO UPDATE arp SET end_time=NOW() WHERE netboxid=OLD.netboxid AND end_time='infinity'; CREATE OR REPLACE RULE netbox_close_cam AS ON DELETE TO netbox DO UPDATE cam SET end_time=NOW() WHERE netboxid=OLD.netboxid AND end_time='infinity'; -- Redefine this rule to make sure it is present also on a PostgreSQL -- 8.3 database. CREATE OR REPLACE RULE rrdfile_deleter AS ON DELETE TO service DO DELETE FROM rrd_file WHERE key='serviceid' AND value=old.serviceid; WHERE key='serviceid' AND value=old.serviceid::text; COMMIT;

1 0

NAV and HP ProCurve Switches
by Stokkenes Vidar 25 Jun '08

25 Jun '08

Hello, This might be a stupid question, but can someone with HP ProCurve equipment please guide me through the progress of getting them to work with NAV? I've added the device (HP Procurve 2824) in the database, but NAV doesn't seem to be pulling port info from the switch. The switchview shows it's been polled, but there is no "portview" on the polled switch. Any ideas? Any input is appreciated. ------------------------------------------------------ Vidar Stokkenes Konsulent Nettverk Seksjon for nettverk og telekom HN IKT - Tromsø Tlf: 76 16 61 87 / 77 66 99 55 Mobil: 95 87 99 42 e-post: vidar.stokkenes(a)hn-ikt.no<mailto:vidar.stokkenes@hn-ikt.no> [cid:image001.png@01C8D6C3.7182BF60]

1 0

The new IP device Info interface (django based) fails
by Stokkenes Vidar 16 Jun '08

16 Jun '08

Hello, After upgrading my system to NAV 3.4.0 (apt-get dist-upgrade) I get the following error when searching for a random device on the new IP Device Info feature: Mod_python error: "PythonHandler django.core.handlers.modpython" Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/mod_python/apache.py", line 299, in HandlerDispatch result = object(req) File "/var/lib/python-support/python2.4/django/core/handlers/modpython.py", line 189, in handler return ModPythonHandler()(req) File "/var/lib/python-support/python2.4/django/core/handlers/modpython.py", line 162, in __call__ response = self.get_response(request) File "/var/lib/python-support/python2.4/django/core/handlers/base.py", line 132, in get_response return callback(request, **param_dict) File "/var/lib/python-support/python2.4/django/views/defaults.py", line 89, in server_error t = loader.get_template(template_name) # You need to create a 500.html template. File "/var/lib/python-support/python2.4/django/template/loader.py", line 79, in get_template source, origin = find_template_source(template_name) File "/var/lib/python-support/python2.4/django/template/loader.py", line 72, in find_template_source raise TemplateDoesNotExist, name TemplateDoesNotExist: 500.html Any ideas what this might be? Oh, when looking at the new Netmap beta, it also turns out to be blank every time :( Any help appreciated! ------------------------------------------------------ Vidar Stokkenes Konsulent Nettverk Seksjon for nettverk og telekom HN IKT - Tromsø Tlf: 76 16 61 87 / 77 66 99 55 Mobil: 95 87 99 42 e-post: vidar.stokkenes(a)hn-ikt.no<mailto:vidar.stokkenes@hn-ikt.no> [cid:image001.png@01C8CF8E.64014690]

3 5

Announcement: NAV 3.4.0 released
by Morten Brekkevold 06 Jun '08

06 Jun '08

NAV 3.4.0 final is now available for download. As SourceForge's upload system is currently unavailable for maintenance reasons, the source tarball can be downloaded from the MetaNAV web site: http://metanav.uninett.no/files/nav-3.4.0.tar.gz (md5 checksum: 8ee1b3739db7c5af2b07987ea3f6d2bb) This is a feature release, the list of features and bugs fixed can be found in the attached changelog. Changes since the release candidate include a small regression in a CSS stylesheet, and some added schema changes that were missing the first time around. Binary packages for Debian will be available soon. The Debian package is maintained by Morten Werner Forsbring, on commission from UNINETT. Happy NAVing everyone! -- mvh Morten Brekkevold UNINETT

3 5

Funky Network Explorer error
by Stokkenes Vidar 04 Jun '08

04 Jun '08

Hello there, For some reason I've started to get a "random" error when accessing the Network Explorer map on my NAV installation. Can someone please tell me what might be wrong? Here is the error output in my browser: Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/nav/web/pyproxy/proxy.py", line 61, in handler user=user, session=req.session.id) File "/usr/lib/python2.4/site-packages/nav/web/pyproxy/proxy.py", line 124, in doRequest request.request(method, path, query, headers) File "httplib.py", line 804, in request self._send_request(method, url, body, headers) File "httplib.py", line 827, in _send_request self.endheaders() File "httplib.py", line 798, in endheaders self._send_output() File "httplib.py", line 679, in _send_output self.send(msg) File "httplib.py", line 646, in send self.connect() File "httplib.py", line 630, in connect raise socket.error, msg error: (111, 'Connection refused') Any ideas? Thanks. ------------------------------------------------------ Vidar Stokkenes Networking Consulant Dep. for networking og telecommunications HN IKT - Tromsø Tlf: 76 16 61 87 / 77 66 99 55 Cell: 95 87 99 42 e-mail: vidar.stokkenes(a)hn-ikt.no<mailto:vidar.stokkenes@hn-ikt.no> [cid:image001.png@01C8C22E.0DC9C3F0]

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