NetXMS Support Forum

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

Hi!

Looks like your database is somewhat broken. Could you please run netxmsd with -D 9 option (highest debug level) for a short time and post netxmsd log to [email protected]?

Best regards,
Victor

Hello!

You cannot send SNMP traps from agent. Agent can only communicate with NetXMS server using it's own protocol. You can however send traps from NetXMS server simply by defining command type action and calling any trap sending utility, for example snmptrap from net-snmp package.

You can retrieve node's custom attributes in scripts in event processing policy in two ways:

1. If name of your attribute conforms to NXSL identifier naming conventions (contains only letters, digits, _ and $ and do not start with digit), you can access any attribute as attribute of node object. For example, to access custom attribute named attr1, you can use


$node->attr1


2. You can use NXSL function GetCustomAttribute. For example, to custom attribute named attr2, you can use


GetCustomattribute($node, "attr2")


Also, if you just need to add custom attribute's value to event or alarm message, you can use macro %{attribute_name}, for example, you can define alarm message as


Some alarm - custom attribute attr1 goes here: %{attr1}



Best regards,
Victor

Hello!

Did you set VID_PARAMETER variable before sending CMD_GET_PARAMETER request? You should have something like

msg.SetVariable(VID_PARAMETER, "Agent.Version");

before converting message into binary format and sending. Also, check VID_RCC variable in response message - may be it contains error.

Best regards,
Victor

Hello!

In fact, there are two timeouts - one on agent side, for script execution, and one on server side - for agent response to command. If you have external parameters with long execution time, you should also increase value for server's parameter AgentCommandTimeout, which is 2 seconds by default.

Best regards,
Victor

Try to replace netinfo.cpp with attached one.

Best regards,
Victor

Your database user netxms does not have access rights to database netxms. Try to grant required rights with the following MySQL query:


GRANT ALL ON netxms.* to netxms@localhost;


Best regards,
Victor

Hi!

You need Platform SDK, OpenSSL, and ZLib.  Others required only for some components:

DDK - for UPS subagent;
libgd - for nxhttpd;
DB library - for MSSQL database driver;
Scintilla - for management console;
Microsoft Speech SDK - for management console;
MySQL client - for MySQL database driver;
PostgreSQL client - for PostgreSQL database driver;
Oracle client - for Oracle database driver;

Packages not listed here are not needed for NetXMS build.

Best regards,
Victor

Probably something is wrong with headers you are using. Attached is my startup file for VC6, may be it will help. I use Platform SDK for Windows Server 2003, because many headers and libraries in VC6 distribution is outdated or missing.

Best regards,
Victor

Popravil node.cpp.

Could you please post complete error message from server's log?

Best regards,
Victor

Did you have libmysqlclient.so somewhere in the system? If yes, where?

Best regards,
Victor