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. Network devices

Preparing network devices

This page describes what your network devices must support for COD and how to check it.

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

Overview

COD reads and controls network devices through standard protocols. COD installs no agents on the devices.

ProtocolPurposeDirectionRequired
LLDPDevice neighbours, edges of the layer 2 mapbetween the devices. COD reads the neighbours over SSH or a vendor APIrequired for the topology
SNMP v1 or v2cPort discovery, port status, uptimeCOD to the devicerequired for the Network module
SSHNeighbours, clients, VLANs, routes, terminal, backup, configurationCOD, Backup service or Ansible service to the devicerequired
Vendor APIDiscovery through the vendor's interfaceCOD to the deviceoptional
RADIUSNetwork access with NACDevice to the NAC servicewith NAC
TACACS+Administrator login on the deviceDevice to the TACACS+ servicewith TACACS+

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

COD discovers devices from nine vendors: Allied Telesis, Arista, Aruba, Cisco, Extreme, Juniper, MikroTik, Ruijie and Sophos. Allied Telesis, Cisco and Ruijie can also be configured.

LLDP

RequirementWhyCheck
Send and receive LLDP on all ports of switches and routersEdges of the layer 2 map come from LLDP onlyThe device's neighbour view shows the neighbours
TLV system-nameCOD matches a neighbour to an asset by its system name only. Without a system name the device is nameless to its neighboursThe neighbouring device's neighbour view shows the system name
TLVs system-description, system-capabilities, management-address, port-descriptionComplete information on neighbour and portThe neighbour view shows description, capabilities, address and port
System name equal to the asset name in COD, character for characterotherwise no edgeCompare the system name in the neighbour view with the asset name

Devices without LLDP, such as cameras, storage systems or building technology, do not appear in the topology automatically. You can draw these devices in by hand. You monitor their availability through the Zabbix connection.

More on naming: One name for everything

SNMP

COD queries SNMP in versions 1 and 2c with a community.

RequirementWhyCheck
SNMP v1 or v2c with a communityPort discovery, port status and uptimeSNMP query from the COD server
Read-only communityCOD only reads over SNMPCommunity on the device without write access
Access list for the COD source address, plus the Zabbix proxy if Zabbix polls the device over SNMPThe community is transmitted without encryptionA query from another address is rejected
SNMP only in the management network or through VPNLimits who can read the communityNetwork plan and access lists
The port MIB (IF-MIB) respondsWithout it, port discovery failsAn SNMP query of the IF-MIB from the COD server returns the ports

Polling: COD polls port status every 30 seconds. The full query runs on a schedule that can be set per device. Port history goes back 90 days.

LimitWhat you can do
COD queries SNMP in versions 1 and 2cUse a read-only community, restrict it to the COD source address, allow SNMP only in the management network or through VPN
If SNMP port discovery fails, the whole query counts as failed, even if SSH workedCheck SNMP and the access list first
Small switches without a port MIB stay in the status "port discovery failed"Keep these devices as assets and draw them in the topology by hand

SSH

RequirementWhyCheck
SSH server enabled on the deviceNeighbours, clients, VLANs, routes, terminal, backup and configuration run over SSHLog in from the COD server
A dedicated user for COD, not a personal accountTraceability in the device logLogins in the device log
Read rights for discovery and backup, configuration rights only for automationRights as small as possible. You receive the minimum rights as part of the project.Run the discovery commands as this user
SSH only from the management network and from the source address of COD and the module serversLimits the attack surfaceA login from another address is rejected
Paging can be switched offCOD reads command output in one pieceLong output without interruption
Login with user name and passwordThe network object stores user name and password. Whether SSH keys can be used instead of passwords is clarified in the project.
Enable password only if the enable secret differs from the login password, for example on CiscoAccess to privileged mode

Older devices: on the network object you can set the SSH host key, key exchange and cipher. An administrator makes this setting in COD.

Session limit: many devices allow only a limited number of simultaneous SSH sessions. By default the COD collector opens at most 5 sessions at a time. If many backups run against the same target, stagger the start times.

LimitWhat you can do
Configuration backup requires SSH or SFTP on the deviceClarify devices without SSH with your partner in advance

Vendor API

For some vendors, COD can use the vendor's interface instead of the CLI. On the network object, enter the API port, API user and API password, and switch on "API". One example is Aruba CX with its REST interface over HTTPS.

RADIUS with NAC

RequirementWhyCheck
The device supports 802.1X or MAC authenticationBasis of NACData sheet or device configuration
RADIUS source address equal to the device's management addressOtherwise no NAC sessions appear on the portNAC sessions appear on the switch port in COD
Shared secret identical in COD and on the deviceOtherwise the RADIUS server rejects the requestTest login on a port
Send accountingConnection statisticsAccounting entries in NAC

More: NAC module in the documentation

MikroTik

Routers running RouterOS are kept in the MikroTik module. It provides the routes for the layer 3 map, live views and the terminal.

RequirementWhyCheck
Router’s REST interface reachable for CODFor the MikroTik sync, the router’s REST interface must be reachable for COD. You receive the details as part of the project.A query from COD returns routes and interfaces
Access to the REST interface restricted to the COD source addressOnly COD should reach itAccess from another address is rejected
A dedicated user with small rightsTraceability and a small attack surface. You receive the minimum rights as part of the project.Logins in the router log
SSH enabledTerminal and backupLog in from the COD server
Field noteWhat you can do
RouterOS allows only a limited number of simultaneous SSH sessions, 20 in practiceStagger backup start times
Backup by export usually needs full rights on the router in practiceCreate a dedicated user just for backup
Routers in the MikroTik module do not appear in the Network inventory by themselves, and so not as nodes of the layer 2 mapClarify in the project how to keep MikroTik routers for the layer 2 map
RouterOS has no TACACS+ client of its ownDo not connect MikroTik routers through TACACS+

Firewalls

COD manages firewalls from AIMdefense, OPNsense, pfSense and DynFi. The self-registration plugin and Captive Portal are available for OPNsense only.

RequirementWhyCheck
Asset with the built-in asset type "Firewall". Do not rename the typeCOD recognises firewalls by this typeType on the asset
Asset enabled, vendor setSelects the right connectionDetails on the asset
API user with API key and API secret. Administrator by default. Without administrator rights, the layer 3 map needs at least the rights "Interfaces: Virtual IPs: Status" and "System: High Availability" for clustersFirmware, state, VPN, aliases, zones. You receive the minimum rights as part of the project.A query from COD returns the state
SSH user on the firewallReading rules and terminalLog in from the COD server
Your own CA stored in COD if the firewall uses a certificate from your CAVerification of the peerQuery without certificate errors
Reachability through ICMP and a connection attempt to the APICOD checks reachability regularlyStatus in COD
With the plugin only: the firewall reaches COD's addressThe firewall registers itself with COD onceThe firewall appears in COD for approval

More: Firewall module in the documentation

Access points

RequirementWhyCheck
Access point name in the controller equal to the asset nameThen COD draws the edge between access point and switchEdge in the layer 2 map
LLDP on the access point and on the switch portThe switch learns the access point as a neighbourThe switch's neighbour view

Vendor notes

The general requirements on this page apply to all nine vendors. You receive the minimum rights as part of the project.

VendorField note
Allied TelesisThe optional LLDP TLVs are selected per port (lldp tlv-select). Configuration through automation is possible
ArubaAruba CX can optionally be discovered through its REST interface over HTTPS
CiscoEnter an enable password only if the enable secret differs from the login password. Configuration through automation is possible
MikroTikSee the section MikroTik
RuijieConfiguration through automation is possible
Arista, Extreme, Juniper, SophosNo verified notes beyond the general requirements

On the asset in COD

RequirementWhy
Network flag set on the assetOnly then does the device belong to the Network module
Vendor and model family maintained correctlyThey decide which collector runs. An unknown vendor leads to an error
"Routing" enabled on the network object if the device routesNeeded for layer 3 and for addresses and VLANs

Further reading

  • Network and MikroTik module in the documentation
  • Names and addresses
  • Troubleshooting
  • FAQ: requirements
← Previous: Names and addressesNext: Time and DNS →
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