<![CDATA[LAGs and Peer Nodes]]>Hi,

I noticed that the Interfaces tab seems to only accept 1-to-1 links.
When two switches are connected via LAG for example, only one of the interfaces one each switch will show as being connected to the other end. Same with servers connected via LAG.

We also encountered a network the other day, which did have a network loop in it. STP had blocked one of the interfaces so there was no obvious impact.
In this case, NetXMS was showing interface A on switch A to be connected to interface X on switch B - and the interface was down.
Switch A's interface B was also connected to switch B on interface Y - and this interface was up. However, NetXMS did not show peer nodes on those interfaces.
Interface A's peer node had been detected via STP, while Interface B was showing in LLDP.

I am not sure if NetXMS' design allows for handling of n-to-n relations when it comes to peer nodes?

Cheers

]]>https://forum.netxms.org/topic/5090/lags-and-peer-nodesRSS for NodeFri, 13 Nov 2026 20:30:04 GMTFri, 02 Jun 2017 05:21:23 GMT60<![CDATA[Reply to LAGs and Peer Nodes on Tue, 27 Jun 2017 21:40:55 GMT]]>Hi,

peer node is an interface attribute, so nodes connected by multiple interfaces should be shown as peers for each interface. I will try to simulate this issue in my lab network tomorrow - maybe something is broken.

Best regards,
Victor

]]>https://forum.netxms.org/post/22557https://forum.netxms.org/post/22557Tue, 27 Jun 2017 21:40:55 GMT