NetXMS Support Forum

Hi,

yes, it is ready. We had enormous load last week so I had no time for finishing downloads and so didn't make official announce.

Best regards,
Victor

Yes, it is still considered. But it is much more complicated then template graphs, so we need more time/resources for implementation.
Best regards,
Victor

Hi,

you can transform it when form event message. Instead of %1, %2, etc. for inserting trap parameters you can use macro %[script_name], and create appropriate script in script library. Whatever this script returns will be inserted. For example, if you have parameter 2 set to either 0 or 1 and you want to return true/false, you can create script like this:


switch($event->parameters[2])
{
   case 0:
      return "true";
   case 1:
      return "false";
}

return "unknown";


Best regards,
Victor

I will install it play with it. But I think we should add support for that. I've registered a feature request for that: https://track.radensolutions.com/issue/NX-1221.

Best regards,
Victor

Hi!

You can uninstall NetXMS server completely (it will left database intact), and then install it without installing bundled SQL Server client and attach to existing database.

Best regards,
Victor

Hi,

yes, we will switch to SHA256 eventually.

Best regards,
Victor

You want to get value as MAC address for table cell? And this table was retrieved by SNMP? Or you are doing direct SNMP request from the script?

Best regards,
Victor

Hi,

currently not. You can fill feature request for that.

Best regards,
Victor

You can't use them in script without node context when CheckTrustedNodes is on.

Best regards,
Victor

Hi,

we will check. You can report issues at https://track.radensolutions.com

Best regards,
Victor

Hi,

there should be no changes to it. Could you please turn on debug on agent and post log for parameter request?

Best regards,
Victor

Then NetXMS server cannot match it to correct device - there are just no enough information. You can setup syslog proxy on agent behind NAT so it will receive syslog messages from original addresses and forward to NetXMS server.

Best regards,
Victor

Hi,

it is known issue caused by incorrect handling of counter reset. It comes from the fact that NetXMS do not know if DCI is cumulative value or can change both ways. So it assumes latter and when new value less than old value you get those extra large values (not negative because for traffic counters usually used unsigned data types). We plan to fix it by introducing new DCI data types - counter 32 bit and counter 64 bit (to match SNMP types) - for them system will now that they are cumulative and handle resets correctly.

Best regards,
Victor

Hi,

if IP addresses are readable from vendor MIB on Netonix and Ubiquity AirOS devices we can add a driver for them to create management interfaces correctly.

Best regards,
Victor

Hi,

default ordering is currently hard-coded. Feel free to add feature request for that.

Best regards,
Victor