NetXMS Support Forum

https://www.netxms.org/forum/general-support/netxms-video-tutorial-series/

As I said before, use auto-bind script on the template.

What you want is already possible, just use the script that I gave you a few posts ago.

It will bind the nodes under the folder to the template during a configuration poll.

This is already entirely possible.

Simply use auto-bind scripts...
Here is an example:

parents = GetNodeParents($node);

foreach(p : parents) {
  // if the node has a parent with this name
  if (p->name == "Something") {
    // auto-bind node
    return true;
  }
}

// otherwise do not auto-bind the node
return false;


I know this is not exactly what you are looking for, but check out Pushover.
Its a message push service, has clients for iPhone, Android, etc...

Its cheaper then sending SMS, we actually use it for everything now.
Integration with NetXMS is under 5 minutes as well.

As for the actual SMS service, cant help there, sry

Definitely a bug
I registered it as #817 on bug-tracker.

As to why no correlation for other events - Victor will have to answer that.

This assumes node has atleast snmp v2c+ and support IfXTable!
This also assumes you are running atleast 2.0-M3!

Create a new DCI

In general tab

Description - Traffic on {instance-name} - bits/s IN
Parameter - .1.3.6.1.2.1.31.1.1.1.6.{instance}
Origin - SNMP
Data Type - Unsigned 64bit Int.

In Transformation tab

Delta calc
Avg delta per second

Transform script:
return $1 * 8;


Instance discovery tab

Instance discovery method
SNMP Walk - OIDs

Base OID
.1.3.6.1.2.1.31.1.1.1.1


Performance Tab tab

Check to show on perf tab
Give it a title, color, etc.


Then create a 2nd DCI for traffic OUT on that interface.
Use .1.3.6.1.2.1.31.1.1.1.10.{instance}

Also on Perf Tab, attach it to the previous DCI.
This is so you get both IN/OUT traffic for each interface on the same graph.

Quote from: Dani@M3T on April 30, 2015, 01:17:25 PM
Thanks Victor. I see in all test cases the same root event ID. In the DB I saw it is a "SYS_NETWORK_CONN_LOST" event (Event Code 50) several days ago.
I don't understand why this very old event is relevant in the event correlation. Of course the NetXMS server has network connection.

It seems you have Beacon Probing enabled, and your NetXMS server see Beacon Probe hosts as down.

Check your server config variables regarding Beacon Probing.

1) Since 2.0-M2, you can also see aliases in the "Interfaces" tab, without needing to modify any Server Config Variables.
Or you can use the solution in the previous post.

2) Currently not

3) Yes, use an Instance Discovery DCI, then you can attach graphs to the performance tab automatically
You can use filtering to only create certain DCIs/graphs, etc.

Come and visit us in the support IRC channel, it will be much faster to get this resolved

Create your own event for your SNMP trap.
In that event %2 and %3 will be accessible for the parameters you map from your Trap.

Dont use the default SNMP_UNMATCHED_TRAP event.

Then create your own EPP to catch that event.
You can test and just see if you catch it properly without filtering for FAIL/SUCCESS.

Then when you have that working, you can start playing with the scripting.

Do it step-by-step, dont do everything at once, because you then dont know what isnt working.

As I mentioned, create 2 Event Processing policies.

1st will catch the event with 'Fail' in Event message; and create a critical alarm on the node and send the email.
2nd will catch the event with 'Success' in Event message; terminate/resolve the previous alarm, and also send email.

Awesome, see you there

Here is how I would do it:

1) Create SNMP Trap with trap OID .1.3.6.1.4.1.31023.1.1.1.0.1
    From the trap, pass parameter from the OID .1.3.6.1.4.1.31023.1.1.103

2) Create event for the SNMP trap. In event, you will get that parameter as %2
    You can use %2 to interpret job completion in the event message.

3) Create 2x Event processing policy for this event (one for fail, one for success)
    In filtering script filter for the fail or success from event message.

You can either set it globally in Server Configuration Variables under "PollCountForStatusChange" (requires server restart).

Or you can set it per-interface.

Can the old repo at https://www.netxms.org/apt/ please be redirected to http://packages.netxms.org/debian/ as well?
To keep backwards compatibility with people who already have their apt sources configured to the old one.

Of course, they will still have to add the gpg key, but atleast they will know something is happening by an error from "apt-get update".

Thanks!