NetXMS Support Forum

Windows agent nstaller on netxms.org/downloads has been updated, please try it

Pollers ans Datacoll look ok, also it's worth to check the wait time for them.
Syncer is good.

Main is not good - it has average wait time of 59 seconds. Main thread is doing a lot of different things - executes commands on management server, communicates with proxies, calculates business service related stuff...

What are values of
ThreadPool.Main.MaxSize
ThreadPool.Main.BaseSize
?

А можно и мне эти логи, здесь в личном сообщении

В Event Processing Policy есть правило которое реагирует на SYS_INCORRECT_NETMASK. Можно в нем добавить исключение на конкретную ноду.

Про ICMP в доке достаточно подробно описано, но спрашивайте если там что-то не понятно
https://www.netxms.org/documentation/adminguide/icmp-ping.html

Hi!

What exactly version of netxms are you running?
Can you show output of "sh st" from Tools -> Server Console?


Are default System -> NetXMS server templates up to date? They are not imported automatically - you can set server configuration parameter Server.ImportConfigurationOnStartup to "Always" and restart the server.

From the server template it would be worth to see graph for DCI "NetXMS server: physical memory used by process" (together with "System: available physical memory").
And graph for "Server QueueSize DBWriter.Total: Current" - that's how much data is waiting to be written to the DB. If DB is slow, this might grow and consume memory.


What about DB, is it running on the same VM?
Anything else running on this VM? NetXMS Web UI?

Can you share the actual images you use in this rack?

По умолчанию при добавлении новых устройств у интерфейса ставится такое ожидаемое состояние, как оно было в тот момент. Т.е. если порт был UP то мы будет ожидать, что он должен быть UP и будет генерить алармы, если это не так.

В Configuration -> Server Configuration можно поменять этот дефолт для новых устройств - параметр Objects.Interfaces.DefaultExpectedState

Если зайти в Properties любого интерфейса, то там на закладке Polling будет выбран Expected State - там это можно поменять для уже существующих устройств.

Ну и еще можно скриптом поменять для существующих устройств, например добавив в Hook::ConfigurationPoll такое:

for (i : GetNodeInterfaces($node)) {
  i->setExpectedState("IGNORE");
}

Usage% is showing how many threads have been created in relation to the maximum number of threads. Maximum number of threads is configured in Configuration -> Server configuration, e.g. ThreadPool.Main.MaxSize.

So e.g. if you have 100 as ThreadPool.Main.MaxSize and at some point the system decided to launch all 100 threads, it does not necessarily mean that you have problems - may be these threads, while being at maximum number are still handling the job. Check statistics for "current load" and "average wait time" - this should give more information.

You can merely increase the MaxSize server configuration parameters in increase thread count.

There are two parts:

1) On a node you have a DCI with Origin="Script". The script itself is in script library, DCI has name of that script in "Parameter" (renamed to "Metric" in most recent version) field. It's also possible to pass some parameters to the script by putting:
script_name("parameter_1", "parameter_2")
or
script_name(123,456)

Script does it's job, reads some values from nodes, etc. Finally script returns some value with the help or return operator. The value returned by the script is stored as the value of the DCI - it's visible in last values, can be seen on graph, etc.

2) On the map, "DCI image" object has this DCI as data source. In properties of the DCI image you can configure the default image and what images should be used if DCI value goes to  some specific value.

Hi!

By "Client folder" you mean a container in object tree with all the nodes related to that specific client?

What about history of DCIs on these nodes, do you also want to migrate it?

Returning a bit back - there was another approach - to have script DCIs which are pulling several OIDs and doing calculation right within the script. Code of such script DCI might look like this:

transport = $node->createSNMPTransport();
if (transport == null) return null;

value1 = transport->getValue(".1.2.3.4.5.6.7.8");
if (value1 == null) return null;
   
value2 = transport->getValue(".1.2.3.4.5.6.7.8");
if (value2 == null) return null;
   
return value1/value2;   
Then on the map you can add "DCI Image" objects. In properties of these "DCI Images" you can configure what image to display depending on the value of the DCI. 

If you go with this approach, is there anything that is missing?

Да, это как раз таки NetworkDiscovery.ActiveDiscovery.EnableTCPProbing

В Configuration -> Network Credential можно задавать списки Agent Ports (для NetXMS агента) и SSH ports. Задавать можно или глобально, или по зонам. Если эти списки пустые, берутся порты по умолчанию - соответственно 22 для SSH и 4700 для агента.

https://github.com/netxms/netxms/blob/master/src/server/core/network_cred.cpp#L359

Происходит ли этот опрос раз в час (это дефолтовый интервал для configuration poll) или с другим интервалом?

На Configuration Poll да, было такое, что даже если в свойствах ноды не был прописаны ssh логин/пароль, сервер пытался подключаться с пустым паролем. Это достаточно давно исправлено.
Ну и стоит проверить в Configuration -> Network Credentials - нет ли там ssh логинов в списке, если есть, то сервер будет пытаться их перебирать.
Ну и можно автоматом расставить галочку "Disable SSH usage for all polls" на все ноды, добавив в Hook::ConfigurationPoll строчку $node->enableSsh(false);

Вторая возможность - что он пытается подключатсья по ssh в процессе Network Discovery - тогда период этого опроса должен совпадать с интервалом Network Discovery.

Node status depends on three things
- Status of interfaces
- Severity of alarms present on the node
- Value of DCIs that have "Use this DCI for node status calculation" checkbox set.

By default most severe status is taken as status of the node.

So first of all you need to figure out, is it coming from an alarm or an interface

Can you show screenshot of your gauge configuration and also the value of the DCI from last values?