Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Network Performance Monitor (NPM) > "0 discovered links mapped" in ConnectNow on Orion Network Atlas NPM

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

Created by Ezgi Muderrisoglu, last modified by Caroline Juszczak on Dec 14, 2017

Views: 3,414 Votes: 8 Revisions: 17

Overview

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

connectnow2.png  connectnow1.PNG

 

Note - 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.

Environment

For NPM version: 11.5.2

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:

  • Pick two Nodes which has direct connection.
  • Go to the Node Details page of each and do list resource and make sure to select L2 & L3 and all interfaces are selected and submit.
  • “Update Topology” action calculates topology according to the data gathered by topology pollers.  

  • 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 short 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: 

https://support.solarwinds.com/Success_Center/Network_Performance_Monitor_(NPM)/Object_IDs_and_information_Orion_Platform_poll_for_NTM

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).

Compare and see does the IP address of the second device appear in the table?

Now look for the NodeID of the second device, and compare does the IP address of the first device appear 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.

 

Last modified

Tags

Classifications

Public