NetXMS Support Forum

Hi!

No, there are no such standard functionality. However, if you are familiar with Python programming language, you can create simple tool using nxshell that will export node configuration from container into file and then import it into another server. More information about nxshell can be found here: https://wiki.netxms.org/wiki/Using_nxshell_to_automate_bulk_operations.

Best regards,
Victor

Hi,

in DB.Query you specify actual SQL query to be executed, like this:

DB.Query(dbid,"SELECT col FROM my_table")

If you specify query in agent's config then it is executed in background and DB.QueryResult returns cached result from last run. Pre-configured queries are good when you have long-running query - if you use it directly server request may fail on timeout. If you have simple query that executes in less than a second you can use DB.Query.

Best regards,
Victor

Hi,

the problem is that in transformation script you got table as it received from agent. If you want to fill additional column in transformation script you should add it in script like this:

$1->addColumn("Col6");

Best regards,
Victor

Параметр ConfigurableQuery создает запрос который выполняется только по запросу с сервера. Обычно он используется для создания новых метрик с параметрами. Если вам нужен запрос, который выполняется агентом в фоне, то надо использовать Query.

Hi,

there is a bug in active discovery code (it was brojken when we add IPv6 support in 2.0-M3). I fix it in 2.0-M5.

Best regards,
Victor

Мы сейчас собираем и выкладываем 2.0-M5, в этой версии было исправлены несколько утечек. Если обновление не поможет, то будем разбираться.

Только если использовать какую-то внешнюю утилиту для отсылки писем вместо встроенного SMTP клиента.

Hi,

the you have to set search base to the top of the tree, and filter out non-IT users in LDAP search filter. Filter to include only users from IT OUs could look like following (not tested):


(ou:dn:=Information Technology)


I took the OU name from log posted earlier: "CN=a1,OU=Information Technology,OU=Staff,OU=xxx1,DC=mycompany".

Here is more information on such filtering: http://help.globalscape.com/help/eft6/Advanced_LDAP_Filtering.htm.

Best regards,
Victor

Hi,

problem is that you set search base to group object itself, so NetXMS reads only that group object (you can see hint on this in line "Found entry count: 1" - it means that only one matching object was found). You have to set search base to OU=Information Technology,OU=Staff,OU=xxx1,DC=mycompany. If you want to import only users that are member of that group, you should control it with LDAP search filter.

Best regards,
Victor

Hi,

try to run server with debug level 6 and check what's in the log regarding active discovery.

Best regards,
Victor

Hi,

currently it's not possible. We have plans to add IPFIX/NetFlow support in 2.1.

Best regards,
Victor

Hi,

1.2.17 has few known LDAP bugs that was fixed in 2.0. I'm not sure though if that's one of those known bugs. If you can try 2.0-M4 (or wait for 2.0-M5 which will be available next week) it will be great.
Also, is is possible that LDAP server do not respond to requests from NetXMS server? This can be the reason of timeout on client connect.

Best regards,
Victor

В 2.0-M5 добавуил параметр агента File.FolderCount - аналогичен File.Count, только считает папки, а не файлы. Теперь получить кол-во папок новее одного дня можно так:

File.FolderCount(C:\Install,*,0,,-86400)

возможность использования File.Time.Change() похоже зависит от операционки - на Windows меняется после создания подпапки.

Отправил адрес в личку. Смогу заняться в понедельник-вторник думаю.

That actually make sense to interpret runtime error / abort in auto apply script as no action - otherwise small typo can cause mass remove of templates. I've made change in server logic - now only explicitly returned false will cause unbind - runtime errors will be interpreted as "no change". It will be included in 2.0-M5 release.

Best regards,
Victor