NetXMS Support Forum

Hi!

Am I understand your correctly - you have one three-node cluster, and each node has two SNMP agents?

Right now the only working solution I could imagine is to configure lot of external parameters on agent which will call nxsnmpget - but this cannot be considered as good solution. I think that easiest way is to allow change of SNMP port on node and DCI basis - this is relatively easy change and will solve this problem. I'll try to implement it in 1.0.8 release.

Best regards,
Victor

Hi!

Could you please post a screenshots of your trap configuration? Also, try to set server's configuration parameter LogAllSNMPTraps to 1 and check SNMP trap log. Ensure that server generating the trap is registered as a node in NetXMS.

Best regards,
Victor

I create full build with changed memory management. Installer available at https://www.netxms.org/download/rc/netxms-1.0.8-rc1.exe. It can be installed as usual, and replaced back to 1.0.7 if needed.

Best regards,
Victor

Thank you! I hope that we will be able to finally solve this issue without forcing you to switch to another OS.
Donations are welcome in any form In fact, even your patience with this strange issue resolution is very helpful - because we are unable to reproduce this issue at our systems. And yes, Raden Solutions is owned by me and Alex.

Attaches is another build of libnetxms. Could you try to run server with it?

Best regards,
Victor

Most likely you have one extra 0 in your event code. Automatically assigned codes starts with 100000, so 100009 could be correct.

Parameters after event code are event-specific data, accessible on server via %1, %2, etc. macros and appropriate variables in NXSL scripts.

Best regards,
Victor

Command line tool for integration already exist - it's called nxevent. It's available on WIndows in server and management console packages, and if you need to build it on UNIX, you must use --with-client option for configure. This tool uses client library for communication with server, and therefore requires login and password. User used for sending event must have "Send events" right on object given as source for event.

Best regards,
Victor

Sorry, looks like this will not help, because modern Windows version ignores local copy of msvcrt.dll and always use one from system directory because it's in a list of "known DLL". I suspect that there could be incompatibility with new versions of msvcrt.dll, because netxmsd.exe built with VC6. I'll try to do special build this evening.

Best regards,
Victor

Could you please try to put attached msvcrt.dll into NetXMS bin directory and restart server?

Best regards,
Victor

Hi!

It's not possible now to change event source directly - only by resending event via external commands on behalf of different node. I'll think about built-in functionality for changing event source or easy event resending.

Best regards,
Victor

Hi!

FindNodeObject can return null in two cases: if requested node was not found or access to it was denied. By default access from script running for one node to another nodes are not allowed for security reasons (because if, for example, you have a user with write access to node A and no access to node B, it can create transformation script which will access node B and get information about it, thus breaking your security settings). You can disable this behavior completely by setting server's configuration variable CheckTrustedNodes to 0. Otherwise, you have to maintain trusted nodes lists for each node being accessed from another node's scripts. For example, if $node in your scripts refers to NODE1, and you call FindNodeObject($node, "NODE2"), NODE1 must be added to list of trusted nodes for NODE2.

Hope this helps!

Best regards,
Victor

Alarm termination by regular expression implemented in 1.0.7. You have to upgrade both server and management console to be able to configure it.

Best regards,
Victor

Hi!

Please try to upgrade to 1.0.7, and select "Install PDB files" in components during upgrade. If it will continue to crash, and you are running on multiprocessor/multicore server, try to bound netxmsd process to single core by adding

ProcessAffinityMask = 1

to netxmsd.conf. This will bound server process to CPU #0. If you wish to bound to CPU #1 or other, use value 2 for CPU #1, 4 for CPU #2, 8 for CPU #3, and so on.

Best regards,
Victor

Hi all!

NetXMS version 1.0.7 is out. It's a minor bugfix release. Changes from version 1.0.6:

- Implemented automatic alarm termination using regular expressions
- Added support for ODBC connection strings in ODBCQUERY subagent and ODBC database driver
- Added server configuration parameter ProcessAffinityMask
- Fixed issues: #309, #310

Best regards,
Victor

Agent reload config on restart - so if change agent's config, you have to restart it. Maybe you just press "Save" instead of "Save & Apply" after first change?

Best regards,
Victor

Hi!

This can be done by setting "proxy" attribute for a DCI. For example, if you need to have DCI on node A, but get information from node B, you can configure DCI on node A and set it's "proxy" attribute to node B. For security reasons, you must also add node A to list of trusted nodes for node B, or disable trusted nodes checking globally.

Best regards,
Victor