NetXMS Support Forum

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

Hi,

currently you cannot change DCI from NXSL scripts. However, you can use nxshell scripts to modify DCIs (some examples on our wiki: https://wiki.netxms.org/wiki/Using_nxshell_to_automate_bulk_operations).

Best regards,
Victor

Hi,

are you using web or desktop client? If you go to main menu View -> MIB Explorer, do you see MIB tree correctly?

Best regards,
Victor

Hi,

you can use private messages on forum to send me access info.

Best regards,
Victor

Hi!

Agent usually runs under local system account. Are you sure that your script will work correctly under local system?

Best regards,
Victor