NetXMS Support Forum

Hi,

recommended database engines are PostgreSQL and TimescaleDB, depending on deployment size. For small deployments (few thousands of DCIs) you most likely won't get any significant performance gains. The larger your deployment is the more performance improvement you'll see.

Support for TimescaleDB in 2.2.17 was still experimental, and I would not recommend to do migration to TimescaleDB using 2.2.17. I would do as following:
1. Install new server and initialize TimescaleDB database
2. Upgrade old database to 3.0 using new nxdbmgr
3. Migrate old database to new one

We are planning to add in-place conversion from plain PostgreSQL to TimescaleDB but I'm not sure when it will be ready.

Best regards,
Victor

Sorry, I miss that first part with file names. Will check static builds, looks like this is issue specific to either static linking or non-UNICODE build. Usually you do not need static agents though - generic Linux agent (nxagent-3.0.2357-linux-x86_64.tar.gz) should work as well.

Best regards,
Victor

Please provide agent configuration file and configure options used for build.

Best regards,
Victor

You can mark interfaces em0.0 as "exclude from topology" if they does not have any valid addresses. I believe those are for stacking/clustering and not visible from outside anyway.

Best regards,
Victor

Currently it is not possible. If you don't mind please create feature request in our bug tracker for that.

Best regards,
Victor

So I see two unrelated problems here:

1. Duplicated 10.0.0.0/8 subnets - definitely a bug in the server. We have similar reports for duplicate subnets and will investigate that.

2. Node is placed into 10.0.0.0/8 subnet because address 10.100.7.1 is within that subnet. The question is why you have 10.0.0.0/8 in the first place - if it was created by server that means that at least one node has IP address 10.x.x.x with network mask /8 (or had it before). That looks like misconfiguration to me. I suggest to check all nodes within 10.0.0.0/8 for addresses with /8 mask, and if there is none just delete 10.0.0.0/8 subnet object (making sure that nodes are bound to some container or other subnets so they won't be deleted) and run forced configuration poll on them - it will create correct subnets.

Best regards,
Victor

Server generates event SYS_SCRIPT_ERROR for runtime errors in scripts, including instance discovery filter scripts, and also generates "warning" record in server's log. First parameter contains script identification string and second parameter contains error message. Unfortunately event is not generated if there is compilation error like in your case (although warning message in log still generated). I've fixed that in development branch, starting with next release you'll also get SYS_SCRIPT_ERROR event for instance discovery filter compilation errors.

On a side note, script syntax didn't change in that part - expression like

if (a < b) && (c < d) { }

was always a syntax error. Whole "if" expression should always be enclosed in parenthesis.

Best regards,
Victor

Hi,

I was able to reproduce this on my system. It's a bug in server. It is already fixed in development code and will be included into next patch release.

Best regards,
Victor

Hi,

the standard one. You can check manual here: https://www.netxms.org/documentation/adminguide/upgrade.html

Best regards,
Victor

Нет, но есть продукт наших партнеров - https://unimus.net/. Там есть импорт узлов из NetXMS, он делает резервные копии конфигурации и показывает различия между версиями.

И то и другое похоже баг в клиенте. Посмотрим.

Как-то так:


return $1 / GetDCIValueByName($node, ".1.3.6.1.2.1.43.11.1.1.8.1.1");


Small addition: if you have lot of values to convert or they change frequently you may want to create mapping table on the server (via Configuration -> Mapping Tables) and use NXSL function map (https://www.netxms.org/documentation/nxsl-3.0/#func-map) to map code to text.

Best regards,
Victor

Everything looks good. Please show object overview for few duplicating access points (I'm mostly interested in MAC address) and output of manual configuration poll on node.

Best regards,
Victor

Another option to avoid storing double events is to remove "write to event log" option from original event.

Best regards,
Victor