NetXMS Support Forum

We just published NetXMS version 5.0. This major release was mostly focused on improving network maps, wireless network monitoring, internal scripting language (NXSL), and new UI. And of course there is lot of smaller improvements and fixes.

Make sure to check list of breaking changes, as there are few.

Full change log is following:
-  Improved network maps
-  Added network map link styling script
-  Delegate access option that allows read access to network maps without full read access to objects on a map
-  Reworked monitoring of wireless access points and controllers
-  Major overhaul of sensor objects
-  Many NXSL function deprecated in favor of object methods
-  Improved NXSL classes and functions for date/time handling
-  Add option to check alarm details from alarm log view
-  Log parser rules can define metrics that are populated from match data
-  Special NXSL return codes for data collection and transformation scripts (DataCollection::ERROR, DataCollection::NOT_SUPPORTED, DataCollection::NO_SUCH_INSTANCE)
-  New NXSL function FindAccessPointByMACAddress
-  New NXSL function GetMappingTableKeys
-  "Stop" function in script executor view
-  Desktop client can reconnect automatically after short connectivity loss
-  New agent metric File.Hash.SHA256
-  New agent list and table Net.IP.Neighbors
-  Index property displayed in MIB browser
-  Root object can be set for object query
-  Improved SNMP trap processing performance
-  New log parser file option "removeEscapeSequences"
-  Added peer certificate verification in ticketing system connectors
-  Housekeeper scripts (NXSL and SQL)
-  Improved REST API
-  Introduces new object class "Collector"
-  Downtime log controlled by EPP

Fixed issues:
-  NX-797 (Automatic reconnect of management console)
-  NX-1790 (Drag-n-dropped object are positioned to wrong place when map is scrolled down or right)
-  NX-1870 (Representation of float DCI that gets string data as input)
-  NX-1935 (Introduce hook script on map regeneration with ability to set link names)
-  NX-2006 (Remove example event templates (code 4000-4011) from database)
-  NX-2076 (Raw value should be always displayed as string)
-  NX-2292 (Automatic maps should not include nodes that are connected through a node that was excluded by filter script)
-  NX-2323 (Make parameters in all events named)
-  NX-2343 (Several changes in NXSL syntax in v 5.0)
-  NX-2375 (Use "varchar(max)" instead of "text" on Microsoft SQL Server)
-  NX-2403 (Add support for AES-192 and AES-256 in SNMPv3)
-  NX-2444 (On demand background external metrics)
-  NX-2455 (Ability to check TLS.Certificate.* for protocols with STARTTLS command)
-  NX-2481 (Add ability to manually poll network map generation)
-  NX-2507 (Add ability to cancel timers from NXSL)
-  NX-2520 (Remove "Channel name" selector from "Send notification" dialog)
-  NX-2523 (New agent metric Process.MemoryUsage (percentage of memory used by process))
-  NX-2524 (Option to disable threshold without deleting it)
-  NX-2525 (Add the ability to specify multiplier values in threshold)
-  NX-2526 (When editing a template with a DCI without instance to use instance - DCI becomes unsupported)

Hi

It's already renewed and uploaded a while ago.

I highly recommend to use netxms-release package, which update keys automatically.

Key locations:
https://packages.netxms.org/netxms-keyring.gpg -- binary keyring
https://packages.netxms.org/netxms.gpg -- armoured key

Also it's available from key servers.

Make sure that key is not imported into trusted keys (e.g. using apt-key), but is stored in separate key store, as recommended in recent Debian/Ubuntu.

Hi,

Time to renew this?

After upgrade i noticed that infrastructer object browser doesent auto refresh anymore, for example container binding or renaming. user has to press manual refresh.

Thank you Filipp. 

Ahh makes sense thanks for the reply

This feature might not have been transferred from the old client to the new one. Will be fixed.

Hi everyone,

Please, anyone knows if is it possible to configure color on the alarm list using the Management Client Version 4.5.6? That feature was available in previous version, but after upgrade to 4.5.6 I can´t found that option to set up.

PS: This problem is not present when accessing by webbrowser.

Thanks in advance.

You can check raw values in history of a DCI and do the calculation manually, but I am afraid that's just the data that this switch provides.

More experienced people might correct me, but as long as I remember, reading status of link duplex was pretty non-standard thing that differed accross device make and models. For your specific devices you can create SNMP DCIs. If you need to check across peer devices, it's possible in nxsl as interface class has peerInterface attribute.