Network Management
Network Topology not creating connections on Intelligent Maps [SolarWinds Platform Maps]
This article addresses issues where Network Topology connections fail to appear on Intelligent Maps within the SolarWinds Platform Maps.
First published date
Last published date
Overview
Users may experience missing or incomplete topology connections between devices on Intelligent Maps in the SolarWinds Platform. This typically occurs when the platform cannot correctly associate interface information between nodes, resulting in absent connections on the Network Topology widget.
Product section
Cause
The SolarWinds Platform relies on matching the RemotePortId from the NodeLldpEntries table with the corresponding InterfaceName in the Interfaces table. If these interface names do not match exactly, the platform cannot establish topology connections between devices, leading to missing links on the map.
Resolution
Consider two nodes connected as follows:
- Leafl201-XXXX on interface Ethernet1/49
- Spine1101-XXXX on interface Ethernet1/1
The platform uses SNMP OID 1.3.6.1.2.1.31.1.1.1.1 to retrieve interface names and stores them in the Interfaces table. LLDP Remote Port IDs are stored in the NodeLldpEntries table.
- From Leafl201-XXXX, SNMP returns interface name: Ethernet1/49
- LLDP RemotePortId from Leafl201-XXXX points to Eth1/1 (note the abbreviated interface name)
- From Spine1101-XXXX, SNMP returns interface name: Ethernet1/1
- LLDP RemotePortId from Spine1101-XXXX points to Eth1/49
Because the interface names differ in format (Ethernet1/xx vs. Eth1/xx), the platform cannot match these entries, resulting in missing topology connections.
Resolution
Approach #1: Correct Interface Naming on Devices
Edit the interface names directly on the network devices to ensure that the names returned during LLDP polling match exactly with those obtained via SNMP polling. This alignment allows the SolarWinds Platform to correctly associate interfaces and create topology connections.
For more information on the OIDs used for polling interface information, refer to:
Approach #2: Enable Complementary Link Selector
If interface names cannot be aligned or the environment includes devices from multiple vendors using different topology protocols, you can enable a platform setting to merge incomplete connections:
- Navigate to the Advanced Configuration page: /Orion/admin/advancedconfiguration/global.aspx
- Locate and edit the CalculationConfiguration setting.
- Find the ComplementaryLinksSelectorL2 property and set its value to true.
- Click OK and then SAVE.
- Recalculate the topology and allow time for the update to complete.
Note: Enabling this setting may create connections with invalid interfaces if multiple links exist between nodes.