NetXMS Support Forum

Hi!

There should be no changes in syslogd. Can you send me XML file with parser configuration? Also, there are still problems with editing syslog XML config from Java console. Please use legacy console until 1.2.6 release.

Best regards,
Victor

Hi!

Discovery process is running all the time in the background. You can speed it up a bit by:
1. adding key devices manually
2. putting more frequently used SNMP community strings to the top of community string list
3. decreasing value of server's configuration parameter DiscoveryPollingInterval

Best regards,
Victor

Я думаю сделать возможность выставить тип отображения объектов по умолчанию. Добавил уже в багтрекер для 1.2.6: https://www.radensolutions.com/chiliproject/issues/204.

Да, он предполагался и в шаблонах тоже. В 1.2.6 обязательно будет.

Hi!

Yes, you can upgrade directly.

Best regards,
Victor

I replace WIndows installers on web site with updated version (file names was not changed). Try to uninstall existing version, clear/drop database, and install updated version.

Best regards,
Victor

Yes, nxdbmgr set broken as well

Try to add line

DataDirectory = C:\NetXMS\var

to netxmsd.conf.

I'll also put fixed installer on web site later today.

Best regards,
Victor

Теперь надо запустить


nxdbmgr.exe upgrade


чтобы закончить обновление схемы.

Hi!

Try to run command


nxdbmgr set DataDirectory C:\NetXMS\var


from command line in C:\NetXMS\bin. It's a bug in server configurator.

Best regards,
Victor

Hi!

I agree that this is needed. I'm thinking of adding "default icon type" option to "Map Options" property page for map object. Issue in bug tracker to track: https://www.radensolutions.com/chiliproject/issues/204.

Best regards,
Victor

Upd: в аттаче SQL скрипт для конвертации таблицы event_log в правильный формат.

Оффтопик: кто-нибудь может дать мне invite для регистрации на хабрахабре? Если да, то пишите в личные сообщения.

Hi!

It's not possible to specify such relation manually. Anyway, it is layer 2 connectivity issue, not layer 3, as both nodes (physical host and VM) are in same subnet, so 192.168.1.10 is not involved in the routing process, but acting as Ethernet bridge. I will add a feature request for including layer 2 topology into event correlation process.

As a workaround, you can check status of the host node in the script in event processing policy, but this may not work as expected if VM polled first (so server don't know that host is already down).

Best regards,
Victor

Похоже что изначально таблица была создана с опцией ANSI_NULLS = OFF (так было по умолчанию на старых версиях MS SQL). Единственный вариант похоже - это пересоздать таблицу EVENT_LOG заново с опцией ANSI_NULLS = ON. Одно из предлагаемых решений: http://stackoverflow.com/questions/10010042/update-ansi-nulls-option-in-an-existing-table.
На всякий случай - DDL для создания таблицы:

CREATE TABLE event_log
(
event_id bigint not null,
event_code integer not null,
event_timestamp integer not null,
event_source integer not null,
event_severity integer not null,
event_message varchar(255) null,
root_event_id bigint not null,
user_tag varchar(63) null,
PRIMARY KEY(event_id)
) ;
CREATE INDEX idx_event_log_event_timestamp ON event_log(event_timestamp);


Microsoft про ANSI_NULLS: http://msdn.microsoft.com/en-us/library/ms188048.aspx

Hi!

In 1.2.5 we improve event correlation based on topology, so if NetXMS knows full path between itself and remote node it should correlate events automatically and only pass NODE_DOWN event for router. You can check this by selecting management server node object in object tree, then select "IP Route" from context menu, select remote node, and check that correct IP path is shown.

Sorry, I didn't fully understand web site question. Can you give a simple scenario please?

Best regards,
Victor