Names and addresses
This page describes how to name and address devices so that COD can link topology, monitoring and backup.
As of: November 2026, COD 3.8.6
Documentation
One name for everything
COD links topology, monitoring and backup through identical names. A device therefore carries the same name everywhere.
| Where | Name | What depends on it |
|---|---|---|
| COD | Asset name | Reference point for all other names |
| Device | Host name | Backup with "Check Server Name" compares the host name with the Server Name in Backup |
| LLDP | System name (system-name) | COD matches an LLDP neighbour to an asset by its system name only. The edges of the layer 2 map come from this |
| Zabbix | Host name | Matching between Zabbix host and asset compares whole names |
| WLAN controller | Access point name | COD draws the edge between access point and switch only if the names match |
The comparison is exact. If a name differs by one character, no connection appears. Write the names identically everywhere, including upper and lower case.
Note: COD synchronises with Zabbix every night. If you rename a host in Zabbix, the link to the asset is dropped at the next synchronisation. Change names in all systems at the same time.
Naming scheme
Recommendation: a scheme of customer, location, device type and sequence number.
| Part | Example | Note |
|---|---|---|
| Customer | EXA | Short code, unique in the installation |
| Location | BER | Short code per location |
| Device type | sw, rt, fw, ap | short, fixed list |
| Sequence number | 01 | with leading zero |
| Result | EXA-BER-sw01 |
COD rules:
| Rule | Why |
|---|---|
| At most 50 characters | Limit for asset names |
| Unique across the installation | Asset names apply to the whole installation, not per location or tenant. Two locations cannot both have a sw01. The customer and location codes prevent duplicates |
Fixed management addresses
| Requirement | Why | Check |
|---|---|---|
| Management address static or by DHCP reservation | Network object, backup host and Zabbix interface depend on the address | Reservation in the DHCP server or fixed address on the device |
| Update address changes in COD | COD does not take over changed addresses and credentials automatically. The Backup entry is a copy and does not change with the asset | Compare the address on the network object, the backup host and in Zabbix |
| A dedicated management network for device administration (recommended) | Limits the attack surface of device access. COD connects only there | The devices' access lists show only the management network |
Fixed COD source address
All queries come from the COD server, backups from the Backup service, configurations from the Ansible service. The devices see these hosts as the sender.
| Requirement | Why | Check |
|---|---|---|
| The COD server and module servers reach the devices with a fixed source address | Access lists for SNMP, SSH and APIs need a fixed address | A capture or log on the target device shows the sender address |
| For remote locations, a path through VPN, and NAT to a fixed address at a VPN hub | Otherwise the sender changes and the access lists do not match | Query from COD and capture on the device at the remote location |
| Allow this source address in all device access settings | No query without a rule | Access lists for SNMP, SSH and API on the device |
| Hosted models: source address of Shared Hosted and Private Hosted | Firewall rules at the customer | You receive the source address as part of the project. |
Customers and partners receive the list of connections and firewall rules as part of the project.
Field note: If a query does not arrive, first use a capture on the target device to check whether packets arrive at all and with which sender address.
Two access paths at remote locations
| Requirement | Why |
|---|---|
| Two independent access paths at every remote location | A change to firewall, VPN or SSH services must not cost you access |
| Make changes that affect access only with a second path in reserve | No lock-out from afar |
Further reading
- Preparing network devices
- Time and DNS
- "Ready for COD" checklist
- Monitoring module in the documentation
- FAQ: requirements