Hello, anybody was successful monitoring Alcatel switches in NAV? (for example X590), especially in cricket? regards -- Woj
From woj at tstd.pl Fri Jan 13 10:12:01 2006 From: woj at tstd.pl (Wojciech Kozicki) Date: Fri Jan 13 10:12:30 2006 Subject: [Nav-users] logger.conf In-Reply-To: <200601041459.11900.woj@tstd.pl> References: <200601041459.11900.woj@tstd.pl> Message-ID: <200601131012.01521.woj@tstd.pl>
On Wednesday 04 January 2006 14:59, Wojciech Kozicki wrote:
Hello,
how should be cisco box configured to have correct analyse in NAV Syslog Analyzer?
I have cisco communicates in following format:
Jan 4 14:50:47 <router_name> 2951: Jan 4 13:50:46: %SYS-5-CONFIG_I: Configured from console by vty0 (<ip>)
I can see this communicates in NAV, but only in: https://nav_ip/logger/?error ("parsing errors" link)
I still have this problem, can anybody help? Which log I should check? regards -- Woj
From morten.vold at ntnu.no Fri Jan 13 10:46:51 2006 From: morten.vold at ntnu.no (Morten Vold) Date: Fri Jan 13 10:46:44 2006 Subject: [Nav-users] Difference between netboxid and deviceid In-Reply-To: <200601021436.k02Eabuc065387@duke.cc.uit.no> References: <200601021436.k02Eabuc065387@duke.cc.uit.no> Message-ID: <43C7770B.30508@ntnu.no>
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/01/2006 15:36, Borge Brunes uttered:
see subject.
The reason why I ask? I get a lot of these in getDeviceData-stderr.log :
SQLException for update statement: UPDATE netbox SET deviceid='4177' WHERE netboxid='374' org.postgresql.util.PSQLException: ERROR: duplicate key violates unique constraint "netbox_deviceid_key SQLException for update statement: UPDATE netbox SET deviceid='4177' WHERE netboxid='377' org.postgresql.util.PSQLException: ERROR: duplicate key violates unique constraint "netbox_deviceid_key"
manage=# select * from netbox WHERE deviceid='4177'; netboxid | ip | roomid | typeid | deviceid | ----------+--------------+----------+--------+----------+ 369 | 129.242.X.X | fp2N4119 | 16 | 4177 |
It's three Cisco AP1200 (witch different serial#) fighting about "deviceid='4177'"
A device is any networking equipment that (may) have a serial number; think of it as any device in your equipment inventory. A netbox is a device that has been assigned an IP address and is monitored by NAV (in the user interface, a netbox is usually referred to as an IP Device). The only reason I can think of why this is happening on your installation, is that two netboxes on your network are reporting the same serial number when queried by SNMP (I have actually seen this happen on a couple of boxes here at NTNU). Before we consider the alternative scenario (NAV bug), I would like you to retrieve information about the device with id 4177: SELECT * FROM device WHERE deviceid=4177 (censor any data you don't want to go public with). Then, attempt to retrieve the serial number by snmpget/walk from the three IP addresses in question. - -- Morten Vold, ITEA, NTNU -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDx3cLXxIl0kpcOkQRAh7KAKDoyPyy43kpt/osENSvBzlVC8wD3gCgkQoE eGPw1TlOehjWsUdOxaZIMGA= =4yhd -----END PGP SIGNATURE-----
From woj at tstd.pl Fri Jan 13 10:46:23 2006 From: woj at tstd.pl (Wojciech Kozicki) Date: Fri Jan 13 10:46:50 2006 Subject: [Nav-users] Alcatel devices In-Reply-To: <200601131010.07073.woj@tstd.pl> References: <200601131010.07073.woj@tstd.pl> Message-ID: <200601131046.23651.woj@tstd.pl>
On Friday 13 January 2006 10:10, Wojciech Kozicki wrote:
Hello,
anybody was successful monitoring Alcatel switches in NAV? (for example X590), especially in cricket?
To be more specific, these are Xylan devices branded by Alcatel. Where I should put xylan mibs to make NAV support it? regards -- Woj
From woj at tstd.pl Fri Jan 13 11:02:10 2006 From: woj at tstd.pl (Wojciech Kozicki) Date: Fri Jan 13 11:02:39 2006 Subject: [Nav-users] logger.conf In-Reply-To: <200601131012.01521.woj@tstd.pl> References: <200601041459.11900.woj@tstd.pl> <200601131012.01521.woj@tstd.pl> Message-ID: <200601131102.11342.woj@tstd.pl>
On Friday 13 January 2006 10:12, Wojciech Kozicki wrote:
On Wednesday 04 January 2006 14:59, Wojciech Kozicki wrote:
Hello,
how should be cisco box configured to have correct analyse in NAV Syslog Analyzer?
I have cisco communicates in following format:
Jan 4 14:50:47 <router_name> 2951: Jan 4 13:50:46: %SYS-5-CONFIG_I: Configured from console by vty0 (<ip>)
I can see this communicates in NAV, but only in: https://nav_ip/logger/?error ("parsing errors" link)
I still have this problem, can anybody help? Which log I should check?
Hello again, can anybody show mi a properly classified (in NAV-logger) cisco-log line? Maybe this is format problem, some extra parameters I have in my cisco config - for example timestamp. thanks -- Woj
From morten.vold at ntnu.no Fri Jan 13 11:11:22 2006 From: morten.vold at ntnu.no (Morten Vold) Date: Fri Jan 13 11:11:14 2006 Subject: [Nav-users] logger.conf In-Reply-To: <200601041459.11900.woj@tstd.pl> References: <200601041459.11900.woj@tstd.pl> Message-ID: <43C77CCA.5020301@ntnu.no>
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/01/2006 14:59, Wojciech Kozicki uttered:
how should be cisco box configured to have correct analyse in NAV Syslog Analyzer?
I'm sorry to say that the syslog analyzer is an ill conceived subsystem of NAV, and it is debated whether it belongs there or not. The developer that wrote it no longer works on the project, and hardly anyone I know of cares to use it (most sysadmins I know prefer to grep the log files manually). With regards to your actual question, I have no idea about the required format. Cisco equipment at NTNU still logs to our NAV 2 installation, and the syslog analyzer har been rewritten from scratch in NAV 3. - From what I can see, our logs look something like this: Jan 13 11:03:48 <router_name> 370245: Jan 13 11:03:52: %SEC-6-IPACCESSLOGP: list vlan18out denied udp <ip1>(50186) -> <ip2>(427), 1 packet What I do know, is that your logger.conf must point to the actual log file to pick up the log lines from. The default is /usr/local/nav/var/log/cisco.log, which means your syslog daemon must be configured to write log entries from external hosts to this file (or configure a different file name). The logengine cron job runs every minute to dump new entries from this file into the database. I also believe logengine will truncate the log file after it has been read. - -- Morten Vold, ITEA, NTNU -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDx3zKXxIl0kpcOkQRAiuGAKDpLWmxswuK2raIQCRS9iqDlp0MlQCdGFXg Aa2aflR3AyWhZmoaUAXiCbU= =gv6K -----END PGP SIGNATURE-----
From woj at tstd.pl Fri Jan 13 11:20:39 2006 From: woj at tstd.pl (Wojciech Kozicki) Date: Fri Jan 13 11:21:05 2006 Subject: [Nav-users] logger.conf In-Reply-To: <43C77CCA.5020301@ntnu.no> References: <200601041459.11900.woj@tstd.pl> <43C77CCA.5020301@ntnu.no> Message-ID: <200601131120.39752.woj@tstd.pl>
On Friday 13 January 2006 11:11, Morten Vold wrote:
On 04/01/2006 14:59, Wojciech Kozicki uttered:
how should be cisco box configured to have correct analyse in NAV Syslog Analyzer?
I'm sorry to say that the syslog analyzer is an ill conceived subsystem of NAV, and it is debated whether it belongs there or not. The developer that wrote it no longer works on the project, and hardly anyone I know of cares to use it (most sysadmins I know prefer to grep the log files manually).
Well, I am a console person :) But I thin that Logger module is really usefull, sometimes clicking is not so good...
With regards to your actual question, I have no idea about the required format. Cisco equipment at NTNU still logs to our NAV 2 installation, and the syslog analyzer har been rewritten from scratch in NAV 3.
From what I can see, our logs look something like this:
Jan 13 11:03:48 <router_name> 370245: Jan 13 11:03:52: %SEC-6-IPACCESSLOGP: list vlan18out denied udp <ip1>(50186) -> <ip2>(427), 1 packet
Thank You for this info.
What I do know, is that your logger.conf must point to the actual log file to pick up the log lines from. The default is /usr/local/nav/var/log/cisco.log, which means your syslog daemon must be configured to write log entries from external hosts to this file (or configure a different file name). The logengine cron job runs every minute to dump new entries from this file into the database. I also believe logengine will truncate the log file after it has been read.
This works ok, because nav has got my logs, but it puts them into error table. regards - Woj
From morten.vold at ntnu.no Fri Jan 13 11:45:07 2006 From: morten.vold at ntnu.no (Morten Vold) Date: Fri Jan 13 11:45:00 2006 Subject: [Nav-users] Again? In-Reply-To: <200601061309.18822.woj@tstd.pl> References: <200601061309.18822.woj@tstd.pl> Message-ID: <43C784B3.8030303@ntnu.no>
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/01/2006 13:09, Wojciech Kozicki uttered:
There is so many threads without answers... What about "2006 NAV activity" ?
I don want to be pain in the a... , but please, write more help-files or increase mailing list activity.
Thank You, and please, no offense, I just want to be happy nav-user ;)
I'm sorry you feel this way, and I realize this is a problem. I feel I must comment on the state of NAV development. The history of NAV up to 2004 can be found here: http://metanav.ntnu.no/moin.cgi/HistoryOfNAV The point is, more than 90% of the code in NAV has been developed by NTNU employees, mostly part-time students. UNINETT have contributed the AlertEngine and AlertProfiles (and about 50% of the financial funding since 2001), while an extremely tiny portion consists of voluntary contributions from third parties. The net result of NTNU having used mostly part-time employees to develop NAV, is that most of them are gone now, and their knowledge with them. As of today, I'm the only active NAV developer left (being a full-time employee at NTNU). John-Magne Bredal is also a full-time employee here, but he mostly maintains the code he has contributed earlier (being our Cricket/RRD expert, and author of the new Arnold subsystem). Also, you'll see Kristian Eide pop by with some helpful comments now and then (being the author of the entire collection and event systems), but he works full-time for an unrelated company now. I try to keep this mailing list going, but unfortunately, it is impossible for me to know every little wrinkle and oddity of NAV. I rely on the kind help of people like Kristian and John-Magne. They don't really work that much with NAV anymore, so they cannot always be expected to help. Since my current boss prioritizes my other assignments, I don't always have the time to figure out the intricate issues that people ask for help for on this list, when I don't already know the answer up front. On to the good news: The past year, NAV activity has been miniscule, mostly due to NTNU focusing on other projects. UNINETT aren't quite satisfied with this, as they see NAV as a strategic advantage. As Vidar Faltinsen has announced on this list, UNINETT will invest quite a lot in NAV this year (and the coming years), to put development and support back on track. Among the things I expect UNINETT to fix, is improved stability and documentation (which, by now, must the the most requested "features" by UNINETT customers). And of course, they plan to implement new features as well :) Most importantly, NAV is free software. If you wish to contribute, it is very much appreciated. Anything helps - code, documentation - you name it. - -- Morten Vold, ITEA, NTNU -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDx4SzXxIl0kpcOkQRAn5hAJ0dhM+2/4+7VrBW0dZadVFEiE/t4wCghn2t 14BZ0GpOnpnLOSsW0fbgljw= =zt9/ -----END PGP SIGNATURE-----
From gro-anita.vindheim at ntnu.no Fri Jan 13 12:31:20 2006 From: gro-anita.vindheim at ntnu.no (Gro-Anita Vindheim) Date: Fri Jan 13 12:31:14 2006 Subject: [Nav-users] Feature requests anyone? In-Reply-To: <1087.129.240.76.159.1137055274.squirrel@webmail.uio.no> References: <200601100953.k0A9rrTV049797@dis.cc.uit.no> <Pine.LNX.4.64.0601120025060.13344@tyholt-ng.uninett.no> <1087.129.240.76.159.1137055274.squirrel@webmail.uio.no> Message-ID: <43C78F88.10308@ntnu.no>
Kjetil Otter Olsen wrote:
- Differenciate between anonymous (not logged in) users and users that have been authenticated (but have no privileges)
Have you tried editing privileges in the user admin view ? At NTNU, Morten has made a "Authenticated Users (logged in)" group, and this group has been given basic privileges (such as access to the preferences page etc). All logged in users are by default a member in this group. I'm sure Morten can provide you with the SQL needed.
- A system to check that all NAV-processes are up and running (and doing what they are supposed to do)
I've made a small script that does a diff between a previous "NAV status" (/usr/local/nav/bin/nav status) and the current one. It runs in the "cron system" provided by NAV (I guess Morten can give a link to documentation of the nav status/start/stop system, and how to add local cron jobs). I can send a copy to the list if anyone is interested. Peder Magne Sefland also mentioned in a mail to this list a few weeks back that he has done something similar. Gro-Anita
From morten.vold at ntnu.no Fri Jan 13 12:44:03 2006 From: morten.vold at ntnu.no (Morten Vold) Date: Fri Jan 13 12:43:57 2006 Subject: [Nav-users] Feature requests anyone? In-Reply-To: <43C78F88.10308@ntnu.no> References: <200601100953.k0A9rrTV049797@dis.cc.uit.no> <Pine.LNX.4.64.0601120025060.13344@tyholt-ng.uninett.no> <1087.129.240.76.159.1137055274.squirrel@webmail.uio.no> <43C78F88.10308@ntnu.no> Message-ID: <43C79283.3000606@ntnu.no>
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 13/01/2006 12:31, Gro-Anita Vindheim uttered:
At NTNU, Morten has made a "Authenticated Users (logged in)" group, and this group has been given basic privileges (such as access to the preferences page etc). All logged in users are by default a member in this group. I'm sure Morten can provide you with the SQL needed.
Correction: I have checked in such a feature to the Subversion trunk, and NTNU happens to use a recent trunk revision of NAV. Merely executing some SQL on a NAV 3.0 installation won't cut it, you need to upgrade to bleeding edge code from trunk, or wait for NAV 3.1. - -- Morten Vold, ITEA, NTNU -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDx5KDXxIl0kpcOkQRAoubAKC8rPrfx1bQ8k4y7g5TSlZKFMV/7ACg8RlU 6D2gnsQxZK3GinkIwj2EZro= =VAvC -----END PGP SIGNATURE-----
From morten.vold at ntnu.no Fri Jan 13 12:49:06 2006 From: morten.vold at ntnu.no (Morten Vold) Date: Fri Jan 13 12:48:59 2006 Subject: [Nav-users] Errors when trying to make NAV on a Gentoo system with blackdown-jdk/jre In-Reply-To: <WorldClient-F200601071038.AA38330001@witelcom.com> References: <WorldClient-F200601071038.AA38330001@witelcom.com> Message-ID: <43C793B2.7010802@ntnu.no>
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/01/2006 10:38, Evert Meulie uttered:
When trying to make NAV on this system, I get the following error(s): [...] compile: [javac] Compiling 3 source files to /root/nav-3.0.0/src/SimpleSnmp/build [javac] /root/nav-3.0.0/src/SimpleSnmp/src/no/ntnu/nav/SimpleSnmp/SimpleSnmp.java:36: package snmp does not exist [javac] import snmp.*; [javac] ^
Unfortunately, there is little documentation on what is needed to build NAV from source. The problem here seems to be that you're missing the JavaSNMP library (whereas NAV was previously dependent on the WestHawk Java SNMP stack). I've made an attempt at documenting this requirement a little better on the metanav site now. What you need to download JavaSNMP 1.4 from this site: http://gicl.cs.drexel.edu/people/sevy/snmp/ Unpack, build and then install JavaSnmp.jar somewhere on your Java classpath. - -- Morten Vold, ITEA, NTNU -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDx5OyXxIl0kpcOkQRAsJLAKDmPpTVt+ywvuW5CH1LkXtinMvxLQCfVZ/d 5f5kNUSeAbTzYHEIY37V05o= =auTA -----END PGP SIGNATURE-----
From morten.vold at ntnu.no Fri Jan 13 13:05:10 2006 From: morten.vold at ntnu.no (Morten Vold) Date: Fri Jan 13 13:05:03 2006 Subject: [Nav-users] Router down, but no notification. In-Reply-To: <002a01c6154d$c5a27020$6500a8c0@llewdislappy> References: <002a01c6154d$c5a27020$6500a8c0@llewdislappy> Message-ID: <43C79776.7080606@ntnu.no>
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/01/2006 19:51, Joshua Sidwell uttered:
We are using Nav 3.0, and have a router that we monitor that went down on Friday night, and found out about it this morning when the remote location called. I am currently setup to receive notification on any box down, and received nothing via e-mail. Additionally, we monitor 24/7 on the Traffic Map, but it never showed the device as down/unreachable. What debug info would help troubleshoot this problem? What configuration settings can I verify to make sure this box is configured correctly?
I've never heard of anyone using the traffic map for status monitoring before, so I cannot exactly speak of it's reliability in that area. You should check with your IP Device Center whether there were any boxState alerts in the last 7 days for this box (Go to http://yournavhost/report and enter the box name or IP in the first form field there). Most importantly, box state changes are monitored by the pping backend process. If this process isn't running, NAV won't know what's up and what's down. Check the output of the "nav status" command, make sure pping is up (and everything else for that matter - the only exceptions are processes you've disabled by choice). - -- Morten Vold, ITEA, NTNU -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDx5d1XxIl0kpcOkQRAjwAAJ94baVu5DHUqy4ptXu9zh6zYyKILgCeJKss r4VEfLg+ylLdcINNupcS+Kg= =2R1Q -----END PGP SIGNATURE-----
From morten.vold at ntnu.no Fri Jan 13 13:11:21 2006 From: morten.vold at ntnu.no (Morten Vold) Date: Fri Jan 13 13:11:14 2006 Subject: [Nav-users] Trouble with editdb and UTF-8 In-Reply-To: <20060110215953.Q68239@duke.cc.uit.no> References: <20060110215953.Q68239@duke.cc.uit.no> Message-ID: <43C798E9.5020706@ntnu.no>
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/01/2006 22:01, Borge Brunes uttered:
It's working OK, but I have one issue with editdb. When I add some (not all) devices I got this message:
How did you add them? Bulk import? If so, where did the bulk file come from, did you generate it from the dump script or write it by hand?
ProgrammingError: ERROR: invalid UTF-8 byte sequence detected near byte 0xa6
select deviceid,productid from device where serial='TSC072200EF' or serial='TSC072200EF' or serial='SAL0723EGL7' or serial='SAL0724ES3J' or
Ok, first off: Yuck, ugly SQL, bad editdb! ;)
serial='0402072350198996' or serial='0402072342552745' or serial=' ??!,'
The serial number ' ??!,' looks kind of suspicious, if you ask me. So do several others in the list. Again, it comes back to your bulk import file and what it contained. May I see it?
I know that the encoding-consistency for Unicode has been tightened down in postgres 8.1: http://archives.postgresql.org/pgsql-hackers/2005-10/msg00972.php
Yep, that is probably what triggers the error, question is still what the input actually was. Editdb will interpret everything fed to it as UTF-8 (at least if that's what your browser indicates), but if your actual input contains invalid UTF-8 characters, editdb won't know. - -- Morten Vold, ITEA, NTNU -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDx5jpXxIl0kpcOkQRAiwGAJ9f1YxCpTNtO4ZfsuZqriFWmgSNYACfft4r y2rORQdN+zkiZ4UaV50dCGs= =L7qh -----END PGP SIGNATURE-----
From evert at witelcom.com Fri Jan 13 13:19:57 2006 From: evert at witelcom.com (Evert Meulie) Date: Fri Jan 13 13:19:56 2006 Subject: [Nav-users] Errors when trying to make NAV on a Gentoo system with blackdown-jdk/jre In-Reply-To: <43C793B2.7010802@ntnu.no> References: <WorldClient-F200601071038.AA38330001@witelcom.com> <43C793B2.7010802@ntnu.no> Message-ID: <43C79AED.7040005@witelcom.com>
Thanks! :-) That got me a bit further. Now crashing at: Building webapps/navAdmin ... (cd webapps/navAdmin && /usr/bin/ant ) && touch webapps/navAdmin Buildfile: build.xml BUILD FAILED /root/nav-3.0.0/src/webapps/navAdmin/build.xml:163: taskdef class org.apache.catalina.ant.DeployTask cannot be found Total time: 0 seconds make[1]: *** [webapps/navAdmin] Error 1 make[1]: Leaving directory `/root/nav-3.0.0/src' make: *** [all] Error 1 Regards, Evert Morten Vold wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 07/01/2006 10:38, Evert Meulie uttered:
When trying to make NAV on this system, I get the following error(s): [...] compile: [javac] Compiling 3 source files to /root/nav-3.0.0/src/SimpleSnmp/build [javac] /root/nav-3.0.0/src/SimpleSnmp/src/no/ntnu/nav/SimpleSnmp/SimpleSnmp.java:36: package snmp does not exist [javac] import snmp.*; [javac] ^
Unfortunately, there is little documentation on what is needed to build NAV from source. The problem here seems to be that you're missing the JavaSNMP library (whereas NAV was previously dependent on the WestHawk Java SNMP stack). I've made an attempt at documenting this requirement a little better on the metanav site now.
What you need to download JavaSNMP 1.4 from this site: http://gicl.cs.drexel.edu/people/sevy/snmp/
Unpack, build and then install JavaSnmp.jar somewhere on your Java classpath.
- -- Morten Vold, ITEA, NTNU -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDx5OyXxIl0kpcOkQRAsJLAKDmPpTVt+ywvuW5CH1LkXtinMvxLQCfVZ/d 5f5kNUSeAbTzYHEIY37V05o= =auTA -----END PGP SIGNATURE-----
participants (1)
-
woj＠tstd.pl