Nav-users

nav-users@lister.sikt.no

1 participants
1378 discussions

adding cisco 2900XL switch to NAV
by woj＠tstd.pl 14 Feb '05

14 Feb '05

Hi, After adding another Cisco Catalyst 2900xl switch to NAV I get following error: --> Mod_python error: "PythonHandler editdb" Traceback (most recent call last): File "/usr/lib/python2.3/site-packages/mod_python/apache.py", line 299, in HandlerDispatch result = object(req) File "/var/www/nav/editdb/editdb.py", line 156, in handler output = editPage(req,pageList[table](),request,unicodeError) File "/var/www/nav/editdb/editdb.py", line 463, in editPage outputForm,action) File "/var/www/nav/editdb/editdb.py", line 2435, in add disabled=True)) TypeError: __init__() takes at least 2 non-keyword arguments (1 given) <-- One 2900xl is running in NAV, but I had to add new type, because NAV don't recognize these switches. When I am trying to add another 2900 switch, after clicking add I have: "Error: pysnmp.asn1.error.ValueConstraintError: Single value constraint for Version: 0 not within allowed values" then, clicking continue once again, I have proper recognize of type (because I added it earlier), but serial number is: "0x10". So, continue once again and... there is error which I quoted on top. Also - in beta9: - IP scope is not working, - Traffic Map crashes my FireFox sometimes, in Konqueror there is applet failed info. - still no desc for routers interfaces in Cricket - what about traffic measure in traffic map? I am using Debian packet of NAV best regards -- Wojciech (Woj) Kozicki >From woj at tstd.pl Fri Feb 11 11:15:42 2005 From: woj at tstd.pl (Wojciech Kozicki) Date: Fri Feb 11 11:16:14 2005 Subject: [Nav-users] adding cisco 2900XL switch to NAV Message-ID: <200502111115.42876.woj(a)tstd.pl> Dnia czwartek, 10 lutego 2005 08:31, Fredrik Holmberg napisa?: > nav3:~ # diff /usr/local/nav/cricket/cricket-config/router-interfaces/.nav > /usr/local/src/nav-3.0_beta9/subsystem/statTools/cricket/cricket-config/rou >t er-interfaces/.nav > 14c14 > < descr = select nettype,netident from gwportprefix left join prefix using > (prefixid) left join vlan using (vlanid) where gwportid=$id and netident is > not null > --- > > > descr = select nettype,netident from gwportprefix left join prefix > > using > > (prefixid) left join vlan using (vlan) where gwportid=$id and netident is > not null ok, I patched it and it worked! But. In Debian installation navcron user hasn't got bash (/bin/false only). When I gived bash to navcron user and started makecricketconfig.pl there where some access denied errors. But it worked after running makecricketconfig.pl as root. Another question. After adding new switch to nav, and running makecricketconfig.pl, when I should see first stats for this switch? I have some new switches in NAV, but I can't see them in cricket. best regards. -- Wojciech (Woj) Kozicki

2 4

Release-notice: NAV 3.0 beta 10
by morten.vold＠ntnu.no 12 Feb '05

12 Feb '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 NAV 3.0 beta 10 is now available download at http://metanav.ntnu.no/ . Upgrading from beta 8 ===================== Memory collection has been added, and requires a small update to the NAVdb schema. Please run 3.0_beta10.sql and snmpoid.sql from doc/sql/upgrades/ as documented in the README file of the same directory. CHANGES ======= Version 3.0_beta10 (released 11 February 2005) ##################################################################### ## WARNING WARNING WARNING WARNING WARNING WARNING WARNING ## ##################################################################### ## ## ## This release makes changes to the NAV database. If you are ## ## upgrading from a previous release you also need to upgrade your ## ## database schema. For information on how to upgrade the database ## ## schema, please take a look in doc/sql/upgrades for more ## ## information. ## ## ## ##################################################################### Improvements: * gDD now makes sure to give priority to new devices when its work load with old devices is high. * gDD now refers to IP Devices by sysname in its logs, making it easier to track its actions when reading the logs. * gDD now correctly updates the netident of elinks. * gDD will now also attempt to extract software version information from a device's sysDescr OID (also collects sw_ver for the device itself, and not just its modules). * A bug that prevented the service monitor's LDAP plugin from functioning from time to time was fixed. * Router ports that are administratively down are removed from NAVdb by gDD. * The report generator now supports multi-line and complex SQL queries. * The SQL queries of the netbox, gw, sw, edge and wlan reports were optimized for speed. Additions: * gDD will now collect memory information from devices. Be advised that I haven't had time to test this release, good luck! - -- Morten Vold NTNU ITEA Integrasjonsgruppen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCDMJjXxIl0kpcOkQRAjpLAJ9/WKL/PYy33e4zb7Vfe1vnhAIO+gCgvZSJ CFtL8itSXRWK5LJoG7jWoiI= =kN/H -----END PGP SIGNATURE----- >From Ketil.Forselv at hin.no Fri Feb 11 18:36:31 2005 From: Ketil.Forselv at hin.no (Forselv Ketil) Date: Fri Feb 11 18:36:37 2005 Subject: SV: [Nav-users] Release-notice: NAV 3.0 beta 10 Message-ID: <4147C56944E2B64D978FA0EAB10A14FA4B0980(a)fagserver2.fag.hin.no> Hi I get compile-error for building getDeviceData when trying to compile source-code for Beta_10 (Redhat 9.0) Regards Ketil Building getDeviceData ... (cd getDeviceData && /usr/local/ant/bin//ant ) && touch getDeviceData Buildfile: build.xml init: [mkdir] Created dir: /root/beta10/nav-3.0_beta10/src/getDeviceData/build compile: [javac] Compiling 15 source files to /root/beta10/nav-3.0_beta10/src/getDeviceData/build [javac] /root/beta10/nav-3.0_beta10/src/getDeviceData/src/OidTester.java:76: cannot resolve symbol [javac] symbol : method setNetbox (java.lang.String) [javac] location: class no.ntnu.nav.logger.Log [javac] Log.setNetbox(nb.getSysname()); [javac] ^ [javac] /root/beta10/nav-3.0_beta10/src/getDeviceData/src/OidTester.java:286: cannot resolve symbol [javac] symbol : method setNetbox (<nulltype>) [javac] location: class no.ntnu.nav.logger.Log [javac] Log.setNetbox(null); [javac] ^ [javac] /root/beta10/nav-3.0_beta10/src/getDeviceData/src/QueryNetbox.java:720: cannot resolve symbol [javac] symbol : method setNetbox (java.lang.String) [javac] location: class no.ntnu.nav.logger.Log [javac] Log.setNetbox(sysName); [javac] ^ [javac] /root/beta10/nav-3.0_beta10/src/getDeviceData/src/QueryNetbox.java:849: cannot resolve symbol [javac] symbol : method setNetbox (<nulltype>) [javac] location: class no.ntnu.nav.logger.Log [javac] Log.setNetbox(null); [javac] ^ [javac] 4 errors BUILD FAILED /root/beta10/nav-3.0_beta10/src/getDeviceData/build.xml:62: Compile failed; see the compiler error output for details. Total time: 2 seconds make[1]: *** [getDeviceData] Error 1 make[1]: Leaving directory `/root/beta10/nav-3.0_beta10/src' make: *** [all] Error 1

2 1

Uplink (eLink) in vLanPlot
by odd.hauge＠himolde.no 08 Feb '05

08 Feb '05

Hi. In Nav2 it was possible to get the uplink in the Traffice Map (vLanPlot) by adding something like this in the vlan.txt file: 999:elink,molde-gw,trd-gw:128.39.46.132/30. Is there a similar method in Nav3 to get the uplink shown without having snmp-access to the uplink router ? - odd arne hauge

1 0

vlanplot and relation "boks"
by Aage.Olai.Johnsen＠hitos.no 07 Feb '05

07 Feb '05

Hi there. Having troubles with vlanplot on Nav 3beta8. Since everything seems to be working, no updates have been done to the installation. But the vlanplot-interface show error "an error occured fetching data from server:" when accessing lokal lans. Example: h**ps://nav.ingok.hitos.no/vlanPlot/ , and doubleklick on "158.39.19.1". Havent found any "boks" relations in any of the .sql-files from nav. Any tips? The tomcat gives this error: org.postgresql.util.PSQLException: ERROR: relation "boks" does not exist at org.postgresql.util.PSQLException.parseServerError(PSQLException.java:139) at org.postgresql.core.QueryExecutor.executeV3(QueryExecutor.java:156) at org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:101) at org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:43) at org.postgresql.jdbc1.AbstractJdbc1Statement.execute(AbstractJdbc1Statement .java:517) at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement .java:50) at org.postgresql.jdbc1.AbstractJdbc1Statement.executeQuery(AbstractJdbc1Stat ement.java:233) at org.postgresql.jdbc1.AbstractJdbc1Statement.executeQuery(AbstractJdbc1Stat ement.java:221) at no.ntnu.nav.Database.Database.query(Database.java:740) at no.ntnu.nav.Database.Database.query(Database.java:723) at SqlBoks.listBoks(vPServer.java:1243) at SqlBoks.serviceRequest(vPServer.java:129) at vPServer.service(vPServer.java:87) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applicati onFilterChain.java:200) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilter Chain.java:146) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve. java:209) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.inv okeNext(StandardPipeline.java:596) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433 ) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve. java:144) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.inv okeNext(StandardPipeline.java:596) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433 ) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2358) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:1 33) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.inv okeNext(StandardPipeline.java:596) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValv e.java:118) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.inv okeNext(StandardPipeline.java:594) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:1 16) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.inv okeNext(StandardPipeline.java:594) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433 ) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.ja va:127) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.inv okeNext(StandardPipeline.java:596) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433 ) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:152) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processCon nection(Http11Protocol.java:705) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.j ava:683) at java.lang.Thread.run(Thread.java:534) -Åge ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/

2 1

Nav3-Beta9 not collecting data
by kreide＠online.no 04 Feb '05

04 Feb '05

>It seems like the problem only occurs on re-added devices, because all of >the old devices are being updated as they should. I have investigated this problem, and the culprit turned out to be the transition to the new SNMP library. Specifically, the OID tester did not work properly, and that is why this problem only manifested itself for new or re-added devices. Our release coordinator, Morten Vold, is in Oslo this week, but he is back on Monday and we hope to have a new beta 10 release out early next week with this (and a few others) problem sorted out. We are sorry for the inconvenience. -- Kristian

1 0

IP address scope
by woj＠tstd.pl 01 Feb '05

01 Feb '05

Hi, In new NAV beta9 (debian version) IP address scope report still not working? best regards. -- Wojciech (Woj) Kozicki >From odd.hauge at hiMolde.no Thu Feb 3 22:18:49 2005 From: odd.hauge at hiMolde.no (Hauge Odd Arne) Date: Thu Feb 3 22:18:53 2005 Subject: [Nav-users] Nav3-Beta9 not collecting data Message-ID: <8EEE7738AEDF6947B3E5508A0244D1C201A3EA(a)stam.himolde.no> Hi. As mentioned in a previous email, NAV3b9 stopped collecting data after recreating and seeding the database. No swports, gwports, vlan, arp information are collected at all, as far as I can tell. Am I the only one with this problem ? I noticed some others had problem after they re-added devices. The nav-box can still be accessed through ssh if someone in the developer-team wants to take a further look. Regards Odd Arne Hauge

1 0

some adjustments
by kreide＠online.no 01 Feb '05

01 Feb '05

>I tried to re-add some devices, for example a Catalyst 2980 GA >(1.3.6.1.4.1.9.5.51) and a Catalyst 2948 G (1.3.6.1.4.1.9.5.42). >Would some logs be of any interest? If you could send the getDeviceData.log file as well as the IP numbers of the devices in question that would be helpful. -- Kristian

2 2

SV: [Nav-users] some adjustments
by fredrik.holmberg＠luh.hihm.no 31 Jan '05

31 Jan '05

Thank you for helping out here, Kristian :) Restarted NAV with the new getDeviceData.jar, and it has been running for about three hours now. It still seems like NAV is having problems with collecting information about ports and modules. I tried to re-add some devices, for example a Catalyst 2980 GA (1.3.6.1.4.1.9.5.51) and a Catalyst 2948 G (1.3.6.1.4.1.9.5.42). Looked through some tables in the database, where I can find data from other switches, but I can't find any port/module information from those two. Cricket on the other hand collects Memory and SysUptime from them, but no statistics about the ports. Would some logs be of any interest? - Fredrik Holmberg -----Opprinnelig melding----- Fra: Forselv Ketil [mailto:Ketil.Forselv@hin.no] Sendt: 30. januar 2005 22:17 Til: Fredrik Holmberg Kopi: nav-users(a)itea.ntnu.no Emne: RE: [Nav-users] some adjustments I'm also experiencing this (for Cat7200, Cat6509 and Cat3750). Cat2948G and 2980G, which beta 8 couldn't handle, works fine in beta 9. - Ketil Hauge Odd Arne said: > > Yes I'm experiencing this. I thought it was problems with the switch > type... But may be it's not... > > - odd arne hauge > > Fredrik Holmberg said: >> >> After upgrading to Beta 9, re-adding a switch to the database results in >> NAV >> having trouble showing switchports/modules etc. in Report (and Cricket as >> well). It just says "0" on both modules and ports. >> Anyone else experiencing this? >> >>

1 0

some adjustments
by odd.hauge＠hiMolde.no 28 Jan '05

28 Jan '05

Yes I'm experiencing this. I thought it was problems with the switch type... But may be it's not... - odd arne hauge -----Original Message----- After upgrading to Beta 9, re-adding a switch to the database results in NAV having trouble showing switchports/modules etc. in Report (and Cricket as well). It just says "0" on both modules and ports. Anyone else experiencing this?

1 0

NAV Problem with 7206 and 6509
by Jan.Susegg＠hint.no 26 Jan '05

26 Jan '05

After upgrading to NAV 3.0 beta 9 I added a Cisco 7206 router to NAV and NAV doesn't detect any interfaces :( I also added a Cisco 6509 with supervisor card and NAV doesn't detect any router interfaces or switchports and it doesn't extract any vlan information Doesn't NAV 3.0 beta 9 support 7206 and 6509? if it does, what might the problem be? Here are some error messages from getBoksmac.log Jan 26 10:10:40 2005 getBoksData_00 QUERY_NETBOX-6-RUN Now working with(79): levanger-gsw.hint.no (cat6509) (50 of 51 left) Jan 26 10:10:40 2005 getBoksData_00 QUERY_NETBOX-6-GET_OID OID is missing for oidkey: cdpNeighbour Jan 26 10:10:40 2005 getBoksData_00 QUERY_NETBOX-6-GET_OID OID is missing for oidkey: cdpNeighbour Jan 26 12:10:49 2005 getBoksData_01 QUERY_NETBOX-6-PROCESS_CDP cdpList is null for netboxid: 79 OID: null Jan 26 12:10:49 2005 getBoksData_01 QUERY_NETBOX-6-PROCESS_MAC Missing vlanSet for netboxid: 79, aborting Jan 26 12:10:49 2005 getBoksData_22 QUERY_NETBOX-6-RUN Now working with(77): levanger-gw.uninett.no (cis7206) (32 of 51 left) Jan 26 12:10:49 2005 getBoksData_22 QUERY_NETBOX-6-GET_OID OID is missing for oidkey: cdpNeighbour Jan 26 12:10:49 2005 getBoksData_22 QUERY_NETBOX-6-GET_OID OID is missing for oidkey: cdpNeighbour Jan 26 12:10:49 2005 getBoksData_22 QUERY_NETBOX-6-PROCESS_CDP cdpList is null for netboxid: 77 OID: null Jan 26 11:39:08 2005 getDeviceData_00 QUERY_NETBOX_T00-6-RUN Now working with(79): levanger-gsw.hint.no, type=cat6509, ip=xxx.xxx.xxx.xxx (device 51 of 51) Jan 26 11:39:14 2005 getDeviceData_00 ServerPlugin-6-canHandleDevice We cannot serve levanger-gsw.hint.no Jan 26 10:10:55 2005 getBoksData_13 QUERY_NETBOX-5-RUN Link, but no swports, for: (79) levanger-gsw.hint.no If: GigabitEthernet9/4 (33) snmpwalk -On -c xxxxxxx -v 1 levanger-gsw.hint.no 1.3.6.1.2.1 .1.3.6.1.2.1.2.2.1.2.75 = STRING: Vlan1 .1.3.6.1.2.1.2.2.1.2.76 = STRING: EOBC0/0 .1.3.6.1.2.1.2.2.1.2.77 = STRING: Null0 .1.3.6.1.2.1.2.2.1.2.78 = STRING: Loopback0 .1.3.6.1.2.1.2.2.1.2.79 = STRING: Loopback1 .1.3.6.1.2.1.2.2.1.2.81 = STRING: Vlan10 .1.3.6.1.2.1.2.2.1.2.82 = STRING: Vlan15 .1.3.6.1.2.1.2.2.1.2.83 = STRING: Vlan20 .1.3.6.1.2.1.2.2.1.2.84 = STRING: Vlan30 .1.3.6.1.2.1.2.2.1.2.85 = STRING: Vlan32 .1.3.6.1.2.1.2.2.1.2.86 = STRING: Vlan34 .1.3.6.1.2.1.2.2.1.2.87 = STRING: Vlan40 .1.3.6.1.2.1.2.2.1.2.88 = STRING: Vlan50 .1.3.6.1.2.1.2.2.1.2.89 = STRING: Vlan60 .1.3.6.1.2.1.2.2.1.2.90 = STRING: unrouted VLAN 1 .1.3.6.1.2.1.2.2.1.2.91 = STRING: unrouted VLAN 1002 .1.3.6.1.2.1.2.2.1.2.92 = STRING: unrouted VLAN 1004 .1.3.6.1.2.1.2.2.1.2.93 = STRING: unrouted VLAN 1005 .1.3.6.1.2.1.2.2.1.2.94 = STRING: unrouted VLAN 1003 .1.3.6.1.2.1.2.2.1.2.95 = STRING: unrouted VLAN 2 .1.3.6.1.2.1.2.2.1.2.96 = STRING: unrouted VLAN 10 .1.3.6.1.2.1.2.2.1.2.98 = STRING: unrouted VLAN 15 .1.3.6.1.2.1.2.2.1.2.99 = STRING: unrouted VLAN 20 .1.3.6.1.2.1.2.2.1.2.100 = STRING: unrouted VLAN 30 .1.3.6.1.2.1.2.2.1.2.101 = STRING: unrouted VLAN 32 .1.3.6.1.2.1.2.2.1.2.102 = STRING: unrouted VLAN 34 .1.3.6.1.2.1.2.2.1.2.103 = STRING: unrouted VLAN 40 .1.3.6.1.2.1.2.2.1.2.104 = STRING: unrouted VLAN 41 .1.3.6.1.2.1.2.2.1.2.105 = STRING: unrouted VLAN 50 .1.3.6.1.2.1.2.2.1.2.106 = STRING: unrouted VLAN 60 .1.3.6.1.2.1.2.2.1.2.107 = STRING: unrouted VLAN 90 ******************************************************** Jan Susegg F?rstekonsulent, IT-tjenesten H?gskolen i Nord-Tr?ndelag R?stad 7600 LEVANGER tlf: 74022711 mob: 91184451 ********************************************************

1 0

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