Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Discovery does not honor exclude-range inside a definition

Description

Given a discovery-configuration.xml that looks basically like:

<discovery-configuration "xmlns=http://xmlns.opennms.org/xsd/config/discovery" … <definition location="Default"> <detectors> <detector name="reverse-dns-lookup" class-name="org.opennms.netmgt.provision.detector.rdns.ReverseDNSLookupDetector"/> <detector name="SNMP" class-name="org.opennms.netmgt.provision.detector.snmp.SnmpDetector"/> </detectors> … <exclude-range> <begin>10.0.0.1</begin> <end>10.0.0.254</end> </exclude-range> … <include-range> <begin>10.0.0.1</begin> <end>10.255.255.254</end> </include-range> </definition> </discovery-configuration>

The exclude-range should exempt addresses such as 10.0.0.37 from discovery's ping sweeps. The discovery.log on this system, however, indicates that this address is being pinged:

2019-11-06 12:02:13,384 DEBUG [ping-sweep-0] o.o.p.r.RequestTracker: Scheding timeout for request to [ID=JniPingRequestId[addr = /10.0.0.37, ident = 31638, seqNum = 1, tId = 2120497],Retries=1,Timeout=2000,Packet-Size=64,Expiration=1573059735384,Callback=org.opennms.netmgt.icmp.LogPrefixPreservingPingResponseCallback@6bb5097f] in 2000 ms2019-11-06 12:02:14,384 DEBUG [ping-sweep-0] o.o.n.i.j.JniPingRequest: 1573059734384: Sending Ping Request: [ID=JniPingRequestId[addr = /10.0.0.38, ident = 31638, seqNum = 1, tId = 2120566],Retries=1,Timeout=2000,Packet-Size=64,Expiration=-1,Callback=org.opennms.netmgt.icmp.LogPrefixPreservingPingResponseCallback@2cd6be79]

Environment

Host dr-ems-2

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Chandra Gorantla November 7, 2019 at 9:29 PM

Fixed

Details

Assignee

Reporter

Labels

Components

Sprint

Fix versions

Affects versions

Priority

PagerDuty

Created November 6, 2019 at 9:54 PM
Updated November 26, 2019 at 1:36 PM
Resolved November 26, 2019 at 1:36 PM
Configure

Flag notifications