Skip to Content
  •  +49 (861) 88 00 32 00
COD powered by extocode GmbH
  • 0
  • Sign in
  • English (US) Français Deutsch Español Türkçe
  • Open the demo
  • Home
  • COD Overview
    Platform
    OverviewPlatform: tenants and brandFeaturesProblems & SolutionsArchitectureDocumentationIntegrationsPricing
    Operations & Network
    MonitoringNetworkNetwork Access Control (NAC)TACACS+Captive PortalFirewall
    Security & Resilience
    Governance, Risk & ComplianceBackupHypervisorOTPPasskeeprAutomation
    Solutions & More
    NIS2 & CompliancecodPassAI documentation (InfraScan add-on)Open the demoReferencesDownloadsFAQ
  • Pricing
  • News
    • Blog
    • Roadmap
  • FAQ
  • About us
    • About us
    • Careers
    • Partners
    • References
  • Academy
  • Contact
COD powered by extocode GmbH
  • 0
    • Home
    • COD Overview
    • Pricing
    • News
      • Blog
      • Roadmap
    • FAQ
    • About us
      • About us
      • Careers
      • Partners
      • References
    • Academy
    • Contact
  •  +49 (861) 88 00 32 00
  • English (US) Français Deutsch Español Türkçe
  • Sign in
  • Open the demo
  1. Home
  2. Documentation
  3. Modules
  4. Inventory and CMDB import

Inventory and CMDB import

This page describes how the asset inventory is built, how assets get into COD and which rules apply to names and catalogues.

As of: November 2026, COD 3.8.6

Documentation contents
  • Overview
  • Getting started
  • Requirements
  • Names and addresses
  • Network devices
  • Time and DNS
  • Installation
  • Deployment shapes
  • Initial setup
  • Updates
  • Modules
  • Network and MikroTik
  • Automation
  • NAC
  • TACACS+
  • Firewall
  • Captive Portal
  • Monitoring
  • Backup
  • Hypervisor
  • OTP
  • Passkeepr
  • GRC
  • Inventory and CMDB import
  • Troubleshooting
  • Security
  • Versions
  • Version history
  • Support

Documentation

  • Overview
  • Getting started
  • Requirements
  • Names and addresses
  • Network devices
  • Time and DNS
  • Installation
  • Deployment shapes
  • Initial setup
  • Updates
  • Modules
  • Network and MikroTik
  • Automation
  • NAC
  • TACACS+
  • Firewall
  • Captive Portal
  • Monitoring
  • Backup
  • Hypervisor
  • OTP
  • Passkeepr
  • GRC
  • Inventory and CMDB import
  • Troubleshooting
  • Security
  • Versions
  • Version history
  • Support

Tenants, locations and permissions are described on the Platform page. What COD exchanges with i-doit and Odoo is listed under Integrations.

Overview

PropertyValue
PurposeThe inventory is the backbone of COD. Network, Firewall, Monitoring, GRC and further modules work with the same assets
CataloguesType, vendor, family, model, status, condition. They apply installation-wide
Asset namesUnique across the installation, at most 50 characters
Flags on the assetNetwork, Backup, NAC, Firewall
LocationEach asset belongs to a location. The location is the smallest boundary for permissions and data
ImportCSV import and i-doit import
i-doitJSON-RPC over HTTPS, API key mandatory, read only
Connection and directionCOD opens the connection to i-doit and optionally to Odoo
Ticket systemOptionally Odoo, via JSON-RPC over HTTPS

Requirements

RequirementWhy
A naming schemeAsset name, hostname, LLDP system name and Zabbix hostname should be identical. COD links through exact names. See Names and addresses
Complete catalogues, correct vendor and familyVendor and family decide which collector queries a device
Built-in asset type “Firewall” unchangedThe Firewall module recognises firewalls by this type. Do not rename it
A role with the permission for the Asset module, for imports with the “CSV import” permissionNo creating and no import without it
For i-doit: API switched on in i-doit, API key, reachable over HTTPS from the COD serverCOD reads through the i-doit API
For Odoo: a reachable Odoo with a ticket systemTickets per location

Customers and partners receive the list of connections and firewall rules as part of the project.

Setup

  1. Create the catalogues: type, vendor, family, model, status, condition. They apply to all tenants of the installation.
  2. Decide on the naming scheme. A scheme of customer, location, device type and running number has proven itself.
  3. Choose the location in the top bar.
  4. Create assets: by hand, by CSV import or by i-doit import.
  5. Set the flags on the asset. The Network flag is mandatory for collection in the Network module.
  6. For i-doit: enter address and API key in the CMDB configuration of the location, plus user and password if needed. Choose the objects and start the import.
  7. Maintain rooms, racks and layer 1 cables. You need GRC permissions for this.
  8. Optional: set up the ticket integration with Odoo per location.

Technical details

Catalogues

CatalogueAppliesNote
Typeinstallation-wideContains the built-in type “Firewall”
Vendorinstallation-wideMust match the device. An unknown vendor leads to an error during collection
Familyinstallation-wideSelects the collector together with the vendor
Modelinstallation-wide
Status, conditioninstallation-wide

Asset names

  • At most 50 characters.
  • Unique across the installation, so also across tenants and locations.
  • Layer 2 edges, Zabbix matching and the name check in Backup compare whole names. A single differing character is enough for no link to be made.

Flags on the asset

FlagMeaning
NetworkMandatory for collection in the Network module
BackupMarks the asset for the Backup module
NACMarks the asset for the NAC module
FirewallMarks the asset for the Firewall module. The module also needs the built-in type “Firewall” and a vendor set

Vendor, family and collector

COD's collector queries network devices via SNMP, SSH or vendor API. Vendor and family on the asset decide which collector runs. An unknown vendor results in an error. Which vendors COD collects from is listed under Network and MikroTik.

CSV import

CSV import exists for Asset, Network, Backup and NAC. It is a separate permission in the role.

i-doit import

PropertyValue
Interfacei-doit JSON-RPC over HTTPS
AccessAPI key mandatory, user and password optional
ConfigurationPer location
DirectionCOD reads from i-doit. COD writes nothing back

i-doit remains your CMDB. COD only reads and writes nothing back.

Asset page

Each asset has its own page with monitoring, placement, interfaces, contacts, contracts and dependencies. With GRC permission it also shows the risk and the process that depends on the asset through its asset group.

Rooms, racks and layer 1

You maintain rooms and racks by drag and drop. Layer 1 cables document the cabling. All three need GRC permissions.

Moving

Assets can be moved between locations. Only a SuperAdmin may move an asset across a tenant boundary. An assigned OTP token moves along.

Copies in the modules

Some modules keep records of their own that are filled from the asset when created and are separate afterwards.

ModuleBehaviour
BackupThe host entry is a copy. Address and password do not change there by themselves
NACThe list of NAS devices is not linked to the asset
HypervisorNo link to the asset

Odoo ticket system

COD searches tickets per location in Odoo and links them with a GRC case and an acknowledgement. You create tickets directly from COD, with prefilled fields. Other ticket systems are not connected.

Known limits

LimitWhat you can do
Asset names unique across the installation, at most 50 charactersInclude customer and location in the naming scheme
Catalogues apply installation-wideAgree catalogues between the tenants of an installation
A wrong or unknown vendor causes collection errorsCheck vendor and family before the first collection
No permissions per deviceSeparate devices by location
i-doit import is read only, nothing is written backKeep maintaining the CMDB in i-doit
Modules such as Backup and NAC keep their own copiesChange address and credentials there as well
Rooms, racks and layer 1 only with GRC permissionGive the GRC permission to the roles that maintain the inventory
Odoo is the only ticket systemOther ticket systems stay outside COD
Changes to addresses and credentials on the device do not reach COD by themselvesAssign fixed management addresses and apply changes in COD

Further reading

  • Platform: tenants, locations, permissions
  • Integrations
  • Names and addresses
  • Network and MikroTik
  • GRC in the documentation
  • What your network needs for inventory and integrations
  • Troubleshooting
  • Questions about the modules
← Previous: GRCNext: Troubleshooting →
Folgen Sie uns
​
  • COD Overview
  • Features
  • Demo
  • Pricing
  • Integrations
  • NIS2
  • codPass
  • References

Help

  • FAQ
  • Documentation
  • Downloads
  • Contact

Kotzinger Straße 21 • 83278 Traunstein • Deutschland

  • ​+49 (861) 88 00 32 00
  • ​info@extocode.com
Datenschutz Impressum ​
Copyright © extocode GmbH
English (US) Français Deutsch Español Türkçe

We use cookies to provide you a better user experience on this website. Privacy Policy

Decline Accept