NetXMS Support Forum

Hi,

in server log (on debug level 5 or higher) there should be record like

EVENT 28 (ID: ...

for each SYS_NODE DOWN event. Has it also mark CORRELATED?

Best regards,
Victor

Hi all!

NetXMS 2.0-M4 released. This release mostly targeted to fix issui]es found in 2.0-M3, but there is also improvements in configuration export/import and few other changes. Full change log is following:

- Script export/import
- Object tools export/import
- DCI summary tables export/import
- Template hierarchy preserved during export/import
- NXSL functions and classes to work with alarms
- MEGATEC protocol support in UPS subagent
- Fixed broken WoL functionality
- Fixed broken PING subagent
- Fixed database upgrade issues on MS SQL
- IPv6 support in PING subagent
- Network device driver can be manually selected for node by setting snmp.driver custom attribute
- Added default melodies for alarms
- Added option to play sound on alarm sound preference page
- Interface objects can be used on network maps
- Android Agent:
   - Added support for Lollipop MR1 (v5.1)
   - Updated support library
- Android Console:
   - Changed order of overview items to match Java console (node browser)
   - Added MTU field in interface details (node browser)
   - Updated support library
- Fixed issues: #655, #657, #696, #701, #724, #799, #800, #803, #804, #805, #811, #812, #813

Best regards,
Victor

Скрипт может выглядеть например так:


snmp = CreateSNMPTransport($node);
if (snmp == null)
   return 0;

varbinds = SNMPWalk(snmp, ".1.3.6.1.2.1.25.3.3.1.2");
if (varbinds == null)
   return 0;
   
count = 0;
total = 0;
foreach(v : varbinds)
{
   total += v->value;
   count++;
}

return (count > 0) ? total / count : 0;


It's just made available for download.

Best regards,
Victor

Hi,

it looks perfectly fine. I re-run tests on my system, and agent picks up everything as expected. Let's try to upgrade this system to 2.0-M4 (just to make sure I'm checking latest codebase) , and if it will not help I'll create special build with additional debug.

Best regards,
Victor

см. скриншот

Hi,

I've added additional level mask 256 to match critical events.

Best regards,
Victor

Hi,

are you sure those events are generated (you can check it with event monitor or event log)? Also, SYS_NODE_UNREACHABLE may be generated instead of SYS_NODE_DOWN if server considers that there is network failure in between.

Best regards,
Victor

In version 2.0-M4 I've added ability to manually select device driver for node by setting custom attribute snmp.driver. Please check if S5500 will work correctly with HPSW driver, and if it will do, I'll update driver matching for it.

Best regards,
Victor

This script:


if ($1 =~ "[:/]") {
  value = AgentReadParameter($node, "FileSystem.Total(" . $1 . ")")
  return (value > 5*1024*1024*1024 && value < 1*1024*1024*1024*1024);
}
return false;


has few typos - match operation is ~= and semicolon is missing in line 2. It should be


if ($1 ~= "[:/]") {
  value = AgentReadParameter($node, "FileSystem.Total(" . $1 . ")");
  return (value > 5*1024*1024*1024 && value < 1*1024*1024*1024*1024);
}
return false;


Best regards,
Victor

Hi,

you miss <event> tag in your parser - so there is nothing to send. You should create new event and your parser should look like this:

<parser trace="9">
  <file>*System</file>
  <rules>
    <rule>
      <match>(.*)</match>
      <event params="1">MY_EVENT</event>
    </rule>
  </rules>
</parser>

Best regards,
Victor

Hi,

if you do not specify config file in command line, both agent and server will look into /<install prefix>/etc and only then in /etc - so if you build with default prefix /usr/local it will check /usr/local/etc first.

Best regards,
Victor

Да, планируется. Уже даже коллектор есть

Internal DCI на ping time работает не совсем так, как агентский - если нода недоступна, то возвращается ошибка сбора данных. Можно повесить threshold на data collection error.

Еще можно пробовать увеличивать кол-во сэмплов в настройке DCI типа "performance counter".