NetXMS Support Forum

.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

Yes, it's possible to call action when some event happens (from Event Processing Policy). And it's possible to run agent action from Object Tool (there it's currently called Agent Command).
Can you give more details on what you want to configure and we will go through the process.

Try putting the token into password field for Bearer authentication. Pls give us an update, if this works.

Это новый management client, он пока что в процессе разработке, публикуется чтоб люди могли посмотреть куда идет развитие. В старом nxmc есть весь функционал.

Мы добавим в следующем релизе в логе более подробную информацию, что было причиной этого curl_easy_perform()

Yes, there is json support in nxsl, there is JsonParse() which would produce JsonObject or JsonArray. Support for jsons which have array at the root level (which is the case in your example) was added just recently, it will be available in next patch release. So after that release is out you could do something like this:

s = """[
   {
      "id": 178
   },
   {
      "id": 179
   },
   {
      "id": 181
   }
]""";
       
p = JsonParse(s);
println(classof(p));       
count = 0;
for (v: p->values) {
  println(classof(v));
  count = count + v->get("id");
}
println(count);


which would produce the following:
Result:

JsonArray
JsonObject
JsonObject
JsonObject
538


*** FINISHED ***

There are two options - to send value for a single DCI or for a number of DCIs (array is used in this case);

One value:
{
      nodeId : 10,
      dciId : 20,
      value : "Value"
}


Or, alternatively node name and DCI name (parameter name) can be used:
{
      nodeName : "Node name",
      dciName : "DCI name",
      value : "Value"
}


When sending multiple values:
data :
[
   {
      nodeId : 10,
      dciId : 20,
      value : "Value"
   },
   {
      nodeName : "Node name",
      dciName : "DCI name",
      value : "Value"
   }
]

I've created an issue for this feature, you can watch the issue to see when it's done (also there's no exact plan when this could happen).
https://track.radensolutions.com/issue/NX-2294