<![CDATA[Mikrotik/RouterOS isCDP]]>Hi. I am not sure why, but NetXMS does not seem to be able to use Mikrotik CDP/LLDP implementation. The only details it gets from L2 networks are interfaces that are connected to a Bridge, however not all interfaces are always in a bridge and therefore NetXMS cannot reliably build l2 topology. Is there something special I must do to make this work? This is on Wireless Routerboards as well as switches (although the switches are less of an issue as everything is in a bridge then)

]]>https://forum.netxms.org/topic/6102/mikrotik-routeros-iscdpRSS for NodeFri, 13 Nov 2026 16:07:44 GMTSat, 24 Aug 2019 07:19:36 GMT60<![CDATA[Reply to Mikrotik/RouterOS isCDP on Thu, 30 Apr 2020 15:37:07 GMT]]>Hi.

I just wanted to find out if there has been any progress on this yet?

]]>https://forum.netxms.org/post/27804https://forum.netxms.org/post/27804Thu, 30 Apr 2020 15:37:07 GMT<![CDATA[Reply to Mikrotik/RouterOS isCDP on Mon, 26 Aug 2019 07:44:39 GMT]]>Hi. Thanks for the reply.

According to Mikrotik WIKI from 6.44 LLDP should run on slave interfaces (instead of the "master" port) which should hopefully fix the issue? I tried upgrading to 6.44.3 however NetXMS still does not recognise isCDP or isLDP

https://wiki.mikrotik.com/wiki/Manual:IP/Neighbor_discovery#LLDP

]]>https://forum.netxms.org/post/26381https://forum.netxms.org/post/26381Mon, 26 Aug 2019 07:44:39 GMT<![CDATA[Reply to Mikrotik/RouterOS isCDP on Sat, 24 Aug 2019 18:03:18 GMT]]>Mikrotik LLDP implementation is not entirely correct, sometimes it reports bridge interface instead of actual port. This was discussed recently in another topic. I have some ideas how to deal with it, will try to implement in next few releases.

Best regards,
Victor

]]>https://forum.netxms.org/post/26372https://forum.netxms.org/post/26372Sat, 24 Aug 2019 18:03:18 GMT