NetXMS Support Forum

This is about to happen after a few months at least.

Template Graphs will be replaced by new dashboard feature that allows to use dashboard as a template on any node.

Instead of conditions it's possible to use e.g. scripted DCIs. If conditions are somewhat valuable thing for you, please drop a message so we can discuss your use case.

А при отправке большого количества уведомлений ошибка такая же, curl_easy_perform() failed ?

It's not possible to initiate node polling for a script. However, there is an option to change polling interval for a specific node, so you can set status polling interval to e.g. 10 or even 5 seconds for the problematic node. For this, create a custom attribute on the node with name
SysConfig:Objects.StatusPollingInterval
and value for the interval in seconds. Status, configuration, discovery, icmp, tpology, routing, autobind intervals are supported to specify that way.

Will check with developers, looks like it was not built. Meanwhile you can check previous version https://www.netxms.org/download/releases/4.1/nxmc-4.1.404-aarch64.dmg

There is a special format string supported:
%*s
It should display the value using multipliers.

https://www.netxms.org/documentation/adminguide/visualisation.html#adding-links-between-objects

Format strings are used when displaying values on maps.

In last values try enabling "Use multipliers" in context menu - it should automatically display in KBits or MBits, depending how big the number is. Or you can set "enable multipliers" in properties of the DCI.

In coming 4.2. version there will be option to fix multipliers to e.g. mbits and also option to display measurement units next to the value.

System.CurrentTime returns unix time in UTC time zone.
You can use System.TimeZone to get time zone.

.eclipse is a hidden folder. Try enabling "show hidden folders" in your file explorer.


Also check /home/name/.nxmc/data/.metadata/.log   it might contain some information.

Yes, you can use snmpwalk from nxsl script, e.g.

transport = CreateSNMPTransport($node);
if (transport != null) {
    oid = ".1.2.840.10036.1.1.1.7";
    vars = SNMPWalk(transport, oid);
    if (vars != null) {
      foreach (v: vars) {
          println(v->name." = ".v->value);
      }
    }
}

Then you just need some logic how to parse the results returned by SNMPWalk

Looks like it's missing in Windows builds. I've created an issue for this, so one day developers will have a look.

Meanwhile you can put netxms agent on any linux machine and configure it as a proxy - token support should be working on Linux.

Pls see DCI configuration in the attached images. It will perform SNMP walk starting from specified OID and create DCIs for all OIDs encountered in this walk. {instance} macro will contain last part of OID, {instance-name} - value from that OID.

My Mikrotik device has two items there:
.1.3.6.1.4.1.14988.1.1.1.3.1.4.1
.1.3.6.1.4.1.14988.1.1.1.3.1.4.2
so two DCIs would been created.


The other approach is to make a script DCI, perform SNMP walk from the script and may be join results into one DCI. I can prepare example of this if needed.

Let's start from why nxdbmgr check is failing. Same as netxmsd executable does, nxdbmgr is trying to open netxmsd.conf configuration file from some predefined places, normally it's C:\netxms\etc\netxmsd.conf
If your netxms server is running, then the file should be there. Could it be that you are running cmd under regular user, not admin and there are no acess rights to the config file?

try running this in command line of your server:
telnet ip_addess 4700where ip_address is the address of your agent. 
What output would this command produce?

Hi!
mode should be either PDU or TEXT, not T. 
Notification channel is activated right after you finish editing it's configuration, there is no need to do anything else. You can watch what's happening in server log, by setting debug level for specific debug tags. In Tools -> Server console issue:

debug nc.* 6
debug ncd.* 6
After you change setting of notification channel, log file should have some messages. 

Hi!

So here's a few prerequisites for server to connect to the agent:

- agent process should be running
- no firewall should be blocking agent's port (it's TCP port 4700)
- In nxagentd.conf configuration file MasterServers parameter should include IP address of your NetXMS server