NetXMS Support Forum

Ну да. Loopback не считается валидным адресом, поскольку в нормальной ситуации это ошибка кроме как для самого сервера. А такой случай мы не обрабатываем отдельно.

I think it will be easyer for you to use NXShell script for this purposes. Examles cn be found there: https://wiki.netxms.org/wiki/Using_nxshell_to_automate_bulk_operations

You can create dummy DCI or script DCI, that will take last value of the DCI and transform it to 0 in case of error.

Подключение к ноде идёт через primary host name (это IP аддресс или Hostname). Оно видно в properties объекта во вкладке Communications.

Should work in next release: 2.2.3

I mean status of interface objects, that are under this switch (in object tree).

Yes we have found the bug. It well be fixed in one of next versions.
https://track.radensolutions.com/issue/NX-1387 - issue will be fixed in one of next releases

From what version? It looks like some upgrade procedures were not executed or failed.

Try to execute next sql queries on NetXMS DB and run server again:
CREATE TABLE policy_pstorage_actions (
rule_id integer not null,
ps_key varchar(255) not null,
value varchar(2000) null,
action integer not null,
PRIMARY KEY(rule_id,ps_key,action)


CREATE TABLE persistent_storage (
entry_key varchar(256) not null,
value varchar(2000) null,
PRIMARY KEY(entry_key))

Check that in server log there are no other sql errors.

Looks like database was somehow corrupted.
What was the steps you made before it spoted working? (Upgrade to new version?) What errors were there and what commad you used to fix them?

As not reachable you mean, that on configuration poll node shows "Node is (still) unreachable"?

Do you have errors in interfaces?

By default status is calculated based on polling results, status of underlying objects, associated alarms and status DCIs. So if there are no alarms(Node down alarma was terminated) and no errors for interfaces, then node will be in status ok.

What does the server writes in log? Try to run server in console with debug and check what messages does it write?

Right click on the node -> create -> VPN Connector (It is possible to create VPN connection only under the node)

Can you please describe in more details your network(nodes, networks, configuration). How do networks outside know which interface to use?

For now it looks like without code change it is not possible to configure. If we will know more network details we may find a quick solution. The right and long way solution is to support VRF, but it will require a lot of changes and can't be implemented quickly.

Hi,

I think you are looking for Zoning:
https://www.netxms.org/documentation/adminguide/advanced.html#zones

Quote from: kiaj on October 08, 2013, 01:10:23 PM
добрый день, с каким интервалом ( если он вообще есть ) отрабатывает Discovery Instance ? пытаюсь мониторить VPN туннели на Cisco, но из-за слишком долгого интервала пропадает смысл, есть ли возможность задавать интервал в ручную ?

Настраивается в Server Configuration Variables параметр "InstancePollingInterval".