NetXMS Support Forum

В серверных командах можно использовать серверные макросы, как в событиях или алармах. Для передачи IP адреса надо использовать %a, например

/usr/local/bin/nxsnmpset -c private -t INTEGER %a .1.3.6.1.4.1.259.6.10.94.1.7.3.0 3

С динамическими адресами пока довольно плохо. Можно делать discovery и искать вновь появившиеся адреса, но это не совсем то.

По поводу NAT - сервер подключается к агентам, поэтому один прокси на сеть скорее всего понадобится.

Hi!

Unfortunately it's not possible. You can only expand macros in template items, and only at the moment when you apply template to node.

Best regards,
Victor

Dobrij den'!

Sborok pod Ubuntu poka net, k sozaleniju. V attache sobrannij na Ubuntu Server 10.10 MySQL driver dlja NetXMS. Dostatochno ego prosto polozit' v /usr/lib i postavit' package netxms-server - po idee dolzno rabotat'.

Добрый день!

Распределение примерно такое:

0 = дебаг выключен
1 = дополнительные сообщения при инициализации и остановке сервера
2 = + больше сообщений при инициализации, некоторые внутренние ошибки
3 = + дебаг авторизации пользователей, исполнения команд
4 = + дебаг network discovery и ISC
5 = + дебаг событий, поллеров, push параметров, дополнительный дебаг ISC и network discovery
6 = + дебаг клиентских сессий, дополнительный дебаг поллеров и network discovery
7 = + дополнительный дебаг поллеров и сбора данных
8 = + дополнительный дебаг сбора данных
9 = + все SQL запросы

Общая идея примерно такая - до уровня 5-6 дебаг можно держать включенным постоянно (хотя сильно зависит от количества узлов). Начиная с 7 уровня дебаг очень подробный, туда пишутся записи о повторяющихся каждые несколько секунд операциях - соответственно и растет он очень быстро. Я обычно использую уровень 5 или 6 при отладке - 7 и выше нужны обычно при поиске дедлоков.

В отдельный лог писать нельзя, давно хочу это сделать, но никак не доберусь.

Hi!

Scripting slowly moves to more and more areas of NetXMS I agree that creating and binding objects from scripts is a very good idea. I'm not sure, however, that auto bind script is the best place to create additional objects. For network discovery purposes, additional hook will be better. For example, it can be done that way that for each newly added node system executes some script from library. Or take more generic approach, and allow script execution as action in event processing policy - that way you will be able to execute your script on each SYS_NODE_ADDED event, as well as do many other things for other events.

Best regards,
Victor

Hi!

For syslog-based events to be generated, host which is source of the event must be registered as node in NetXMS. Also, I suppose you just omit <parser> tag from posted config - <rules> must be wrapped in it.

Best regards,
Victor

Ошибка в названии счетчика - должно быть

Counter = Active Remote Delivery Queue Length:"\MSExchangeTransport Queues(_total)\Active Remote Delivery Queue Length":60:A:INT:SMTP Active Remote Delivery Queue Length

MSExcahngeTransport  ->  MSExchangeTransport

Я сам это заметил только минут через 10 экспериментов

Hi!

jsut check it on my machine, and it looks like cscript suppresses output of WScript.Echo in batch mode, so agent cannot get the result. Changing

ExternalParameter = MyParameter:c:\windows\system32\cscript.exe //B //Nologo "c:\MyScript\myscript.vbs"

to

ExternalParameter = MyParameter:c:\windows\system32\cscript.exe //Nologo "c:\MyScript\myscript.vbs"

gives correct result for MyParameter.

Best regards,
Victor

Yes, or any value less than that - you can set it to 1 second for example. On each DCI poll if repeat event is set, server checks if time passed from previous event is longer than given interval, and if yes, generates new event. So, setting this to any value less than poll interval will cause new event to be generated at each poll.

Best regards,
Victor

Hi!

By default, new event is fired only once, when threshold's condition comes from false to true. If you wish to fire event on each check, you should turn on "repeat event" and set repeat interval less or equal to polling interval.

Best regards,
Victor

Hi all!

NetXMS version 1.0.10 is released. It's a bugfix version which should fix most of the network discovery problems in 1.0.9 along with few other issues. Changes from previous release:

- Network discovery improved
- Added VRRP support
- Added new object tools type: server command
- New MIBs added: VRRP-MIB
- Fixed issues: #320, #321, #322

Best regards,
Victor

Hi!

Currently you cannot execute tool on an alarm - you can call object tool, but server will not pass alarm's data to it. It's a good idea to have an "alarm tools" as well - I'll add this as feature request. It should be relatively easy to implement based on object tools - just add few more macros.

Best regards,
Victor

Hi!

Question about debian packages to experts: currently, my postrm script looks like following:


#!/bin/sh

if test "x$1" = "xpurge"; then
        rm -f /etc/nxagentd.conf
        rm -f /etc/nxagentd.conf.backup
        rm -f /etc/nxagentd.conf.sample
fi


It supposed to remove configuration files only when package uninstalled completely. However, during upgrade configuration files also got removed. What I am doing wrong?

Best regards,
Victor

Hi!

That's very strange, because German characters should be supported even by latin1 (ISO 8859-1) encoding. On what platform you are running NetXMS server and what database you are using?

Best regards,
Victor