NetXMS Support Forum

We don't have a concept of DCI summary table from table DCIs. 
One option is to have a number of single-value push DCIs, then in transformation script of your table DCI you can push values into these. 
Or, via the API you can call   /objects/{object-id}/execute-script endpoint and call a script that would return the data you need. 

This can be discussed with developers, but we need to understand the use case in details. 

So the idea is to keep like misc metainformation about the node? Would be nice if you can share a screenshot of what you keep there (via PM if needed). 

As a brainstorm - this can be just stored in node's comments as markup-formatted table. Or yes, to use Table DCI for that. You can have a context dashboard that automatically opens in a tab and displays contents of that table. 

Yes, tables with script source are collected on schedule. Also you can force collection by using 
forcePoll() method of DCI class (https://netxms.org/documentation/nxsl-latest/#_instance_methods_8)

Yes, in this case you'll have one script for all nodes. Buy you can call other scripts from that script. And you can pass parameters to that script (in metric field in DCI's properties)

After policies are deployed agent should be restarted, as it reads configuration on it's startup. 

Agent logs it's configuration to it's log when it starts - you can check the log. Or you can get agent's list "Agent.RunningConfig" - it will contain current configuration. 

If things feel wrong - you can put
DebugLevel = 6
to agent's config - it will collect detailed log, during configuration poll this log should contain info on what's happening with the policies. 

Also pls inform what are server and agent versions. 

Hi, 

Sorry, vacation time here so answering was delayed. 

Setting number of samples to 24 means that all 24 samples should return "true". It would trigger only if 24 consecutive data collections will return different value. So not what we need here. 

We don't have built-in thing for "no changes within given time", so we will use a bit of scripting. In the Transformation page of your DCI put the following: 

oldValue = GetDCIRawValue($node, $dci.id);

if (oldValue != $1) {
  $node.setCustomAttribute("lastChangeTime", time());
}

lastChangeTime = $node.getCustomAttribute("lastChangeTime");
if (lastChangeTime == null) lastChangeTime = 0;

return time() - lastChangeTime;
Set Data type after transformation to Integer (this is relatively new feature, if you don't have it, upgrade to 5.x).

On the General page set Units to Uptime.


This should be it. Now how it works - in the transformation script we compare new value to the previous raw walue. If they differ we save timestamp into custom attribute on the node. And we subtract value of this custom attribute from current time - so result of the DCI is time in seconds since last change of the value. You can just set a treshold > 86400 and it should work.

Agent configuration from policy does not change main agent configuration file - one of the reasons is that it could be write-protected.
So instead policy files are stored in what's called data directory - this is set by DataDirectory parameter in main agent config, by default it's /var/lib/netxms on Linux and C:\Windows\System32\ config\systemprofile\AppData\Local\nxagentd on Windows. Specifically agent configuration policies are under config_ap folder there.

Agent is only needed for tools that talk to agent, like "Restart agent", "Restart system", ...

For HTTP/HTTPS agent is not needed. I've just tried on my 5.2.4 and HTTP object tool works, both in Deskton and Web UI. 
Make sure you've specified correct Object when adding an object tool. 
For desktop client pls check client log file, it's in user's home folder /.nxmc4/nxmc.log - may be some errors appear there after you click on that dashboard element. 

There's UI drawback that tables show same list of Origins as single-value DCIs, but in reality only Agent, Internal, SNMP and script sources are availble for tables. So it's not possible to push into table DCIs, but you use Script origin. 

Hi!

Drill-down seems to be an issue, created ticket for that: https://track.radensolutions.com/issue/NX-2823

For object tool - what exactly is that tool, if it's related to agent connectivity - is the agent online at that moment?

(56: response reading failed (errno: 0)) - this means that we did not get some response from the mail server that we expected. "we" is actually libcurl that is used in NetXMS to work with SMTP. 
Since you use TLSMode=NONE which means that communication is unencrypted, you can install Wireshark and check what exactly communication is happening with the server. But it could be that server expects TLS, you can try other settings of TLSMode (and port)

Do you use the new client, not legacy one?

In new client's properties (button in upper right corner) there's Themes page, you can try selecting Light or Dark theme there. 

What exactly flavor/version of Ubuntu and what is the name of OS theme that they use?

In the UI-AF60-MIB.txt file it's saying

      FROM SNMPv2-TC
    uiAF60, uiAF60Groups

Is there a version of SNMPv2-TC.mib file in Ubuntu downloads? 

For Extreme:
What do you have in Driver field on the Overview tab?
Pls share information from Interfaces tab in a csv file.


For Huawei - yes, this needs processing 802.1x information from a custom mib. Currently SNMP drivers do not support 802.1x part, so this needs to be added, will take some time, but will be done at some moment. Created an issue for this: https://track.radensolutions.com/issue/NX-2821

When developing Huawei driver the best would be if you could provide us remote access to a huawei device - if this is possible  id would speed up the development

Could it be possible to get remote access to your NetXMS server, or one of these Mikrotik devices? That would be beneficial for debugging this. Feel free to respond in PM. 

1) 
- можно сделать DCI summary table и его встроить в дашборд
- на контейнере есть закладка Data Collection, там можно поиском ограничить какие DCI отобразятся. Можно каким-нибудь тегом отметить интересующие DCI (это на закладке Other options в свойствах DCI) и по тегу искать. Но это, конечно, не дашборд. 
- сделать коллектор (это как контейнер, но со сбором данных) и в нем наделать скриптовых DCI которые будут находить нужные DCI на нодах под этим коллектором и собирать их значения. И уже эти DCI можно использовать в контекстном дешборде. 

2) 
Алармы на дешборде ограниченно фильтруются, только по severity и состоянию, так что какой-то отдельный аларм не получится вывести

nxsnmpwalk that Alex mentioned is a command-line tool included with NetXMS. On linux it should be available in PATH, on Windows it's in C:\NetXMS\bin