<![CDATA[About Subnet Object's Status]]>Hi, Victor!

    A question confused me a lot for long time, according to my understanding, the status of Subnet Object can only be changed by the related 2 interfaces status of network nodes belong to the subnet object, as the graph shows:

A(X) --- B --- (Y)C

A is a router, C is also a router,  B is the subnet through which the A & C are connected. X is the interface belongs to subnet B, Y is the interface belongs to subnet B, and by ordinary understanding, only X's and(or) Y's status change to down, B's status will be changed to down.

But i find as long as A or C's status changes to error(including errors related or not related to the subnet), the B's status will changed to Error and an emergent alarm will arise. This characteristic makes me very confused, because i cannot locate the real problem in the network through monitoring the topology map'icon status changes.

Please follow with interest, thank you!

Best Regards!

]]>https://forum.netxms.org/topic/1739/about-subnet-object-s-statusRSS for NodeFri, 13 Nov 2026 16:32:16 GMTSat, 26 May 2012 17:09:16 GMT60<![CDATA[Reply to About Subnet Object's Status on Sat, 26 May 2012 18:17:09 GMT]]>Thank you! i'll try to change the percent.

]]>https://forum.netxms.org/post/7513https://forum.netxms.org/post/7513Sat, 26 May 2012 18:17:09 GMT<![CDATA[Reply to About Subnet Object's Status on Sat, 26 May 2012 17:15:31 GMT]]>Status of subnet object will change if any of the node in this subnet will change it's status. It is not important if node status changes because of any one interface is down, or alarm was created for that node. You can slightly change the behaviour of subnet status calculation by changing status calculation rule for subnet object. For example, you can make subnet changing it's stats to critical only if 80% of nodes within this subnet is in critical state.

Best regards,
Victor

]]>https://forum.netxms.org/post/7512https://forum.netxms.org/post/7512Sat, 26 May 2012 17:15:31 GMT