I agree Vegard, Netdisco is a neat application. I would love to see the best of both applications combined.
Configuration file backup, perhaps even in a versioning system.
Vegard Vesterheim Vegard.Vesterheim@uninett.no 03/14/05 6:22 AM
On Mon, 14 Mar 2005 13:35:21 +0100 Magnus Nordseth magnus@ntnu.no wrote:
Wojciech Kozicki:
In my opinion main NAV problem is, that it is not flexible, there is
no
interface for adding custom devices. I was writing about this, but
there is
no feedback.
The SNMP::Info module is probably cool, but as the SNMP handling in
NAV is
written in java, it doesn't help us much.
I don't know enough details about the NAV database, but I would assume that alternative methods for harvesting SNMP data for insertion into the NAV database would be possible. Wouldn't it?
List of devices supported by SNMP::Info: http://snmp-info.sourceforge.net/DeviceMatrix.html
BTW, people taking interest in the SNMP::Info package should also be aware of the netdisco application (http://netdisco.org) for which SNMP::Info was created.
netdisco is an application similar to NAV in many respects. It is implemented solely in perl, has auto-discovery capabilities, has a full-fledged API for extensions, the main interface is web-based but a command line interface is provided as well. A nifty functionality is layer 2 traceroute which displays switch port details along one possible route between two IP adresses. netdisco also provides a 'Duplex Mismatch Finder'.
The web interface in netdisco is more basic, nowhere near as slick as NAV, but I guess some ideas from netdisco could be incorporated into NAV.
- Vegard - _______________________________________________ Nav-users mailing list Nav-users@itea.ntnu.no http://mailman.itea.ntnu.no/mailman/listinfo/nav-users
From kreide at online.no Mon Mar 14 16:16:50 2005
From: kreide at online.no (Kristian Eide) Date: Mon Mar 14 16:16:53 2005 Subject: [Nav-users] Use SNMP::Info to manage device types? Message-ID: 423687E7@epostleser.online.no
I don't know enough details about the NAV database, but I would assume that alternative methods for harvesting SNMP data for insertion into the NAV database would be possible. Wouldn't it?
Certainly, but we would also need some way to actually interpret the collected data, which is why we have not added more OIDs than those for which we actually have a way to process the data.
command line interface is provided as well. A nifty functionality is layer 2 traceroute which displays switch port details along one possible route between two IP adresses. netdisco also provides a
We have also implemented this in NAV (a short command line python program, as all the required data is already in the NAV database), in fact, it seems we can do better since we also collect the STP data and thus can see where the data is actually traveling, not just find the shortest path. Making a web version is not much work, perhaps we will include it as well if there is demand.
'Duplex Mismatch Finder'.
I think we already have such a report (?).
The web interface in netdisco is more basic, nowhere near as slick as NAV, but I guess some ideas from netdisco could be incorporated into NAV.
I liked the "network map". Since Netdisco is BSD licenced perhaps this could be integrated into NAV.
-- Kristian