NetXMS Support Forum

Why are you generating alarms when interfaces come back up?

Normally in EPP event SYS_IF_UP should only resolve/terminate alarms that were generated by SYS_IF_DOWN, not generate new alarms.

Sorry, error in script.

I edited the original script, please try with the updated one

Yes, you can compile from the hourly snapshot of GIT repo and test with that.
The fixes were mostly to snmp in relation to agent proxying and to snmp discovery, but maybe you will see some difference.

If none of these help (so your issue is still present after testing these newest changes), we will know yours is a totally separate issue.

The develop branch is pretty stable at the moment (I run 2 medium sized installs ~150 nodes each on it atm.), but of course be advised that it is not released code and consider backups of db/server before deploying it

There has been a bunch of SNMP discovery fixes in the develop branch this weekend, any chance you can build from develop and try if issues still persist?

You can create an EPP (Event processing policy) rule to do this.

Simply create a new EPP all the way at the top.
Set "Source Objects" to appropriate node, and set "Event" to "SYS_MAC_ADDR_CHANGED".

You can then specify the interface with the following script:

if ($event->parameters[3] ~= "interface_name_reg_ex")
  return true;

return false;


In action, do "Stop event processing".

And done, these events will not generate alarms from now on.

You can change this dehaviour. Currently, NetXMS agent or SNMP agent un-responsiveness already creates an event, so you can create alarms based on those events in EPP.

In future versions, this will be the default behaviour, see ticket #963 on bugtracker for more details.

Putting a node in maintenance mode already creates an event, simply handle that event in EPP and create an alarm if you wish.

This will actually be done automatically in future versions, see bugtracker ticket #983 for more details.

Yes, please open a separate ticket for that (issue 2.)

Yes, this is currently a known limitation / issue.

See #859 on bug tracker.

Only non-inverted sources are stacked according to the ticket.
Can you please confirm that is how it behaves (seems so from your screenshots).

I have modified the script for you so you can use it directly as a bind script.

So use this as an auto-bind script on a template, and you dont need DCIs or custom attributes.
It will also solve your issue no. 1.


if (! $node->isAgent)
  return false;

table = AgentReadTable($node, "System.InstalledProducts");

colName = table->getColumnIndex("NAME");

for (currentRow = 0; currentRow < table->rowCount; currentRow++)
{
  value = table->get(currentRow, colName);

  if (value == "Microsoft Exchange Server")
    return true;
}

return false;


What version of NetXMS are you using?
What OS is the server running on?

Few things:

1) Check if your MySQL is using binary logging.
If it is and you dont need it, disable it.
2) Set lower retention period on your DCIs.
3) Set lower retention period on your Syslog and/or SNMP Traps, etc.

Currently, you must specify username/pass per device.

Sorry for the inconvenience.

You also need a newer version of the management console (client).

Yes, this feature is only available since 2.0-M3.