Observability

Incorrect links in the Topology table because of duplicate CDP data

This article includes instructions on how to correct situations where incorrect topology links are created because of duplicates in CDP data.

First published date

7/25/2023 8:35 AM

Last published date

7/25/2023 8:35 AM

Overview

This article addresses situations where incorrect topology links are created because of duplicates in CDP data.

Product section

Hybrid Cloud Observability

Cause

If there are different device IDs for the same IP address in CDP data, nodes are 'merged' together during topology calculation, and incorrect links are created.

For example, the following SWIS query returns the following results:

Query

SELECT NodeID, IfIndex, CacheAddressType, IpAddress, DeviceId, DevicePort
FROM Orion.NodeCdpEntry

Results

NodeIDIfIndexCacheAddressTypeIpAddressDeviceIdDevicePort

1

438394770

1

192.168.0.1

device.id.one

Ethernet5/1

2

438394771

1

192.168.0.1

device.id.two

Ethernet3/2

Resolution

Option 1: Reconfigure devices so that there are no duplicates reported by CDP

Reconfiguring devices so that there are no duplicates is the best solution.

Option 2: Configure SolarWinds Platform Web Console to skip duplicates

Warning: Enabling SkipCdpIdDuplicates can remove existing connections calculated based on duplicate values.

  1. Log in to the SolarWinds Platform Web Console.

  2. Navigate to Advanced Configuration:
    http(s)://{OrionServer}/Orion/Admin/AdvancedConfiguration/global.aspx

  3. Search for the CalculationConfiguration setting.

  4. Click the pencil icon to edit the value and locate the following setting.

    <ProviderConfig Key="SkipCdpIdDuplicates" Value="false"/>

    image.png

  5. Change this value to true.

    <ProviderConfig Key="SkipCdpIdDuplicates" Value="true"/>

    Note: If SkipCdpIdDuplicates is missing, add the previous string inside the DataProviderConfig tag.

  6. Click OK.

  7. Click Save.