Re: [opennms-discuss] Best practices questions

[Rob M. <rmc...@fi...>]

This may be off topic, but in reading through the "DNS Importing" wiki page and attempting to implement it in my installation I ran into an issue with discovery actually using IXFR instead of AXFR like the wiki page says to test.  Which way is this intended to work?  Should it work as described in the wiki page where it should grab the entire zone every time and update nodes as it sees changes or using incremental (IXFR) queries and changing only what ONMS' current version of the zone file vs. the master DNS zone shows?

The reason I ask is because the name servers I query allow AXFR but not IXFR and the errors I am seeing is:

Discovery.Pinger] Discovery: Error reading URL: dns://mydnsserver/myzone: Problem getting input stream: org.xbill.DNS.ZoneTransferException: server doesn't support IXFR

Any suggestions?


Thank you,

Rob


On 11/3/09 7:56 PM, "David Hustace" <da...@op...> wrote:


On Nov 2, 2009, at 1:57 PM, Alexander Finger wrote:


In the next release of OpenNMS you will have the option to present the nodes as well to people grouped by Surveillance Categories.

Also, you may also provision nodes as groups.  These "groups" will become more and more prevalent as 1.8 matures.


We depend very much on the IP of a Node. If Nodes swap IP it's a tough call. In general, if speaking of servers and routers and so on, you won't change their IPs.
 For PC-Networks you will want to think about what you want to monitor, down to the point of considering to ignore the "popular" used IPs.

If you are directly provisioning nodes, then you can change the IP and maintain the node's integrity.  Also, now in 1.8, there is the notion of DNS as a source for provisioning.  The node-label (i.e. hostname from the A record) is used as the key and the zone or zone filter is the source/group name.  Now, if the host IP address changes, then the next DNS import will change the IP address of the node.  So, if you are running dynamic DNS, changes to the IP address related to the node will be reflected in OpenNMS on the next import.

http://www.opennms.org/wiki/DNS_Importing



David Hustace
The OpenNMS Group, Inc.