NetXMS Support Forum

There are no hardcoded limit for number targets. The only limit is system and network resources (sockets, memory, etc.) but 35 targets definitely should be no problem.

Best regards,
Victor

Quote from: kozlov_ao on July 24, 2014, 01:38:02 PM
Это понятно... но тем не менее, вот это не проглатывает, ругается:
Широта - N 55° 42' 27,544"
Долгота - E 37° 41' 18,956"

Надо использовать . а не , для обозначения дробной части числа.

Hi!

You can send events to NetXMS server using nxevent command line tool. You can call it from Zabbix when event need to be reported.

Best regards,
Victor

Hi!

1) It is done automatically by server, usually on startup. If you don't want NetXMS server node under "Infrastructure Services", you can unbind it instead of deleting (right click on infr. services object, select unbind, select server node). That way it will still exist in the system (under Entire Network) and so will not be re-created.

2) Yes, you can. NetXMS server uses own agent for collecting information about itself (interfaces, routing table, ARP cache, etc.) but is able to run without local agent. Local agent only used for polling network services - all standard polls done directly by server.

3) If agent is installed, server prefers interface list provided by agent. Windows agent does not return all those service interfaces as usually it is meaningless.

Best regards,
Victor

Hi!

Are you trying to configure DCI on node you are pinging? If yes, then you have to set proxy node to your management server node.

Best regards,
Victor

Географические координаты можно указывать в следующих форматах:

1) число с плавающей точкой в диапазоне -180 .. 180
2) полушарие градусы
3) полушарие градусы минуты
4) полушарие градусы минуты секунды

Примеры:

1) 74.78291
2) N 24.7245
3) E 56 11.422'
4) W 25 14' 27"

Можно указывать знак градуса: N 24° 11' 14.400"

Указать адрес для агента и сервеа можно параметром ListenAddress  в nxagentd.conf/netxmsd.conf:

ListenAddress = 192.168.1.1

У пользователя нет доступа к обьекту карты. Добавьте доступ (правая кнопка мыши на обьекте, закладка Access Control).

Пока никак. Можно будет добавить такую опцию на карты.

SNMP walk is an actual SNMP request which returns actual data. You cannot send request to template as it is just a configuration element.

Best regards,
Victor

Hi!

I would suggest a reboot for whole system if possible. Error message is from DB itself, not from NetXMS - so it's not that lock.

Best regards,
Victor

Yes, it is possible that node down event comes after DCI threshold violation events. The reason is that data collection is not synchronized with status polls - so when node went down there is no guarantee that status poll will detect it first - so you can get some of the DCI events before SYS_NODE_DOWN. One of the possible solutions is to change number of polls required to trigger thresholds - if you set it to 2 (assuming data collection interval is the same as status polling interval) you will already have SYS_NODE_DOWN received when threshold generates event. Drawback of course is that you'll get service down notification one poll interval later.

Best regards,
Victor

This message could popup if you try to call SNMP walk on non-node object (for example, template or cluster).

Best regards,
Victor

Hi,

it will be included in 1.2.15 (just implemented).

Best regards,
Victor

А как собирается информация об интерфейсах - через агента или по SNMP?