Issue with CDP Queries After Upgrade to 2023.4.2

Hi,

We recently upgraded to 2023.4.2 earlier this week, and I am just now noticing that my SWQL/reports that had previously utilized CDP no longer seems to work. Previously, I was able to use the remotedevice within NCM.ciscocdp and it would pull back the name of any WAPs learned via CDP. That doesn't seem to be the case any longer, as it just shows NULL.

For anyone else on 2023.4.2, can you please run the following SWQL query and let me know if you have any luck pulling back any info that isn't NULL?

select c.RemoteDevice, c.RemotePlatform, c.RemotePort

from orion.nodes i LEFT JOIN ncm.ciscocdp c on c.node.CoreNodeID = i.NodeID

where i.UnManaged='False'

Thanks

Find more posts tagged with

cdp

SWQL

ncm

Accepted answers

All comments

lynchnigel

Im using 2023.3.1 and there is no data being pulled to that table anyway

try SELECT TOP 1000 * FROM [dbo].[NodeCiscoCdpEntries]

Orion.Nodes is NodeData table where all the nodes are

k_barton

Hi,

Thanks for your response. That query did not work for me in SWQL. I don't see anything called NodeCiscoCdpEntries in the object explorer.

I've also tried the following queries:

select c.DisplayName
from orion.NodeCdpEntry c

-All 6521 results are NULL

select c.CiscoCdp.DisplayName
from ncm.Interfaces c

-no results

select c.ciscocdp.DisplayName
from ncm.NodeProperties c

-all 1680 results are NULL

select c.DisplayName
from cirrus.CiscoCdp c

-no results

maciej.sandecki

Hi,

I'm on 2023.4.2 since Dec 2023 and it was working okay until now. Today I noticed the NodeID in NCM.CiscoCdp does not reference correct nodes in NCM.Nodes and consequently cannot be linked to Orion.Nodes.

I also noticed that my NCM Inventory job completed with an error below, not sure though if this could be the reason (but I think CDP data in NCM does come from Inventory results).

ERROR: Run job error: Violation of PRIMARY KEY constraint 'PK_NCM_CiscoCDP'. Cannot insert duplicate key in object 'dbo.NCM_Cisco_CDP'. The duplicate key value is (5b6305a9-fa7a-4b0d-ad2a-c0912462f2e0, 10103.4).

I will run the Inventory job overnight and see the result tomorrow.

Orion.NodeCdpEntry still works well for me.

k_barton

I ended up opening a ticket with SolarWinds support, and although it took weeks, they finally reported this as a bug and provided me with two SQL files that were used to update the SQL database, and it looks like that did the trick. I can finally link both nodeid & corenodeid again.

maciej.sandecki

Great! I wonder if this is fixed in 2024.1. Would you mind sharing the SQL files?

maciej.sandecki

After the inventory job finished today I again had CDP data in NCM.CiscoCdp that could be correctly linked to NCM.Nodes.