Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Network Performance Monitor (NPM) > No Topology connection with established CDP entries

No Topology connection with established CDP entries

Table of contents
Created by Matthew Lamb, last modified by MindTouch on Jun 23, 2016

Views: 182 Votes: 1 Revisions: 6

Overview

This article gives information on why you may see no or only one topology connections even if the CDP data showing connection information is fully populated, both on the device and in the database.

Environment

NPM v10 and later

Detail

One of the methods that NPM determines topology is through a IP to IP connection utilizing CDP data for Cisco devices. This data is gathered through SNMP, specifically for these OIDS:

 

cdpCacheAddressType
cdpCacheAddress
cdpCacheDeviceId
cdpCacheDevicePort
1.3.6.1.4.1.9.9.23.1.2.1.1.3
1.3.6.1.4.1.9.9.23.1.2.1.1.4
1.3.6.1.4.1.9.9.23.1.2.1.1.6
1.3.6.1.4.1.9.9.23.1.2.1.1.7
L2 entries gathering for CISCO-CDP-MIB

This information will match the interface ifindex of the host device to the ifindex on the connected device, as well as provide IP based information. This information is mapped through index value tracking, so it takes some back and forth to determine the connection. This information is then stored in the NodeCiscoCdpEntries table like this example:

 

 

These entries show that NodeID 1521 (Device 2) has four Interface connections through CDP to NodeID 1861 (Device 1). However, when you look into the TopologyConnections table, you only see the following:

 

 

One of the key components from this data is gathering the MAC address of the interface in question, being used on the host device. The topology calculator looks at the ifindexes of the interfaces in question, then checks the Physical Address of the interfaces in the Interface table. 

 

If all of the ifindexes for the CDP connections are different, then each is considered a unique connection and the TopologyConnections table should reflect this. However, in the event that the MAC addresses are all the same, the topology calculation will take only a single entry to show a connection. This is built into the calculation to avoid showing what could be considered redundant connection information in the event of port channels or other such technology.

 

 

Unfortunately, there is no method to work around this or alter the functionality, short of changing the MAC addresses to something unique. If you would like to have this changed, you can submit a feature request to have it included. There are also methods through database query that can manually add in the entries you want. You will need to contact the SolarWinds Technical Support, reference this article and they should be able to direct you how to do so and submit the feature request for you.

 

More information on the Topology OIDs used by NPM, you can find them here.

 

 

 

Last modified
22:52, 22 Jun 2016

Tags

Classifications

Public