CDP Neighbors Table

There is even yet another way of doing this that might be simpler, depending on your environment.   There is both a CDP neighbors table in NPM, which is what the link you gave leverages, and another CDP neighbors table in NCM, which of course means you have to be running NCM!   Quite a bit of differences between the two though, with the main difference being that NCM gets the information by doing an "Inventory", which doesn't depend on you managing the interface.

That being said, this inventory is done on a schedule, so depending on how often this inventory is done depends on how valid the information is.   Odds are it would be quite a bit lower impact than a UnDP, although I'd also doubt it would be updated as much.   So, which approach you take depends on how your environment is set up and how often you want these CDP neighbors to be scanned.  In our environment, ideally I'd like all interfaces with CDP neighbors to be monitored, so my original approach works ok, but if you have a limited # of interfaces you can monitor or something this might not work with your environment.

But, if you do have NCM and you're ok with the information being updated when you do inventory updates, then this works quite well without a UnDP!

SELECT CDP.Interfaces.InterfaceName AS [Local Interface], RemoteIPAddress AS [IP Address], RemoteDevice AS Device, RemotePort AS [Remote Interface], N.DetailsURL AS [_LinkFor_Device]

FROM NCM.CiscoCdp CDP

JOIN Orion.Nodes N ON (CDP.Node.CoreNodeID = N.NodeID)

WHERE N.NodeID = ${NodeID}

Sorry I didn't post it earlier!!

So, the way I see it, there are 3 choices now!

NPM Based CDP - Pro's that it doesn't need any other modules or UnDP, cons that you have to manage an interface to see it in the CDP table.

UnDP Based CDP - Pro's are that you don't need NCM, gets the interface regardless of whether its managed, but requires a bit more setup plus you have to assign the UnDP to the device.  But, you can manage the schedule that it polls very well too.

NCM based CDP (ie: this message).  Cons are that you need NCM, only updates when you do an inventory update, but gets all involved interfaces regardless of managed state.  You do have to have NCM assigned to the device also.

Nice job on the UnDP though mmarchand, even if someone decides to use a different method its a good example!   Also always cool to show different ways of accomplishing things, shows how flexible Solarwinds truly is!!

Hi Craig

Thanks for the comments, unfortunately no NCM for me and more then 4000 switch port to monitor, $$$ only for CDP, Had to find a way to do it.

Actually I will change the polling interval of the UnDP it is at 30 minutes now, but since it is only use for the name associated to the ifIndex of the port this never changes so it will not take much resources on the polling engine, everything else comes from NPM cdp Neighbors native poller.