NetXMS Support Forum

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

Hi,

did you run it from local desktop session? If it is remote session, do you have DISPLAY environment variable set correctly?

Best regards,
Victor

Delta calculation for tables is not implemented yet.

Best regards,
Victor

Hi,

I will add workaround for it in 2.2.5.

Best regards,
Victor

Hi,

there are multiple command line options to Windows agent installer. You can get standard installer options by running it with /?. Generally for unattended install you'll have to specify /VERYSILENT and /SUPPRESSMSGBOXES options. There are also custom command line options that allows you to pass information for generated agent configuration file:

/SERVER= 
Set server IP address or host name (will be set in configuration file as MasterServers)

/CENTRALCONFIG
Read configuration from server on startup

/LOCALCONFIG
Use local configuration file (it is the default)

/SUBAGENT=
Add sub-agent loading directive to configuration file. Possible sub-agent names are ECS, FILEMGR, LOGWATCH, PING, PORTCHECK, WINPERF, WMI, and UPS. You can specify this parameter multiple times to add more than one sub-agent.

Best regards,
Victor

Hi,

looks like a bug. Could you set debug level to 4 or higher and check for records with Node::createSubnet prefix? Then check what nodes are mentioned when duplicate subnets are created.

Best regards,
Victor

Hi,

no, it's irrelevant for Windows Event Log. Agent uses appropriate Windows API to access events in event log.

Best regards,
Victor

Hi,

NetXMS has interface for ticketing system integration (called helpdesk link), but so far we have developed only two drivers - for Jira and for Redmine. What exact ticketing system you are interested in?
Some level of integration can be achieved with external scripts - you can run external commands as actions that will create tickets and you can use nxalarm command line tool to manipulate alarms from external scripts.

Best regards,
Victor

Hi,

it is not possible to delete data from within script. Reset to 0 will work (you can check current date and time in script and return 0 if it is first poll after midnight).

Another possible option is to create two DCIs - one short term and one long term. Long term DCI will have custom schedule to collect it once per day/week/month/etc. and it will get get sum of values from short term DCI for required period. Retention time for short term DCI can be set to desired time interval plus some extra time to allow long term DCI collector script to run.

Best regards,
Victor

Hi,

could you please share your agent configuration and log so I can check if it set up correctly? You can set debug level on agent to 7 to get MQTT diagnostic messages.

Best regards,
Victor

Hi,

agent opens file being monitored with "shared for write" access. However, if application that writes to the file attempts to open it without specifying "shared for read" option it will get file open error. In upcoming 2.2.5 release we have added log parser option "keepOpen" that can be set to false to instruct parser to re-open file every time to get new records.

Best regards,
Victor

Hi,

are you sure you download correct agent again? I just downloaded agent 2.2.4 (https://netxms.org/download/releases/2.2/2.2.4/nxagent-2.2.4-linux-x86_64.tar.gz) and get the following ldd output:

   linux-vdso.so.1 =>  (0x00007fffe67fb000)
   libappagent.so.2 => /home/victor/tmp/agent/opt/netxms/lib/libappagent.so.2 (0x00007fe6af982000)
   libnxagent.so.2 => /home/victor/tmp/agent/opt/netxms/lib/libnxagent.so.2 (0x00007fe6af77d000)
   libnxdb.so.2 => /home/victor/tmp/agent/opt/netxms/lib/libnxdb.so.2 (0x00007fe6af569000)
   libnetxms.so.2 => /home/victor/tmp/agent/opt/netxms/lib/libnetxms.so.2 (0x00007fe6af2dc000)
   libnxsnmp.so.2 => /home/victor/tmp/agent/opt/netxms/lib/libnxsnmp.so.2 (0x00007fe6af0c6000)
   libnxexpat.so.2 => /home/victor/tmp/agent/opt/netxms/lib/libnxexpat.so.2 (0x00007fe6aeea3000)
   libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fe6aec6e000)
   libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fe6aea51000)
   libssl.so.1.0.0 => /home/victor/tmp/agent/opt/netxms/lib/libssl.so.1.0.0 (0x00007fe6ae7e1000)
   libcrypto.so.1.0.0 => /home/victor/tmp/agent/opt/netxms/lib/libcrypto.so.1.0.0 (0x00007fe6ae3a7000)
   libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fe6ae025000)
   libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fe6add1c000)
   libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fe6adb05000)
   libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fe6ad73b000)
   libnxtre.so.5 => /opt/netxms/lib/libnxtre.so.5 (0x00007fe6ad529000)
   libnxzlib.so.1 => /home/victor/tmp/agent/opt/netxms/lib/libnxzlib.so.1 (0x00007fe6ad314000)
   libnxjansson.so.4 => /home/victor/tmp/agent/opt/netxms/lib/libnxjansson.so.4 (0x00007fe6ad108000)
   /lib64/ld-linux-x86-64.so.2 (0x000055d0dfb86000)
   libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x00007fe6acede000)
   libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007fe6accc4000)
   libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007fe6acaa8000)
   libjemalloc.so.1 => /usr/lib/x86_64-linux-gnu/libjemalloc.so.1 (0x00007fe6ac871000)

As you see it references correct libssl library from it's own directory.

Best regards,
Victor

Hi,

there are separate agent parameters that returns used and free space in bytes - respectively FileSystem.Used and FileSystem.Free. You can either replace parameter names in template or create new template DCIs with same settings but usiong different parameters.

Best regards,
Victor

Hi,

you can create template with DCI using OID you have provided and apply as necessary. Then you can create DCI summary table and use it to get serial numbers for all switches in one table. For SFP modules you likely can use instance discovery to create DCI for each SFP (I don't know how this information exposed on your devices so I'm not sure). If you'll have DCIs for SFP modules you can add them to the same summary table as additional columns.

Best regards,
Victor