NetXMS Support Forum

Hello!

You have to configure UPS subagent. Add to agent's configuration file the following:

in main section:

SubAgent = ups.nsm


at the end of file:

*UPS
Device = 1:"COM1:":APC

Replace COM1 with actual port name. If your have UPS other than APC, change communication protocol to BCMXCP or MICRODOWELL, depending on what your UPS supports. Restart agent.

After that, you'll be able to collect information about UPS. All parameters require device id, which is set to 1 in our example.

Best regards,
Victor

Hi!

First, you have to specify your requirement in more details. How status of your application can be monitored? Do you have a script or command line tool which returns current status of your application?

Best regards,
Victor

Hello!

I've fixed this problem in next release. For building 0.2.31, replace line 339 in file net.cpp (it should looks like


if (rti_info[RTAX_DST] != NULL && !(rtm->rtm_flags & RTF_WASCLONED))


) with


if (rti_info[RTAX_DST] != NULL)


Best regards,
Victor

You can download it at https://www.netxms.org/download/dev/scilexer.lib.

Best regards,
Victor

I check my setup - i have two different scilexer.lib for some reasons. One of them contains these functions (and looks like static library), other are not (and looks like import library for scilexer.dll). Check what scilexer.lib you are linking.

Best regards,
Victor

Hi!

Snapshots does not contain configure script - it is created as part of distribution preparation. In the root of NetXMS source tree there are script called reconf which will create configure - but you must have autoconf, automake, and libtool installed.

Best regards,
Victor

Hi!

What version of Scintilla library you are using? Class PropSet defined in PropSet.h from Scintilla library. I use version 1.67, which probably outdated - may be this is the problem.

Best regards,
Victor

A kakoj u faila pravil'nij timestamp? Ne zabivajte, chto eti parametri vozvraschajut UNIX timestamp, t.e. kolichestvo sekund s 1 Jan 1970 00:00:00 UTC. Esli nado perevesti v drugoj format, to eto mozno sdelat' cherez transformation script dlja DCI.

Currently we don't have blackberry device for testing, and I have no idea how hard development for blackberry could be. It's not very popular in my country, so I just forgot to include it in the list. However, I'll add blackberry to the list to see how big is demand for blackberry client.

Best regards,
Victor

Hi!

You need flex version 2.5.33 or above.Looks like GnuWin32 still uses 2.5.4. I personally use flex and bison (and other tools like grep, etc.) from MSYS (http://www.mingw.org/).

Best regards,
Victor

Hello!

Looks like double quotes are missing somewhere, and because bison is installed into C:\Program Files\... it breaks on a space in a path. Try to install GnuWin32 tools into directory without spaces in the path.

Best regards,
Victor

Quote from: wonderboy on January 15, 2010, 03:04:02 PM
Спасибо за помощь, но сразу возник еще один вопрос.

Так как на разном оборудовании разные порты могут быть серверными, транковыми и т.д.
Решил в дескрипшенах писать что-то типа Trunk ... , User ... , Server ...
И иметь всего 3 правила на все устройства.

Пишу в политике для эвента SYS_IF_DOWN скрипт ($2 - содержит имя интерфейса в указанном выше формате):

Code Select Expand

sub main() {
if ($2 ~= "Trunk")
{
  return 1;
}
}

Но вот видимо не срабатывает, потому что алярмы свой приоритет не меняют.

PS: Stdout куда выводятся print, println это где? Куда нужно смотреть?

Скрипт выглядит правильно. Stdout доступен только если скрипт запущен через nxscript. Приведенный выше скрипт можно протестировать например так:

1. создать файл test.nxsl, скопировать в него скрипт;
2. запустить команду

nxscript -r test.nxsl param1 param2


Результат будет примерно такой:


C:\Source\NetXMS\debug>nxscript -r test6.nxsl param1 param2
NetXMS Scripting Host  Version 1.1.0-rc10
Copyright (c) 2005-2009 Victor Kirhenshtein

Result = (null)

C:\Source\NetXMS\debug>

C:\Source\NetXMS\debug>nxscript -r test6.nxsl param1 Trunk
NetXMS Scripting Host  Version 1.1.0-rc10
Copyright (c) 2005-2009 Victor Kirhenshtein

Result = 1

C:\Source\NetXMS\debug>


Если в скрипте для отладки нужна печать на экран, то можно использовать print / println:


sub main()
{
   println "$2='" . $2 . "'";
   if ($2 ~= "Trunk")
   {
      println "match";
      return 1;
   }
   println "no match";
}


Получим


C:\Source\NetXMS\debug>nxscript -r test6.nxsl param1 param2
NetXMS Scripting Host  Version 1.1.0-rc10
Copyright (c) 2005-2009 Victor Kirhenshtein

$2='param2'
no match
Result = (null)

C:\Source\NetXMS\debug>

C:\Source\NetXMS\debug>nxscript -r test6.nxsl param1 Trunk
NetXMS Scripting Host  Version 1.1.0-rc10
Copyright (c) 2005-2009 Victor Kirhenshtein

$2='Trunk'
match
Result = 1

C:\Source\NetXMS\debug>


В заголовке окна видна пометка "modified". Event processing policy вступает в силу только после того, как она сохранена на сервере. Эти тестовые изменения были сохранены?

Hello!

Not directly from console. However, you can upload any file to agent via nxupload command line tool (should be run from server). All uploaded files will be placed in agent's upload directory, defined by FileStore parameter in agent's configuration file.
You can also create fake upgrade package which will just deliver required file and distribute it via agent upgrade mechanism from console.

Best regards,
Victor

Привет!

В нынешней версии это сделать не получится. Я добавил NXSL функцию GetInterfaceName, в следующей версии она будет доступна. Тогда можно будет подставлять имя интерфейса через скрипт, например так:

1. Сделать скрипт в Script Library под названием resolve_if_name


sub main()
{
   return GetInterfaceName($node, $event->parameters[2]);
}


2. В текст сообщения добавить вызов скрипта:


Link is down (interface name %[resolve_if_name])


Best regards,
Victor