NetXMS Support Forum

Ок, спасибо. Покажите, плс, первую страницу настроек этого DCI.

Проверьте в 6.0.3 клиенте, он сегодня вышел

Да, повторили, будет чинится в этом тикете: https://track.radensolutions.com/issue/NX-2929

It uses GLOB matching, so supports * and ? wildcards. What NetXMS version you are using, is it web or desktop UI?

Configuration poll не происходит при раскрытии ноды - он происходит по своему расписанию, по умолчанию раз в час. Здесь больше похоже на какую-то проблему клиента из-за того, что интерфейсов слишком много, вероятно он на самом деле их не стирает.

Проверьте, плс вот таким скриптом с любого другого объекта:

n = FindObject("ISW001"); // или по ID ноды: FindObject(12345);
println(n.name);
println(n.interfaces.size);

скрипт напечатает имя ноды и количество интерфейсов под ней. Затем попробоваться удалить интерфейсы и еще раз запустить скрипт.

А, кстати, в какой момент происходит добавление интерфейсов? Нет такого, что после рестарта этого коммутатора?

Можно воспользоваться хук скриптом Hook::CreateInterface, там поставить


if (($1.node.name == "ISW001") and ($1->name ~= "^VLAN.*"))
{
  return false;  // Block creation
}

return true;


Про галочку запрета проверим.

Audit log is retained after node deletion, same for syslog.

For event log there's Events.DeleteEventsOfDeletedObject setting in Configuration->Server Configuration, if set to true (default), they are deleted. And there's similar setting for alarms - Alarms.DeleteAlarmsOfDeletedObject.

DCI data is deleted.

If database is Postgres Timescale, then event log and DCI history is not deleted.

In all above situations when data is not deleted, it would be problematic to view it since you need to know node's ID.

New decommissioning functionality is basically node unmanage with addition of automatic deletion at later time. So for now you can just unmanage your nodes.

Это на всех нодах так, или только на некоторых?
На какой ОС клиент?

This issue was fixed, fix will be available in next patch release.

If you do not want to wait for it, you can run these queries to the database:

ALTER TABLE userdb_custom_attributes ALTER COLUMN attr_value varchar(max) NULL;
UPDATE metadata SET var_value='34' WHERE var_name='SchemaVersionMinor';

and nxdbmgr upgrade again after that

1) will get back later
2) I was mentioning custom attribute, please consult the documentation: https://netxms.org/documentation/adminguide/object-management.html#custom-attributes

Not sure how your config looks for oracle.nsm part, but the dbquery example issue is due to # char - it's treated as comment when configuration file is parsed.

You can enquote the whole value:
Database = "id=CDB0;driver=oracle.ddr;server=//hostABC:1521/CDB0;login=c##netxms_agent;Password=mypassword"

Or it's better to use new configuration format that goes in a section, just make sure login is in quotes:

[DBQUERY/Databases/db1]
driver=pgsql
server=10.0.0.4
login="netxms"
password=netxms1
name=test_db

(https://netxms.org/documentation/adminguide/application-monitoring.html#configuration-example)

1) Yes, you need to configure DCIs with relevant OIDs. This typically is done in a template, for modular things like PSUs instance discovery can be used to autodetect things. Feel free to ask for more details.

2) Since v 5.something we have out-of-the-box templates for traffic monitoring, see under Templates->Interface traffic. They are not applied by default (to avoid surprise on large installations with thousands of network devices), so you need to add custom attribute "Template.InterfaceTraffic" with value "YES", you can just do it on Infrastructure Services and put "Inheritable" checkbox.

UPD: reproxy has no repository, but there's .deb package - you can just install that: https://github.com/umputun/reproxy/releases

Reproxy on linux needs it to be installed manually, as it's not easily available from package. On linux we might use something else in the future. So currently nginx is the way.

Supported parameters are basically Address and Port, Address supports "*" or "any" to bind to all interfaces. (https://github.com/netxms/netxms/blob/master/src/server/core/webapi.cpp#L410)

Rest of params are for reproxy which is not relevant if using nginx (https://github.com/netxms/netxms/blob/master/src/server/core/webapi_tls.cpp#L205)