NetXMS Support Forum

Hi!

I've added new configuration parameter ProcessTrapsFromUnmanagedNodes (0 by default).

It is possible to create alarm from external script in two steps - first you send event using nxevent command line tool and then create alarm from that event as usual.

Best regards,
Victor

From your description it seems that it's enough to create multiple rules for same event, but with different sources. No script is required in that case. And even if you need more complex filtering, you can implement it as filtering script for the rule.

Best regards,
Victor

Looks like a bug in image library. Edit action supposed to do exactly this - replace existing image with new one.

Best regards,
Victor

I plan to add initial support for IPv6 topology later this year (most likely not before late Autumn). It should not be too hard, but still requires significant rework of server internals. So far IPv6 can be used for management console connection, and agent connection over IPv6 is the next easy to implement option.

Best regards,
Victor

Hi!

Log file seems to be truncated. Valgrind finalizes log file only when process exists, so you should stop netxmsd first.

Best regards,
Victor

Hi!

You don't have to use instance discovery to monitor single item. All you have to do is to put .1.3.6.1.4.1.11369.10.3.2.1.0 as "parameter" on general page. Make sure that instance discovery is off.

Best regards,
Victor

Script should be run in a same manner on Windows, just omit -Djava.io.tmpdir=/tmp/ and use \ instaed of / in path separators.

Best regards,
Victor

I forgot to put it into installer. x64 version attached.

Best regards,
Victor

Try to execute manually query

UPDATE metadata SET var_value='322' WHERE var_name='SchemaVersion';

then netxmsd should start.

Best regards,
Victor

Oops, typo in PostgreSQL query Run nxdbmgr with -X option and the run manually the following queries:

ALTER TABLE users ALTER COLUMN system_access TYPE bigint;
ALTER TABLE user_groups ALTER COLUMN system_access TYPE bigint;

Best regards,
Victor

Quote from: Marco Incalcaterra on June 13, 2014, 12:49:06 AM
seems a good idea, I tried with an UPS but as far as I can see the node B will inherit the interfaces of the node A, can be avoided?

you need devemu subagent for that. This is how config for emulated device on my PC looks like:


MasterServers = 0.0.0.0/0
LogFile = C:\DevEmu\ATM001\log\nxagentd.log
ListenPort = 9001
EnableSubagentAutoload = no
SubAgent = devemu.nsm

*DEVEMU
IpAddress = 192.168.84.11
IpNetMask = 255.255.255.0
MacAddress = 551010000001
InterfaceName = Local Area Connection


Best regards,
Victor

Можно сделать такой configuration poll hook скрипт:


foreach(i : GetNodeInterfaces($node))
{
   if ((i->ifType == 24) && !AddrInSubnet(i->ipAddr, "127.0.0.1", "255.0.0.0"))
   {
      PostEvent($node, "BAD_LOOPBACK_CONFIG", null, i->name);
   }
}


Он будет посылать событие с именем BAD_LOOPBACK_CONFIG на каждый найденный интерфейс с типом 24 и адресом не из 127.0.0.0/8. Естественно, событие должно быть сначала создано. В %1 попадет имя интерфейса.

Not yet. Hopefully will be documented until 1.2.15 release.

Best regards,
Victor

Hi!

You can try to do SNMP walk from MIB Explorer view on different parts of MIB tree - but most likely you'll have to find some additional information about your devices - often data you get via SNMP is meaningless without description.

Best regards,
Victor

Происходит это так: NetXMS исключает loopback интерфейсы из топологии (что вроде как правильно). Loopback интерфейс определяется по адресу (из 127.0.0.0/8) или по типу (24 - software loopback). При дисковери проверяется, есть ли уже найденный IP адрес в системе. Поскольку loopback интерфейсы исключены из топологии, адрес не находится - создается новая нода. И так далее. Если таких устройств немного - можно добавить их адреса в фильтр discovery. Какой правильное решение - пока не знаю, возможно добавить конфигурационный параметр, который разрешит учет loopback в топологии если у них адреса не из 127.0.0.0/8?