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

#4816
General Support / Re: Discovery issue - over 40 subnets
January 26, 2013, 09:46:34 PM
Hi!

Looks like MySQL issue. You should try to run REPAIR TABLE on all reported tables: http://dev.mysql.com/doc/refman/5.0/en/repair-table.html. Probably there also should be a tool to repair all of them.

If you decide to re-create database, you can try to do export and then import into empty database with nxdbmgr export and import commands. I also suggest to try out PostgreSQL as backend database.

Best regards,
Victor
#4817
Hi!

Make sure that console version match your server's version.

Best regards,
Victor
#4818
General Support / Re: Discovery issue - over 40 subnets
January 25, 2013, 05:36:21 PM
could you run server with debug level 5 for some time and send me the log? Preferrably with screenshot of network discovery configuration?

Best regards,
Victor
#4819
General Support / Re: Configuration of Situation
January 25, 2013, 05:34:33 PM
Hi!

Is it possible to send me diagram of how nodes and management server are connected? You can send it to my e-mail to avoid posting on the forum.

Best regards,
Victor
#4820
General Support / Re: Problem agent feedback.
January 23, 2013, 04:52:40 PM
Hi!

I suppose it's a UNICODE issue. Can you try to downgrade agent on one of the servers to 1.2.2 and see if problem disappears?

Best regards,
Victor
#4821
Then it looks strange. Can you run server for some time with debug level 5 and send me the log after you got unexpected SYS_NODE_UNREACHABLE?

Best regards,
Victor
#4822
General Support / Re: Configuration of Situation
January 23, 2013, 04:49:21 PM
Hi!

Yes, it should work. You should get SYS_NODE_UNREACHABLE instead of SYS_NODE_DOWN, and node should go to UNKNOWN state instead of CRITICAL. It then become NORMAL again when connectivity restored.

Best regards,
Victor
#4823
Автобинд скрипт - это атрибут контейнера, и всегда выполняется только для того контейнера, в котором определен. Если вы используете общий скрипт из библиотеки, то при вызове из каждого конкретного контейнера можно передавать его имя или идентификатор как параметр. Перебрать все custom attributes нельзя, надо знать их имена.
#4824
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
#4825
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
#4826
General Support / Re: Configuration of Situation
January 22, 2013, 02:20:51 PM
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
#4827
Thank you, I'll take a look at the dumps in next few days!

Best regards,
Victor
#4828
General Support / Re: Agent Detection - v1.2.5
January 21, 2013, 08:30:47 AM
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
#4829
Hi!

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

Best regards,
Victor
#4830
Hi!

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

Best regards,
Victor