Eventprocessing/Eventgeneration curious behavior
-
Having two installations of Netxms one for testing purposes (Netxms 1.2.5, Windows Server 2003, 32 bit) one that should go into production (Netxms 1.2.5, Windows Server 2003R2, 64bit) both updated from Netxms 1.2.4 there is different behavior in eventgeneration.
The problem occures when monitoring a node that is reachable and will get unreachable. Here are the events of the two systems.
Production system:
SYS_NODE_NORMAL -> SYS_NODE_UNREACHABLE -> (directly to) SYS_NODE_UNKNOWN -> (when node will be reconnected) SYS_NODE_UP -> SYS_IF_UP -> SYS_NODE_NORMALTest system:
SYS_NODE_NORMAL -> SYS_NODE_DOWN -> SYS_IF_DOWN -> SYS_NODE_CRITICAL -> (when node will be reconnected) SYS_NODE_UP -> SYS_IF_UP -> SYS_NODE_NORMALThe behavior at the testsystem is what I expect for monitoring. At the production system before upgrading to 1.2.5 I did not investigate events, but there I got an alarm too when the node was detached. Now with 1.2.5 on the production system this isn't the case.
Can anyone help me solving this problem?
Best regards
Georg
-
Hi!
This is due to topology-based event correlation. Idea is to suppress multiple SYS_NODE_DOWN events if they are caused by intermediate router failure. If only end node was disconnected and still server generates SYS_NODE_UNREACHABLE instead of SYS_NODE_DOWN, then this is a bug. Unfortunately this feature cannot be turned off. I'll add appropriate option in 1.2.6. As a workaround, you can disable routing table polls on intermediate routers - if NetXMS server will not know full route to the node, it will not try to do such correlation.
Best regards,
Victor -
Hello Victor,
first the node I'm looking for events is a normal switch that I can plug into the network or detach.
The two managementservers are in the same IP-subnet with the switch. On the server for prospective pruduction use I have a node for the relevant router in that network, but routing topology discovery is turned off for all configured nodes. There are no other nodes created that are behind this node.Best regards and thanks fast reply
Georg
-
Then it looks strange. Can you run server for some time with debug level 5 and send me the log after you got unexpected SYS_NODE_UNREACHABLE?
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