NetXMS Support Forum

Looks like you have MIB called AT-SMI-MIB missing. Check that you have MIB file with .txt extension starting with

AT-SMI-MIB DEFINITIONS ::= BEGIN

Best regards,
Victor

Добавим - скорее всего не в виде встроенной карты, а показа маркера в навигационном приложении по умолчанию. Сейчас есть функция "navigate to" для нод с выставленноми координатами.

Hi,

it's not possible yet.

Best regards,
Victor

Hi,

it's problem with reading data from database, not with storing. It is caused by bug in MariaDB client library https://jira.mariadb.org/browse/CONC-281. It is supposed to be fixed in latest client version, but could be not. Our MariaDB driver has check for client version that activates workaround - maybe it erroneously assumes version number where this issue was fixed. You can try to find the following lines in src/db/dbdrv/mariadb/mariadb.cpp:


/* workaround for MariaDB C Connector bug CONC-281 */
if (mysql_get_client_version() < 100209)  // for any client before 10.2.9
{
    mysql_stmt_store_result(hStmt->statement);
}


and comment out version check so it will look like this:

/* workaround for MariaDB C Connector bug CONC-281 */
//if (mysql_get_client_version() < 100209)  // for any client before 10.2.9
{
    mysql_stmt_store_result(hStmt->statement);
}


then recompile MariaDB driver.

Best regards,
Victor

Hi,

currently it's not possible. Starting with 2.2.8 complete event information in XML format stored in event log table, but not yet available in UI. In next release we will provide access to that information.

Best regards,
Victor

Hi,

MIB browser will show whatever MIBs are installed in your system. If you need more AT MIBs, just install them onto the server as described and you should see them in MIB browser.

Topology displayed depends on information received from switches. If they report correct information through any standard topology MIB (LLDP, CDP, etc.) then correct topology will be displayed.

Best regards,
Victor

Hi,

Error message "Table 'metadata' already exists" suggests that you are trying to initialize same database after unsuccessful initialization attempt, so it is not possible to determine root cause. Please drop existing database, create a new one, run nxdbmgr init once, and post it's output.

Best regards,
Victor

Hi,

there could be multiple reasons for that - firewall issues, no SNMP devices within subnets (needed for passive discovery), etc. Active discovery can take long time if subnets are big. You can try to set debug level to 6 and check messages with DiscoveryPoller prefix.

Best regards,
Victor

Hi,

please try upgrading agent to 2.2.8. There were lot of fixes since 2.1.2.

Best regards,
Victor

А сделайте экспорт шаблона - мы бы его добавили как стандартный.

В FindObject передается имя объекта или его идентификатор. Я не сообразил что SERVERS/TERMINALS скорее всего имелось ввиду контейнер TERMINALS в контейнере SERVERS. Если это так, то надо как параметр передавать строку "TERMINALS".

Можно зайти пользователем system. Если он неактивен, то можно остановить сервер, выполнить команду

nxdbmgr reset-system-account

и запустить сервер. После этого зайти пользователем system с паролем netxms.

Hi,

$dci is not set for data collection script, only for transformation and threshold scripts.

Best regards,
Victor

Исправили в 2.2.8.

Hi,

please update to 2.2.8 when it becomes available. We just fix few issues related to link colors (although I was unable to reproduce your exact issue), and on our test system all works as expected with and without data sources set on a link.

Best regards,
Victor