From: Sam S. <sam...@sp...> - 2007-06-26 06:54:48
|
Oliver Gorwits wrote: > Sam Stickland wrote: > >> OK, the problem is related to SNMP::Info::root_ip. The device in >> question is running EIGRP so there is no router-id to speak of, but >> it has a loopback address. root_ip doesn't seem to be returning the >> Loopback address. It's probably returning undef causing the code to >> stick to the original IP address. >> > > I've also had trouble with root_ip in the past, returning what I > consider to be the "wrong" address. It's a matter of opinion :-) > > Here's what I said before, in case it helps: > > Hi Oliver, I wouldn't mind so much if it was consistently returning the "wrong" address, but because it can't detect an address to use it isn't consistently returning one address for one device - it depends on what the IP address used for discovery is. I don't think it's going to particularly difficult to emulate the mechanism that's used for OSPF router-id selection though. Hopefully I'll have a patch to submit by the end of today (GMT). S >> I wrote a small patch to provide just a hacky solution, which is to >> give netdisco a list of "override" IPs for certain devices which it >> uses instead of querying the OSPF Router ID. Because our routers and >> Router IDs don't change very often, this has a low overhead, and is >> manageable. >> >> http://users.ox.ac.uk/~oliver/data/files/netdisco/device_root_override.diff >> >> >> To use the patch, just populate the root_override DB table with the >> "wrong" root IPs in the 'ip' column and the desired IPs in the >> 'root_ip' column. The patch should apply cleanly to NetDisco 0.95. >> > > regards, > oliver. > |