Nav-users

nav-users@lister.sikt.no

3 participants
1372 discussions

Router down, but no notification.
by jsidwell＠perisys.net 09 Jan '06

09 Jan '06

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? Joshua Sidwell >From Ingeborg.Hellemo at cc.uit.no Tue Jan 10 10:53:53 2006 From: Ingeborg.Hellemo at cc.uit.no (Ingeborg Hellemo) Date: Tue Jan 10 10:54:00 2006 Subject: [Nav-users] Feature requests anyone? In-Reply-To: Your message of "Wed, 04 Jan 2006 14:01:44 +0100." <Pine.LNX.4.64.0601041322380.18181(a)tyholt-ng.uninett.no> Message-ID: <200601100953.k0A9rrTV049797(a)dis.cc.uit.no> Vidar.Faltinsen(a)uninett.no said: > We are currently working on a list of new features to implement. I could > present the list, but at this stage I will rather ask the NAV community... > what do you want? The University og Troms? now proudly presents their wish list: (Well Vidar, you asked for it...) ----- Programming/packaging style: * Fewer languages NAV of today is dependent of almost every scripting language known to man, except ruby (oops, I shouldn't have said that!). Please make sure that new features does not involve more languages and small packages (which must be of exactly version x.y-rc2) only found on obscure and badly connected websites. * Less JAVA The first language we would like to say goodbye (and good riddance!) to is Java. It is a PIA to get to work on FreeBSD and a problem for all platforms to configure and get all paths etc. correct. Of course you still need Java for visualisation, but for the data collector we would like to see threaded python or even C as this would be more portable and easyer to maintain. ----- Features: * Please make today's features work before you put all your resources on new features. * Please implement the features we have lost from earlier versions of NAV and the features you have promised us for the last years before you put all your resources on new features. Some of the things we have noticed: * The world is down NAVv3 does not recognice that it has lost connection to its switch and wrongly reports this as "the world is down!" * Alert profile - Filters based on "Sub category" does not work. - Double messages/sms-es are sent out - Need more documentation * Better sms-handling. We loose messages today during large outages. * Traffic map - Same problems as reported by others * cricket - We miss the zoom-in function fram NAVv2. Perhaps this is just a FreeBSD-loss, but we would really like this integrated into the main cricket-package so that we can upgrade cricket at will without having to wait for a NAV-patch. * Larger fields in some database tables (we have problems with 'room' and 'location') ----- When you have done all this we would please like to have: * Support for boxes that NTNU does not use (i.e. 3750) and stacked switches. * Support for weatherducks. * Better handling of modules * System for receiving alerts (and generating alarms) from other systems i.e. snmptraps, email, syslog. * Support for data collection via http, telnet/ssh from systems that does not support snmp. * Snapshot view of VLAN, duplex etc. of a port/interface * cricket - Better cricket-integration for servers and UPS-es (and wireless). What we want is makecricketconfig.pl to automatic update a cricket-subtree for these devices. - sorted load statistics * Better support for threshholds (responce time, filling of disks, cpu load etc.) * We want to set individual threshholds for when a box/service is registered as down. (A well connected server is down if unreachable for 1 minute, a server behind a shaky radiolink is down if unreachable for 10 minutes) * Better service monitoring - More services - Take into consideration that a service may have its own IP-address that runs on another server. I.e. box host.uit.no has IP-address 10.10.10.1 The host runs services smtp.uit.no with address 10.10.10.2 and web.uit.no with address 10.10.10.3. I only need _service_ monitoring on the two latter addresses (no need to ping them) and if I put host.uit.no on maintenance I do not want receive alarms about smtp.uit.no or web.uit.no (neither ip-addresses nor services) * Maintenance - Must be able to put a service on maintenance. - Better user interface. - Be able to put "all" boxes and services at a given location on maintenance. * Better "devicemanagement"/"IP Device Center". Should these perhaps merge? When we do a https://nav.uit.no/browse/some_box we also want to see info from devicemanagement like - IOS-version - upgraded when? - register comments about device - etc. * RSS-feed * Possibility to exclude subnet (in a config-file) that we don't want NAV to use. Eg. 127.0.0.1/8 ----- Regarding syslog: Our view is first of all that syslog does not belong in a database. Period. (Prosessed and aggregated information from syslog may be put in a database, but only after you have identified what you are looking for.) Syslog from Cisco is particularly difficult to parse because every type of device has its own syntax, and small configuration changes on the device will result in completely different syntax. This is why today's syslog module in NAV does not work for anyone besides those who implemented the parser. There exist a number of syslog collecting/parsing systems out there, some good, some not so good. To put much effort into implementing syslog collection in NAV is to reinvent the weel. We think it would be better to implement a system that can receive alerts from an external syslog-parsing system. What we would like to see in NAV is the ability to show normal syslog-files with moderate search/grep functionality. We are currently doing som work on this for our helpdesk so they can check the radius-syslog without having access to our main syslogserver. ------ Best wishes for the new NAV year... Ingeborg and B?rge -- Ingeborg ?strem Hellemo -- ingeborg(a)cc.uit.no (Univ. of Troms?, Norway)

1 0

Errors when trying to make NAV on a Gentoo system with blackdown-jdk/jre
by evert＠witelcom.com 07 Jan '06

07 Jan '06

Hi all! When trying to make NAV on this system, I get the following error(s): ************************* (cd SimpleSnmp && /usr/bin/ant ) && touch SimpleSnmp Buildfile: build.xml init: [mkdir] Created dir: /root/nav-3.0.0/src/SimpleSnmp/build 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] ^ [javac] /root/nav-3.0.0/src/SimpleSnmp/src/no/ntnu/nav/SimpleSnmp/SimpleSnmp.java:70: cannot resolve symbol [javac] symbol : class SNMPv1CommunicationInterface [javac] location: class no.ntnu.nav.SimpleSnmp.SimpleSnmp [javac] private SNMPv1CommunicationInterface comInterface = null; [javac] ^ [javac] /root/nav-3.0.0/src/SimpleSnmp/src/no/ntnu/nav/SimpleSnmp/SimpleSnmp.java:598: cannot resolve symbol [javac] symbol : class SNMPVarBindList [javac] location: class no.ntnu.nav.SimpleSnmp.SimpleSnmp [javac] SNMPVarBindList var = null; [javac] ^ [javac] /root/nav-3.0.0/src/SimpleSnmp/src/no/ntnu/nav/SimpleSnmp/SimpleSnmp.java:605: cannot resolve symbol [javac] symbol : class SNMPVarBindList [javac] location: class no.ntnu.nav.SimpleSnmp.SimpleSnmp [javac] var = new SNMPVarBindList(); [javac] ^ [javac] /root/nav-3.0.0/src/SimpleSnmp/src/no/ntnu/nav/SimpleSnmp/SimpleSnmp.java:608: cannot resolve symbol [javac] symbol : class SNMPVarBindList [javac] location: class no.ntnu.nav.SimpleSnmp.SimpleSnmp [javac] SNMPVarBindList nextpair = comInterface.getNextMIBEntry(nextoid); [javac] ^ [javac] /root/nav-3.0.0/src/SimpleSnmp/src/no/ntnu/nav/SimpleSnmp/SimpleSnmp.java:609: cannot resolve symbol [javac] symbol : class SNMPObject [javac] location: class no.ntnu.nav.SimpleSnmp.SimpleSnmp [javac] SNMPObject snmpobj = nextpair.getSNMPObjectAt(0); [javac] ^ [javac] /root/nav-3.0.0/src/SimpleSnmp/src/no/ntnu/nav/SimpleSnmp/SimpleSnmp.java:610: cannot resolve symbol [javac] symbol : class SNMPNull [javac] location: class no.ntnu.nav.SimpleSnmp.SimpleSnmp [javac] if (snmpobj instanceof SNMPNull) break; [javac] ^ [javac] /root/nav-3.0.0/src/SimpleSnmp/src/no/ntnu/nav/SimpleSnmp/SimpleSnmp.java:611: cannot resolve symbol [javac] symbol : class SNMPSequence [javac] location: class no.ntnu.nav.SimpleSnmp.SimpleSnmp [javac] SNMPSequence pair = (SNMPSequence)snmpobj; [javac] ^ [javac] /root/nav-3.0.0/src/SimpleSnmp/src/no/ntnu/nav/SimpleSnmp/SimpleSnmp.java:611: cannot resolve symbol [javac] symbol : class SNMPSequence [javac] location: class no.ntnu.nav.SimpleSnmp.SimpleSnmp [javac] SNMPSequence pair = (SNMPSequence)snmpobj; [javac] ^ [javac] /root/nav-3.0.0/src/SimpleSnmp/src/no/ntnu/nav/SimpleSnmp/SimpleSnmp.java:612: cannot resolve symbol [javac] symbol : class SNMPObjectIdentifier [javac] location: class no.ntnu.nav.SimpleSnmp.SimpleSnmp [javac] SNMPObjectIdentifier snmpOID = (SNMPObjectIdentifier)pair.getSNMPObjectAt(0); [javac] ^ [javac] /root/nav-3.0.0/src/SimpleSnmp/src/no/ntnu/nav/SimpleSnmp/SimpleSnmp.java:612: cannot resolve symbol [javac] symbol : class SNMPObjectIdentifier [javac] location: class no.ntnu.nav.SimpleSnmp.SimpleSnmp [javac] SNMPObjectIdentifier snmpOID = (SNMPObjectIdentifier)pair.getSNMPObjectAt(0); [javac] ^ [javac] /root/nav-3.0.0/src/SimpleSnmp/src/no/ntnu/nav/SimpleSnmp/SimpleSnmp.java:623: cannot resolve symbol [javac] symbol : class SNMPBadValueException [javac] location: class no.ntnu.nav.SimpleSnmp.SimpleSnmp [javac] } catch (SNMPBadValueException exp) { [javac] ^ [javac] /root/nav-3.0.0/src/SimpleSnmp/src/no/ntnu/nav/SimpleSnmp/SimpleSnmp.java:626: cannot resolve symbol [javac] symbol : class SNMPException [javac] location: class no.ntnu.nav.SimpleSnmp.SimpleSnmp [javac] } catch (SNMPException exp) { [javac] ^ [javac] /root/nav-3.0.0/src/SimpleSnmp/src/no/ntnu/nav/SimpleSnmp/SimpleSnmp.java:627: cannot resolve symbol [javac] symbol : class SNMPGetException [javac] location: class no.ntnu.nav.SimpleSnmp.SimpleSnmp [javac] if (!(exp instanceof SNMPGetException && exp.getMessage() != null && exp.getMessage().indexOf("not available for retrieval") >= 0)) { [javac] ^ [javac] /root/nav-3.0.0/src/SimpleSnmp/src/no/ntnu/nav/SimpleSnmp/SimpleSnmp.java:651: cannot resolve symbol [javac] symbol : class SNMPSequence [javac] location: class no.ntnu.nav.SimpleSnmp.SimpleSnmp [javac] SNMPSequence pair = (SNMPSequence)(var.getSNMPObjectAt(i)); [javac] ^ [javac] /root/nav-3.0.0/src/SimpleSnmp/src/no/ntnu/nav/SimpleSnmp/SimpleSnmp.java:651: cannot resolve symbol [javac] symbol : class SNMPSequence [javac] location: class no.ntnu.nav.SimpleSnmp.SimpleSnmp [javac] SNMPSequence pair = (SNMPSequence)(var.getSNMPObjectAt(i)); [javac] ^ [javac] /root/nav-3.0.0/src/SimpleSnmp/src/no/ntnu/nav/SimpleSnmp/SimpleSnmp.java:652: cannot resolve symbol [javac] symbol : class SNMPObjectIdentifier [javac] location: class no.ntnu.nav.SimpleSnmp.SimpleSnmp [javac] SNMPObjectIdentifier snmpOID = (SNMPObjectIdentifier)pair.getSNMPObjectAt(0); [javac] ^ [javac] /root/nav-3.0.0/src/SimpleSnmp/src/no/ntnu/nav/SimpleSnmp/SimpleSnmp.java:652: cannot resolve symbol [javac] symbol : class SNMPObjectIdentifier [javac] location: class no.ntnu.nav.SimpleSnmp.SimpleSnmp [javac] SNMPObjectIdentifier snmpOID = (SNMPObjectIdentifier)pair.getSNMPObjectAt(0); [javac] ^ [javac] /root/nav-3.0.0/src/SimpleSnmp/src/no/ntnu/nav/SimpleSnmp/SimpleSnmp.java:653: cannot resolve symbol [javac] symbol : class SNMPObject [javac] location: class no.ntnu.nav.SimpleSnmp.SimpleSnmp [javac] SNMPObject snmpValue = pair.getSNMPObjectAt(1); [javac] ^ [javac] /root/nav-3.0.0/src/SimpleSnmp/src/no/ntnu/nav/SimpleSnmp/SimpleSnmp.java:657: cannot resolve symbol [javac] symbol : class SNMPOctetString [javac] location: class no.ntnu.nav.SimpleSnmp.SimpleSnmp [javac] if (!decodeHex && snmpValue instanceof SNMPOctetString) { [javac] ^ [javac] /root/nav-3.0.0/src/SimpleSnmp/src/no/ntnu/nav/SimpleSnmp/SimpleSnmp.java:663: cannot resolve symbol [javac] symbol : class SNMPOctetString [javac] location: class no.ntnu.nav.SimpleSnmp.SimpleSnmp [javac] if (data.length() == 0 && !(snmpValue instanceof SNMPOctetString)) { [javac] ^ [javac] /root/nav-3.0.0/src/SimpleSnmp/src/no/ntnu/nav/SimpleSnmp/SimpleSnmp.java:806: cannot resolve symbol [javac] symbol : class SNMPv1CommunicationInterface [javac] location: class no.ntnu.nav.SimpleSnmp.SimpleSnmp [javac] comInterface = new SNMPv1CommunicationInterface(snmpVersion, hostAddress, cs_ro); [javac] ^ [javac] 22 errors BUILD FAILED /root/nav-3.0.0/src/SimpleSnmp/build.xml:30: Compile failed; see the compiler error output for details. Total time: 2 seconds make[1]: *** [SimpleSnmp] Error 1 make[1]: Leaving directory `/root/nav-3.0.0/src' make: *** [all] Error 1 ************************* Does anybody has any suggestions on how to fix? It clearly seems snmp-related...? Regards, Evert

1 0

Cricket error
by kreide＠gmail.com 06 Jan '06

06 Jan '06

> OID key * This is a unique idenitifier for the OID and is used in the source code to refer to that OID. Usually we use some variation of the OID name. > Snmpoid * This is the actual numeric OID. > OID source This field does not have a good name; I it is supposed to be from which subsystem the OID comes from, but I think it is used by cricket to identify the OID that it collects. If the OID source is 'cricket' then cricket will collect data for this OID (JM: correct me if I am wrong). > Match regexp The data collected from an OID must match this regex (if it is not null, in which case everything matches which is the normal case) if data is to be collected. > OID name > MIB > Description These are just description fields. -- Kristian

1 0

Again?
by woj＠tstd.pl 06 Jan '06

06 Jan '06

Hello, 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 ;) regards -- Woj >From woj at tstd.pl Fri Jan 6 13:18:58 2006 From: woj at tstd.pl (Wojciech Kozicki) Date: Fri Jan 6 13:19:14 2006 Subject: [Nav-users] Again? In-Reply-To: <20060106121512.GA3837(a)itea.ntnu.no> References: <200601061309.18822.woj(a)tstd.pl> <20060106121512.GA3837(a)itea.ntnu.no> Message-ID: <200601061318.59054.woj(a)tstd.pl> On Friday 06 January 2006 13:15, Bjorn Ove Grotan wrote: > Wojciech Kozicki: > > Hello, > > > > There is so many threads without answers... > > > > What about "2006 NAV activity" ? > > It's in the "feature request"-thread - which started the other day. Well, new features... I don't have old-ones working ;-) > > > 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 ;) > > Don't we all :-) :-) -- Woj >From kreide at gmail.com Fri Jan 6 09:24:06 2006 From: kreide at gmail.com (Kristian Eide) Date: Fri Jan 6 18:24:18 2006 Subject: [Nav-users] Cisco 7140 - nav can't see some of router interfaces In-Reply-To: <200601050901.26319.woj(a)tstd.pl> References: <200601041322.24818.woj(a)tstd.pl> <Pine.LNX.4.64.0601041333510.18181(a)tyholt-ng.uninett.no> <200601050901.26319.woj(a)tstd.pl> Message-ID: <b4c110fd0601060924o15754d33l4a597cb037c3257(a)mail.gmail.com> > I have similar problems with one of our 2900 catalyst switch with ATM port, > snmpwalk shows interfaces, nav not. In cricket there is only CPU statistics. > What is the best way to debug such problems? There is a report which shows the snmpoid's a device responds to (or at least NAV thinks it does). If the OID you are looking for is not in the list then NAV will not collect any info for it. The solution then is to get NAV to try to auto-detect the OIDs again, by setting the field 'netbox.uptodate'=false in the database (am I not sure if editDB can do this, however). > What about adding user-specific OIDs? Any help to this nav-section? See other mail. -- Kristian

1 0

Cisco 7140 - nav can't see some of router interfaces
by woj＠tstd.pl 05 Jan '06

05 Jan '06

On Wednesday 04 January 2006 13:41, Vidar Faltinsen wrote: > On Wed, 4 Jan 2006, Wojciech Kozicki wrote: > > Hello, > > > > I have couple of cisco 7140, and NAV can't see all routers interfaces. In > > router-ports report I can see only some of ATM interfaces, but not all. > > Also, there is lack of Fast Etherent interfaces. I tried re-adding device > > to nav, but it didn't help. > > > > Missing subinterfaces are on different modules... > > > > What I should check? > > > > MRTG is working with this routers with no problem. > > MRTG has traffic counters for the interfaces that NAV are missing? > > You should verify what the router returns of ifindexes/ifdescr from > the interfaces MIB. I know the support has been varying in respect > to fast/gigethernet-based subinterface support. At one point ios > gave us the ifindexes, but the octet counters were not maintained. > > Do a snmpwalk directly to the router in question, something like: > > snmpwalk -On -c <snmp read community> -v2c <ip address> ifdescr > > or > > snmpwalk -On -c <snmp read community> -v2c <ip address> > .1.3.6.1.2.1.2.2.1.2 > I have similar problems with one of our 2900 catalyst switch with ATM port, snmpwalk shows interfaces, nav not. In cricket there is only CPU statistics. Question no1: What is the best way to debug such problems? Question no2: What about adding user-specific OIDs? Any help to this nav-section? regards -- Woj >From odd.hauge at hiMolde.no Thu Jan 5 23:45:36 2006 From: odd.hauge at hiMolde.no (Hauge Odd Arne) Date: Fri Jan 6 00:11:49 2006 Subject: [Nav-users] Problems adding users Message-ID: <8EEE7738AEDF6947B3E5508A0244D1C21B8C17(a)stam.himolde.no> FYI: A recompile of Nav (bleeding edge) solved the problem. Nothings better ;) - odd arne > -----Original Message----- > From: Hauge Odd Arne > Sent: Thursday, January 05, 2006 8:51 AM > To: Hauge Odd Arne; nav-users(a)itea.ntnu.no > Subject: RE: [Nav-users] Problems adding users > > Seems like som postgres problem to me. After trying to add a > new user I did a ps command on the nav-box: > postgres 5836 0.0 2.9 41216 14936 pts/0 S 01:16 > 0:00 postgres: navwrite navprofiles 127.0.0.1(55524) idle in > transaction > postgres 5850 0.0 3.0 41480 15908 pts/0 S 01:16 > 0:00 postgres: navwrite navprofiles 127.0.0.1(55530) idle in > transaction > postgres 5852 0.0 2.9 41216 14940 pts/0 S 01:16 > 0:00 postgres: navwrite navprofiles 127.0.0.1(55532) idle in > transaction > postgres 5856 0.0 2.8 41216 14848 pts/0 S 01:16 > 0:00 postgres: navwrite navprofiles 127.0.0.1(55534) INSERT waiting > > I'm not sure what the idle in transaction and insert waiting means... > It seems to me it's only the navprofiles database I have > problems adding information into. I can not add new accounts > or groups. But I can manage profiles for existing nav users > (read admin user). > > - odd arne hauge > > > > > > > -----Original Message----- > > From: nav-users-bounces(a)itea.ntnu.no > > [mailto:nav-users-bounces@itea.ntnu.no] On Behalf Of Hauge Odd Arne > > Sent: Wednesday, January 04, 2006 3:47 PM > > To: nav-users(a)itea.ntnu.no > > Subject: [Nav-users] Problems adding users > > > > Hi. > > > > While testing the bleeding edge of Nav I'm having problem adding > > users. > > I get the following output in my browser when I tries to add a new > > user: > > "no such account 1000" > > > > Any suggestions ? > > > > Regards > > Odd Arne Hauge > > > > > > _______________________________________________ > > Nav-users mailing list > > Nav-users(a)itea.ntnu.no > > http://mailman.itea.ntnu.no/mailman/listinfo/nav-users > >

1 0

SV: Re: SV: [Nav-users] logger.conf
by peder.sefland＠hivolda.no 04 Jan '06

04 Jan '06

> Do you have any false alerts on dns-mismatch? I'm not shure that this > has anything to do with this. > > All device names are resolved correctly, beacuse all hostname informations are in NAV machine /etc/hosts file. -- Woj Is this how it should work? I have thought that my colleagues at computer-dep. only needs to registrer their servers or wireless in the web-interface, but not to edit /etc/host file on the nav-box. Peder >From odd.hauge at hiMolde.no Thu Jan 5 08:50:57 2006 From: odd.hauge at hiMolde.no (Hauge Odd Arne) Date: Thu Jan 5 08:51:06 2006 Subject: [Nav-users] Problems adding users Message-ID: <8EEE7738AEDF6947B3E5508A0244D1C27D128E(a)stam.himolde.no> Seems like som postgres problem to me. After trying to add a new user I did a ps command on the nav-box: postgres 5836 0.0 2.9 41216 14936 pts/0 S 01:16 0:00 postgres: navwrite navprofiles 127.0.0.1(55524) idle in transaction postgres 5850 0.0 3.0 41480 15908 pts/0 S 01:16 0:00 postgres: navwrite navprofiles 127.0.0.1(55530) idle in transaction postgres 5852 0.0 2.9 41216 14940 pts/0 S 01:16 0:00 postgres: navwrite navprofiles 127.0.0.1(55532) idle in transaction postgres 5856 0.0 2.8 41216 14848 pts/0 S 01:16 0:00 postgres: navwrite navprofiles 127.0.0.1(55534) INSERT waiting I'm not sure what the idle in transaction and insert waiting means... It seems to me it's only the navprofiles database I have problems adding information into. I can not add new accounts or groups. But I can manage profiles for existing nav users (read admin user). - odd arne hauge > -----Original Message----- > From: nav-users-bounces(a)itea.ntnu.no > [mailto:nav-users-bounces@itea.ntnu.no] On Behalf Of Hauge Odd Arne > Sent: Wednesday, January 04, 2006 3:47 PM > To: nav-users(a)itea.ntnu.no > Subject: [Nav-users] Problems adding users > > Hi. > > While testing the bleeding edge of Nav I'm having problem > adding users. > I get the following output in my browser when I tries to add > a new user: > "no such account 1000" > > Any suggestions ? > > Regards > Odd Arne Hauge > > > _______________________________________________ > Nav-users mailing list > Nav-users(a)itea.ntnu.no > http://mailman.itea.ntnu.no/mailman/listinfo/nav-users >

1 0

A couple of bugs
by kjetil.olsen＠usit.uio.no 04 Jan '06

04 Jan '06

We have problems when we configure IP-addresses directly on physical interfaces on routers (cisco catalysts or ordinary cisco-routers e.g. 7206) and connect them to switches (we use switches to interconnect several routers). The interfaces are discovered by gdd, but not placed in the correct VLAN even if we use the correct description-field (with VLAN ID) and the VLAN is known to NAV, and the switch is correctly configured with VLAN. This messes up the traffic-map, making it usesless.... (In NAV2 this works like a charm....) I would think that more detailed debugging is needed :-) Contact nett-drift(a)usit.uio.no to get access. And while I'm at it.... A second bug (that I think has been mentioned before, but): The cricket-config does not contain the correct decription-fields on routers. The router is OK, and the "Router ports" report (.../report/gwport) is also OK, but cricket says "No decription available". On switches we do not see this problem, port descriptions show up fine in cricket. I guess that "makecricketconfig" is to blame in one way or another :-) And a third one :-) In the traffic-map I can right-click on a router and get a router-menu. Choosing "Netlist" tryes to access cricket, not the reports.... --Kjetil

2 1

Feature requests anyone?
by kjetil.olsen＠usit.uio.no 04 Jan '06

04 Jan '06

Use of SNMPv2-counters (64-bit) in cricket. We have a number of interfaces that already have problems with interfaces having more than 2^32 bytes pr minute of traffic. --Kjetil

1 0

Feature requests anyone?
by Vidar.Faltinsen＠uninett.no 04 Jan '06

04 Jan '06

Hi, As I mentioned in a previous posting NTNU and UNINETT are currently planning the 2006 NAV activity. We are more ambitious this year and are prepared to put a lot of resources into maintaining and further developing NAV. We are currently working on a list of new features to implement. I could present the list, but at this stage I will rather ask the NAV community... what do you want? We certainly have some ideas ourselves, partly based on feedback, both on- and offline. Nevertheless, please empty your (navish) heart and express your wishes! This is your chance (well, one of them). We are interested in request for both the short and long term. I assume more smooth installation, maybe support for certain equipment types, etc, is on the list. Further - in terms of new and/or improved functionality - what would you like? As NAV is an open source project, contributions are very much welcome. If you have plans or hopes in this respect, please let us know. All input is of value. This includes criticism. Looking forward to this thread! - Vidar >From woj at tstd.pl Wed Jan 4 14:08:58 2006 From: woj at tstd.pl (Wojciech Kozicki) Date: Wed Jan 4 14:09:16 2006 Subject: [Nav-users] Cisco 7140 - nav can't see some of router interfaces In-Reply-To: <Pine.LNX.4.64.0601041333510.18181(a)tyholt-ng.uninett.no> References: <200601041322.24818.woj(a)tstd.pl> <Pine.LNX.4.64.0601041333510.18181(a)tyholt-ng.uninett.no> Message-ID: <200601041408.59366.woj(a)tstd.pl> On Wednesday 04 January 2006 13:41, you wrote: > On Wed, 4 Jan 2006, Wojciech Kozicki wrote: > > Hello, > > > > I have couple of cisco 7140, and NAV can't see all routers interfaces. In > > router-ports report I can see only some of ATM interfaces, but not all. > > Also, there is lack of Fast Etherent interfaces. I tried re-adding device > > to nav, but it didn't help. > > > > Missing subinterfaces are on different modules... > > > > What I should check? > > > > MRTG is working with this routers with no problem. > > MRTG has traffic counters for the interfaces that NAV are missing? yes, I am using in mrtg simply: ./cfgmaker <snmp read community>@$<ip address> > mrtg_file.cfg I just checked, mrtg also can't see fast ethernet subinterfaces, but it can see main fast etherent interfaces, and ALL atm subinterfaces. Missing (in NAV) atm interfaces are configured typically. > You should verify what the router returns of ifindexes/ifdescr from > the interfaces MIB. I know the support has been varying in respect > to fast/gigethernet-based subinterface support. At one point ios > gave us the ifindexes, but the octet counters were not maintained. > > Do a snmpwalk directly to the router in question, something like: > > snmpwalk -On -c <snmp read community> -v2c <ip address> ifdescr > > or > > snmpwalk -On -c <snmp read community> -v2c <ip address> > .1.3.6.1.2.1.2.2.1.2 > I did it. I can see there missing atm subinterfaces, and fast Ethernet interfaces but no fast ethernet subinterfaces (802.1q). regards, thanks for help -- Woj >From woj at tstd.pl Wed Jan 4 14:16:53 2006 From: woj at tstd.pl (Wojciech Kozicki) Date: Wed Jan 4 14:17:09 2006 Subject: [Nav-users] Cricket error In-Reply-To: <b4c110fd0601040447k55a8ddedp1f28b253ead29847(a)mail.gmail.com> References: <OF63248337.796A72F9-ONC12570E5.003234BD-C12570E5.003740CC(a)uis.no> <43BBC1DB.7030408(a)ntnu.no> <b4c110fd0601040447k55a8ddedp1f28b253ead29847(a)mail.gmail.com> Message-ID: <200601041416.54494.woj(a)tstd.pl> On Wednesday 04 January 2006 13:47, Kristian Eide wrote: > > I am not sure how to add OID's to NAV without messing with the database, > > perhaps some other NAV-developer may answer this? > > I think editDB has support for adding new OIDs. > Yes, there is, but I can't find descriptions Howto fill form: OID key * Snmpoid * OID source Match regexp OID name MIB Description Can somebody give some detailed info, how to fill these fields, and how will this work with cricket? regards -- Woj >From ddeineka at gmail.com Wed Jan 4 15:39:43 2006 From: ddeineka at gmail.com (Dmitry Deineka) Date: Wed Jan 4 14:39:53 2006 Subject: [Nav-users] Feature requests anyone? In-Reply-To: <Pine.LNX.4.64.0601041322380.18181(a)tyholt-ng.uninett.no> References: <Pine.LNX.4.64.0601041322380.18181(a)tyholt-ng.uninett.no> Message-ID: <a6fee5220601040539h59214bc6h(a)mail.gmail.com> So, Happy New Year to all ! I with to say thanks to NAV developers and community for great monitoring/network inventory software (but a bit difficult for install :-) We switch from nagios to NAV for number of reasons: 1) More visualizations 2) More reports 3) Great search functions (per mac, vlan, ports etc). Its really great! What I need with NAV: 1) SNMP trap handling. For example, we have number of small POPs with APC Smart UPS+AP9617 mgmnt cards installed. I wish to monitor power outages within NAV - for our duty staff (much less skilled than noc people :) is better to see one application on screen 2) SNMP polling and thresholds. Is link quality bad ? Is interface load too high or too low ? 3) More FreeBSD support. I think that following message from archive must be on NAV wiki: http://desperados.itea.ntnu.no/pipermail/nav-users/2005-December/001117.html With best regards, Dmitry 2006/1/4, Vidar Faltinsen <Vidar.Faltinsen(a)uninett.no>: > > Hi, > > > We are currently working on a list of new features to implement. > I could present the list, but at this stage I will rather ask the > NAV community... what do you want? > - Vidar > _______________________________________________ > Nav-users mailing list > Nav-users(a)itea.ntnu.no > http://mailman.itea.ntnu.no/mailman/listinfo/nav-users > -- Dmitry A.Deineka >From woj at tstd.pl Wed Jan 4 14:59:11 2006 From: woj at tstd.pl (Wojciech Kozicki) Date: Wed Jan 4 14:59:31 2006 Subject: [Nav-users] logger.conf Message-ID: <200601041459.11900.woj(a)tstd.pl> 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) Thanks for info regards -- Woj >From peder.sefland at hivolda.no Wed Jan 4 15:14:48 2006 From: peder.sefland at hivolda.no (Peder Magne Sefland) Date: Wed Jan 4 15:15:16 2006 Subject: SV: [Nav-users] logger.conf Message-ID: <s3bbe67d.030(a)HVO-3.hivolda.no> I have experience the same thing. But some of my switches that has only ip-adresse and no dns-name turn up in the Syslog Analyser. All the others turn up under "parsing errors" link. Do you have any false alerts on dns-mismatch? I'm not shure that this has anything to do with this. Peder Sefland >>> Wojciech Kozicki <woj(a)tstd.pl> 04.01.2006 14:59:11 >>> 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) Thanks for info regards -- Woj _______________________________________________ Nav-users mailing list Nav-users(a)itea.ntnu.no http://mailman.itea.ntnu.no/mailman/listinfo/nav-users >From woj at tstd.pl Wed Jan 4 15:20:18 2006 From: woj at tstd.pl (Wojciech Kozicki) Date: Wed Jan 4 15:20:35 2006 Subject: SV: [Nav-users] logger.conf In-Reply-To: <s3bbe67d.031(a)HVO-3.hivolda.no> References: <s3bbe67d.031(a)HVO-3.hivolda.no> Message-ID: <200601041520.19244.woj(a)tstd.pl> On Wednesday 04 January 2006 15:14, Peder Magne Sefland wrote: > I have experience the same thing. But some of my switches that has only > ip-adresse and no dns-name turn up in the Syslog Analyser. All the > others turn up under "parsing errors" link. > > Do you have any false alerts on dns-mismatch? I'm not shure that this > has anything to do with this. > > All device names are resolved correctly, beacuse all hostname informations are in NAV machine /etc/hosts file. -- Woj >From Vidar.Faltinsen at uninett.no Wed Jan 4 15:28:53 2006 From: Vidar.Faltinsen at uninett.no (Vidar Faltinsen) Date: Wed Jan 4 15:29:12 2006 Subject: [Nav-users] Feature requests anyone? In-Reply-To: <7DA8B65EACA61E4B8DC3FA6668A53E420FF471(a)edxmb3.jdnet.deere.com> References: <7DA8B65EACA61E4B8DC3FA6668A53E420FF471(a)edxmb3.jdnet.deere.com> Message-ID: <Pine.LNX.4.64.0601041525220.18181(a)tyholt-ng.uninett.no> On Wed, 4 Jan 2006, McDermott Troy wrote: > First off, thank you all very much for creating and maintaining this > software; it's made my job (and life) much easier. ...and life - wow! Thank you! > One little suggestion: a non-cisco syslog module, where syslog output > from devices like UPS, non-cisco switches, and so on could be viewed > through the web interface. Even something simple that would be > searchable with text strings and regexp would be very helpful. Thank you for your input. We will definitely consider this. > Thanks for asking! > > -Troy - Vidar > >> -----Original Message----- >> From: nav-users-bounces(a)itea.ntnu.no >> [mailto:nav-users-bounces@itea.ntnu.no] On Behalf Of Vidar Faltinsen >> Sent: Wednesday, January 04, 2006 7:02 AM >> To: nav-users(a)itea.ntnu.no >> Subject: [Nav-users] Feature requests anyone? >> >> Hi, >> >> As I mentioned in a previous posting NTNU and UNINETT are >> currently planning the 2006 NAV activity. We are more >> ambitious this year and are prepared to put a lot of >> resources into maintaining and further developing NAV. >> >> We are currently working on a list of new features to implement. >> I could present the list, but at this stage I will rather ask >> the NAV community... what do you want? >> >> We certainly have some ideas ourselves, partly based on >> feedback, both on- and offline. Nevertheless, please empty >> your (navish) heart and express your wishes! This is your >> chance (well, one of them). >> >> We are interested in request for both the short and long term. >> >> I assume more smooth installation, maybe support for certain >> equipment types, etc, is on the list. Further - in terms of >> new and/or improved functionality - what would you like? >> >> As NAV is an open source project, contributions are very much welcome. >> If you have plans or hopes in this respect, please let us know. >> >> All input is of value. This includes criticism. Looking >> forward to this thread! >> >> - Vidar >> _______________________________________________ >> Nav-users mailing list >> Nav-users(a)itea.ntnu.no >> http://mailman.itea.ntnu.no/mailman/listinfo/nav-users >> >> > >From Vidar.Faltinsen at uninett.no Wed Jan 4 15:36:38 2006 From: Vidar.Faltinsen at uninett.no (Vidar Faltinsen) Date: Wed Jan 4 15:36:48 2006 Subject: [Nav-users] Feature requests anyone? In-Reply-To: <a6fee5220601040539h59214bc6h(a)mail.gmail.com> References: <Pine.LNX.4.64.0601041322380.18181(a)tyholt-ng.uninett.no> <a6fee5220601040539h59214bc6h(a)mail.gmail.com> Message-ID: <Pine.LNX.4.64.0601041529320.18181(a)tyholt-ng.uninett.no> On Wed, 4 Jan 2006, Dmitry Deineka wrote: > We switch from nagios to NAV for number of reasons: > 1) More visualizations > 2) More reports > 3) Great search functions (per mac, vlan, ports etc). Its really great! Valuable feedback, on behalf of the team, thank you! > What I need with NAV: > 1) SNMP trap handling. For example, we have number of small POPs with APC > Smart UPS+AP9617 mgmnt cards installed. I wish to monitor power outages > within NAV - for our duty staff (much less skilled than noc people :) is > better to see one application on screen This is on our list to. SNMP traps will be implemented. We will also have a particular focus on power, UPS and temperature statistics and alarms. > 2) SNMP polling and thresholds. Is link quality bad ? Is interface load too > high or too low ? On the list, been there (too) long. > 3) More FreeBSD support. I think that following message from archive must be > on NAV wiki: > http://desperados.itea.ntnu.no/pipermail/nav-users/2005-December/001117.html I agree. Will be done. > With best regards, > Dmitry - Vidar

2 1

Problems adding users
by odd.hauge＠hiMolde.no 04 Jan '06

04 Jan '06

Hi. While testing the bleeding edge of Nav I'm having problem adding users. I get the following output in my browser when I tries to add a new user: "no such account 1000" Any suggestions ? Regards Odd Arne Hauge

1 0

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