Here is a successful discovery that discovered 3 devices with two activities showing “Identified, ignored extra IP” messages. That’s because a CMDB CI record was created for “al1winmid” on the first IP address it identified it with: 10.0.103.30. Discovery was able to identify that same device on two additional IP addresses: 10.0.103.34 and 10.0.103.35. However, since we don’t want Discovery to explore the same device 3 times, Discovery just ignores the additional IP addresses as stated in that message and lets you know that it had identified those two other IP addresses.
The IP Address Discovery uses is determined by chance. It uses the first IP address it finds that it is able to use to process identification.
So, a completed activity value of “Identified, ignored extra IP” is not an error. It is a normal discovery behavior.
Finding Multiple matches in the CMDB is not normal and will bring Discovery to a halt. For example, below, you can see there is multiple entries station that matches for “diamond” that was found so it could not determine what record to update.
In the identifier phase, several identification scripts tried to identify the identity of the target machine. Each identifier checks different things. In the case shown below, the Name, Class Name, and Network Identifier found multiple matches which are linked in the Message for easy review such as “diamond” is shown as a link since it is underlined.
So, when Discovery stops in the Identification phase and the Discovery Log displays “Multiple matches were found in the CMDB message, it indicates that there was a duplicate record found for the same configuration item (CI) in the CMDB. Duplicate records can get into the CMDB through manual entry or through a source that imported an incomplete record. To resolve such an issue, clean up the CMDB by merging or deleting duplicate records for the same CI.