Thanks for the help, I will do a test with the script

Bump, any idea?

One of the groups in my object viewer has the "unknown" status symbol, I can't seem to figure out why this is. It's reachable by NetXMS, status polling is enabled, none of the checks are giving me any problems. [image: hhu139.png] Polling the status manually doesn't change the status either

answer in russian (sorry for bad english, it's just a quick and dirty translation - I'll update it later) You can use add custom performance counter to agent's config. Configuration sample, add this to nxagentd.conf: *WinPerf Counter = DiskWriteBytes:"\PhysicalDisk(_Total)\Disk Write Bytes/sec":60:A:INT:Average number of bytes per second written to disk for last minute "*WinPerf" - section name "Counter" - counter definition. Format:     Counter = ParameterNameForNetXms:"\PDH\Counter\Name":SamplesCount:Queue:Type:Description "ParameterNameForNetXms" - this name you will see in management console, in DCI configuration "\PDH\Counter\Name - Counter name, e.g. "Memory\Available Bytes". "SamplesCount" - number of samples taken for calculation of average value "Queue" - querying queue, it can be: A, B or C. A - counter will be read every second, B - every 5 seconds, C - every 30 seconds. Example: if you will set SamplesCount to 60 and queue to A, this parameter will return average value for last minute. count=30 and queue=C - this will be average for 15min.

Your third option sounds the best Giving the specific interfaces that you do not want to monitor on nodes an attribute which would stop their "network range" from being created -------------------------------------------------------------------------------------------------- This is an example of what would work nicely: I add a router with two ports, one LAN port and one DMZ port, the LAN port runs at 192.168.130.* and the DMZ runs at 192.168.210.* Now after the router has been added, both ranges are created in the object viewer. I select the DMZ port of the router and select the option "Ignore for topology" , now I delete the 192.168.210.* range from NetXMS, I do a configuration poll on the router and the DMZ port is not added again.

Great, thank you

Currently it looks normal (except for DCI queue time peak - it can be caused by high CPU load at the moment or excessive number of simultaneous polls - you should watch if it will happen again). In any case, single peak is not an indicator of problem - problem is when these parameters instantly high. For performance - from my experience, MSSQL performs better on large database. But maybe I just don't know how to tune MySQL... Best regards, Victor

Crashes when copying to the clipboard appears to have been fixed  The window title problem still exists unfortunately (https://www.netxms.org/forum/index.php/topic,330.0.html) The problem occurs with both physical and pdf printers. I just tested with one predefined graph , 3 different drivers and 2 different printers and 2 nodes. Node1: PCL PCL6 and PS drivers work perfectly on printer 1 Printer 2 also prints perfectly , running 0.2.21 Node2: PCL PCL6 and PS drivers print an entirely black graph on printer 1 printer 2 gives the exact same output, running 0.2.21 Also did a reinstall of the console on node2 It does appear to be a NetXMS problem    I don't know what's causing this, I've tried pretty much all I can try.

Hi Victor, thank you again for the quick reply. I thought that a configuration poll will update the device name. Nice to have, but not really important. It's ok for me to delete the devices I have renamed. At the next discover they are found correctly. Greetings Tom

As attachment you see the map how it looks at my network. Just as an information for you Scale 1:4 Btw: I played around with more maps in the latest release - but unfortunately there are no links between the devices, or I didnt check it I will wait for the next release and then post again. Greetings Tom [image: netxms_map.jpg]

I'd set something like "average >= 10 for last 5 polls"

this modify hashes of source package

So, it means database inconsistency - object id exist, but it has no properties set. Such inconsistencies supposed to be cleaned up by nxdbmgr, but unfortunately I just check it and it has a bug and doesn't check templates. I'll fix that. Currently, you can just do the following queries: DELETE FROM templates WHERE id=412 DELETE FROM dct_node_map WHERE template_id=412 DELETE FROM items WHERE node_id=412 to clean up. Or leave it as is - it doesn't affect anything except annoying message in log on startup. Best regards, Victor

Please check this thread: https://www.netxms.org/forum/index.php/topic,131.0.html

Oops.... find old topic and solved issue by nxmibc -d . -z   

Thanks so much. It was good for me. Best Regards, Terry

Thanks, that did the trick.

Great 

Great, just made policies for them

Great! This appears to be working perfectly