NetXMS Support Forum

PM sent.

Best regards,
Victor

Hi,

you can create VPN connector objects to match your VPN topology - then NetXMS server will know that remote network is behind VPN gateway and will correlate gateway down event properly.

Best regards,
Victor

Hi,

I suppose you are talking about server side syslog parser. Seems like a bug, I'll check.
But anyway, I don't see how invert will help you - I suppose you'll need two rules anyway: first rule will match "xyz" and stop processing, and second rule will match "abc" and do what is needed.

Best regards,
Victor

Hi,

there is installation guide, outdated, but still mostly valid: https://wiki.netxms.org/wiki/Server_Installation_Guide. Check upgrade section. If you monitor only SNMP devices, then you don't need agent packages. You'll have to download appropriate server package and upgrade server. Then you'll need new managemet console (if you are using desktop version) and/or new web UI package if you are using it.

Best regards,
Victor

Yes, it should pick correct location then. Also, you can set config file location in registry by setting: HKLM\Software\NetXMS\Agent\ConfigFile (and optionally HKLM\Software\NetXMS\Agent\ConfigIncludeDir).

Best regards,
Victor

По подтверждению - как workaround можно в текст добавить макрос %n, например:

Are you sure to execute this on node %n?

Можно любое имя выбрать для атрибута - как-то специально описывать их не надо.

Возможно стоит добавить кавычки вокруг %m?

Т.е. сводится все к тому, чтобы открыть Topology - Switch forwarding database через object tools?

Hi,

for historical reasons events generated by threshold violation and threshold rearm has parameters in different order. They are modelled by SYS_THRESHOLD_REACHED and SYS_THRESHOLD_REARMED events respectively - you can check descriptions for parameter list. Also, you can use named parameters: dciName, dciDescription, thresholdValue, currentValue, dciId, instance, isRepeatedEvent - so for example you can replace %4 with %{currentValue} in threshold violation event processing.

Best regards,
Victor

Hi,

so ultimately you only need some mark that MS SQL is running on node to be able to apply templates? Then it could be accomplished much easier using configuration poll hook:

1. Create script in script library named Hook::ConfigurationPoll like this:


if ($node->isAgent)
{
   state = AgentReadParameter($node, "System.ServiceState(mssqlserver)");
   if (state == 0)
   {
      SetCustomAttribute($node, "sqlServer", "true");
   }
}


it will set custom attribute sqlServer to true if service is running. Please note that service name might be different, I cannot remember correct name for SQL Server service.

2. To auto apply templates, use the following auto-apply filter script:


return GetCustomAttribute($node, "sqlServer") == "true";


Best regards,
Victor

Hi,

object tools of type "server command" had always expanded macros on server side, and use event processing macros (https://www.netxms.org/documentation/adminguide/event-processing.html#macros-for-event-processing). Starting with 2.0-RC1, all other object tools with macros (local command, agent action, URL) uses as close as possible macros, with the following exceptions:

%A and %m expands to alarm message when tool executed from alarm;
%c expands to source event code when tool executed from alarm;
%N expands to source event name when tool executed from alarm;
%s expands to alarm's severity when tool executed from alarm;
%S expands to alarm's severity as text when tool executed from alarm;
%U expands to user name (of currently logged in user);
%y expands to alarm state code when tool executed from alarm;
%Y expands to alarm ID when tool executed from alarm;
%(...) expands to value of appropriate input field

Macros %u, %t, %T, %M, %[...], %{...}, %1...%99 are not supported.

Best regards,
Victor

Hi,

you have configured vertical span incorrectly - it should be 1 for all three gauges.

Best regards,
Victor

а сделайте:

cd /usr/include
grep -r AF_INET6 *

что выдаст?

SYS_NODE_DOWN может не быть если SNMP отвалился, но на ping коммутатор уже ответил. Тогда сервер считает, что проблема только с SNMP агентом.