NetXMS Support Forum

Hi,

then solution could be different. You can leave poll count for status change at 1, and create script based DCI which will return 1 if node is down and 0 if not. Then you can create threshold which will fire if value is 1 for at least 5 polls, and send notification based on that threshold's event. Script could be like this:


return ($node->runtimeFlags & 0x0004) ? 1 : 0;


More information about Node class can be found here: https://wiki.netxms.org/wiki/NXSL:Node.

Best regards,
Victor

Authentication settings in agent config and in node properties should match - either enable it on both sides or disable on both sides. In this log it seems that you turn off authentication on agent but enable it in node properties.

Best regards,
Victor

You have to apply patch to proxy agent as well, because server uses ping subagent on proxy to ping nodes in remote zones.

Best regards,
Victor

Communications is ok now, you won't get any difference with or without authentication. Do you see any difference in status poll? Also, what version you are using?

Best regards,
Victor

You have set RequireAuthentication to yes in agent config. Did you set correct shared secret in node properties? Also, try to turn off authentication in agent config and in node properties.

Best regards,
Victor

Я бы предложил сделать скриптовый DCI, который SNMP walk'ом находит индекс ppp0, и затем считывает значение через snmp get. Как вариант, если интерфейс меняетя не очень часто - индекс брать из объекта интерфейса (находить его по имени) - он будет обновлятся во время configuration poll.

Я не уверен что проблема в индексах - в логе опроса пишет "Unable to get interface list from node". А capabilities не поменялись? Configuration poll скорее всего именно capabilities выставляет.

Did you update ping subagent on proxy or only on NetXMS server?

Best regards,
Victor

Hi,

you can use filtering scripts to filter out events at specific time periods. Server uses topology information to suppress node down events if node is behind router - but it should now route to it across the network. Scripts could also help in event suppression - you can check status of peer node in filtering script and stop event processing if peer node is a router and it is down.

Best regards,
Victor

Hi,

there could be different reasons for such messages. Most often it's a bug in a server code, or lack of resources. Item poller may hang if data collection configuration of one of the nodes is locked for too long. Do you monitor server internal queues? Also you can check size of the queues when item poller hangs (by running command show queues on server's debug console).

Best regards,
Victor

Hi,

there was a patch for ping subagent that likely will help you as well (somewhere in this thread: https://www.netxms.org/forum/announcements/netxms-2-0-m3-released/).

Best regards,
Victor

Hi,

I'll try to reproduce this issue on my system and fix it. Have registered it in bug tracker: https://dev.raden.solutions/issues/806.

Best regards,
Victor

Hi,

it's actually a bug. I register it in our bugtracker (https://dev.raden.solutions/issues/805).

Best regards,
Victor

Hi,

do you have LB address on separate interfaces of web servers? If yes, you can mark those interfaces as "excluded from topology".

Best regards,
Victor

Hi,

there are few different options available. Simpler one is to set "required poll count" option on node interfaces to number of polls needed to consider interface down. So of you have set it to 2 for example, server will consider interface (and node) as down if it will not respond for two consecutive status polls (once per minute by default).

Best regards,
Victor