NetXMS Support Forum

Hi all!

NetXMS version 2.1 is released. It is first stable release in 2.1.x branch which also makes 2.0.x branch obsolete. We strongly encourage 2.0 users to migrate to 2.1. Changes since previous release (2.1-RC1):

- Improved audit logging
- Improved data reconciliation between agent and server
- Improved Grafana integration
- Server detects changes in installed packages during configuration poll
- Added MariaDB database driver
- Fixed excessive CPU usage by agent on AIX
- nxshell can connect to server on non-standard port
- Driver for Netonix switches
- NXSL:
        - New methods for arrays: append, insert, pop, push, remove
        - Table methods get and set can accept column name instead of column index
        - Table row method get can accept column name instead of column index
        - Added table row method set
        - Access to DCI owner object in data collection and instance discovery scripts via $targetObject variable
- Management console:
        - Improved layout of dashboard elements
        - Added option to indicate alarm severity with background color in alarm list
        - Fixed bug in folder download in file manager
        - Proper support for ANSI colors in object tools output in web UI
        - Object dragging on map disabled if user don't have write access to map object
        - Option to hide sub-interfaces in UI (currently works only for Juniper switches)
- Fixed issues: NX-1039, NX-1041, NX-1166, NX-1180, NX-1194, NX-1195, NX-1212, NX-1214, NX-1215, NX-1234, NX-1236, NX-1243, NX-1244, NX-1251, NX-1253, NX-1256, NX-1257, NX-1260, NX-1262, NX-1264

Best regards,
Victor

Hi,

tables are cleaned by internal housekeeper process according to configured retention times. All tdata_* tables contains data for table DCI. You can reduce their size by reducing retention times on table DCis. Also, version 2.1 uses different format for table data storage, more efficient in terms of consumed space (but less efficient for random access).

Best regards,
Victor

Hi,

if standard MIBs are working then there is no need for changes in a driver. If you don't see LLDP peers then problem is missing and/or incorrect information in these MIBs.

Best regards,
Victor

Hi,

fixed in release 2.1

Best regards,
Victor

Hi,

peer node is an interface attribute, so nodes connected by multiple interfaces should be shown as peers for each interface. I will try to simulate this issue in my lab network tomorrow - maybe something is broken.

Best regards,
Victor

Hi,

added to bug tracker: https://track.radensolutions.com/issue/NX-1269

Best regards,
Victor

Hi,

added to bug tracker: https://track.radensolutions.com/issue/NX-1268

Best regards,
Victor

Hi,

what NetXMS version you are using? If on 2.1, make sure administrator user and/or group has access right "Manage DCI summary tables" set.

Best regards,
Victor

Hi,

seems to be a bug in the server. What NetXMS  version you are using?

Best regards,
Victor

Hi,

you'll have to use scripts. There are two slightly different options:

1. create new script in script library that will use GetDCIValueByName or GetDCIValueByDescription to read current values from two DCIs and return their sum. Then create new script DCI on any node.

2. Use transformation script on one of the nodes to read value from other node and return sum of two values.

Best regards,
Victor

Hi,

could you set logging to file, set debug level to 7 (you can do that by adding DebugLevel = 7 to nxagentd.conf) , and try to start agent? Then send me log file.

Best regards,
Victor

Hi,

it's a bug, we will fix it for upcoming release.

Best regards,
Victor

Hi,

common cause also wrong time zone settings on client or server. For example:

on server you have EET time zone (GMT+2), and on client you set it to CET (which is GMT+1). If you set clock on both server and client to be visually equal, they will in fact differ:
8:00 on server will be 6:00 UTC (because EET is 2 hours ahead of GMT).
8:00 on client will be 7:00 UTC (because CET is 1 hour ahead of GMT).
As system internaly uses only UTC time, when your client will request last hour data it will request 6:00 UTC to 7:00 UTC, but because on server it's only 6:00 UTC, you won't get any data.

Best regards,
Victor

Hi,

just to comment a bit on push/pull - you actually can switch agent into push mode by turning on agent cache. When cache is on, server will upload data collection configuration to the agent, and agent will do data collection according to schedule and push collected values to the server (or keep them in local cache if server is disconnected). This will not change bandwidth requirements though (besides few bytes on server poll requests).

Best regards,
Victor

Fixed in upcoming 2.1 release. DCI owner can be accessed in instance discovery and data collection scripts via $targetObject global variable.

Best regards,
Victor