Nav-users

nav-users@lister.sikt.no

1376 discussions

Release-notice: NAV 3.0 beta 9
by morten.vold＠ntnu.no 21 Jan '05

21 Jan '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 NAV 3.0 beta 9 is now available download at http://metanav.ntnu.no/ . We will only be making RPM packages for SuSE Linux Enterprise Server from now on, since this is NTNU's primary server platform nowadays. We do encourage others to build binary packages for their favorite distribution, though. Upgrading from beta 8 ===================== The Java SNMP library now replaces WestHawk SNMP. Please remove your old WestHawk .jar file, download, compile and install Java SNMP 1.4 from http://edge.mcs.drexel.edu/GICL/people/sevy/snmp/snmp_package.html (or get binaries if available). Also, a few Cricket/makecricketconfig changes have taken place (as mentioned in the CHANGES file). The default configuration tree for Cricket needs to be reapplied from the new tarball (a few extra directories and files have been added). In the tarball, it is located at nav-3.0_beta9/subsystem/statTools/cricket/cricket-config/ - in the RPM installation it is found at /usr/local/nav/doc/cricket/cricket-config/ . You don't need to remove your existing generated Cricket config, just copy this files over the existing ones. Also, subtree-sets has been updated and must be overwritten. In the tarball you'll find it as nav-3.0_beta9/subsystem/statTools/cricket/cricket/subtree-sets, in the RPM it is found as /usr/local/nav/doc/cricket/cricket/subtree-sets Rerun makecricketconfig.pl after these changes. CHANGES ======= Version 3.0_beta9 (released 21 January 2005) User-visible changes: * For performance reasons, the WestHawk Java SNMP library has been discarded in favor of Java SNMP, which has a nice GPL license and doesn't hog resources by creating lots of threads. * Machine tracker searches have been redone to be more like in NAV 2, due to the complexity of automatic attempts at correlating CAM and ARP records.1 * Makecricketconfig should now generate correct interface descriptions for router interfaces in Cricket. * The previously disabled Server statistics support of Makecricketconfig has ben re-enabled and fixed. * Start/stop scripts now use "su -" when switching from root to navcron, to reset the environment before starting processes. This may have adverse effects if root has his/her environment variables set to locate NAV libraries while the navcron user doesn't. * The report system should now correctly count the number of gwports registered for a device in NAVdb. * Edit database no longer throws exceptions if NAVdb contains organizations without descriptions. * The default priorities of the web tools have been adjusted. * getDeviceData should no longer come out of sync with NAVdb, as it no longer works on a memory cache of the NAVdb. * getDeviceData no longer deletes prefixes of the 'scope' type (which makes the prefix matrix of the Report system work again). * Improvements to the module monitor of getDeviceData. * Load data is now available in the Traffic map. Known bugs in this version: * getDeviceData will at times seemingly "forget" some IP devices and stop retrieving updated information from them. Until this has been fixed, this can be worked around by restarting getDeviceData, either on a regular basis, or when inconsistencies between NAVdb and the real world are seen. 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 iD8DBQFB8R36XxIl0kpcOkQRAodWAJwMNR5/qW3yDE1YNQhlmYeeXn/rSACdHdMO klGsqgL2RZmGYpQSKK8vl/s= =CQbM -----END PGP SIGNATURE----- >From Ketil.Forselv at hin.no Fri Jan 21 20:00:58 2005 From: Ketil.Forselv at hin.no (Forselv Ketil) Date: Fri Jan 21 20:01:09 2005 Subject: [Nav-users] Release-notice: NAV 3.0 beta 9 Message-ID: <4147C56944E2B64D978FA0EAB10A14FA4B090D(a)fagserver2.fag.hin.no> Hi Compiled and install tarbal for Nav 3.0 beta 9 on Redhat 9.0 on my test box http://jimmie.hin.no, and everything seems to work fine. (Don't forget to change src/webapps/navAdmin/build.xml line 131 to match your jakarta-tomcat installation) Morten Vold said: > > * Makecricketconfig should now generate correct interface > descriptions for router interfaces in Cricket. Not yet, still get "No description available" This release solved the problems with collecting data from 2980-switches. Regards Ketil > > 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 > > iD8DBQFB8R36XxIl0kpcOkQRAodWAJwMNR5/qW3yDE1YNQhlmYeeXn/rSACdHdMO > klGsqgL2RZmGYpQSKK8vl/s= > =CQbM > -----END PGP SIGNATURE----- > _______________________________________________ > Nav-users mailing list > Nav-users(a)mailman.itea.ntnu.no > http://mailman.itea.ntnu.no/mailman/listinfo/nav-users >

1 0

no VLAN information in NAV
by kreide＠online.no 21 Jan '05

21 Jan '05

>Yes, I tried... nothing in Cricket, but NAV itself can list all the interfaces >in report/swport?b1.netboxid=9, but in browse mode, in switchports section >there is nothing. >In report/swport?b1.netboxid=9 >sections: >duplex,media,trunk,vlan,portname,Connected to netbox,Module - empty. So the switch interfaces are indeed listed with ifindex number and speed, but the other fields you mention are empty, is this correct? If this is the case then we would need specific Alcatel support. Does the Alcatel devices support CDP? And are any MAC addresses from them collected? >I dont understand - support in NAV means support in Cricket too? Probably not, however, I am not responsible for Cricket in NAV and thus I do not have complete knowledge of this. -- Kristian

1 0

no VLAN information in NAV
by woj＠tstd.pl 21 Jan '05

21 Jan '05

Dnia pi?tek, 21 stycznia 2005 15:30, Kristian Eide napisa?: > >But... I have whole bunch of alcatel stuff, which is not supported... > > Have you tried? If they use the same OIDs as other device types NAV should > be able to support them. Yes, I tried... nothing in Cricket, but NAV itself can list all the interfaces in report/swport?b1.netboxid=9, but in browse mode, in switchports section there is nothing. In report/swport?b1.netboxid=9 sections: duplex,media,trunk,vlan,portname,Connected to netbox,Module - empty. I dont understand - support in NAV means support in Cricket too? > >PS. What about progress in beta9? > > The plan is to get it out the door by the end of the day. > :) -- Wojciech (Woj) Kozicki

2 1

no VLAN information in NAV
by kreide＠online.no 20 Jan '05

20 Jan '05

>The best solution would be some interface for adding something new devices, >and snmp-specific data for them. So, You want me to send snmpwalk, or just >oids for collecting data from interfaces or cpu? Snmpwalks please (but include the full numeric OID as well). >I haven't got any link that allows any vlan on trunk, but I have static vlans >administration, in VTP the maybe different. Since for most of our trunks this is dynamic we found it easier to handle all trunks in the samme manner, also for the static cases. >=> Running makeinterfaceTargets with dir=router-interfaces <= >Use of uninitialized value in concatenation (.) or string >at /usr/lib/nav/makecricketconfig.pl line 831. I have informed our Cricket responsable of this error. -- Kristian

1 0

no VLAN information in NAV
by woj＠tstd.pl 20 Jan '05

20 Jan '05

Dnia czwartek, 20 stycznia 2005 11:09, John Magne Bredal napisa?: > Wojciech Kozicki wrote: > > Last question, bugfixes (ip prefix scope graph, cricket desc for routers > > etc.) - when? :) > > Hi. > > The description on router-interfaces is found by making a SQL-query by > your own preference and adding this query to the .nav-file in > cricket-config/router-interfaces. Of course this is only possible if you > know the database and thus there exists a default query. And the default > query is not working at the moment :) but in beta9... :) > So a fix for description on router-interfaces: > > Open the file cricket-config/router-interfaces/.nav with your preferred > text-editor (which of course is emacs ;) ), or VIM :-P > and find the line that > starts with descr. Replace the table gwport with gwportprefix in the > query. The next time makecricketconfig.pl runs, it should use this query > to make the description on the router-interfaces. regards -- Wojciech (Woj) Kozicki

1 0

no VLAN information in NAV
by kreide＠online.no 20 Jan '05

20 Jan '05

>Well, but via SNMP you have direct info about trunks, vlans and so on. Maybe >if finding whole chain fails You can always display the vlan number on port, >because it really is true. It doesn't have to be though, many devices will just have the vlan at the default '1' value which is why we have the current solution. >I can provide snmp walk and oids for this, we are running mrtg and rrdtool for >taking stats from linux machines, it is really no problem, mrtg does it >automatically. If you make some interface for this I can try to put some >linux stuff to Nav. Do you have experience with Java programming? If so it should be easy to add yourself. If not please send any SNMP walks and we can try to add it for you. >> However, we cannot display VLAN numbers for trunks >> without actually traversing the whole chain. We can only access the VLANs allowed on the trunk (we already collect this info), but this might be very different from what is actually running (many sites simply allow all VLANs on the trunks). For this reason we try to determine which VLANs are actually active on the trunk. >Last question, bugfixes (ip prefix scope graph, cricket desc for routers etc.) >- when? :) Fixes will be part of the beta9 release, due out shortly (hopefully today or tomorrow). As for the cricket bug you can apply the fix ourself. Edit the file: /usr/share/doc/nav/cricket/cricket-config/router-interfaces/.nav On the line starting with descr = change the SQL statement to: select nettype,netident from gwportprefix left join prefix using (prefixid) left join vlan using (vlan) where gwportid=$id and netident is not null Then run makecricketconfig. -- Kristian

2 1

no VLAN information in NAV
by woj＠tstd.pl 20 Jan '05

20 Jan '05

Dnia czwartek, 20 stycznia 2005 09:50, Kristian Eide napisa?: > You are right that at least some of the problems are related to your > network architecture. NAV tries to build its own view of the network > structure so it can determine exactly which VLANs run on each trunk. This > does require an unbroken chain, however, and in your case we do not support > all parts of the chain. Well, but via SNMP you have direct info about trunks, vlans and so on. Maybe if finding whole chain fails You can always display the vlan number on port, because it really is true. > You can certainly help with adding such support! The data collection > system, getDeviceData, is written in Java. You can look here for docs: > > http://metanav.ntnu.no/javadoc/no/ntnu/nav/getDeviceData/deviceplugins/Devi >ceHandler.html > > > The procedure for adding a new device plugin is relatively straight forward > if you know how to collect the required data from the devices. I would be > happy to extend any assistance in this process. Does the Linux server run > an SNMP daemon which can be queried for the required info? I can provide snmp walk and oids for this, we are running mrtg and rrdtool for taking stats from linux machines, it is really no problem, mrtg does it automatically. If you make some interface for this I can try to put some linux stuff to Nav. > As for the case where you have a normal router -> switch link, which router > is this and what type (I assume you have added it to NAV)? We also make use > of CDP to determine on which port on the router and switch the link is > connected, thus CDP must be enabled and supported on both ends for this to > work. for default I always disable cdp, but I will make some tests today, and will turn it on. Our cisco routers: 7507 7140 7206 > > As for ATM, I don't believe we support this case currently. We would like > to expand our support for such cases of course, but a solution where we > display the VLAN number even if NAV has not been able to verify the chain > might be a good idea. I think so too. > However, we cannot display VLAN numbers for trunks > without actually traversing the whole chain. why? [cut] Last question, bugfixes (ip prefix scope graph, cricket desc for routers etc.) - when? :) regards -- Wojciech (Woj) Kozicki

1 0

problem with prefix scope
by woj＠tstd.pl 19 Jan '05

19 Jan '05

Hi, I'm trying to add prefix scope, I have some subnets belong to this scope in report/prefix, but after lunching /report/matrix it shows nothing. Second - my scope disappears after while from database... what I should check? -- Wojciech (Woj) Kozicki >From kreide at online.no Wed Jan 19 14:09:18 2005 From: kreide at online.no (Kristian Eide) Date: Wed Jan 19 14:09:27 2005 Subject: [Nav-users] no VLAN information in NAV Message-ID: <41EF51B3(a)epostleser.online.no> >well, this is mine main problem - NAV can't see my vlans from cisco 2900, >2900xl Can you see them via SNMP? What does the following command give: snmpwalk -c public <ip> 1.3.6.1.4.1.9.9.68.1.2.2.1.2 -- Kristian

2 1

no VLAN information in NAV
by kreide＠online.no 19 Jan '05

19 Jan '05

> netboxid | vlanid | vlan | sysname | to_netboxid | to_swportid | trunk | >substr Ok, this helps. Can I ask which VLANs are missing on the switches? Where do they originate? NAV starts at the top (at the router) and explores downward, and if it cannot find the starting point the VLAN will not be visible in any reports. Could you give the output of this SQL too with slightly more information? SELECT DISTINCT module.netboxid,typename,gwport.interface,vlanid,vlan.vlan,sysname,gwport.to_n etboxid,gwport.to_swportid,trunk,substr(hexstring,0,3) FROM prefix JOIN vlan USING(vlanid) JOIN gwportprefix ON (prefix.prefixid = gwportprefix.prefixid AND (hsrp='t' OR gwip::text IN (SELECT MIN(gwip::text) FROM gwportprefix GROUP BY prefixid HAVING COUNT(DISTINCT hsrp) = 1))) JOIN gwport USING(gwportid) JOIN module USING(moduleid) JOIN netbox USING (netboxid) JOIN type USING(typeid) LEFT JOIN swport ON (gwport.to_swportid=swportid) LEFT JOIN swportallowedvlan USING (swportid) ORDER BY vlan.vlan; Thank you, I hope we can get this sorted out soon. -- Kristian

1 0

no VLAN information in NAV
by kreide＠online.no 19 Jan '05

19 Jan '05

>Report: (found 0 records) > New count: 0, Update count: 0 Dup count: 0, Rem count: 0 Unused count: 0, >Rename vlan count: 0 The problem is the networkDiscovery module doesn't find any routers to start exploring VLANs from. This is a bit complex to debug, but could you send me the output of: SELECT DISTINCT module.netboxid,vlanid,vlan.vlan,sysname,gwport.to_netboxid,gwport.to_swportid ,trunk,substr(hexstring,0,3) FROM prefix JOIN vlan USING(vlanid) JOIN gwportprefix ON (prefix.prefixid = gwportprefix.prefixid AND (hsrp='t' OR gwip::text IN (SELECT MIN(gwip::text) FROM gwportprefix GROUP BY prefixid HAVING COUNT(DISTINCT hsrp) = 1))) JOIN gwport USING(gwportid) JOIN module USING(moduleid) JOIN netbox USING (netboxid) LEFT JOIN swport ON (gwport.to_swportid=swportid) LEFT JOIN swportallowedvlan USING (swportid) ORDER BY vlan.vlan; Thank you for assisting us in debugging this problem. -- Kristian

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