NetXMS Support Forum

Но вообще-то это довольно типичная ситуация, мы подумаем, может быть добавим какой-то специальный список сабнетов, для которых дубликаты будут игнорироваться

Да, в рамках одной зоны в NetXMS не может быть интерфейсов с одинаковыми адресами. Выход - в хук скрипте, который запускается перед созданием новых интерфейсов (Hook::CreateInterface) можно запретиться создание интерфейса, например:

for (i : $1.ipAddressList) {
  if (i.address == "10.2.1.188") {
    PollerTrace("  Blocked interface creation, because it is 10.2.1.188");  // this prints in conf poll output
    return false;
  }
}
return true;
Но уже существующие интерфейсы это не удалит, их можно или удалить вручную, или если их много, то можем сделать скрипт, который пройдет по нодам и удалит интерфейсы.

You can do type conversion this way:

b = Math::Floor(12.34);
b = int32(a); println(typeof(b), b);
b = int64(a); println(typeof(b), b);
b = uint32(a); println(typeof(b), b);
b = uint64(a); println(typeof(b), b);
b = real(a); println(typeof(b), b);
b = boolean(a); println(typeof(b), b);

Can you also show screenshot of interfaces for tower's main router? Does it see APs as peer nodes?

As for "route from" NetXMS server - it shows 10.240.8.1 as the next hop, but looks like there's no corresponding node in NetXMS, that's why it can not continue.

Quote from: Akira on September 23, 2024, 08:42:35 AMТут явно что-то не так, как минимум с кавычками. Парсер в таком виде дает сразу ошибку

да, апостроф со скобочкой не в том порядке были

Great, thanks for the update

Created https://track.radensolutions.com/issue/NX-2596 for this

Yes, correct. It's a container, but with data collection capabilities. 
A typical use would be some script DCIs that walk through child nodes to get some summary values, or Web Services. But you can also use "Source node override" on a DCI and collect by agent/snmp/etc from any other node.

Does it happen with some remote agent, or also with agent that runs along with the server?

For now the reason is not clear. Can you enable DebugLevel 8 on the server and that agent and share their logs?

Any chances we can remote access to this Windows system?

The crash collector service seems to be running fine, so seems that server is nor really crashing.

Can you stop netxms core service and run it from command line:

C:\NetXMS\bin\netxmsd -D 6

and once the issue occurs, pls share the screenshot of whole cmd window.

NetXMS has automatic event correlation based on topology. For this to work, NetXMS server should have snmp access to all routers between itself and your APs, then it would have full topology picture.

You can check by right-clicking on an AP, Route from... and choosing NetXMS server node. The other way to check is probably an automatic L3 network map.

I might be wrong about peculiarities of how all this works, would be good to hear if this works on your system.

Note that there are two options:

NetworkService.Status(smtp://domain.org:port)
NetworkService.Status(smtps://domain.org:port)

Try specifying port in the metric, e.g. NetworkService.Status(smtps://domain.org:465), make sure you can connect to that port using telnet from your netxms server's command line, e.g.:

telnet domain.org 465

Log file in C:\NetXMS\crash ?
Pls share it

Looks like DumpDirectory should be specified for dump collection to work. Pls create C:\NetXMS\crash
 folder and try the following in netxmsd.conf:

CreateCrashDumps=yes
DumpDirectory=C:\NetXMS\crash

Well, could be that something related to crash dumps is broken.

As additional check, can you stop NetXMS Core service and run server manually from Windows command line:

c:\NetXMS\bin\netxmsd -D 6

pls show last line of output, when it crashes.