<![CDATA[SYS_AGENT_UNREACHABLE alarm not until 3 polls fail]]>Hello everyone!

Let me first thank you for a great piece of software as well as a very useful forum! I've been using NetXMS for about 2 months now, so I'm still learning a lot here.

My configuration works quite well, but here's my problem: To get a warning if an agent fails, I included SYS_AGENT_UNREACHABLE in the event processing policy, but I can't find a way to avoid alarms that emerge from reboots or just short network issues. Is there any way to set the alarm to wait for 3 failed polls like you can do for every data collector as well as the general node reachable state?

Sorry if I overlooked some solution here. The only idea I can think of is to set the AgentCommandTimeout variable to some very high value, but I think this could influence the NetXMS behaviour generally.

Thanks a lot, bye!

]]>https://forum.netxms.org/topic/3921/sys_agent_unreachable-alarm-not-until-3-polls-failRSS for NodeFri, 13 Nov 2026 12:29:40 GMTMon, 10 Aug 2015 06:37:08 GMT60<![CDATA[Reply to SYS_AGENT_UNREACHABLE alarm not until 3 polls fail on Fri, 21 Aug 2015 13:32:32 GMT]]>Hello Victor,

Thank you for your reply and the great work - I finally found time to change to the AgentStatus parameter.

Best regards

]]>https://forum.netxms.org/post/17594https://forum.netxms.org/post/17594Fri, 21 Aug 2015 13:32:32 GMT<![CDATA[Reply to SYS_AGENT_UNREACHABLE alarm not until 3 polls fail on Tue, 11 Aug 2015 05:44:57 GMT]]>Hi,

instead of processing SYS_AGENT_UNREACHABLE event you can collect internal parameter AgentStatus. It returns 0 if agent is connected and 1 if unreachable. Then you can use thresholds as usual to generate alarm only if agent is unreachable for more then specific time period.

Best regards,
Victor

]]>https://forum.netxms.org/post/17525https://forum.netxms.org/post/17525Tue, 11 Aug 2015 05:44:57 GMT