|
From: Ingen S. J. v. (ICTS) <j.v...@ut...> - 2011-04-07 16:12:42
|
Hi Ivan, all, * wrt VRFs: correct... Netdisco doesn't understand VRFs, so you'll get incorrect results when there are overlapping networks. * I created a ticket for this in the Netdisco feature tracker on SF; see https://sourceforge.net/tracker/?func=detail&aid=3279530&group_id=80033&atid=558511. * Improved SQL is posted in the ticket (without formatting :-/ ); let me know if it's better. I verified the exact IP addresses for a couple of subnets and it looked OK with our data (even cross-checked with our tracking DB separate from Netdisco). * IMHO, this is not only useful for the community, I have to renumber large parts of our address space in the coming months. This feature will benefit me too, so that's the main reason for jumping on it immediately. Sorry to say but I'm a selfish coder :) Regards, Jeroen van Ingen ICT Service Centre University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands On Thu, 2011-04-07 at 17:49 +0200, Ivan Brunello wrote: > one last note: > - we use Cisco VRF-lite, and netdisco catches also arp entries in VRF :-) > > Ivan > > On Thu, Apr 7, 2011 at 5:34 PM, Ivan Brunello <iva...@gm...> wrote: > > I saw this. > > > > Right know it fits my needs: > > - I need to check against /26 and greater access networks, where > > device arp missing has little importance. > > - besides, if I have two network devices in same network (e.g. > > redundant default gateway), I can find one device arp looking at its > > twin. > > > > I know it may sound somehow selfish. > > My full answer is: > > - enough for me right now > > - please don't loose time in creating fancy reports unless you find it > > useful for the community > > - I'd share with others a full working query which gives reliable > > results before proceeding into html. > > > > I can give you feedback on any further enhancement you may find useful. > > > > Thank you |