NetXMS Forum

Thanks for the suggestion — I've opened an issue for it: https://github.com/netxms/netxms/issues/3409 At the moment all backup-related read operations (list of backups, latest backup, individual backup by ID) are gated only by "Read" access on the node, so anyone who can see the node can also pull the full device configuration with whatever it contains. Splitting that into a separate right for the backup list and another for viewing/exporting the actual content makes sense to me. There are a few things to settle first — mainly what the default should be for existing installations, and the fact that the object access rights mask is nearly out of free bits — so I'll discuss it with the team before we implement anything. Feel free to add your thoughts to the issue.

For XML error - I don't see it in current development version log, so changes are that it's already fixed, pls double-check when v.6.2 is out. For MIB error - I guess MIB compiler is failing on some specific MIB file. You can try removing some of your MIB files until you find which one is causing the issue (you can remove half of them, recomplie, then another half, etc...). Or you can just share your whole MIB file collection.

@victor said in Information about the 802.1x status on the switch ports: Just closed issue 3023 (former NX-2821) - will be part of release 6.2.0. Thank you, Victor!

Hi, I think it would also be nice to have a configuration in the agent file that would allow the implementation of policies similar to "EnableActions".

These scripts were not converted during migration (for multiple reasons, we'll handle that). You can convert scripts using "nxscript -5" command. Copy script from the chart into a file, then run "nxscript -5 file.nxsl", it will output updated script.

NXSL functions accept OIDs both with and without the leading dot. Returned values are without the dot. So both of below lines will print "System description: 1.3.6.1.4.1.14988.1" println("System description: " .. $node.createSNMPTransport()?.getValue(".1.3.6.1.2.1.1.2.0") ); println("System description: " .. $node.createSNMPTransport()?.getValue("1.3.6.1.2.1.1.2.0") ); ?. is safe dereference which appeared in 5.0 - should createSNMPTransport() return null, this will not produce script error.

Hi, Everything is OK. Thanks!

Hi, Everything ok with the display. Thank you very much!

We will increase the limit, fix will be in a patch release that should be out in a few days.

4.4.2-30 Work fine, without crashes..

Hi, I noticed that the error appeared again, but observing the repetition of the event I understood that when NetXMS adds a new node through network discovery, this node would later generate the error in the database. I'm not sure what the reason is, but it seems to me that if the node is not compatible with the agent, simply check the option to disable the use of the NetXMS agent in the status poll and the error would disappear. It seems to be some bug.

It works normally now, thanks

Portuguese-Brazil translation file is src/client/nxmc/java/src/main/resources/po/pt_BR.po. Link to current version in repository: https://github.com/netxms/netxms/blob/84ef97d41905f3dc2cdf39a8b5c52d234b3fe1c0/src/client/nxmc/java/src/main/resources/po/pt_BR.po You can either edit it and send us updated version, or create a pull request with updated texts. Thank you! Best regards, Victor

Hi Victor, Thank you very much for your attention. I believe it will help other users as well. When it's ok, I'll test and come back here.

A great improvement will make it easy. Thanks for the answer.  ;D

Hi! Would you like to know how to apply settings to send messages via google chat? thanks in advance.

Hi, make sure that other UPS software is not running when you try to monitor it via agent - otherwise COM port could be in use and agent may not be able to use it. Best regards, Victor

@victor said in Client Error - Invalid DCI ID: Hi, what exact console version you are using? Is it desktop or web based? Best regards, Victor Hi Victor, I am using version 3.1.300, the error is both Web and desktop. The program freezes and I have to close and restart it. Thank you for your attention,

The issue was resolved by simply updating the configuration pool. New Issue: On an ESXi host via esx, the agent can connect and collect data. On a host VCenter, connection through Active Directory user credentials with connection type VPX fails. The same parameters entered work with the virsh tool. Thank you for your help,

In a dashboard, when I add a rack diagram and mark the title option, instead of the title appears the name of the object.