NetXMS Support Forum

You can just do "Execute script" on your node and try the following script from there:

r = $node.executeSSHCommand("ping 8.8.8.8 repeat 3 timeout 1");
println(typeof(r));
println(r);
It will print the result of executeSSHCommand() function.

One probable issue is that ssh communication goes through the agent that runs along with the server. So this agent should have
SubAgent = ssh
in it's configuration file (make sure you restart the agent after making the changes).

To debug you can add
DebugLevel = 6
to agent configuration file - agent log should give some information the moment when you execute your script.

Hi, 

For Huawei the information might be here: https://support.huawei.com/hedex/hdx.do?docid=EDOC1100333029&id=EN-US_CONCEPT_0176370110

Can you show walk output for
1.3.6.1.4.1.2011.5.25.40.4.1.14.1

Hi, 

Quite a few things changes between these two version, one of them is that for performace reasons interfaces are synchronized only when needed. In most places this works quite transparently and they are received from the server as needed, but in object tree the search is actually a filter and finds only objects that are syncronized. 
There's a setting that changes this behavior, it's in client's properties, Objects->Full object synchronization on startup

Still not resolved, created bugtracker ticket so it won't be forgotten
https://track.radensolutions.com/issue/NX-2813

Changes were made in the code, please try v.5.2.4 

Yes, looks that there's still a bug with webapi packaging, will check with developers. 
Webui should now be available for download (but, just in case, you can use any 5.2 webui or desktop ui with 5.2.4)

New Android client uses new WEB API that is a server module. 

Quick setup guide:
- add "Module=webapi,Y" to netxmsd.conf, module listens on port 8000 by default. You can change it:
[WEBAPI]
ListenerPort=12345

Please note, it's unencrypted HTTP!
- add nginx, reproxy, traefic - or any other ssl offloading app in front of it.
- connect to the APi endpoint.

But for testing you can skip this and just use HTTP

Hi, 

A few changes were made in the code, including better logging and special handling if 0.0.0.0/0 subnet was received during network discovery. This will be included in next patch release that should be in the coming days. 

PING3 is something niche and yes, looks that it's being auto-detected incorrectly. You can put PING3 into NetworkDeviceDrivers.BlackList server configuration parameter, this will prevent the auto-detection

After the moment when system shows "request timeout message" please capture dump of netxmsd process. You can do this using Windows Task Manager, there's "Create Dump File" if you right-click the process.

You can share the dump with us using this link: https://cloud.radensolutions.com/s/SHniBXHz5PJKpeR

Pls drop a message when you've uploaded the file

Agent uses GetSecurityInfo win api function, please check information about needed access rights here:
https://learn.microsoft.com/en-us/windows/win32/api/aclapi/nf-aclapi-getsecurityinfo#remarks

Please try to run the agent under system user to see if that makes any difference

Well, that explains why the metric does not return what you expect. 

How do you run the agent - under SYSTEM user or in some other way?

Yes, I think you are right - if it's SYS_NODE_UNREACHABLE, then alarm is not created and timers are not set. 

Actually SYS_NODE_UP event has parameter at index 1 which is set to 1 if node is returning from "unreachable" state and 0 if from "down", so you can filter by that in your recovery EPP rule by the following script:

return $event.getParameter("reason") != 1;

Да, не совсем напрямую с сервера, а с агента которой на сервере (или через прокси-агента, который указан в свойствах зоны). В любом случае на агенте должен быть включен TCP Proxy.

В десктопном клиенте VNC viewer встроенный - там используется какой-то, написанный на java. Так что имплементации VNC вьювера на десктопе и в вебе разные, от этого могут быть различия.

Что не запрашивает пароль - это странно, может, конечно ему не нравится именно MS logon. А если указать логин-пароль в свойствах ноды?