NetXMS Support Forum

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

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

Надо смотреть правила - возможно ошибка в правили обработки события 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). Какой драйвер выбран для устройства? Он не менялся?

Hi,

I suggest to check 2.2.5 - most likely it will work without issues.

Best regards,
Victor

Hi,

you need some SQL database, it could be MySQL or any other supported database (PostgreSQL, Oracle, MS SQL). If you plan to use web UI, the you'll need Tomcat or Jetty.

Best regards,
Victor

UPDATE: this version change event log, alarms, syslog, and SNMP trap log tables, and will take significant amount of time to complete on large installations (>100mil records). We are working on the solution. In the meantime either postpone upgrade, or plan some downtime (up to couple of hours).

Hi all!

NetXMS version 2.2.5 is out. Changes since previous release:

- Agent tunnel falls back to unbound mode in case of agent certificate validation failure
- Zone information added to alarm log, event log, SNMP trap log, and syslog
- Agent returns correct free memory value on Windows
- Parameter System.Memory.Physical.Cached supported on Windows
- Fixed issues:
        NX-333 (Add windows service descriptions for both server and agent)
        NX-622 (Alerts will not be generated in certain conditions: events, that persist after maintenence and node down after unreachable)
        NX-640 (File manager should show file owner and permissions)
        NX-716 (Server configurator on Windows should be marked as require-administrator)
        NX-922 (Service check template objects disappears after server restart)
        NX-1097 (Configuration option to ignore alarm's helpdesk state when doing resolve or terminate)
        NX-1157 (configure --with-dist fails if OpenSSL is not installed)
        NX-1397 (Implement Windows Update information parameters for Windows 10 and Windows Server 2016)
        NX-1415 (Windows 10 upgrades break agent tunnels)
        NX-1417 (File.Size parameter not working for Windows pagefile.sys)
        NX-1418 (Sort scripts in Execute Server Script dropdown)
        NX-1419 (AgentTunnels.ProcessUnbound scheduled task should be hidden)
        NX-1420 (Do not use unmanaged devices with SNMP for MAC resolving)
        NX-1421 (Configuration poll for node without SNMP and agent always read ARP cache from all SNMP devices in subnet)
        NX-1427 (Max manual Y values for graphs limited to 2147483647)
        NX-1431 ("Don't Fragment" option for ping sub-agent)
        NX-1433 (LDAP timeout blocks internal user database)
        NX-1434 (Return from function from within foreach loop in NXSL can cause unexpected runtime error)
        NX-1436 (Write hostname to agent log on startup)
        NX-1442 (Generic device driver cannot read interface list if device does not support ifNumber MIB object)
        NX-1446 ( Only one agent policy editor can be opened, if another policy is opened for editing, previous is closed without saving)

Best regards,
Victor

Hi,

you can ignore those errors - recently we have changed driver structure and some old drivers that are not used anymore show those errors on load. Make sure you have correct SNMP settings in node communication properties and that SNMP requests are allowed from NetXMS server's IP address.

Best regards,
Victor