NetXMS Support Forum

We had an issue with version number not being updated, and correct packages were uploaded on Monday. This is pure cosmetic issue though.

For agent issue, please show all System.Memory.Physical.* values.

Best regards,
Victor

Hi,

driver list seems incomplete. Did you install server from sources or from deb package?

Best regards,
Victor

Hi,

try to remove old NetXMS libraries from /usr/local/lib or run make install instead of make.

Best regards,
Victor

Hi,

try to remove libraries from previous installation or run make install instead of simple make.

Best regards,
Victor

Пока не реализавано. Планируем сделать.

похоже на баг, посмотрим

Надо смотреть правила - возможно ошибка в правили обработки события SYS_AGENT_OK (или оно вообще удалено). Если возможно, пришлите скриншот правил, отфильтрованых по SYS_AGENT.

А какой собственно драйвер? Generic?

Hi,

log file location is set in server configuration file, usually C:\NetXMS\etc\netxmsd.conf on Windows. Debug level 9 is very verbose, in most cases you won't need to set it higher than 6.

For UPS you should check if there are any MIBs around for your UPS (usually vendors made them available along with the drivers and other software). If you can find MIBs then you can add them to standard MIB collection on your server and use for configuring DCIs.

Best regards,
Victor

Hi,

you can create another script DCI with script like this:


return GetAvgDCIValue($node, FindDCIByName($node, "\\MSExchange ADAccess Domain Controllers(DC)\\LDAP Search Time"), time() - 3600, time());


It will return average value for last hour. Note that \ are doubled in DCI name because it is an escape character in NXSL string.

Best regards,
Victor

Hi,

try to delete all cookies related to web UI server.

Best regards,
Victor

Hi,

I'm afraid no easy solution here. You can run separate agent process use PING subagent - but you can not specify source IP in agent configuration, so you'll have to limit this agent process somehow to see only one interface. Other (probably easier) solution is to create script that will ping targets from correct interface and use it as external parameter or external parameters provider in NetXMS agent.

Best regards,
Victor

Hi,

you can run agent and server as any user. If you start them as a service, you can use configuration file parameters UserId and GroupId or command line options -u and -g to change effective uid/gid after startup.
For server it is recommended to enable raw socket access (required for ICMP ping) as described here: https://wiki.netxms.org/wiki/How_to_enable_ICMP_ping_for_NetXMS_server_running_under_non-root_account

Yes, rpm packaged are planned.

Best regards,
Victor

Hi,

do you mean that you select driver manually and it's not working anymore, or that automatic driver selection was changed from Catalyst to generic driver?

Best regards,
Victor

Пришлите пожалуйста результат SNMP walk на список интерфейсов (.1.3.6.1.2.1.2). Какой драйвер выбран для устройства? Он не менялся?