teemIP / IPAM
IP blocks, subnets, addresses and network equipment.
A CMDB is only useful if its data stays current. iTop provides a REST API and collectors to feed the repository from existing sources.
A good integration keeps the CMDB alive by connecting it to trusted sources.
Both modes can be used separately or combined.
The REST API lets external systems read, create, update or delete iTop objects through standard HTTP calls.
Collectors automate recurring synchronization with mapping, reconciliation and logs.
CI creation, updates, BI exports and monitoring-triggered tickets.
Scheduled sync with AD, inventory, virtualization, IPAM or cloud.
Rules compare source data and iTop without uncontrolled overwrites.
Reports show created, updated, ignored or obsolete objects.
IP blocks, subnets, addresses and network equipment.
Users, groups, computers and contacts.
VMs, clusters, cloud resources and accounts.
Ticket creation from Nagios, Zabbix, PRTG or similar tools.
OCS Inventory, GLPI, Lansweeper or existing exports.
Enrichment with vulnerabilities and risk levels.
The collector queries the source and retrieves raw data.
Values are normalized according to the target mapping.
iTop compares incoming data with existing records.
Creation, update or obsolescence according to rules.
A report highlights errors and changes.
We analyze your sources and build the collection architecture adapted to your IT estate.