Network Management

"0 discovered links mapped" in ConnectNow on Orion Network Atlas NPM

Topology connection between devices is not working as expected when using ConnectNow option in network atlas

First published date

10/23/2018 8:36 PM

Last published date

12/14/2021 10:36 PM

Overview

When selecting ConnectNow, for L2 + L3 connections, the message: 0 discovered links mapped appears. 
 

  

 

 

Product section

Orion Platform

Cause

This is not an error. This is simply a message that indicates we don't have any topology data available for the selected nodes/interfaces which you are trying to connect. You may have the wrong interface added or the device may not expose topology data over SNMP.

Resolution

If NPM is not aware of the connection, then the Connect Now will not create the connection. You can try  three different quick checks below to confirm if the NPM is aware of the connection or not:

 

1. Web Console Check:

  • On Orion web console, go to Settings > Manage Nodes.
  • Search and select the source node, click List resources, e.g:
    • image.png
  • Ensure the topology Layer 2 & Layer 3 and all interfaces are selected and submit:
    • image.png
  • Go to Manage Nodes page > More Action, select the source node and click Poll Now, and then Update Topology to calculates topology according to the data gathered by topology pollers:  
    • image.png
  • Perform the same steps for the destination node.
  • Wait 15 minutes and go to the Network Tab > And check: Does Network Topology resource appear in this nodes page?
  • Do the correct connections appear?

If the topology list is not on the web console, then this indicates that the NPM is not aware that a connection exists and you may need to proceed to next step

 

2. SNMP Walk Check:

Run an SNMP walk from the Orion Server to one of the devices in question.
 

SolarWinds SNMP Walk: A new tool for collecting SNMP MIB walks  and a short video: Collect MIB walk data using the SolarWinds SNMP Walk Tool - video .

 

Now compare and search in the OID's returned from the SNMP walk, is the device returning the correct OID's for the Layer2 or Layer3 communication?
 

Search through the resulting OID's list. for the OID's that Orion is expecting to receive: 
 

Object IDs and information Orion Platform polls
 

If the device isn't returning the expect OID's then this is a device/vendor issue. Then the user should then check on the device why the OID's are not being sent to Orion.

 

3. Database Table Check for Layer 3:

Topology data is stored in the TopologyConnections table in the Orion database.
 

Look for the NodeID of the devices, starting with the 1st device (this can be found on the URL of the node details page in the web console, or in the Nodes table in the database).


Check the database to determine if the IP address of the second device appears in the Nodes table.


Now look for the NodeID of the second device, and determine if the IP address of the first device appears in the table as a connection.


This will confirm if the information has been sent from the device to Orion, and saved in the tables. If the entries do not appear in the tables then this is another definite confirmation that the information was never received from the device.
 

If the device isn't returning the expect OID's then this is a device/vendor issue. The user should then check on the device why the OID's are not being sent to Orion.