NetXMS Support Forum

Not sure how timeout could be set from nxshell side.

From server side:
- try checking number of connected sessions - show sessions in server console or using nxadm. Are there stuck sessions from previous nxshell connections?

- try checking with netstat if there are hanging sockets to port 4701


What is the version of netxms?

DebugLevel=6 в конфиг агента и его перезапустить.
Ну и LogFile=C:\NetXMS\log\nxagentd удобнее поставить вместо сислога, который по умолчанию.

(а на сервере можно на лету менять - команда debug в server console)

А что в логе агента при этом на 6 уровне дебага?

DCI matching is performed by parameter, so the parameter of your DCI should be "LOCAL_TEST".

Try setting debug level for the agent and server to 6, in there anything in the logs when you execute nxapush?

Chances are that you are missing EnableWebServiceProxy=yes in config file of the agent (web services are collected via the agent that runs on the machine where the server runs, or via proxies if zoning is used).
Also make sure that "Use text parsing..." checkbox is not set.

You can use nxwsget utility to test, e.g.
nxwsget 127.0.0.1 http://api.open-notify.org/astros.json number

Ah, and there's probably the reason - json parser currently does not support arrays (the company that ordered web service functionality did not need this so it was not implemented).
This means that you can request e.g. /cellulareRssi/unit and it should return dBm, but parts in [] are not available for parsing.

Там сейчас как-то криво, на закладке Performace tab раскрывается вроде бы только {instance}, но раскрывается в то, во что обычно раскрывается {instance-name}

В 4.0 в этом планируется навести порядок.

Ага, ну нет, это не тот способ бороться с утечкой дескрипторов. Агент поставлен из пакетов, так? Попробуйте core dump файл собрать при креше.

This could be, if there's no nxagent-3.8.166-x64.exe file in the folder where nxagent-3.8.166-x64.npi resides.

The principle of operation is that console opens the .npi file and it had .exe file specified inside (.npi is simple test file, you can open it with any editor.

Only desktop console can upload packages using .npi file - in web we can not open arbitrary files from the computer where console is open - console would need this to open the .exe that is specified inside .npi.
There are plans for the future to change package format so that everything is packed into one file - in this case web console will also work.

Do they have same settings in properties of these nodes -> Communications -> SNMP?

In View -> Object Details in Capabilities column is isSNMP flag in "Yes" state? If it's not, try running Configuration poll (full).

If no avail from the above, please share Object Details window screenshot and output of Configuration Poll.

Попробуйте версию 3.8.226, какие-то исправления на тему дескрипторов там были.

Если не поможет - что еще делает этот агент? Есть ли какие-нибудь external parameters?

Какого-то удобного способа отображения нет. Можно сделать второй DCI, Origin Internal, в поле parameter "Dummy" и в трансформационном скрипте

offset = 60*60*24;
window = 120;

values = GetDCIValues($node, FindDCIByName($node, "DCI_PARAM"), time() - offset - window, time() - offset);
if (values->size > 0) {
  return values[0];
}
else
{
  abort;
}

Трансформационный скрипт будет искать DCI имеющий параметр DCI_PARAM, искать по нему значения собранные в интервале 24 часа 2 минуты назад - 24 часа назад и брать из этих значений последнее. Если оригинальный DCI собиратеся реже, чем раз в минуту, нужно увеличить window.

Ну и дальше по этим двум DCI строить график.

Попробуйте, плс, 3.8.226, вроде бы недавно были какие-то оптимизации с картами.
Что с загрузкой CPU на машине, где запущена консоль?

2. на этот счет есть план какое-то время сохранять недоступные узлы на карте. Создал issue чтоб разработчики не забыли: https://track.radensolutions.com/issue/NX-2030

It's being read by SNMP. No additional configuration should be necessary, if it can get something from a device via SNMP, it should be able to get topology data.
There is a separate type of polling called Topology poll. You can try briefly setting debug level to 6 on the sever and running topology poll for a node - in the log you should see what exactly it's reading from the device.

Hi!

Here's an example of such script:
global emails = "";

sub parseGroupsOrUsers(arr)
{
  for (i : arr)
  {
    if (i->isGroup)
    {
      parseGroupsOrUsers(i->members);
    }
    else
    {
      if (i->email != "")
      {
        if (emails != "") emails = emails . "; ";
        emails = emails . i->email;
      }
    }
  }
}

parseGroupsOrUsers($node -> responsibleUsers);
println(emails);

In NetXMS users groups can contain not only users, but also user groups, hence the script is recursive.

Here's a not-yet-documented way to print all attributes and values of responsible users/gropus:
for (r : $node->responsibleUsers)
{
  for(a : r->__class->attributes)
     println(a . " = " . r->__get(a));
  println;
}

The intended behavior of NetXMS is the following:
- on each configuration poll we are checking, if we can comminicate with the same community string, as before
- if we can not, then search sequence is started - first using snmp v3, then with v2c and 1 we try the community strings listen in Network credentials.
- If working snmp community is found, it's updated into properties of the node.

So it should be able to restore communication if community name is changed on the device.
Check if "Prevent automatic SNMP configuration changes" is not set in node properties.
Share output of configuration poll after community name change on a node.