NetXMS Support Forum

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

Hi!

There are tutorial on creating alarms and sending notifications: http://wiki.netxms.org/wiki/How_to_send_e-mail_notification_when_disk_space_is_low - just replace NetXMS agent DCI with appropriate SNMP OID.

Best regards,
Victor

Hi!

Your best bet is to create simply script with nxshell (http://wiki.netxms.org/wiki/Using_nxshell_to_automate_bulk_operations) to read list of addresses and create node objects. If you are not good at Python - just ask, I'm quite sure that somebody will create such script.

Best regards,
Victor

Hi!

Change your DCI data type to String - this should help.

Best regards,
Victor

Now I understood Console don't allow SNMP walk if MIB selection dialog opened from template - this is because server does not know on which node it should do SNMP walk. It probably could ask for a node object to walk on instead of giving an error - I would add it as feature request.

Best regards,
Victor

Hi!

It's a new feature intended for monitoring devices without IP address and/or network connectivity. For example, you have serial attached UPS that you want to represent in monitoring as separate node. Then your configuration could be following:

1. connect UPS to some machine with network adapter (node A), setup agent (usually separate instance) and configure UPS subagent as usual
2. configure DEVEMU subagent if needed (it can return fake interface list)
3. create node for UPS (node B), set it's IP address to 0.0.0.0
4. set node B primary IP address to that of node A and check "This is address of remote management node"

After that all requests to NetXMS agent on node B will be actually directed to agent of node A. It is different from just defining node A as proxy node for DCIs on node B because server will handle all information provided by agent (interface list for example) as coming from node B. This gives you ability to use agent for status polls of non-networked box.

This option was created for two purposes - 1) to monitor serial attached controllers - we setup number of agents on a PC, each agent communicating with one controller and impersonating it for NetXMS; and 2) for simulating multiple hosts on one machine without need to create VM for each.

Best regards
Victor

Hi!

I'm finally built an intermediate release. It is available here: https://www.netxms.org/download/1.2.15-M1/.

Best regards,
Victor

Hi!

Can it be that status polling is disabled for that server? Otherwise looks like a bug. If you have debugging level 5 or higher enabled, you can look in log if there was status polls for that server and how they end up.

Best regards,
Victor

Hi!

Looks like memory leak in netxmsd. Could you run it under valgrind for some time and send me valgrind's log?

Best regards,
Victor

Hi!

Currently it's not possible, presentation image is defined once for all maps. You can register this as feature request in our issue tracker.

Best regards,
Victor

Hi!

I've put console builds and source package from current development branch here: https://www.netxms.org/download/1.2.15-M1/. Feel free to try!

Best regards,
Victor

А можно его прислать? Возможно я все-таки увижу что-то подозрительное.

Hi,

I mean NetXMS server log file. Check that NetXMS server log goes to file and set debug level to 5 or 6, then try to find records related to remote agent for approximately same time when connection broken messages pops up.

Best regards,
Victor

Hi!

This bug is already fixed in development branch. Fix will be included into upcoming 1.2.15 release.

Best regards,
Victor

Hi!

Quite strange, walk result shows counters for interface Serial/0/0/0 (I assume that's the interface in question). Could you please provide screenshot of DCI configuration that was created for that interface and is not working?

Best regards,
Victor