Ir al contenido
  •  +49 (861) 88 00 32 00
COD powered by extocode GmbH
  • 0
  • Iniciar sesión
  • English (US) Français Deutsch Español Türkçe
  • Abrir la demo
  • Inicio
  • Resumen COD
    Plataforma
    ResumenPlataforma: clientes y marcaFuncionesProblemas y solucionesArquitecturaDocumentationIntegracionesPrecios
    Operación y Red
    MonitoringRedNetwork Access Control (NAC)TACACS+Captive PortalFirewall
    Seguridad y Resiliencia
    Governance, Risk & ComplianceBackupHypervisorOTPPasskeeprAutomatización
    Soluciones y Más
    NIS2 & CompliancecodPassDocumentación con IA (módulo InfraScan)Abrir la demoReferenciasDescargasFAQ
  • Precios
  • Novedades
    • Blog
    • Hoja de ruta
  • FAQ
  • Sobre nosotros
    • Sobre nosotros
    • Empleo
    • Socios
    • Referencias
  • Academy
  • Contacto
COD powered by extocode GmbH
  • 0
    • Inicio
    • Resumen COD
    • Precios
    • Novedades
      • Blog
      • Hoja de ruta
    • FAQ
    • Sobre nosotros
      • Sobre nosotros
      • Empleo
      • Socios
      • Referencias
    • Academy
    • Contacto
  •  +49 (861) 88 00 32 00
  • English (US) Français Deutsch Español Türkçe
  • Iniciar sesión
  • Abrir la demo
  1. Home
  2. Documentation
  3. Requirements
  4. Names and addresses

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 contents
  • Overview
  • Getting started
  • Requirements
  • Names and addresses
  • Network devices
  • Time and DNS
  • Installation
  • Deployment shapes
  • Initial setup
  • Updates
  • Modules
  • 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
  • Troubleshooting
  • Security
  • Versions
  • Version history
  • Support

One name for everything

COD links topology, monitoring and backup through identical names. A device therefore carries the same name everywhere.

WhereNameWhat depends on it
CODAsset nameReference point for all other names
DeviceHost nameBackup with "Check Server Name" compares the host name with the Server Name in Backup
LLDPSystem 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
ZabbixHost nameMatching between Zabbix host and asset compares whole names
WLAN controllerAccess point nameCOD 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.

PartExampleNote
CustomerEXAShort code, unique in the installation
LocationBERShort code per location
Device typesw, rt, fw, apshort, fixed list
Sequence number01with leading zero
ResultEXA-BER-sw01

COD rules:

RuleWhy
At most 50 charactersLimit for asset names
Unique across the installationAsset 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

RequirementWhyCheck
Management address static or by DHCP reservationNetwork object, backup host and Zabbix interface depend on the addressReservation in the DHCP server or fixed address on the device
Update address changes in CODCOD does not take over changed addresses and credentials automatically. The Backup entry is a copy and does not change with the assetCompare 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 thereThe 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.

RequirementWhyCheck
The COD server and module servers reach the devices with a fixed source addressAccess lists for SNMP, SSH and APIs need a fixed addressA 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 hubOtherwise the sender changes and the access lists do not matchQuery from COD and capture on the device at the remote location
Allow this source address in all device access settingsNo query without a ruleAccess lists for SNMP, SSH and API on the device
Hosted models: source address of Shared Hosted and Private HostedFirewall rules at the customerYou 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

RequirementWhy
Two independent access paths at every remote locationA change to firewall, VPN or SSH services must not cost you access
Make changes that affect access only with a second path in reserveNo lock-out from afar

Further reading

  • Preparing network devices
  • Time and DNS
  • "Ready for COD" checklist
  • Monitoring module in the documentation
  • FAQ: requirements
← Previous: RequirementsNext: Network devices →
Folgen Sie uns
​
  • Resumen COD
  • Funciones
  • Demo
  • Precios
  • Integraciones
  • NIS2
  • codPass
  • Referencias

Help

  • FAQ
  • Documentation
  • Descargas
  • Contacto

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

Utilizamos cookies para proporcionarle una mejor experiencia de usuario en este sitio web. Política de privacidad

Rechazar Aceptar