<![CDATA[Represent found-but-not-known entities in interface list]]>16:12:21.546 *D* [topology.cdp ] CDP(sw1 [165174]): remote IP address 192.168.10.5 16:12:21.547 *D* [topology.cdp ] CDP(sw1 [165174]): node object for remote IP 192.168.10.5 not found

It's found this from the CDP neighbours table, presumably, but there's no hint of this in the UI. It's good information to know about, although could be optional.
Maybe the interface list is not the place for this information, it's already eleventy columns wide and needs another column like I need a hole in the head 😄

]]>https://forum.netxms.org/topic/7455/represent-found-but-not-known-entities-in-interface-listRSS for NodeFri, 13 Nov 2026 20:48:11 GMTFri, 01 Jul 2022 15:44:25 GMT60<![CDATA[Reply to Represent found-but-not-known entities in interface list on Mon, 18 Jul 2022 11:41:46 GMT]]>Great stuff!

]]>https://forum.netxms.org/post/31670https://forum.netxms.org/post/31670Mon, 18 Jul 2022 11:41:46 GMT<![CDATA[Reply to Represent found-but-not-known entities in interface list on Wed, 13 Jul 2022 15:51:16 GMT]]>Currently server just discards information obtained from CDP, LLDP, etc. if it cannot find matching node. I think we can store raw topology data for the nodes as well, and show it in separate view (indicating which of IP/MAC addresses are known nodes of course). I've added it as feature request: https://track.radensolutions.com/issue/NX-2277.

Best regards,
Victor

]]>https://forum.netxms.org/post/31650https://forum.netxms.org/post/31650Wed, 13 Jul 2022 15:51:16 GMT