NetXMS Support Forum

Hello

I think i found a tiny bug:

There is router being monitored currently with subnet a.a.a.a/24 on one interface. Today i added new subnet to this router b.b.b.b/24 on different interface. When adding new nodes with addres from b subnet, they appear on wrong network in netxms. Should be under Default -> b.b.b.b/24. But instead they apear under Default -> 10.0.0.0/8. What could cause this ?

When i would like to see address map for b.b.b.b/24 network, i cant because to netxms this network doesent exist.

Hi,

is it that b.b.b.b/24 is actually 10.b.b.b/24 (i.e. within 10.0.0.0/8)? If not, could it be that those nodes actually have other interface with address in 10.0.0.0/8 subnet?

Best regards,
Victor

Hello, i made few pictures, one picture speaks more that 1000 words

Route node that has 2 /24 networks configured.



Node thats is on subnet "B", for some reason there is no 10.100.7.0/24 network under "Entire Network, default zone". Node gets added to 10.0.0.0/8


Also there are two 10.0.0.0/8 networks, one has only 1 node, other has 30+

So I see two unrelated problems here:

1. Duplicated 10.0.0.0/8 subnets - definitely a bug in the server. We have similar reports for duplicate subnets and will investigate that.

2. Node is placed into 10.0.0.0/8 subnet because address 10.100.7.1 is within that subnet. The question is why you have 10.0.0.0/8 in the first place - if it was created by server that means that at least one node has IP address 10.x.x.x with network mask /8 (or had it before). That looks like misconfiguration to me. I suggest to check all nodes within 10.0.0.0/8 for addresses with /8 mask, and if there is none just delete 10.0.0.0/8 subnet object (making sure that nodes are bound to some container or other subnets so they won't be deleted) and run forced configuration poll on them - it will create correct subnets.

Best regards,
Victor

Found out what made the subnets, unders each 10.0.0.0/8 there is 1 juniper srx router with em0.0 interface and netxms discovers networks 10.0.0.1/8, 10.0.0.4/28, 128.0.0.1/2 and ipv6 address. None of those addresses are configured by me (they dont exist in configuration). Would it be possible to ignore auto creating of such large networks? Or what could be fix for that ?

You can mark interfaces em0.0 as "exclude from topology" if they does not have any valid addresses. I believe those are for stacking/clustering and not visible from outside anyway.

Best regards,
Victor