Submit a ticketCall us

Have You Auto Renewed? If not, you're missing out.
The SolarWinds Renewal Program comes with a host of benefits including the most recent product updates, 24/7 technical support, virtual instructor-led training and more. Experience all of this with the convenience of Auto Renewal, and never worry about missing any of these great benefits. Learn More.

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

Technical troubleshooting for common ConnectNow issues - Part 3

Technical Troubleshooting Steps - Part 3

 

The following procedure provides 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:
    Notes:
  3. Confirm that the two devices you want to connect are, in fact, directly, physically connected on Layer 2, and confirm that devices are bridged on an access port and 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 will only display connections to MAC addresses that exist in a device's Bridge table. Complete the following steps to check a device's Bridge table:
    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 may be used in further debugging. For more information, see Technical Troubleshooting - Part 1, step 5.b.a.
  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. For more information, see www.solarwinds.com.
      1. Install the 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 to which 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, browse the Bridge-MIB::dot1dTpFdbTable (1.3.6.1.2.1.17.4.3) using a community string that is built like: community@<vlan/>.
        For example, if you 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 (1.3.6.1.2.1.17.7.1.2.2) MIB using the raw community string, as in public.
    3. If the MIB-Browser returns with a Table not supported error for either of these table, verify both that you are trying to get 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 be inaccessibile 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 (1.3.6.1.2.1.4.22.1) 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.

Continue to Technical Troubleshooting Steps - Part 4.

This article applies to:
Orion Network Atlas version 1.2 and higher


  1.  
Last modified

Tags

Classifications

Public