Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

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

Technical troubleshooting for common ConnectNow issues - Part 2

Common Customer Issues and Questions

 

The following are common customer questions and issues, provided with answers.

Q: "I upgraded to 10.0, put a bunch of nodes on a map, and then hit ConnectNow. Nothing happened. Why not?"
A: This may be caused by a range of issues. For more information, see steps 1-5 of the Technical Troubleshooting Steps - Part 3 and then steps 1 and 2 of the Technical Troubleshooting Steps - Part 4.

Q: "How does Orion NPM gather topology data?"
A: Topology data is gathered from multiple sources. The primary two sources are the Bridge and ARP tables. For more information about the Bridge and ARP tables, see step 5.b in the Technical Troubleshooting Steps - Part 3.

Q: "ConnectNow shows two devices as connected, but I know for a fact that they are not connected. Why do I see false connections?"
A: This is probably caused by a faulty ARP table. For more information, see step 3 in the Technical Troubleshooting Steps - Part 4.

Q: "What do you mean you don't support Layer 3 connections? I have another Layer 3 switch that is showing connections."
A: Orion NPM discovers connections as they exist in the Bridge MIB. For more information about the Bridge MIB, see step 5.a in the Technical Troubleshooting Steps - Part 3.

Q: "Using ARP and CDP, I can see device connections, but ConnectNow is not showing these connections."
A: In order for Orion NPM to discover device connections, corresponding MAC addresses must be listed in the Bridge MIB for the connected devices. For more information about the Bridge MIB, see step 5.a in the Technical Troubleshooting Steps - Part 3.

Q: "I have two devices that are clearly 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 step 3 in the Technical Troubleshooting Steps - Part 3.

Q: "When I drag a node onto 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 have 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. For more information, 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 in order 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 steps 4-6 in the Technical Troubleshooting Steps - Part 4.

Last modified
18:50, 18 Jan 2016

Tags

Classifications

Public