NVDCT - double Interface names for Layer CDP

CMK version: 2.4.0p18
OS version: RHEL 9

We are testing the NVDCT - Network Visualization Creation Tool ( https://thl-cmk.hopto.org/checkmk/vendor-independent/nvdct ) in Version 1.2.1-20260107.

It works great, we can create the topology.

We have only one small issue where we are not sure if this is a configuration problem on our side.

The Interfaces which are not monitored in checkmk are appearing two times in the Network Topology - e.g. Gi1/0/22 in Layer CDP:

In Layer LLDP everything is working as expected:

The Inventory data for CDP looks fine:

Has someone an idea why this is happening?
Can we configure this behaviour?

Best Regards

Thomas

1 Like

Hi @T.Schmitz
can you show the CDP inventory from the second device also? Most of the time this can happen if NVDCT can not map the neighbor ports to a service of a host in Checkmk.

Cheers
Thomas

Hi @thl-cmk ,

thanks for your response.
Here is the Inventory of the second device:

Gi0/0 is in the Inventory list, but it is not monitored as service on the host.
Due to the high number of interfaces we don’t monitor each Interface in checkmk. They are filtered out with the rule “Network interface and switch port discovery”.

Does it mean that we need to monitor the Interface on the corresponding host to get rid of the situation?

Best Regards

Thomas

the issue is, thos ports have different names on both sides

GigabitEthernet1/0/22 ↔ Gi0/0
GigabitEthernet0/0 ↔ Gi1/022

as those can not matched to a service in Checkmk, for NVDCT this are 2 different connections.

There are two options to deal with such things

  • monitor this interfaces so NVDCT has a way to match them to a service
  • exclude the interfaces from the topology via the FILTER_BY_SERVICE_LABEL option

Cheers
Thomas

4 Likes