NetXMS Support Forum

У пользователя нет доступа к обьекту карты. Добавьте доступ (правая кнопка мыши на обьекте, закладка Access Control).

Пока никак. Можно будет добавить такую опцию на карты.

SNMP walk is an actual SNMP request which returns actual data. You cannot send request to template as it is just a configuration element.

Best regards,
Victor

Hi!

I would suggest a reboot for whole system if possible. Error message is from DB itself, not from NetXMS - so it's not that lock.

Best regards,
Victor

Yes, it is possible that node down event comes after DCI threshold violation events. The reason is that data collection is not synchronized with status polls - so when node went down there is no guarantee that status poll will detect it first - so you can get some of the DCI events before SYS_NODE_DOWN. One of the possible solutions is to change number of polls required to trigger thresholds - if you set it to 2 (assuming data collection interval is the same as status polling interval) you will already have SYS_NODE_DOWN received when threshold generates event. Drawback of course is that you'll get service down notification one poll interval later.

Best regards,
Victor

This message could popup if you try to call SNMP walk on non-node object (for example, template or cluster).

Best regards,
Victor

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