NetXMS Support Forum

При discovery broadcast адреса игнорируются. А сабнеты правильно определились? Поскольку если скажем маска где-то слишком широкая, то broadcast адреса сервер может использовать как обычные.

Это баг. Без изменений в коде с этим ничего не сделаешь. Буду разбираться.

It's hard to tell anything from rule comments only I need to see rules expanded. To avoid making lot of screenshots you can export all rules and attach xml file. Go to Tools -> Export configuration, and add all rules to the export. Then press "Save" icon to save it into XML file.

Best regards,
Victor

Can you please provide a screenshot of your event processing policy? Also, what NetXMS version you are using?

Best regards,
Victor

Looks like you have rule in event processing policy for events SYS_NODE_NORMAL, SYS_NODE_WARNING, SYS_NODE_MINOR, SYS_NODE_MAJOR, SYS_NODE_CRITICAL. Usually you should not generate alarms from those events.

Best regards,
Victor

Hi!

What is exact alarm message?

Best regards,
Victor

Hi!

Check that tools/create_ssa_list.sh has executable permission.

Best regards,
Victor

Topology information updated during topology polls (every 15 minutes by default). You can also do manual topology poll via Poll -> Topology menu on node. If incorrect link information stays more than topology polling interval then it's a bug.

Best regards,
Victor

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