<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Option to change behavior of L2 topology maps]]></title><description><![CDATA[<p dir="auto">I made a thread about this a while ago but can't find it<br />
My understanding was NetXMS builds L2 topology maps by looking at MAC addresses on a port, but it has a restriction that the port must only contain 1 MAC address. This means its impossible to build a L2 topology map if there are wireless links because at minimum there will be 3 (other device/switch, AP and SM radios)<br />
The vast majority of our network is wireless hence L2 topology has been useless to me. But i'd like the ability to use it and create from a seed router in our network and see the links that connect to all other directly connected switches/radios coming off it</p>
<p dir="auto">And i'd also like to use a separate instance of NetXMS to map out unknown networks that contain wireless links between buildings etc</p>
<p dir="auto">I have no idea how hardcoded the current implementation is. But it would be nice if we could override this behavior in server configuration, or on a map-by-map basis so any additional MAC addresses on a port are shown. Or if node for that MAC is not known just add all extra ones as a ? symbol<br />
I.e<br />
SwitchA<br />
   |<br />
? (MAC of AP AND SM)<br />
   |<br />
SwitchB<br />
  /        <br />
Node1  Node2</p>
<p dir="auto">That is much more useful than using SwitchA as seed and nothing at all shows up. And SwitchB only shows Node1/Node2</p>
]]></description><link>https://forum.netxms.org/topic/6259/option-to-change-behavior-of-l2-topology-maps</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 23:10:41 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/6259.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 06 Nov 2019 05:19:49 GMT</pubDate><ttl>60</ttl></channel></rss>