Documentation forNetwork Topology Mapper

Missing connections

NTM may be unable to generate connections among discovered nodes for the following reasons:

  • Invalid credentials

    Use “Test” at the bottom of the Add Credential resource to verify before adding or modifying credential.

  • Device does not support SNMP

    NTM uses SNMP polling to retrieve CDP and LLDP data. Without that Layer 2 and Layer 3 data, NTM cannot map direct connections among discovered nodes.

    So in such a case, assuming a device does not support SNMP but supports and can respond to ICMP, NTM would the node as indirectly connected only to other relevant ICMP devices, through a Network Segment node.

    For detailed information about Network Segments, see Open maps from earlier versions of NTM.

  • Device is configured not to return CDP/LLDP data by SNMP requests

    The result is the same as in the case that the device does not support SNMP.

  • Timeouts are triggered due to slow response from a devices

    If NTM is configured not to retry, or the specified number of retries fail, then the device is treated as an ICMP node.

    You can modify timeout settings in "SolarWinds.NTM.BusinessLayer.dll.config"   (\Program Files\SolarWinds\Network Topology Mapper).

    <appSettings>

     

    ...

    <add key="NtmICMPTimeout" value="5000"/>

    <add key="NtmMaxSnmpReplies" value="5"/>

    <add key="NtmSnmpTimeout" value="3000"/>

    <add key="NtmSnmpRetries" value="0"/>

    ...

    <add key="NtmWmiRetryInterval" value="1000"/>

    <add key="NtmWmiRetries" value="3"/>

    ...

    <add key="NTMVIMTimeout" value="3000"/>

    ...

    </appSettings>