NetXMS Support Forum

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

Hi,

message about DRBD is normal if you don't have DRBD configured. It will not impact agent operations.

Configuration looks correct. Could you please run agent with debug level 9, run status poll on node with network service and share agent's log?

Best regards,
Victor

Hi!

Quote from: d-ray on April 16, 2015, 05:52:03 PM
I upgraded my server today and fixed the ping agent.
It looks it is working when the client is in the same network.

but when the client is contacted over a proxy server (using zones) it doesn't work.

did you upgrade agent on proxy node?

Best regards,
Victor

В аттаче исперавленный nxdbmgr. Замените тот, что в дистрибутиве M3 и сделайте upgrade еще раз.

Quote from: lindeamon on April 15, 2015, 02:00:51 PM
Hi Victor,

when do you plan to publish the new installation packages with all the fixes ?
up until now i was under the impression that all the new releases are stable ones, what happened ? why does 1.2.17 is considered stable ? we are losing a lot of new and cool features if do not use the latest version.
when will the next stable release is due ?

Best Regards,
Lindeamon

Hi,

we do lot of internal changes (mostly targeted at IPv6 support), so few next M releases could have problems. It can be used in production, although you always should test it on test system if possible. We plan to rerlease M4 very soon which will fix most important issues found so far in M3. I think that stability will improve with next releases as major internal changes are already made and we will focus on fixing bugs and adding features that do not require so big changes in system core.

Best regards,
Victor

Hi,

please send result of command

netxmsd -v

and version and build number shown in bottom right corner of Web UI login screen.

Best regards,
Victor

Quote from: djex81 on April 14, 2015, 03:04:57 AM

Quote from: Victor Kirhenshtein on April 13, 2015, 09:14:15 PM
What address you have set as primary host name for management server node? Can you do nxsnmpwall on that address?

Best regards,
Victor

For the server node I am using the local address 10.0.0.2 . Yes, I can nxsnmpwalk on 10.0.0.2 without any issues.

What operating system and SNMP version used? If you are using SNMP v3, do you use authentication and encryption, and what algorithms?

Best regards,
Victor

Hi!

Quote from: brettmilfos on April 13, 2015, 12:36:19 AM
I have found a couple of problems with ping after the upgrade from 2.0-M2 to 2.0-M3.

One is the ping agent not working, but have got around that by reversing the IP addresses in the conf file.

The second is the ICMP proxy is not working. I would assume it is related to the same issue as the ping agent?

yes, both are related to same problem (also discussed in another post). You can apply patch posted earlier if you are building from sources, or I can provide compiled ping subagent for Windows. Also, we likely to publish patch release soon which will fix issues found so far.

Best regards,
Victor