NetXMS Support Forum

Какой NetXMS клиент используется - десктопный или веб?
И как происходит подключение - через TCP Proxy на netxms агенте или напрямую с сервера?

App has been published:
https://play.google.com/store/apps/details?id=org.netxms.android&hl=en

Let's double-check with script to be sure. Pls run this on "Entire network" object:

for (c : $object.children) {
  if (classof(c) == "Subnet")
    println(f"{c.name}: {c.ipAddr}/{c.ipNetMask}");
  else
    for (c2 : c.children) {
      println(f"{c2.name}: {c2.ipAddr}/{c2.ipNetMask}");

    }
}

it will print name of subnet and actual IP/mask (which can differ from subnet name)

Tokens generated from Management Console are intended for different things - currently I think only for publishing network maps.
So yes, current way it to get temporarily session id.

UPD: actually permanent tokens are supported in the new API - the one that is server module and is currently under development. But not in the old one.

File uploads are kept under Configuration -> Scheduled tasks. In the menu (three-dot button on the toolbar) you need to enable "Show system tasks".

Please check if you have subnet 0.0.0.0/0 under Entire Network. If it's not visible there, you pls login using the system user.

If it's there, pls delete it (make sure that nodes under are also present under other subnets or containers, otherwise they'll get deleted).

I've moved your post to a separate thread, most probably it's something different.

Can you show your EPP configuration for SYS_NODE_DOWN and UP events with these blocking timer keys?

Hi,

Sorry, you post got a bit lost.

Current version is 5.2.3, I don't think there were any changes related to this, but anyways, pls upgrade to is to that we are on the same page.

Then, when you observer such situation, pls check Event log for a node that had SYS_NODE_UNREACHABLE event. Check Root ID column for this ID, is it 0 or not? If not, pls find event with that ID. Pls show screenshots

What do you have in Index column in Interfaces tab on the node? Is the index the same or it gets changed? We use the index to identify interfaces on the system, so if a an interface appears with a new index we think that it's a new interface. 

There's a global setting for default expected state - Objects.Interfaces.DefaultExpectedState
Or it can be changed from script - e.g. in configuration poll hook script or interface creation hook script. 

Hi,

Thanks for the feedback (you can also put a star on our github repo )

Yes, right, unsupported, hidden or disabled DCIs may be not shown according to View options. 
The other thing is instance discovery prototypes - they are hidden in view mode, but are visible in Edit mode (pen icon on the toolbar). What settings do you have on Instance Discovery page of the DCI? Pls share screenshot of General and Instance Discovery pages. 

But I am not sure if we have syntax to specify something in brackets after web service name (or was it mentioned somewhere?)

ExternalMetricProvider по идее должен быть нормальным способом запускать что-то периодически. У него тоже есть какой-то таймаут после которого он убивает запущенный процесс, 30 секунд кажется. 

Связь с агентом - по умолчанию агент может поддерживать 32 соединения, можно поднять параметром MaxSessions

Лог агента на 6 или 7 уровне должен подробнее рассказать что происходит в обоих случаях

Have not heard about some existing integration, so you'd need to develop something yourself. Main thing is what exactly you want to synchronize.

From NetXMS side you can talk to NetBox's REST API using NXSL and web services.
Also NetBox supports Webhooks, so may be it can talk to NetXMS REST API

Does this behavior (deletion of interface) happen during scheduled configuration poll, manually called configuration poll or manually called Full configuration poll?

Some improvements were made in transferring SMTP params to the reporting server - that will be in next patch release. But this should not affect your system, as parameters that you have in your configuration were transferred before these improvements.

Can you share your reporting server log for the moment when it should send the email.
If you are on Linux, this command should show it:
journalctl -u nxreportd

For TSDB data is stored in the following tables - number in the name is the retention period

IDATA_SC_7
IDATA_SC_30
IDATA_SC_90
IDATA_SC_180
IDATA_SC_OTHER
IDATA_SC_DEFAULT

If you DCI retention time is "Default", then IDATA_SC_DEFAULT table will be used.
IDATA_SC_OTHER stores DCIs with duration longer the 180 days.

You can check size of these tables (and also TDATA_SC_* for table DCIs) in your database