Nav-users Januar 2005

nav-users@lister.sikt.no

9 participants
29 discussions

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

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

19 Jan '05

> module | port | ifindex | vlan | vlanid >--------+------+---------+------+-------- > 1 | | 28 | | > 1 | 2 | 3 | 2 | Thank you. The vlan-number is there, but before it becomes visible on the web the networkDiscovery module needs to "see" it as well. Could you run the command: /usr/lib/nav/networkDiscovery.sh debug vlan And then send me the file: /var/log/nav/networkDiscovery/networkDiscovery-debug.html With this information I should hopefully be able to tell you what is going on. -- Kristian

2 1

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

19 Jan '05

>===== Original Message From woj(a)tstd.pl ===== >ok, changed descriptons on routers according to guide lines and it worked :) >only switches left. Good to hear! Hopefully the switches will also get the vlan set the next time networkDiscovery is run now that it is correct wrt routers. If not, send me the output of: select module,port,ifindex,vlan,vlanid from netbox join module using(netboxid) join swport using(moduleid) left join swportvlan using(swportid) where ip='<ip>'; Where <ip> is the IP of a switch missing VLAN info. -- Kristian

2 2

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

19 Jan '05

>But in logs, that I send you, and in some tables in database I can find some >vlan numbers... Your suggestion is to use these guide lines: >http://metanav.ntnu.no/moin.cgi/SubnetsAndVlans ? We try to find VLAN numbers on a best-effort basis, and for most devices this works. Where it doesn't, you can specify it manually in the interface descrption: see "Guide lines for configuring router interface descriptions" >> Are you able to look at the output written to the console by the applet? >> There it writes the URL it uses to fetch data from the server; if you could >> paste that link into a browser and provide the output it would be very >> helpful in debugging this issue. >In which log I can find this? You need to look at the Java console. On Windows you can find this by right-clicking the Java tray icon. -- Kristian

2 3

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

19 Jan '05

>> snmpwalk -c public <ip> 1.3.6.1.4.1.9.9.68.1.2.2.1.2 >positive You mean it lists the VLANs? Could you copy a couple of lines so I can verify? But NAV should be able to find the VLAN info in that case. Could you give me the output of the following SQL command? select oidkey from snmpoid join netboxsnmpoid using (snmpoidid) join netbox using(netboxid) where ip='<ip>'; Replace <ip> with the IP of one of your devices. -- Kristian

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Nav-users Januar 2005