I guess its better than nothing but i'm not a fan of scripting when it can be avoided, its just messy, hard to read and hard to make changes or troubleshoot down the track (too many rabbit holes to follow to find what is responsible for what) Any plans to update threshold options and add the ability to specify multiple values?

When I open a dashboard in Edit Mode, make some changes, but decide not to save, the changes remain persistent until I close and reopen the console again. Console build 2284.

Check this thread: https://www.netxms.org/forum/installation/netxms-3-0-2292-configure-error-cannot-find-mysql-h-on-centos7/

Thanks for the clarifications, this helped me alot

Also in dashboard data source "display format" and "display raw values" dont have any effect.

Hi, if your devices supports enable/disable port by changing certain SNMP OID you can use script action with SNMPSet function. Best regards, Victor

Hello Tursiops, thanks for your explanations/clarifications. I wanted to be sure not to have overlooked some options in NetXMS for discovery of switches/routers. So I changed routing such that the MikroTik devices are found and now they are discovered by NetXMS. Thanks and best regards Oliver

Currently, as of 3.0, it works that way, that as soon as you create a node, Full configuration poll is being done. If server is not able to ping AND connect to agent, the node will be marked at unreachable and the only thing that will remove unreachable flag and initiate communications is to manually run Full configuration poll  again. The thing is that after node creation, while user goes to properties of a zone to set that node as a proxy, the node gets unreachable. There is a way to create a node in a zone and set it as proxy for that zone in one step - in new node creation there's a checkbox "Create as zone proxy for selected zone". It's among other checkboxes and is easy to overlook. There are thoughts to improve user-friendliness of all this. As for ZoneUIN parameter - as far as I know, it's related to SNMP Traps and Syslog monitoring; also it's used when tunneling agent connects to server so that server could auto-assign node to correct zone. Proxy should work without this parameter configured.

Since upgrading to 3.0 I notice that network map link bend points seem to be a bit wonky. If you insert or move a bend point the link label no longer closely follows the path of the link.  Instead it stays close to the original 'direct mode' path of the link before the bend point was inserted.  In 2.x it used to stay attached to the path. Dragging bend points or adding removing sometimes seems to snap the link itself back to being direct mode although the bend point circles will stay in place.  This then flickers back and forth sometimes. I found bend points useful to map diverse VPN paths between two locations and separate them enough to read the labels clearly. I assume its a client console issue?  Although the two screenshots show two maps generated in the java console and web console so issue is common to both. NXCM: 3.0.224 Server: 3.0.2292 Edit: created NX-1691 [image: bendpoints.PNG] [image: bendpoint2.png]

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,

Thanks! Confirmed working again 

Yes, it's possible. What is currently missing for that device which should be provided by the driver? Currently driver can be used to get list of VLANs, interfaces, physical port layout, wireless access points and clients. Best regards, Victor

I'd suggest doing away with statically configured DCIs for disk space and replacing them with Instance Discovery ones, which will pick up any volume in your system for monitoring purposes without you having to hardcode any of them. There is documentation on that topic and there are quite a few examples on the forum on that topic, so a quick search should yield some results.

ok i just saw a new netxms build and i upgraded the server to 3.0.2284 and web service API using netxms-websvc-3.0.2284.war after that, DCI values showed up within grafana graphs. No error 46 anymore. Not sure what the fix was, but hey, it works. Happy ;D

Already testing with 3.0 which I planned as our next upgrade but knowing this I may jump to 2.2.17 before that. Thanks!

I suspect that compiler shipped with CentOS 6 may be too old. My recommendation is to upgrade platform to CentOS 7. Best regards, Victor

Version 3 seems to have fixed this. Been up for 45 minutes now.

Working now ... Thank you

Hi, everything is correct. Raw value is in bytes, so if you want it in bits it should be multiplied by 8 (if you got 1 from device that means 1 byte, multiplying it by 8 gives 8, which is correct number of bits). Best regards, Victor

Yes, we will publish packages for Ubuntu 19 in a few days. Best regards, Victor