Invalid network mask
-
-
Hi!
Most likely there are router/host which was discovered first by NetXMS and it reporting network mask 255.255.255.0. Because NetXMS server cannot really know who has correct netmask and who not, it assumes that first discovered node connected to some subnet has correct netmask for that subnet. There also possibility that you have incorrectly created subnet object for some reason. How object(s) for subnet in question looks like?
Best regards,
Victor -
Indeed it was an incorrect subnet dicovery. An orignal system had gon in with the incorrect subnet mask. Then set up some non-SNMP devices which in turn used this subnet mask. So changing the other made no difference to the Subnet, I had to remove the interfaces on the non managed ones to correct the problem.
Thanks guys. -
I have the same problem. But I want to manage the port as well. Are there any way to disable this fault alarm?
-
You can disable appropriate rule in event processing policy (the one processing SYS_INCORRECT_NETMASK event), or make an exclusion in source field of this rule for problematic nodes.
Best regards,
Victor
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login