NetXMS Support Forum

Hi!

This is due to topology-based event correlation. Idea is to suppress multiple SYS_NODE_DOWN events if they are caused by intermediate router failure. If only end node was disconnected and still server generates SYS_NODE_UNREACHABLE instead of SYS_NODE_DOWN, then this is a bug. Unfortunately this feature cannot be turned off. I'll add appropriate option in 1.2.6. As a workaround, you can disable routing table polls on intermediate routers - if NetXMS server will not know full route to the node, it will not try to do such correlation.

Best regards,
Victor

Hi!

You have to escape text properly before passing to command line, or enclose text in quotes. Try to define your command as


/opt/CA/SharedComponents/ccs/bin/cawto -n waqnsm91 NETXMS - ALERT - %n - %a - '%m'


Btw, you don't need to put / twice - only the backslash (\).

Alternative approach could be to use NXSL script to escape special characters in event message with backslash.

Best regards,
Victor

Hi!

This is done automatically. The only requirement is that NetXMS server must know full route to the nodes, so intermediate routers must be accessible and provide routing information.

Best regards,
Victor

Thank you, I'll take a look at the dumps in next few days!

Best regards,
Victor

Hi!

Can you provide more details? You mean that after initial discovery node has isAgent capability set, but after manual configuration poll it is cleared?

Best regards,
Victor

Hi!

It should. Do you still have same issue with 1.2.5?

Best regards,
Victor

Hi!

You can create unmanaged node or container and put it on the map.

Best regards,
Victor

Please share what is your primary target for monitoring with NetXMS.

It's not exactly the same - using templates you cannot create DCIs depending on node capabilities (for example, enumerate all interfaces and create DCI for each interface).

Best regards,
Victor

Hi!

You must remove "always process all thresholds" option from thresholds and put "== 0" threshold first. Then you should get only one deactivation event. See this: http://wiki.netxms.org/wiki/UM:Data_Collection#Threshold_Processing for description why threshold order is important.

Best regards,
Victor

Если сами счетчики реально 32-битные (на хосте), то замена типа в NetXMS проблемы не решит - при переходе счетчика через 0 получится неправильное значение. Я еще проверю, какой тип данных для счетчиков использует операционная система. Если ето действительнно 32 битные, и траффик большой, то единственный вариант наверное - это делать опросы чаще, например каждые 10 секунд.

А какой CodePage стоит в netxmsd.conf? И что возвращает команда


nxget -l <windows_server_address> Net.InterfaceList


?

Hi!

Do they respond to SNMP? Check that SNMP settings are correct and that you can reach them by SNMP. You can do that using nxsnmpwalk or nxsnmpget tools.

Best regards,
Victor

Hi!

Both is not possible - you cannot run script on node, and you cannot create DCI from script. Idea is good, I'll add feature request for that (#219, #220).

Best regards,
Victor

Hi!

Can you send me a screenshot of DCI configuration (thresholds page) and event processing policy rules for threshold activation and deactivation events?

Best regards,
Victor