This is essential step after installing and configuring platform.
Before do any deeper analysis, we need to be sure about asset naming and their inconsistencies.
In real life, this could be a nightmare. For example, for incident reporting. All objects within network and related tools should be in sync for correct and quick responses.
In short, inconsistent asset is object within your network, which is not fully in sync by all possible collections. It can be even duplicated or missing object.
This is probably one of the most common issue. You deploy host and forget to add DNS record for DNS domain. Other scenario is that DNS forward record is known, but reverse record is missing.
There is some server deployed but there is no information within CMDB.
Due to some human error or configuration issue, same asset has different names within different sources. Like local hostname on notebook is "My-notebok" but CMDB name is "Mynotebook".
There are more active assets within CMDB with same IP address. Or there is other IP collected by Ansible and saved within CMDB.
There are many modules and jobs which can help to identify and report inconsistencies within network.
You can use other modules or just part of them. See installation and configuration guide first.
Let us nmap network and import to FCP. Use your local ranges.
nmap 192.168.1.0/24 fcpc nmap import localscan.xml
Let us use DNS module to resolve IPs to names
fcpc dns ips-to-names
And resolve it back to IPs
fcpc dns fqdns-to-ips
Let us index all assets within CMDB
fcpc itop download-and-import-all
Let us run all required jobs to process data.
fcpc job execute assettagger,assetlinker,personlinker
First, let us find all hosts which have inconsistent name
fcpc search ci+ tag=sys:inconcistent:hostname
fcpc search nmaphost ~not-is itophost