Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Victor Kirhenshtein

#3616
Hi!

Yes, instance discovery ignores proxy node settings. I register it as a bug.

Best regards,
Victor
#3617
General Support / Re: too much alarm
June 24, 2014, 11:44:42 PM
I only see event in exported file, not event processing policy rules. Did you add rules for export?

Best regards,
Victor
#3618
Hi!

This bug already fixed in 1.2.15. It's not possible to fix it in 1.2.14 without code change. I can provide a patch for 1.2.14 if you are building from sources.

Best regards,
Victor
#3619
Discovery в удаленных зонах есть в планах. В принципе почти все для этого есть - осталось только сам процесс discovery подправить.
#3620
Не критично - просто эти удаленные объекты будут висеть в памяти до рестарта сервера.
#3621
А можно результат SNMP walk по .1.3.6.1.2.1.2?
#3622
Общие вопросы / Re: Broadcast address
June 24, 2014, 11:47:47 AM
При discovery broadcast адреса игнорируются. А сабнеты правильно определились? Поскольку если скажем маска где-то слишком широкая, то broadcast адреса сервер может использовать как обычные.
#3623
Общие вопросы / Re: Database error
June 24, 2014, 11:43:52 AM
Это баг. Без изменений в коде с этим ничего не сделаешь. Буду разбираться.
#3624
General Support / Re: too much alarm
June 24, 2014, 11:41:56 AM
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
#3625
General Support / Re: too much alarm
June 23, 2014, 10:12:31 PM
Can you please provide a screenshot of your event processing policy? Also, what NetXMS version you are using?

Best regards,
Victor
#3626
General Support / Re: too much alarm
June 23, 2014, 04:38:39 PM
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
#3627
General Support / Re: too much alarm
June 23, 2014, 03:55:45 PM
Hi!

What is exact alarm message?

Best regards,
Victor
#3628
Hi!

Check that tools/create_ssa_list.sh has executable permission.

Best regards,
Victor
#3629
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
#3630
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