Hi, Looks like my 3.0.b10 nav installation isn't doing the automated processes like it should. I'm pretty sure I've done the seeding process correctly, and nav isn't showing any error's. The problem is in that nav isn't monitoring new ip devices I add. i.e. if I plug out a router that is in nav's db, it still shows it as UP, hence my alert profile doesn't work. Also nav makes cricket targets only for sysuptime, no interface targets. I need help in tracking this problem. Note: I have no switches, cabling and patches entered in the nav db, maybe the problem is there!? Also I don't have a switch that has snmp support, where/how do I enter such equipment in nav's db? Perica Veljanovski
Hello !
Looks like my 3.0.b10 nav installation
Doesn't know anything about your problem, but I will advise you to upgrade to nav 3.0.0-release or maybe download the source via svn, this is how I upgrade : - Make a directory, example : /usr/local/src/nav - cd /usr/local/src/nav - svn co http://svn.itea.ntnu.no/repos/nav/navme/trunk/ (You need the subversion package /usr/ports/devel/subversion) A directory /usr/local/src/nav/trunk is created - Some svn commands : svn update svn log 01) nav stop /usr/local/etc/rc.d/apache2.sh stop /usr/local/etc/rc.d/020.jakarta-tomcat50.sh stop /usr/local/etc/rc.d/010.pgsql.sh stop 03) mv /usr/local/nav /usr/local/nav-DATE 04) cd /usr/local/src/nav/trunk svn update 05) cd /usr/ports/net-mgmt/nav make clean unset JAVA_HOME make extract cp -R /usr/local/src/nav/trunk/* /usr/ports/net-mgmt/nav/work/nav-3.0_beta10/ FORCE_PKG_REGISTER=yes make install 06) (new shell) su - . /usr/local/nav/bin/navenv.sh ln -s /usr/local/cricket /usr/local/nav/cricket ln -s /usr/local/cricket/public_html /usr/local/nav/apache/webroot/cricket /usr/local/etc/rc.d/010.pgsql.sh start /usr/local/etc/rc.d/020.jakarta-tomcat50.sh start /usr/local/etc/rc.d/apache2.sh start 07) editer : /usr/local/nav/etc/db.conf /usr/local/nav/etc/pg_backup.conf /usr/local/nav/lib/python/nav/web/pyproxy/proxy.py 08) Start nav + maybe stop some services nav start nav stop logengine -- Med vennlig hilsen / Regards; Roar Pettersen Universitetet i Bergen - The University of Bergen Nygardsgt. 5 - N-5020 BERGEN - Norway Tlf: +47 55 58 40 55 VIP: 81503 fax: +47 55 58 40 70 roar.pettersen@it.uib.no - IT-Avd, UiB - http://www.uib.no
From peder.sefland at hivolda.no Thu Dec 22 13:15:26 2005 From: peder.sefland at hivolda.no (Peder Magne Sefland) Date: Thu Dec 22 13:16:01 2005 Subject: [Nav-users] Syslog Analyzer parsing errors Message-ID: <s3aaa70b.052@HVO-3.hivolda.no>
I have syslogd running on my nav3-box, and in the /etc/nav/logger.conf I have edit and set [start] # enable syslog parsing # the file needs to exisit and the navcron user need write access to the file enable: 1 [paths] # path to syslog file syslog:/var/log/cisco.log [deletepriority] # deletes messages of the given priority older than a limited number of days 0:730 1:730 2:90 3:90 4:90 5:30 6:30 7:1 [priorityexceptions] # defines new priorities for messages # # syntax: # FAC-0-MNEM@x-gsw.university.net:7 # gives the FAC-0-MNEM type new priority 7 (low) for x-gsw # # FAC-0-MNEM:7 # FAC-0-MNEM@ANY:7 # gives all FAC-0-MNEM messages new priority 7 # # unit-gsw.university.net:5 # ANY@unit-gsw.university.net:5 # gives priority 5 to all messages from x-gsw # # the most specific exceptions are considered most important # ##LINEPROTO-5-UPDOWN@erke-gw-trlos.ntnu.no:2 ##LINEPROTO-5-UPDOWN:4 ##ISDN-6-LAYER2DOWN@ANY:2 ##erke-gw-trlos.ntnu.no:1 ##ANY@sb-gsw.ntnu.no:0 /etc/nav/logger.conf (END) And I have checked the permisson for this file -rw-r--r-- 1 navcron nav 0 2005-12-22 13:03 cisco.log When I click on the "Send"-button in the Syslog Ananlyzer it says "Your search did not return any results". But when I click on the parsing errors I get this Total 164 error conditions Dec 22 13:01:15 XXXXX-XXXXX-XX 19349: 1y5w: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/3, changed state to down Dec 22 12:59:57 XXXXX-XXXXX-XX 10235: 1w1d: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/11, changed state to up Dec 22 12:59:54 XXXXX-XXXXX-XX 10234: 1w1d: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/11, changed state to down Dec 22 12:59:26 XXXXX-XXXXX-XX 1807782: 1y31w: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed state to up Dec 22 12:59:23 XXXXX-XXXXX-XX 1807781: 1y31w: %LINK-3-UPDOWN: Interface FastEthernet0/5, changed state to up ................ I'm getting closer, but whats wrong? Peder Sefland Merry Christmas to all the nav-users!
From woj at tstd.pl Tue Dec 27 12:52:39 2005 From: woj at tstd.pl (Wojciech Kozicki) Date: Tue Dec 27 12:53:17 2005 Subject: [Nav-users] NAV 3.0.0 in Debian? Message-ID: <200512271252.39624.woj@tstd.pl>
Hello, are there some plans for packaging stable NAV version to debian? I tried to install some last package generated by Morten Werner Olsen: dpkg -l | grep -i "nav" ii nav 2+3.0rc2-1 Network Administration Visualized using this: http://pkg-nav.alioth.debian.org/install-howto.txt Because of changes in debian unstable repository installing NAV from this old packages is problematic, for example: --- Cricket can't work with debian rrdtool any more (1.2.11-0.4): "Current values not available: RRD file version 0003 not supported on this arch" http://www.mail-archive.com/debian-bugs-rc@lists.debian.org/msg33905.html http://sourceforge.net/mailarchive/message.php?msg_id=12475397 --- Network Explorer prints error: "java.lang.NoClassDefFoundError: no/ntnu/nav/Path" and so on... I think, that if NAV if already stable it should be ported to debian, in my opinion installing this from scratch is really problematic. Maybe there should be some live-cd with preinstalled NAV, what You think? To make some summary: 1. Will be NAV ported to Debian? 2. Will be NAV sources ported to Gentoo? 3. What is the _simplest_ and _fastest_ way to start using newest version of NAV? I just want to use it, don't want to know java problems, catalina/tomcat problems, python problems, cricket problems etc... I think there is really need for "Installing NAV from scratch" - step by step howto. best regards -- Woj
Hi again,
Looks like my 3.0.b10 nav installation isn't doing the automated processes like it should. I'm pretty sure I've done the seeding process correctly, and nav isn't showing any error's. The problem is in that nav isn't monitoring new ip devices I add. i.e. if I plug out a router that is in nav's db, it still shows it as UP, hence my alert profile doesn't work. Also nav makes cricket targets only for sysuptime, no interface targets.
I need help in tracking this problem.
This FAQ entry may help you here: http://metanav.ntnu.no/moin.cgi/NAVFAQ#a-box-is-down-but-it-does-not-show-on... 6.1 A box is down, but it does not show on the status page. Why? First, check if the box has been registered with Edit database, for instance in netbox report. Second, check with 'nav status' if pping and eventEngine are running. Third, check the log file of pping if it detected the outage. If it did, check the log file of eventEngine if it processed the event. If it did not, check if the event is still present in the eventq: In psql do 'SELECT * FROM eventq;'. Further look at FAQ 7.1 for alert engine debugging. To clarify, if confusing, pping will initially detect the outage and report to its log file and on the event queue (eventq). Event engine will in turn process the event and potentially correlate it with other relevant events, i.e. to detect "shadow states". Event engine posts the alarm on the alarm queue (alertq and alerthist), whereas alert engine processes the alarm queue an looks for matches in users active profiles.
Note: I have no switches, cabling and patches entered in the nav db, maybe the problem is there!?
This is no problem. As long as a given ip device is added thru add netbox it will be monitored by pping. Consistant topology information is not a requirement for the status monitor.
Also I don't have a switch that has snmp support, where/how do I enter such equipment in nav's db?
You can't. (I assume the switch has no IP address for management, if it has, but lack snmp support, you can status monitor it using the category OTHER). On a general basis I would strongly recommend snmp support for all switches. Then NAV will be able to derive the switchports, neighbor information, vlan information, machine tracker information, statistics etc, etc. - Vidar
participants (3)
-
perica＠akton.com.mk -
roar.pettersen＠uib.no -
Vidar.Faltinsen＠uninett.no