NetXMS Support Forum

Hi,

NXSL function "replace" was added only in 3.9 branch, which is not released yet.

As for original geolocation issue - geolocation object constructor expects two floating point numbers as latitude and longitude. You have to manually convert d m' s" format into degrees.

Best regards,
Victor

Hi,

could you please show data source configuration for dashboard elements? Also, could it be that you have access restrictions on DCI level?

Best regards,
Victor

Hello!

Currently it's not possible to automatically add data sources to map links. We have plans to implement it though.

Best regards,
Victor

You have to install  SQL Server Native Client on machine where you are installing NetXMS server.

Best regards,
Victor

Quote from: dosura on July 12, 2021, 04:46:23 PM
hello have the same probelem with invalid thread acces thing but would to avoid the cleaningand reinstalling process what can i do 

Doesn't seem to be same problem. What version you are using? When did you get invalid thread access error?

Best regards,
Victor

From the log it looks like connection from server never gets to agent. Try to connect with telnet or nxget to this server from NetXMS server machine - you may get a bit more diagnostic. Also make sure that in node properties you have correct IP address.

Best regards,
Victor

Hi,

just fix it. Fix will be included into next release. You can also try this agent build with a patch: https://cloud.radensolutions.com/s/DWBNYGnGbSBMD59

Best regards,
Victor

Hi,

error message is like this because MS SQL driver uses ODBC API internally. Do you have MS SQL native client installed on the server?

Best regards,
Victor

Hi,

automatic alarm termination is defined by event processing policy. It should have been migrated along with other configuration. Try to check event processing policy rules related to both activation and termination events, and also check event log that termination event was generated.
What version you are using? Is it same version as before migration or you did both upgrade and migration?

Best regards,
Victor

I did a quick look at the code for reading firewall state, and it is indeed strange. Will dig deeper into it in next few days, as time permits.

Best regards,
Victor

Hi,

it looks that DCI data processing for some reason takes too long. Do you have any transformation scripts or script thresholds on those push DCIs?

Best regards,
Victor

Hi,

what is NetXMS version, and what are firmware versions on Mikrotiks? We did some fixes recently for handling incorrectly (in a non-standard way) reported LLDP data by some Mikrotik devices, so if version is relatively old upgrade may help. Otherwise I would like to look at SNMP walk results for .1.3.6.1.2.1.2.2, .1.0.8802.1.1.2.1.4.1.1, and .1.0.8802.1.1.2.1.3.7.1 for all involved devices.

Best regards,
Victor

Yes, currently network discovery code assumes that other zones are only fully reachable via proxy. I will think how to fix that.
Out of curiosity, what is the reason for creation of separate zone if everything within that zone is directly reachable from server?

Best regards,
Victor

Hi,

currently MODBUS/TCP is not supported, although we plan to add it.

Best regards,
Victor

Hi,

it should be possible with simple Java application (or maybe even nxshell script) that will receive data in NMEA format, extract coordinates, and update appropriate node object via NetXMS API. This can also be implemented as server module in C++.

Best regards,
Victor