|
From: <j.v...@ut...> - 2010-08-16 14:05:47
|
Hi Nenad, > As I have already mentioned in my earlier messages, the only > problematic thing with Netdisco for me is aliasing which doesnt > discover neighbours if they have same IP address and I have several > devices in different routing domains which have same private address > on them. OK, so each device has a unique "root ip" and refresh + arpnip work correct? Is it just that a specific set of IP addresses / subnets has to be kept out of the device_ip (aliases) table? > So I have decided to make some dirty postgres hacking; > > #!/bin/bash > for i in `cat /home/netdisco/alias_ip.txt` > do > /usr/bin/psql -q -U netdisco -d netdisco -c "delete FROM device_ip > WHERE alias = inet '$i';" > done > > Alias_ip.txt is a list of duplicate aliases. > > Well, I'm not expirienced database admin, so question is; is it > possible to break database if I put that script in crontab? > It must be executed every few minutes, especially during > rediscovering hole network so can I expect any problems? I don't think this will break anything. > Or maybe someone has better idea? Well, if this works for you, we could perhaps add a config option to ignore certain networks when storing device IPs. However I'm not sure whether your approach will work... let's wait for the results first. In the long run, we'll have to find a way to support duplicate IP addresses on devices for stuff like VRFs and anycast addresses. I'm not sure how we can implement that in a reliable way though. Regards, Jeroen van Ingen ICT Service Centre University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands |