NetXMS Support Forum

Thanks for reporting, I'll fix it.

Best regards,
Victor

Hello!

libnxsnmp.so is not a subagent - it's just our SNMP client implementation used internally by NetXMS server and SNMP-related command line tools (nxsnmpget, nxsnmpset, and nxsnmpwalk). Names of subagent modules always starts with libnsm_.

Best regards,
Victor

Hello!

In this topic (https://www.netxms.org/forum/index.php/topic,485.0.html) you can find description how NetXMS stores collected data in database - probably it should be enough for report generation. If you will need additional information, just to ask me.

Best regards,
Victor

Hello!

You can achieve notification escalation in various ways:

1. If you monitor some DCI, you can define different thresholds with different events, for example one event if CPU utilization exceedes 90% for 1 minute, and other if it exceeds 90% for 10 minutes, and then process these events by sending appropriate emails.
2. You can set timeouts on alarms, and process these timeout events. So, if problem occurs, you create alarm from an event, and if nobody acknowledges this alarm within given timeout period, you get another event which you may process and send another notification (and probably create another alarm with timeout, which will trigger third level of escalation, and so on).
3. If you just need to re-send notifications all the time to same destination for DCI threshold violations, you can simply set "repeat interval" in threshold configuration.

Best regards,
Victor

Hello!

What do you mean by "consolidate SNMP traps"? NetXMS server can log all SNMP traps coming to it - is it what you need?

Best regards,
Victor

Po idee iportitsja dolzno bilo tol'ko odno znachenie - poskol'ku poschitali raznicu mezdu poslednim znacheniem, vzjatim iz 32 bita countera, i pervim 64 bita. Vse posledujuschie po idee dolzni scitatsja normal'no. Script ubirat' ne nado, on perevodit baiti v biti - v etom otnoshenii nichego ne izmenilos' - po preznemu s nodi chitajutsja baiti.

Pohoze ja razobralsja: v properties nodi kakaja versija SNMP stoit - 1 ili 2c? 64bit counteri podderzivaet tol'ko 2c - esli stoit versija 1, to kak raz takoj effekt i budet.

Sudja po snmpwalk - podderzka 64 bit counterov est'. Poproboval na dostupnom mne Cisco switche - rabotaet. Edinstvenno, posle smeni OID v DCI nado pomenjat' ego tip na Unisigned Int64. No v ljubom sluchae on ne dolzen bil perehodit' v sostojanie not supported. A mozno screenshot nastrojki DCI - mozet ja tam kakuju oshibku uvizu?

Ochen' stranno - vrode kak Cisco switchi dolzni podderzivat' ifXTable. A kakaja tochno model' i versija IOS? I chto skazet


nxsnmpwalk -c <community> <switch_address> .1.3.6.1.2.1.31.1.1.1


?

Скорее всего проблема именно в этом. 32 бита - это 4GByte максимум == 32GBit - за 60 секунд вполне может пройти больше. Можно попроьовать использовать 64 битные счетчики из ifXTable - .1.3.6.1.2.1.31.1.1.1.6.<index> для входящего траффика и .1.3.6.1.2.1.31.1.1.1.10.<index> для исходящего.

Hello!

SNMP agent is not part of NetXMS. For Linux/FreeBSD/other UNIX'es you can use net-snmp package, Windows also has it's own native SNMP agent which can be installed via Control Panel -> Add/remove programs -> Windows components.
As soon as you install SNMP agent and add NetXMS server's address to list of allowed addresses for SNMP agent, it will detect SNMP agent presence during next configuration poll.

Best regards,
Victor

Ограничений конечно-же нет
А какие используются SNMP параметры статистики интерфейса - стандартные? И какой интервал между опросами?
Проблема может быть в том, что стандартные счетчики траффика - это 32-битные значения, которые растут до максимума, а потом обнуляются. NetXMS считает траффик по формуле

(currentValue - previousValue) / secondsBetweenPolls

Если интерфейс быстрый, то счетчик может успеть обнулиться несколько раз между опросами, соответственно и результат может быть неправильный.

Hello!

I have found a bug in WMI subagent, which may be the source of your problem. Could you please try to replace wmi.nsm with attached one and test it?
It is built for 0.2.23, but should work for 0.2.22.

Best regards,
Victor

Posledovatel'nost' dejstvij takaja:

1. Sozdaem condition
2. Otkrivaem properties objekta condition, i dobavljaem interesujuschie nas DCI v zakladke Data
3. V zakladke Script pishem skript, kotorij opisivaet uslovie srabativanija - v skripte znachenija DCI budut dostupni cherez $1, $2, i t.d.
4. V zakladke General vibiraem sobitija "Activation event" - budet poslano kogda uslovie, opisivaemoe skriptom, vipolnitsja, i "Deactivation event" - kogda uslovie snova perestanet vipolnjatsja.


Server proverjaet condition'i raz v minutu, delaja status poll. Thresholdi, opredelennie dlja DCI, v condition'e ne ispol'zujutsja.


Dlja opisdannoj situacii:

v pole data dobavljaem DCI

SERV1DCI1 -> System.ServiceState(MSSQL$SQLSERVER1)
SERV1DCI1 -> System.ServiceState(MSSQL$SQLSERVER2)
SERV1DCI2 -> System.ServiceState(MSSQL$SQLSERVER1)
SERV1DCI2 -> System.ServiceState(MSSQL$SQLSERVER2)

v script pishem


(($1 == 0) && ($2 ==  0)) || (($3 == 0) && ($4 ==  0))


v kachestve activation event stavim SYS_CLUSTER_NONOPTIMAL.

Пришлите пожалуйста содержимое registry на проблемном хосте начиная с HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib
Похоже что какая-то проблема с английскими названиями performance counter'ов.