NetXMS Forum

До сих пор проблема в 3.2. Почему фильтры на них не действуют?

For me issue was resolved in 3.1.

Issue was fixed by 3.1. Not really much help here. 

SNMP community string not saving after upgrading to v3. I click apply, reopen properties and it is empty. Database check found no issues. It runs on windows + ms sql.

I just noticed SNMP community is not being updated/saved. it only saves it if it is no longer than 3 characters long... Anyone else has such problem?

I like new templates that came with v3 for SNMP. But they don't have any alerting. If I add those myself or modify templates, will future updates overwrite my changes to them?

Могу подтвердить это тоже. Периодически интерфейсы появляются хотя и я их всех отфильтровал. Я их вручную удаляю каждый раз.

I saw in changelog for 2.2.7 added functionality for "TCP proxy", but I can't find any documentation for that. Can someone point me in the right direction?

Any client OS.
I gave up on  Ubuntu 18.04. Installed server on Windows, worked on first try.

I get this error during windows agent installation. I used older agent 2.2.12 installer, no error during install, 2.2.12 -> 2.2.15 upgrade no error also.

New install on Ubuntu 18.04. I can't make agents tunnel to work. I used netxms documentation to create CA and certificates.

server log:
2019.06.19 21:16:02.510 *D* [crypto.cert        ] Loading CA certificate from /home/user/ssl/rootCA.crt
2019.06.19 21:16:02.510 *D* [crypto.cert        ] Adding CA certificate C=AU,O=Internet Widgits Pty Ltd
2019.06.19 21:16:02.511 *D* [crypto.cert        ] Server certificate: C=LV,O=netxms.org,CN=|product_name| Server
2019.06.19 21:16:02.511 *D* Server certificate loaded
2019.06.19 21:16:02.511 *D* Using server certificate key

2019.06.19 21:16:06.884 *D* [agent.tunnel      ] SetupTunnel(x.x.x.x): cannot create TLS context

client log:
2019.06.19 21:21:55.571 *D* [tunnel            ] x.x.x.x: TLS handshake failed (error:00000005:lib(0):func(0):DH lib)

What am I missing here?

How does one setup network discovery in remote zones?

What is the proper way to setup proxy agent for remote network?

I followed documentation and enabled zones. I have port 4700 open on agent machine. I added agent node manually with external IP address to default zone. I added other nodes to different zone and first node as proxy.

Remote network subnet object appeared twice in both default zone and remote network zone. There are other remote networks that will be added later and they will overlap.

HP printers started generating alarms about invalid network masks. It is was not an issue in 1.2. Bug?
Alarm - [Minor] Invalid network mask 0 on interface "NetDrvr", should be 24.

Same here. I could not make ICMP proxy work on 2.0-M4.