Submit a ticketCall us

Training ClassThe Orion® Platform Instructor-led Classes

Provided by SolarWinds® Academy, these trainings will introduce users to the Orion Platform and its features, management, and navigation. These courses are suitable for users looking to discover new tips, tricks, and ways to adapt their Orion products to better suit their monitoring needs:
Deploying the Orion Platform
Configuring Orion views, maps, and accounts
Configuring Orion alerts and reports

Reserve your seat.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Technical troubleshooting for common ConnectNow issues

Technical troubleshooting for common ConnectNow issues

Created by Interspire Import, last modified by Melanie Boyd on Jun 22, 2018

Views: 5,409 Votes: 1 Revisions: 15


This article discusses troubleshooting options for common ConnectNow issues.


Orion Network Atlas 1.2 and later


Preliminary Recommendations

The following steps are recommended to confirm that a customer is correctly prepared to use the ConnectNow feature:

  1. Watch this video about using ConnectNow to build a map in Network Atlas.
  2. Run Network Sonar Discovery. See SolarWinds Orion NPM Administrator Guide.
  3. Confirm that all discovered nodes and interfaces have been imported. See SolarWinds Orion NPM Administrator Guide.
  4. Open Network Atlas.
  5. Drag Nodes that should be connected on Layer 2 to the open map.
  6. Click ConnectNow.


Q: "I upgraded to 10.0, added nodes to a map, then clicked ConnectNow. Nothing happened. Why not?"
A: This could be caused by many issues. See the following section, ConnectNow Issues and Resolutions.


Q: "How does Orion NPM gather topology data?"
A: Topology data is gathered from multiple sources. The two primary sources are the Bridge and ARP tables. See the following section, ConnectNow Issues and Resolutions.


Q: "ConnectNow displays two devices as connected, but they are not connected. Why do I see false connections?"
A: This is probably caused by a faulty ARP table. See the following section, ConnectNow Issues and Resolutions.


Q: "What do you mean when you say Solarwinds does not support Layer 3 connections? I have a Layer 3 switch that is showing connections."
A: Orion NPM discovers connections as they exist in the Bridge MIB.See the following section, ConnectNow Issues and Resolutions.


Q: "Using ARP and CDP, I can see device connections, but ConnectNow is not showing these connections."
A: For Orion NPM to discover device connections, corresponding MAC addresses must be listed in the Bridge MIB for the connected devices. See the following section, ConnectNow Issues and Resolutions.


Q: "I have two devices on the same subnet. Why does ConnectNow not connect them?"
A: ConnectNow only draws lines between devices that are directly connected on Layer 2. Devices may be on the same subnet, but, if they are not directly connected on Layer 2, Orion NPM will not discover a connection. To confirm if two devices are connected on Layer 2, see the following section, ConnectNow Issues and Resolutions.


Q: "When I drag a node to the map, and click ConnectNow, why doesn't ConnectNow also add the neighbor nodes to the map?"
A: We are aware of this limitation, and we are considering it for a future improvement. As a workaround, drag multiple nodes onto the map and then remove those that do not connect.


Q: "Does ConnectNow automatically update discovered connections?"
A: No. Topology data in Orion can be automatically updated by scheduling a discovery in Network Sonar. However, mapped connections are only updated to correspond with updated topology data when you click ConnectNow in Network Atlas. For more information about scheduling discoveries in Network Sonar, see "Network Discovery Using the Network Sonar Wizard" and "Managing Scheduled Discovery Results" in the SolarWinds Orion NPM Administrator Guide.


Q: "Will ConnectNow remove old links from my map?"
A: No. ConnectNow only adds links to your existing map.


Q: "Why does some of my topology change when I rerun a network discovery?"
A: Topology data is completely deleted and rewritten every time a network discovery runs. If an existing discovery profile is changed, old topology data discovered using the previous profile will not remain in the results set of the previous profile. For more information about Network Sonar Discovery, see "Network Discovery Using the Network Sonar Wizard" in the SolarWinds Orion NPM Administrator Guide.


Q: "If I manually added nodes in Orion, how do I get ConnectNow to work?"
A: Complete the following steps to use ConnectNow on manually added nodes:

  1. Export a list, preferably in .txt, of your manually added nodes with their corresponding IP addresses.
  2. Create a discovery using the Specific Nodes option on the Network page of the Network Sonar Wizard. See "Network Discovery Using the Network Sonar Wizard" in the SolarWinds Orion NPM Administrator Guide.
  3. Complete the discovery.
    Note: You do not need to import these nodes after discovery completes because Orion NPM is already monitoring them. You just have to run discovery to populate the discovery and topology tables.


Q: "Where in the database can I find my topology data?"
A: For more information about viewing topology data in the database, see the following section, ConnectNow Issues and Resolutions.

ConnectNow Issues and Resolutions

The following procedures provide general guidance for addressing ConnectNow issues.

  1. Confirm that you are only looking for Layer 2 connections.
    Note: ConnectNow only detects Layer 2 connections.
  2. Run Network Sonar Discovery again and confirm that the following conditions are met:
    • For more information, see "Network Discovery Using the Network Sonar Wizard" in the SolarWinds Orion NPM Administrator Guide.
    • Confirm that your discovery is defined to cover enough IP ranges to include all the nodes you want to connect. All nodes you want to connect must be discovered in the same discovery.
    • Confirm that the discovery completes successfully. Topology data is populated during discovery and import.
  3. Confirm that the two devices you want to connect are directly, physically connected on Layer 2, and confirm that devices are bridged on an access port, not on a trunk port.
    Note: It is possible to investigate bridging on a Cisco device using the following commands, which should provide the Cisco device in question in the command results:
    • show mac-addr
    • show cam dyn
    • show cdp neigh
  4. Check the Bridge table on the devices you want to display as connected. ConnectNow displays only connections to MAC addresses that exist in the device Bridge table. To check a device Bridge table, complete the following steps:
    1. Open a command line interface (CLI) on the device you are checking to verify that the device is bridging the MAC address you expect to be connected.
    2. Enter show MAC-addr, show cam dyn, or similar.
      Note: If the connected MAC address is found on a VLAN, that information can be used in further debugging.See the following section, More ConnectNow Issues and Resolutions.
  5. Confirm that the Bridge MIB and ARP MIB are available via SNMP from the Orion server, as shown in the following procedure:
    1. Bridge MIB access can be detected using the Switch Port Mapper from the Engineer's Toolset. See
      1. Install SolarWinds Engineer's Toolset, and run the Switch Port Mapper gadget in the WorkSpace Studio.
        Note: The classic version does not support all Bridge MIBs
      2. Provide the IP address and credentials of one of the switches you expect to be connected.
      3. If any results are displayed, the Bridge MIB is reachable.
      4. Confirm that the MAC address of the device where you expect the switch to be connected is listed among the MAC addresses in Switch Port Mapper.
      5. If the MAC address you expect to be connected is not in the Switch Port Mapper results, continue troubleshooting.
    2. Browse the MIBs using the SNMP MIB-Browser in the Engineer's Toolset.
      1. To view the Bridge table via SNMP on a Cisco device, browse the Bridge-MIB::dot1dTpFdbTable( using a community string built like: community@
        For example, if you are looking for a MAC address on VLAN 400 and you are using the community string public, use public@400 to view the bridge table for that VLAN.
      2. To view the Bridge table for a non-Cisco device, browse the dot1qTpFdbTable( MIB using the raw community string, as in public.
    3. If the MIB-Browser returns Table not supported error for either of these tables, verify that you are trying to read the correct table and that you are using the correct community string.
    4. If the table and community string are correct, the Bridge table is not accessible. The table may not be accessible for any of the following reasons:
      • The device does not expose the bridge table via SNMP.
      • There is a view limitation in place limiting the access of the selected community string.
      • There is no bridging occurring on the selected VLAN.
    5. Browse for the ARP-IP::ipNetToMediaEntry( table using the raw community string (no need to add the VLAN ID) on devices on the same subnet that were captured in the discovery, and verify the MAC addresses are found.
      Note: ConnectNow requires Layer 3 information to correlate MAC addresses to Orion nodes.

More ConnectNow issues and resolutions

  1. Check for multiple IP addresses.
    1. Orion does not support multiple IP addresses for nodes, as in the case where a device is accessible from multiple subnets.
    2. If a node has multiple IP addresses, try either of the following:
      1. Orion NPM should manage the one that shows up in the ARP table.
      2. Add a node for each IP address to see which one works for ConnectNow.
  2. Another option is to test with LANSurveyor. For more information about LANSurveyor, see
    1. If LANSurveyor does not draw a connection, neither will Network Atlas.
    2. If LANSurveyor draws a connection, confirm that it is a direct connection and not merely the case that both nodes are connected to the same subnet.
    3. If LANSurveyor draws a direct connection, contact Dev to investigate further.
  3. False Positives
    1. If you are seeing connections that do not exist, there is probably an ARP table somewhere on the network with many wrong IP addresses for a single MAC address.
      1. This could happen if a host does not properly clear the ARP table for a long period of time.
      2. Flush the ARP table to clear old entries.
    2. Look for the offending MAC address in the ARP tables of the devices in the discovery.
  4. Submitting Cases to Development
    1. Before submitting a case to development, gather the following required information:
      • Identification of the nodes that are known to be physically connected, but not connected by ConnectNow. The more details of the expected connection you submit, the better development is able to provide a solution (IPs, subnet masks, MACs, port number, VLAN or not…).
      • SolarWinds Diagnostics.
      • Any additional info on the switch: Brand/model name, VLANs enabled/disabled, stacked or not…
      • Switch Port Map (export as CSV) of the switches in question.
      • The output from show cdp neigh and show cam dyn,show mac-addr, or similar from the Layer 2 device.
    2. The following information is also helpful:
      • A LANSurveyor map, created with the same settings as the Discovery, and the LANsurveyor_Log.txt file, generated with all logging settings enabled.
      • A screenshot of Network Atlas after completing ConnectNow.
      • A wireshark capture of the Network Sonar Discovery session.
      • A wireshark capture of the LANSurveyor session, if available.
      • SNMP image of the switch in question.
      • The output of a command line switch port map from the Engineer's Toolset with the /showraw switch. enabled.
        For example, SWSPMCMD <IP> <Community> /showrow > mapfile.txt
  5. Check the Database. Confirm that the database contains discovery data, as follows:
    Note: This confirmation can help development in the debug process.
    1. Open SQL Server Management Studio or Solarwinds Database Manager.
    2. Confirm that the TopologyData table contains data.
      Note:  Compare with the Nodes table to check specifically for one of the connections that you are not seeing via ConnectNow. If data is shown, Network Sonar Discovery is executing.
    3. If there is no data in the TopologyData table, check the Discovery tables for data.
    4. Confirm that the DiscoveryNodes table contains data.
    5. If there is no data in the DiscoveryNodes table, either Network Discovery has failed or no nodes were imported. Confirm that discovery has completed
    6. Confirm that the DiscoveryEdges table contains data.
    7. If there are no edges, the discovery engine did not find any connections.
  6. Review Diagnostics
    1. The DB folder contains diagnostics for the database tables.
    2. The LogFiles/DiscoveryEngine folder contains the logs created by Network Discovery:
      • DiscoveryJob.log may contain errors.
      • DiscoveryJob.log contains the raw xml results from the discovery
    3. There may also be errors in LogFiles/BusinessLayerHost.log relating to discovery.
Last modified