Here is some information I send out to Troubleshoot ConnectNow Connection issues
Links are detected using the SNMP Bridge and Arp MIB Tables
-We support only layer 2 or link layer connections
In some unusual situations, even with SNMP and the Bridge MIB available, we may fail to detect a link
-This is usually because the MAC address is not available in the mib
We check OIDs QBridge MIB (1.3.6.1.2.1.17.7.1.2.2) or Bridge-MIB::dot1dTpFdbTable (1.3.6.1.2.1.17.4.3 )
Subnets not supported
-There is no object for a subnet in Network Atlas
-Nodes connected only via subnet will not connect
Must have intermediate switches on map
-Nodes must be adjacent to connect
No nodes are added to the map by Connect Now
Requires a discovery
-Topology tables are populated during import and after scheduled discovery
-Topology is populated automatically after scheduled discovery but only for managed nodes
-When discovery is canceled, there may be limited or no topology data available
-When a canceled discovery is imported, the topology data will be incomplete
-Topology data is only as fresh as the last discovery run
-Nodes must be managed
Connect Now does not update links automatically
-It only runs when user clicks Connect Now in Network Atlas
NPM does not allow one node to have multiple interfaces
Connections will only be discovered for the IP that shows in the arp table
Important Documentation for Troubleshooting ConnectNow issues
What is ConnectNow
http://knowledgebase.solarwinds.com/kb/questions/1674/What+is+ConnectNow%3F
ConnectNow Notes (posted above):
http://knowledgebase.solarwinds.com/kb/questions/1848/ConnectNow+Notes
Technical troubleshooting for common ConnectNow issues.
(removed old links for Part 2, 3, and 4. All the information formerly contained in these three KBAs now resides in the parent KB.)
ConnectNow is not linking all nodes
http://knowledgebase.solarwinds.com/kb/questions/1408/ConnectNow+is+not+linking+all+nodes
