NetXMS Support Forum

Hello!

This can be done with alarm keys. When you creating alarm from NETWORK_PRINTER_DOWN event, set key for it to something like PRINTER_DOWN_%i (%i will be expanded to node's unique identifier - complete list of possible macros can be found in user's manual). Then, create rule for opposite event, and in alarm column for it, select "Terminate alarm with given key", and enter the same key.

Best regards,
Victor

From messages:

Quote from: Rando on April 11, 2008, 02:47:38 AM
Sorry, I didn't read the last part of the message.  Yes, you can transfer this to the forum.  I'm still struggling with the scripting.  Is there any examples with descriptions I can look at to see the structure and usage?  I'm just going through the manual right now.

Quote from: Victor Kirhenshtein on April 07, 2008, 04:37:10 PM

Quote from: Rando on April 07, 2008, 09:19:18 AM
I'm still learning the NetXMS software and have a wireless base station and remote wireless radios which is SNMP capable and I do get a signal value and a noise value.  For me to calculate the signal to noise ratio I have to subtract these two numbers to create a 3rd value that I would need to track.  Is there any way NetXMS can do this?

Yes, it's possible. You should define two DCIs, one will collect signal value, and other noise value. Then, for one DCI you can create transformation script, which will access last value of other DCI and use it in transformation. You can access other DCI value using built-in functions GetDCIValue and FindDCIByName or FindDCIByDescription. See user's manual for description of these functions (section 8.5.3).
You script may looks like following (assuming that you are transforming signal value and your noise DCI called "Noise Level"):

Code Select Expand


$1 - GetDCIValue($node, FindDCIByDescription($node, "Noise Level"))


Best regards,
Victor

P.S. Can we move this discussion to the forum because this information may be useful for others?

Could you please check attached WINPERF subagent - it should fix System.Uptime and System.ThreadCount on non-english systems.

Best regards,
Victor

Quote from: xenth on April 10, 2008, 05:42:21 PM
The value returned by agent on hdd space:

System #1: Free:62.7GB     NetXMS reads out: 67G
System #2: Free:8.64GB     NetXMS reads out: 9284M

It's a console display problem, not an agent bug. Actual DCI value for free disk space is in bytes. When you use multipliers in console to view current DCI values, console uses them in common sense, i.e. K = 1000, M = 1000000, and so on, because console has no knowledge about units of DCI - is it bytes or something else. If you multiply 62.7 to 1024 * 1024 * 1024 and then divide by 1000000000 and take whole part, you'll get 67. You can also turn off multipliers and see correct number of bytes.

Thre are no straight-forward solution for this. Probably we should add additional DCI property - units, to give console a hint how to work with the values.

Best regards,
Victor

For entire network, "negate cell" will help - because entire network includes every node registered in system. So to match everything except one printer, you should add only that printer to source and then select "negate cell".
However, if you wish to match all hosts in specific subnet except some host from this subnet, it will not help. In this case, you will need to use "script" column. For example, to exclude device with ID 100, script may looks like following:


OBJECT_ID != 100


Best regards,
Victor

It's the reason for System.Uptime. I'll fix it soon. Load average can be OK, I don't know you actual load. About DiskFree - what is the value returned by agent and what is real value?

Best regards,
Victor

Main problem is to find Linux ODBC driver for MS SQL. Second is to configure unixODBC.  There are some useful links from unixODBC site:
http://www.unixodbc.org/odbcinst.html
http://www.unixodbc.org/config.html

Please note that FreeTDS mosy likely will not work because it doesn't support UNICODE ODBC interface.

Best regards,
Victor

You can select "Negate cell" option - this will mean "everything except listed in this cell". Is it what you mean?

Do you have English version of Windows or in some other language?

Hi!

We have changed UNICODE support in 0.2.20 - this should be the cause. I'll take a look at this today. Could you please post config.log here or send it to [email protected]?

Best regards,
Victor

What operating system agent is running on?

Кстати, а почему бы для пингов не использовать PING субагент? Он специально для этого предназначен...

Проблема в том, что этот скрипт долго работает. На моем компе это выглядит так:


victor@stone:~/netxms$ date && /usr/local/sbin/e1_ms.sh 10.0.0.2 && date
Thu Apr 10 10:12:18 EEST 2008
1
Thu Apr 10 10:12:22 EEST 2008
victor@stone:~/netxms$


У агента есть тайм-аут на выполнение внешних команд, по умолчанию 2 секунды. Если команда не успевает завершиться за это время, то агент возвращает ошибку. Это время можно увеличить, изменив значение параметра ExecTimeout в конфиге агента (значения в миллисекундах). Кроме того, у сервера тоже есть тайм-аут на ожидание ответа на запрос к агенту - те-же 2 секунды по умолчанию. Меняется настройкой параметра сервера AgentCommandTimeout.

Причина, по которой эти тайм-ауты по умолчанию такие маленькие - параметры с агента собираются последовательно, и если сбор какого-то параметра требует 30 секунд, то остальные параметры с данного узла в эти 30 секунд не собирабтся, соответственно может нарушится равномерность сбора данных.

Sdelal - budet v versii 0.2.21

Run nxdbmgr check and answer Y to question about unlocking database.

Best regards,
Victor