<![CDATA[How to stop secondary interfaces showing up on L3 Map]]>I have a Cisco switch that has an interface (vlan) with two IP addresses attached.
2 Objects show up in the device tree after auto discovery, and even though I have set the object with the secondary IP to unmanaged, and deleted it from the L3 map, it keeps popping back up and makes the diagram confusing.
Of course just deleting the object itself means it will turn up again as managed after the next auto discovery.

How can I stop this from happening while keeping the L3 map dynamic?
Can I use an object filter and exclude the secondary IP somehow? To be honest, I would prefer if the object doesn't show up in the device tree at all, while keeping auto discovery enabled.

Thanks,

]]>https://forum.netxms.org/topic/7174/how-to-stop-secondary-interfaces-showing-up-on-l3-mapRSS for NodeFri, 13 Nov 2026 21:23:26 GMTWed, 15 Sep 2021 16:23:20 GMT60<![CDATA[Reply to How to stop secondary interfaces showing up on L3 Map on Tue, 21 Sep 2021 08:47:14 GMT]]>I have added the following (just in case I need to add more IPs) to Hook::AcceptNewNode and it is working.

switch ($ipAddr)
{
	case "1.2.3.4":
		return false;
	default:
		return true;
}

Thanks!

]]>https://forum.netxms.org/post/30533https://forum.netxms.org/post/30533Tue, 21 Sep 2021 08:47:14 GMT<![CDATA[Reply to How to stop secondary interfaces showing up on L3 Map on Thu, 16 Sep 2021 15:01:50 GMT]]>Hi Victor,
Thank you for the reply.
Yes, NetXMS is polling the device via SNMP without problems, so on both instances the device is listing all the interfaces, so it was surprising to me too!

]]>https://forum.netxms.org/post/30501https://forum.netxms.org/post/30501Thu, 16 Sep 2021 15:01:50 GMT<![CDATA[Reply to How to stop secondary interfaces showing up on L3 Map on Thu, 16 Sep 2021 13:04:30 GMT]]>Hi,

does NetXMS server has SNMP access to this Cisco device? Because normally it should read all configured addresses via SNMP and not attempt to create separate nodes for each known IP address.

If for some reason device is not accessible via SNMP, you can block secondary address in discovery filter. You can set discovery filter to script, and use script like this:

if ($node->ipAddr == "1.2.3.4")
   return false;
return true;

you can also use hook script Hook::AcceptNewNode for this, just add the following line to it:

return $ipAddr != "1.2.3.4";

(of course replace 1.2.3.4 with actual IP address).

Best regards,
Victor

]]>https://forum.netxms.org/post/30500https://forum.netxms.org/post/30500Thu, 16 Sep 2021 13:04:30 GMT