NetXMS Forum

Then we'll wait for a new patch release.  Thanks for the quick support. Regards Peter

NXSL tried to interpret the HEX as string and taked first 00 as end of string. Try this way: transport = $node->createSNMPTransport(); if (transport != null) {   println transport->get(".1.3.6.1.4.1.4196.1.1.5.2.100.2.1.4.0")->printableValue; }

Hi, just added severity filter option to wineventsync subagent. Now for every reader you can specify SeverityFilter parameter, which is either bit mask  or severity level names separated by commas. Below are level names and their values: Critical = 0x100 Error = 0x001 Warning = 0x002 Information = 0x004 AuditSuccess = 0x008 AuditFailure = 0x010 To accept only warning and error events: SeverityFilter = 0x012 or SeverityFilter = Warning,Error This change will be included into next patch release. Best regards, Victor

Values in Server Configuration are   StatusPropagationAlgorithm: Unchanged   StatusCalculationAlgorithm: Most critical I'll try to describe the 'issue' in other words: The 'port down' event (minor) leads into 'port status' critical > minor ≠ critical The 'port unexpected up' event (major) leads into 'port status' critical > major ≠ critical A change within StatusPropagationAlgorithm and StatusCalculationAlgorithm won't fix it. It's a decision of development or a bug. Greetings

Many thanks for your answers. @victor said in Function GetDCIValueByDescription returns (once) an empty string: .. GetDCIValueByDescription reads last value from cache. It can happen that it was called faster then cache for queried DCI was populated (either by poll or from database). I'll think what I can do with that. .. It would be nice if the behavior could be changed. (Although a restart is a special situation ..) Best Regards.

+1