Submit a ticketCall us

Announcing NPM 12.2
With NPM 12.2 you can monitor your Cisco ASA firewalls, to monitor VPN tunnels for basic visibility and troubleshooting tunnels. NPM 12.2 also uses the SolarWinds Orion Installer so you can easily install and upgrade one or more Orion Platform products simultaneously.
See new features and improvements.

Home > Success Center > Network Performance Monitor (NPM) > Not seeing expected results in maps

Not seeing expected results in maps

Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 12 Votes: 0 Revisions: 6

This article attempts to answer some of the most frequently asked questions and lists some of the most common issues that you can encounter in the Map resource.

Why do I see a red dashed line?

A red dashed line means that the Topology Calculator could not produce a connection drawn on the map. The drawn connection does not exist between nodes or there are not enabled Topology pollers on these nodes. For connections drawn using ConnectNow, a red dashed line should not appear unless the connection was interrupted.
If you have manually drawn connections, ensure that topology polling is enabled.

What are unidentified nodes (ShadowNodes)?

This is basically a node that was found on the network which is not managed by Orion. These devices might be switches, hubs, routers, or other devices without names or addresses. They may also be virtual, and generated to signify an indirect connection within your map in cases when a Topology calculation cannot find any direct connections between two nodes. In these cases, an unidentified node is generated between the two known nodes.

Why is there an unknown status on connections with unidentified nodes?

If you want to know the connection status of the node, you need to manage the unidentified node in Orion and replace as a managed node.

Why isn't there a connection between a node and an unidentified node on Topology resources?

Resources are meant to display connections between devices that are managed by Orion. Unidentified nodes are exclusively meant to give relevant information on the map.

Why is there no utilization information for custom drawn lines?

Utilization relies on topological data. Custom drawn lines between two interfaces may theoretically work, but provided information won't be accurate. For instance, both interfaces are operationally up, but the connection might get interrupted. When this happens, the calculator excludes this connection from the list and that is the reason you would see red dashed line.
To avoid this, use the No additional information option unless you are sure that connection is calculated by Topology Calculator.

Why is an interface unknown in topological data?

Based on polled topology, the data calculator is either unable to find the interface or it is unable to distinguish between two interfaces. In both cases, it does not guess  about the interface, but places a NULL instead.

Unknown interfaces exist because L3 connections are based on route tables, which do not provide requested information about the other side. 

After upgrading, there is problem with Topology polling?

This is related to environments with multiple pollers. If Additional poller was turned on during the upgrade of the Main poller, there is a chance that the new pollers were not assigned properly.
In this case ensure that the Topology pollers are properly assigned on Nodes you want to monitor by clicking List Resources and confirm that all Topology pollers are checked.

Troubleshooting wireless heat maps

If the wireless signal coverage shown by your wireless heat map is not as expected, verify the following items:

  • Make sure the map scale is correct.
  • Make sure your access points are placed correctly on the map.
  • Verify that your  signals are up-to-date, delete obsolete signal samples and add new ones. For more information, see Taking Signal Samples.
Last modified
22:51, 22 Jun 2016