NetXMS Support Forum

Порт - в смысле интерфейс? С интерфейсами так не получится, их статус жестко определяет при статус полле - по данным с netxms агента, snmp или icmp.
Ну разве что менять expected status интерфейса на обратный текущему, но это так себе идея.

It's the same with session agent.

Hopefully one day this issue will be implemented and life will become easier: https://track.radensolutions.com/issue/NX-1961

Can you show output of status and configuration poll for this host?

You have timestamp with year 1969 - is time on your netxms server correct?
In object details - Overview on the right hand side there is a table called Capabilities? That's communication method available for particular node. What's the value of isSNMP there? If it's No, try running Full configuration poll for that node.
Are you able to get values for these OID using snmpget from command line of the sever where NetXMS is running?

Proxies should not be required, if your servers is able to communicate to these subnets directly.
Passive discovery requires that there's netxms agent or SNMP agent on the remote machines - this way we are getting neighbors from arp tables (and not sure from where exactly in case of SNMP).
For active scanning nodes should reply either ICMP, SNMP or netxms agent - if none is happening we can not discover a node.

You can try temporarily increasing netxms server debug log
nxadm -c "debug 7"
and manually launching a scan of a subnet to better understand what's happening.
Or, alternatively you can try capturing network traffic to that subnet with tcpdump, this can also give some insight.

Thanks for the follow up

Could be added at some point in the future.
Created an issue for that: https://track.radensolutions.com/issue/NX-1971

Something like that:
for(a : $object->alarms)
{
println(a->message);
}


List of alarms is an attribute of any object, not only node - it could be container, subnet, sensor... That's why I am using $object->alarms in the example, but if the object you are querying is a node, you can use $node->alarms

Documentation it's here: https://www.netxms.org/documentation/nxsl-latest/#class-netobj

В свойствах DCI на закладке Other Options есть чекбокс Use this DCI for node status calculation.
DCI про этом должно принимать такие значения 0 -Normal, 1 -Warning, 2 -Minor, 3 -Major, 4 -Critical. Это может быть или скриптовый DCI, или SNMP DCI, у которого получаемое значение преобразуется в transformation script.
Значение этого DCI будует учитываться наравне с алармами при расчете статуса ноды. Ну то есть, например, если если DCI возвращает 1 и алармов на ноде нет, то статус ноды будет Warning. А если одновременно есть аларм со статусом Major, то и статус ноды будет Major, потому что по умолчанию используется most critical алгортм рассчета.


Ну и всего этого можно добиться, посто сделав на этом SNMP DCI threshold last value == 2 и создавать событие с severity warning. Тогда будет создаваться аларм, который также будет менять статус ноды.

What is exact version of your netxms server, did you install it from packages or compile?

If you just need to add one IP address, you can just create new node in object tree under Infrastructure services.
If it's something else, please share a screenshot of what you are trying to configures.

https://www.netxms.org/documentation/adminguide/installation.html#installing-from-sources

Hi!

If I understand correctly what you a trying to achieve, instance discoverу should help. Have a look at attached screenshots. The idea is that NetXMS during instance discovery poll reals all indexes and values under .1.3.6.1.2.1.31.1.1.1.15 and creates DCIs using these indexes. It's possible to filter by OID or value.

Or you can create NXSL script that will communicate to the device via SNMP and query what you need and use that script as a method for instance discovery.

But if you open Data Collection Configuration for that switch, are these DCIs there?

Creae Interface DCI functionality is quite old. It's better to use a template with instance discovery that would get interface list somehow and create DCIs automatically.

NetXMS expects that database is created with UTF-8 charset, which should happend by default in current version of mariadb. I've just tried on my Debian 10, database got created with utf8mb4.

Try creating the database like this:
CREATE DATABASE mydatabase CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;

If you have some data in you database, you can try migrating it to the newly created DB with nxdbmgr.