Details
-
Bug
-
Status: Resolved (View Workflow)
-
Critical
-
Resolution: Fixed
-
1.12.0, 1.12.3
-
OpenNMS running on CentOS 6 or Ubuntu 12.04
-
NMS Sprint 1, NMS Sprint 2
Description
I have the discovery range set to scan 172.20.1.1 through 172.20.1.50. We added a server called "bastion" at 172.20.1.40.
From the opennms server:
- host 172.20.1.40
40.1.20.172.in-addr.arpa domain name pointer bastion.internal.opennms.com.
I know that reverse DNS is working. However, the nodelabel still shows up as "172.20.1.40" despite rescans.
Attachments
Issue Links
- blocks
-
NMS-8767 Auto-Discover architecture/behavior has changed and broke its typical usage
-
- Resolved
-