NetXMS Support Forum

Hi,

it will be included in 1.2.15 (just implemented).

Best regards,
Victor

А как собирается информация об интерфейсах - через агента или по SNMP?

сделал задержку 300 мс в фильтре - будет в релизе 1.2.15.

Hi,

your script has syntax error (in FindSituation call), and there is a bug in 1.2.14 (already fixed for 1.2.15) that may cause server to crash when compiling script with syntax error. Try to fix the script like this:


   s = FindSituation("NodeDown", $node->name);


Best regards,
Victor

Hi,

change already done, so it will be part of 1.2.15 release.

Best regards,
Victor

Hi,

unfortunately console access is not enough. I need SNMP access to see switch responses and to test the driver.

Best regards,
Victor

Здесь может быть несколько вариантов, один из них такой:

1. По событию SYS_NODE_DOWN выставляем custom attribute у ноды в текущее время, например так:


SetCustomAttribute($node, "nodeDownSince", time());


2. По событию SYS_NODE_UP сбрасываем значение атрибута:


SetCustomAttribute($node, "nodeDownSince", 0);


3. Делаем Internal DCI с параметром Dummy и таким transformation скриптом:


t = nodeDownSince@$node;
return ((t != null) && (т != 0)) ? ((time() - t) / 86400) : 0;


Значением DCI будет количество дней с момента SYS_NODE_DOWN. Затем можно поставить threshold как обычно на нужное количество дней.

No, it's a bit different - I was thinking that you are talking about built-in syslog server. Anyway, it is possible to add an option to discard data push for unmanaged nodes.

Best regards,
Victor

Hi,

did you get right package? We have both wheezy and squeeze - web site points to wheezy packages.

Best regards,
Victor

Hi!

Most likely you will need Solaris agent, but for x86 architecture (Solaris 10 agent binaries on our site is for Sparc, and Solaris 11 for x86). I'll check what happens with Solaris 11 agent download - it should be what you need.

Best regards,
Victor

Hi,

this message format dows not conform neither to BSD syslog format (RFC 3164) nor RFC 5424. The main problem is that 2014 as host name is a valid IP address (it's not widely known nor used, but it is valid to write IP addresses not only as n.n.n.n, but also as n, n.n, and n.n.n) so it resolves to 0.0.7.222, which of course is not found. I change node binding logic so that if server cannot find node by hostname/IP address provided in syslog message itself it still try source IP address of the message. This should solve your problem.

Best regards,
Victor

Hi,

if you see threshold triggered, that mean that event was generated. Most likely problem is in event processing policy. Double check the rule that is supposed to show alarm from threshold violation event.

Best regards,
Victor

I hope to made it available in a week or so.

Best regards,
Victor

It could be. Can you provide full syslog packet dump (with original text)? Probably I can tweak syslog parser so it will understand Zyxel variant correctly (we already done that for Cisco for example).

Best regards,
Victor

Hi!

Bug with repeated threshold violation events was fixed in 1.2.14. I had to read our own change log first

Issue 564 is relatively easy to implement, I think I can made it before 1.2.15 release. 563 is more complicated, and most likely it will not be before 1.2.16 release.

Best regards,
Victor