Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > IP Address Manager (IPAM) > IP Address conflicts in IPAM 4.3

IP Address conflicts in IPAM 4.3

Table of contents
No headers
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 183 Votes: 1 Revisions: 8

This knowledge base discusses how IPAM addresses IP Address conflicts. For more information, see IP Address Conflicts.

Conflict Scenarios:

SNMP versus SNMP Neighbor: This type of conflict occurs when there is a difference in MAC addresses retrieved from the ARP table of the configured device and SNMP OIDs during the subnet scan for a particular IP Address.

SNMP versus DHCP: This type of conflict occurs when there is a difference in MAC fetched from SNMP OID and DHCP leases from DHCP Server, for a particular IP Address during a subnet scan.

SNMP Neighbor versus DHCP: This type of conflict occurs when there is a difference in MAC addresses retrieved from ARP table of the configured device and DHCP leases from DHCP Server, for a particular IP Address during subnet scan.

DHCP versus DHCP: A range of IP Addresses within a subnet may be managed by two DHCP servers. This type of conflict occurs when there is a difference in MAC addresses retrieved from two DHCP server lease information for a particular IP Address during subnet scans. This conflict is visible on the IPAM summary page as a conflict if there is a DHCP lease >IP Address conflict.

DHCP versus DHCP (Scope Overlap): A range of IP Addresses under a subnet may be managed by two DHCP servers. There are cases wherein a part of an IP Address range under one DHCP server would be managed by another DHCP server. In both instances, there is an overlap in scopes between two DHCP servers. This is not displayed as a conflict on the IPAM summary page, but you may see the related event in the IPAM Event/Alert section.

IPAM reservation versus SNMP/DHCP/SNMP neighbor: There are situations where you reserve an IP Address under a subnet in IPAM that contains a MAC address for an internal reference. This type of conflict occurs when there is a difference in MAC addressees from either SNMP OIDs, or DHCP leases, or neighbor devices with reserved MAC addresses in IPAM for a particular IP Address during a subnet scan.

Notes:

  • During subnet scans, MAC addresses obtained from SNMP, SNMP neighbor, and IPAM reservations are termed as Static entries and those obtained from DHCP servers are termed as Dynamic entries.
  • The scan interval field under "Automatic Scanning" and "Neighbor Scanning" settings in the Add/Edit subnet view must have the same time period, for conflicts to be detected.
  • In all the above cases a generic event along with an alert warning gets displayed under events. The generic message would read as “The conflict for IP Address: 10.199.193.66 is detected with MACs: 5C-26-0A-5C-AB-DC, 00-59-07-21-89-1C
  • A warning format would normally read as follows: The IP address 10.199.193.64 is in conflict. The following devices were detected on network with same IP address: - PingSweep* vs Neighbor data MAC: 00-DB-DF-15-B0-03, MAC: 20-CF-30-3A-89-AB
Last modified

Tags

Classifications

Public