Nav-users

nav-users@lister.sikt.no

1 participants
1378 discussions

Cabling and patch data removed in NAV 3.6?
by Vidar Faltinsen 13 Nov '09

13 Nov '09

nav-users, As you might know there is ongoing work on preparing a NAV 3.6beta. In 3.6 there are some changes to the database, i.e the interfaces will now relate directly to the netbox (switch or router), not to a module. We will still keep module information, but the strict mapping from interface to module is changed. This effects a number of front end (and back end) tools and we are in the process of updating it all. One system that is effected is the seed database subtool where you can add data on your twisted pair cabling and your patches from switch to jack in the wiring closets. We are seriously considering _not_ to maintain/keep this tool from 3.6. Our feeling is that _not_ many people use this part of NAV. It has never given full effect since the machine tracker does not include these data in its search results (which has been our intention of course). We also argue that by using sensible interface description naming standards you will in effect document the same data. I.e. if you set the jack number and room number as description of the switch ports that are patched to your end users/offices you have these data. The "details" link under interface in the MAC search results in machine tracker give this information (it displays the interface view of ip device info). In my opinion you should in fact do this documentation as part of your interface description, because this is useful when working directly with the switch through the CLI. Should you then double the work and do it both in the seed database patch register in addition?... Another argument is that other systems do cabling documentation more comprehensive. NAV has i.e. no support for documenting your fibre cabling. A system like Telemator (http://www.mxdata.no/) or equivalent cabling information systems do this better. Looking at integration between these systems and NAV is of course interesting. I know the University of Tromsø has done some interesting work here. Yet another mishap with the NAV patch register is that when you replace your switch with a new one, you will in the process loose your patch data for the switch and will have to do this registering from scratch again. So people out there - who is going to miss the patch and cabling part of NAV? Best regards, - Vidar

1 0

Re: EdgeCore ES4612 no port info
by Morten Brekkevold 10 Nov '09

10 Nov '09

On Mon, 09 Nov 2009 14:49:55 +0200 Kostua <kostua(a)innkom.zp.ua> wrote: >> I hope I will find something useful from the getDeviceData.log that >> can tell me why this happens. >> >> > ok, done. sending attachment. [...] > Nov 08 10:34:57 2009 172.16.2.49_13 CGW_DEVHANDLER-4-PROCESS_CGW Oidkeys [ifDescr, ifSpeed] are required, but not supported by 172.16.2.49, type ES4612, unable to fetch data! This tells me that the OID profile of the device is lacking, for some unknown reason. Please browse to Toolbox -> Report and search for 172.16.2.49 in the "IP Device Report" search box. What is the number in the "snmp" column? What is the list of oidkeys reported when you click on the number in the snmp column? To make getDeviceData re-profile the device, browse to Toolbox -> SeedDB -> IP Devices Edit, find 172.16.2.49 and edit it. Don't change anything, just click the "Update" button and finish the procedure. To speed things up, you can then restart getDeviceData. Tail getDeviceData.log and verify that you get several log messages from OID_TESTER about 172.16.2.49. When the messages stop appearing, please check the snmp column in the IP device report again. -- mvh Morten Brekkevold UNINETT

1 0

Re: EdgeCore ES4612 no port info
by Kostua 06 Nov '09

06 Nov '09

Ok. I recently moved NAV from vmware to dedicated server, and Cricket began to draw traffic graph. In "IP Device Info" show right numbers of ports (8) but port status of all ports indicated "Not active"

2 1

FYI: FreeBSD and XMPP
by Ingeborg Hellemo 21 Okt '09

21 Okt '09

In case someone wants to configure XMPP on FreeBSD the correct python-library to install is net-im/py-xmpppy (not net-im/py-pyxmpp...) --Ingeborg -- Ingeborg Østrem Hellemo -- ingeborg.hellemo(a)uit.no Dep. of Information Technology --- Univ. of Tromsø

1 0

Re: VS: Radius service monitor
by Istvan Bernath 16 Okt '09

16 Okt '09

Thanks for the kind reply! Right now all our active switches are registered in NAV. There are about 130 pcs. 2510-48 and a couple of 2600-8, 2610, 2626, 2650, 2810 and 2824. The core switches are two 5406 and a single 5412. Traffic data is collected from the switches correctly. Statistics are presented fine via Cricket. Alerts, like firmware upgrade and cold start, are all noticed via Alert Manager as it should. Topology right now is totally missing, but luckily I've cached a hint of topology with a single 2824 in the middle and one 2626 one 2650 and a 2510 as the neighbors before my colleague, sorry to say, have updated to the latest firmware. The magic surely was, that the 2824 had a complete CDP and LLDP implementation in the old firmware, while all the new HP firmware has only a crippled Receive Only CDP implementation. The missing topology is rather crucial since we can be flooded by SMS and mails in case a box at the top fails. MAC information is collected, so it is possible to find a MAC number belonging to an IP number, but the MAC is not associated to any switch port, so we can not trace MAC, and use Arnold. Service monitoring is rather important for us, since our server people do need a better identification of a functioning server than a simple ping. Needless to say that a process can fail while the server still is pingable. Right now we are monitoring DNS, HTTP, IMAP, SMB, SMTP with success. The only service we are missing, for the time beeing, is the RADIUS. If I can help the developers with any tests, I would be more than happy to do it! Thanks again! Istvan >>> Morten Brekkevold <morten.brekkevold(a)uninett.no> 10/15/09 11:14 AM >>> On Fri, 02 Oct 2009 12:12:41 +0200 "Istvan Bernath" <ibe(a)life.ku.dk> wrote: > Sorry about the inconvenience! > > I've been on the sidelines in the past 3 years, receiving all > messages from the nav-users list and running a maintained and > updated test installation all that time. > > To my pleasure this time it will be official, and the Faculty of > Life Sciences, Copenhagen University gives NAV a chance as the > global monitoring tool of all the new HP 2510 switches our net is > now upgraded to. Music to my ears. Although I'm curious as to how NAV will perform on an all HP network. We've had some problems with HP in the past. Not all of them are completely behind us, but they hopefully will be in NAV 3.6. > Monitoring of several services will also be crucial. NAV's service monitoring capabilities have been somewhat downplayed by UNINETT, due to lack of resources. We've left maintenance of those systems in the capable hands of the University of Tromsø. Hopefully, their developers can answer your questions, as I don't know radius or the service monitor all that well. I've prodded one of their guys to look at your servicemon question. > I have though problems with monitoring the Radius service, and booth > topology and MAC behind a port do not work with the new HP ProCurve > switches. Your topology problems are intriguing. Are you experiencing a total lack of topology information, or just plain wrong topology? I've had reports of the latter from other HP-heavy installations. Are you able to search any MAC data for any of your switches? > I hope somebody can help me rectifying the last problems. It might take some Q&A, but hopefully we can be of assistance :) -- mvh Morten Brekkevold UNINETT

3 2

Re: VS: Radius service monitor
by Istvan Bernath 15 Okt '09

15 Okt '09

Sorry about the inconvenience! I've been on the sidelines in the past 3 years, receiving all messages from the nav-users list and running a maintained and updated test installation all that time. To my pleasure this time it will be official, and the Faculty of Life Sciences, Copenhagen University gives NAV a chance as the global monitoring tool of all the new HP 2510 switches our net is now upgraded to. Monitoring of several services will also be crucial. I have though problems with monitoring the Radius service, and booth topology and MAC behind a port do not work with the new HP ProCurve switches. I hope somebody can help me rectifying the last problems. Kind Regards Istvan

2 1

EdgeCore ES4612 no port info
by Kostua 15 Okt '09

15 Okt '09

Hello nav users! When adding a new device EdgeCore ES4612 not provide information about activity at the ports. At Home > Reports > Switch ports: indicated only ifindex, module and port. via snmp everything looks fine: %snmpwalk -v2c -c some 172.16.2.49 ifSpeed IF-MIB::ifSpeed.1 = Gauge32: 1000000000 IF-MIB::ifSpeed.2 = Gauge32: 1000000000 IF-MIB::ifSpeed.3 = Gauge32: 1000000000 IF-MIB::ifSpeed.4 = Gauge32: 1000000000 IF-MIB::ifSpeed.5 = Gauge32: 1000000000 IF-MIB::ifSpeed.6 = Gauge32: 1000000000 IF-MIB::ifSpeed.7 = Gauge32: 1000000000 IF-MIB::ifSpeed.8 = Gauge32: 1000000000 IF-MIB::ifSpeed.9 = Gauge32: 1000000000 IF-MIB::ifSpeed.10 = Gauge32: 1000000000 IF-MIB::ifSpeed.11 = Gauge32: 1000000000 IF-MIB::ifSpeed.12 = Gauge32: 1000000000 %snmpwalk -v2c -c some 172.16.2.49 ifOperStatus IF-MIB::ifOperStatus.1 = INTEGER: up(1) IF-MIB::ifOperStatus.2 = INTEGER: up(1) IF-MIB::ifOperStatus.3 = INTEGER: up(1) IF-MIB::ifOperStatus.4 = INTEGER: lowerLayerDown(7) IF-MIB::ifOperStatus.5 = INTEGER: lowerLayerDown(7) IF-MIB::ifOperStatus.6 = INTEGER: lowerLayerDown(7) IF-MIB::ifOperStatus.7 = INTEGER: lowerLayerDown(7) IF-MIB::ifOperStatus.8 = INTEGER: lowerLayerDown(7) IF-MIB::ifOperStatus.9 = INTEGER: up(1) IF-MIB::ifOperStatus.10 = INTEGER: up(1) IF-MIB::ifOperStatus.11 = INTEGER: up(1) IF-MIB::ifOperStatus.12 = INTEGER: up(1) IF-MIB::ifOperStatus.19 = INTEGER: up(1) Any idea ?

2 5

VS: Radius service monitor
by Stokkenes Vidar 02 Okt '09

02 Okt '09

For some reason Istvan can't seem to get this mail through to the list. So forwarding it to help him out :) -Vidar -----Opprinnelig melding----- Fra: Istvan Bernath [mailto:ibe@life.ku.dk] Sendt: 30. september 2009 10:09 Til: nav-users(a)uninett.no Emne: Radius service monitor Hi, Is there anybody that can help me with the radius service monitor? In the /var/lib/nav/log/servicemon.log logfile there are entries suggesting that the process tries to communicate with the radius server, but that is not the case. Packet capture with Wireshark shows that there are no radius packages sent to the server. [2009-09-30 09:13:44] abstractChecker.py:run:118 [Info] xxx.yyy.zzz:radius -> Failed connecting to ('130.226.xxx.yyy', 1812): 'User-Name') [2009-09-30 09:13:44] rrd.py:update:109 [Debug] Updated xxx.yyy.zzz.31.rrd Just to be sure, a request with "radtest" produces a log entry on the radius server, and the expected packages can also be captured with Wireshark. rad_recv: Access-Accept packet from host xxx.yyy.zzz port 1812, id=101, length=20 Best Regards Istvan

2 1

Radius service monitor
by ibe＠life.ku.dk 01 Okt '09

01 Okt '09

Hi, Is there anybody that can help me with the radius service monitor? In the /var/lib/nav/log/servicemon.log logfile there are entries suggesting that the process tries to communicate with the radius server, but that is not the case. Packet capture with Wireshark shows that there are no radius packages sent to the server. [2009-09-30 09:13:44] abstractChecker.py:run:118 [Info] xxx.yyy.zzz:radius -> Failed connecting to ('130.226.xxx.yyy', 1812): 'User-Name') [2009-09-30 09:13:44] rrd.py:update:109 [Debug] Updated xxx.yyy.zzz.31.rrd Just to be sure, a request with "radtest" produces a log entry on the radius server, and the expected packages can also be captured with Wireshark. rad_recv: Access-Accept packet from host xxx.yyy.zzz port 1812, id=101, length=20 Best Regards Istvan

1 0

Uplink not show ( switches Cisco )
by jean.tomaz.da.silva＠gmail.com 17 Sep '09

17 Sep '09

Hi, Using "IP Device Info" the information about "Uplink" not is appear in the switch's Cisco. So, the tool "NetMap" show switchs like "disconnected". Does you can to help ? Best Regards, Jean Tomaz

2 6

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