I confirm it works, for virtual chassis too. Thanks. Just one request concerning a different issue: is it possible to add the "vlan view" (in the Topology menù) also in the node overview tab in order to have a visual display of their port status? The port view does not display vlans, don't know if the reason is that vlans are on logical interfaces or for design.

Thank you very much for your advice! This is really the most powerful network manager I have ever tried!

@filipp-sudanov said in freezes while its set images in rack front: Was unable to replicate this. Is this background image configured as rack Passive Element? Can you show properties of that passive elements? Do you also have some other nodes that are present in this rack? Do they useHi, default images or custom? Can you also show screenshots of their rack properties? Hi, I have also seen similar bug adding passive elements. The images do not appear according to the orientation of these elements.

Thanks Victor, I will try to put together something a bit more concrete to investigate the next time I’m on-site.  LLDP is enabled on all switches. MNDP from Mikrotik is also enabled though which makes the neighbor list on a switch contain all the other Mikrotik switches, would this affect NetXMS? Only directly connected switches list LLDP as discovery method though.  / tuxic

Agent communication DCIs are counters (similar as in SNMP), they are always increasing, that's fine. The interesting part is how fast it's increasing. As an option, you can add additional DCIs with enabled delta calculation. Would be interesting to see graphs for these two Agent communication DCI for the same period as memory usage above.

This was just fixed, will be available in 4.3.1 when it will be released.

ok,thank you very much!!

Thank you for all the help! I was able to get the deb package installed after installing a prerequisite for it which then allowed me to install the subagent. Now I just have to figure out the freepbx/asterisk config to allow this to work 

If you are on Windows then I recommend to switch to version 4.3 - web UI installer for Windows also contains API which will be accessible under /api path. Starting with version 4.3 we also deploy complete Jetty server so you'll be able to properly setup SSL, etc. Best regards, Victor

Hello @all, at my NetXMS Server (Win10, MySQL V5.7.30, 16GB RAM) i see the follow event in the windows event log:  InnoDB: Over 67 percent of the buffer pool is occupied by lock heaps or the adaptive hash index! Check that your transactions do not set too many row locks. Your buffer pool size is 16 MB. Maybe you should make the buffer pool bigger?. Starting the InnoDB Monitor to print diagnostics, including lock heap and hash index sizes.For more information, see Help and Support Center at http://www.mysql.com.  Has anyone an idea what buffer pool size i have to use? On this machine is only NetXMS running and no other DB's. Thanks in advance... Greetings Marco

Hi Victor, thanx for the fast response... downloaded, tried and worked for me... But i have to shutdown NetXMS Server, in cause of a locked library...  Now NetworkService.Status is working... Many thanx..  Greetings Marco

I'd suggest to upgrade to 4.3 if possible - it has improved algorithm for thread pool resizing. In any case you can try to increase min and max size for main thread pool, to say 64 (can be 16 for 4.3, it should expand it aggressively if needed) and 512. Best regards, Victor

Both old and new should work correctly in 4.3. Please let us know if you will still have problems. Best regards, Victor

That turned out to work quite well actually. I added som debug outputs to see the responses. Command=curl.exe -vs -o C:\Temp\pixieresponse_${recipient}.txt -G "https://pixie.se/sendsms?account=123&pwd=456&receivers=${recipient}&sender=Company" --data-urlencode "message=${text}" 2>C:\Temp\pixiedebug_${recipient}.txt Thanks for your help.

Great, thank you. That works. But now I have other problems. I have had grouped equipment into containers in such way that I put let's say two conditions into container, another two conditions into second container and then put both into a new container to have status propagation and possibility to unmanage the groups. To do similar thing, I created business services and try similar using script DCI threshold check. The problem is that on false result in script I've got two alarms, one on basic and another on parent business service, and I need only one. Can I somehow disable screen notification (and sound) of parent business service retaining red mark on icon? The second problem is that alarm is deleted in alarm browser view unlike infrastructure services object alarms, which are kept in alarm browser. There is also third problem, unmanaging the business service does not stops the alarms?!

Filipp, Firstly thanks for your response and Happy new year!!! You mention 3 things and I have reviewed this and am trying to better understand what I am missing.. In an effort to show you what I have I am adding an attached docx file that I am hoping you can open and review some screen captures. Netxms.docx   The Test that I do is: On the Server I Stop the Netxms Agent Service.   When I do this I see that the DCI for Internal Status goes from 0 to a number.   On Server A it goes to value 3 On Server B and every other server tested in the same manner it goes to a value of 4.  From what I can tell with my testing the Internal Status is calculated in some way when the Agent is not responding.  It is calculated differently for this one server as apposed to other servers.   I have taken a look at the Netxms database tables and compared Server A with other Servers and don't see anything that stands out.   Reviewing the dependencies you mentioned: Status of interfaces - Netxms Agent is not responding so Interfaces can't be determined. Severity of alarms present on the node - The DCI shows 3 in one case and 4 on all the other servers. (So severity is seemily different when it shouldn't be???) Value of CI that have "Use this DCI for node status Calculation" Checkbox set - We don't have that set on any of our Server Nodes so don't think we need this set.  I did set this on the server 1 server configuration to see what that would do and it didn't fix the issue.   Let me know if you would like to see any other additional screen captures to make this more clear.  Sincerely Thanks for any help you or anyone else can provide. ps.  I have access to the Netxms db and have check tables to see if there is anything that stands out as different and I don't really see anything.  My best guess at this point is that the Agent on Server A is behaving differently than the Agent on the other servers.  Not sure what is causing this and would like to fix it.  Thanks

I'm really sorry I forgot about the post Yes, if I open the same map on the old UI it works like a charm. Thanks

Hi! By "Client folder" you mean a container in object tree with all the nodes related to that specific client? What about history of DCIs on these nodes, do you also want to migrate it?

@alk said in New Android Managment Console: Hello. Yes, it in the works. Hello, Is there any progress on this?

Can you show screenshot of your gauge configuration and also the value of the DCI from last values?