I have no idea what the difference is today verse two days ago but I found the agent is now working. Thanks!

Maybe related to this one? https://www.netxms.org/forum/general-support/problems-with-ping-subagent-after-update-to-v2-2-1/

Thank you  Rainer

Thank you, Victor! That was the problem! The rest of the install went without any errors.

Hi, as far as I can find, SMI keyword is non-standard extension used by SMIC compiler. You will get same error if you will try to compile it with net-snmp for example (and likely any other MIB compiler). You should only add MIBs that use standard syntax, not compiler-specific extensions. And it is recommended not to add those already provided (as RFC1155-SMI or SNMPv2-SMI for example). Best regards, Victor

Update... Changing the transformation script to this works return int64($1) / (1024 * 1024);

Hi, please enable logging to file (by setting LogFile = some_file in netxmsd.conf), set debug level to 9 (by setting DebugLevel = 9 in netxmsd.conf), try to start service, and post log file here. Best regards, Victor

Hi, we just moved our repository to github (https://github.com/netxms/netxms), so if you are familiar with it you can clone it, edit messages_<lang>.properties and bundle_<lang>.properties files (for example: https://github.com/netxms/netxms/blob/master/src/java/netxms-eclipse/AgentManager/src/org/netxms/ui/eclipse/agentmanager/messages_de.properties - German translation for agent management plugin), and submit pull request. Alternatively, I can create a package with all language files extracted so you can fix translations and submit back. Best regards, Victor

Hi Victor Thank you for the patched versions. I already tested on Win2012R2 and Win10. Success! I will deploy it now to the other devices where PING subagent is used. best reagrds Dani

Hi, are you sure that hostname will be resolved correctly? You may try to use %a macro instead that will be expanded into node's primary IP address, or reference to node by name using @%n construct (which is the only option if you are using agent-to-server connection). Best regards, Victor

Thanks it works

Thanks for the response Victor Seems like a lot of additional scripting is required to get close to the sort of notifications we would like I don't mind adding scripts if they are easy to manage and change and I can write a very simple guide on how to do so for our other staff - we don't all have time to learn netXMS scripting language and how/where to change values. And we don't want to be spending a significant portion of our time monitoring the monitoring system... Since we will have multiple types of alarms (node down, low snr, station disconnect etc etc) we don't want to have to change 100 scripts if we decide to change our notification schedule Can we execute actions from within a script? And therefore would something like this be the best way to manage this? In Actions Configuration, edit 'Slack Notification' and change it from 'send SMS' to 'Execute NXSL Script' and type in script name "CheckScheduleTime" Go to Script Library, create script 'CheckScheduleTime'. Add something like.... NotiStart = 6; NotiEnd = 22; now = localtime(); if (now->hour >= NotiStart && now->hour <= NotiEnd) DoAction("Push Slack Notification"); Create another action called 'Push Slack Notification' and set this up to send Slack SMS This way everything under 'event processing policy' can be set up with just 1 action of 'Slack Notification', that calls a script which checks relevant time, that calls the action which actually makes a slack notification. Then if we change our time (i.e. go on holidays and want to disable it) we don't have to edit every single action in 'event processing policy'. We only have to change the time in the "CheckScheduleTime" script. Is that correct?

Hi, from my experience it's usually done via VPNs to remote sites. In many cases we seen Raspberry Pi or similar devices acting as both VPN gateway and proxy agent for remote site. Best regards, Victor

Hi, it seems like a bug to me. Could you provide more detailed information about one such device (how it looks like in the system, log file parts and events related to that device)? Best regards, Victor

Hi, is it an option to upgrade old server to the last version first? It should simplify migration. Alternatively, you can try to upgrade export file directly (although it may fail) - it is essentially an SQLite database, so you can set your netxmsd.conf to be like this: DBDriver = sqlite.ddr DBName = /path/to/export/file and run nxdbmgr upgrade. Then revert netxmsd.conf to correct settings and try import again. Best regards, Victor

In server console or nxadm -i, show stat This will show # of objects, nodes , and DCI's

HI twenrich, Thank you!!!! this is a great script, should be standard in the package!!!! The only thing I have noticed is that for some reason, when I add in extra services to 'ignore' it still shows them AdobeUpdateService and alike but am sure that is something I have done / not doing. ty

Hi all, I have a WMI DCI that pulls the Dell service tag from the windows machines running the netxms agent. WMI.Query(root\cimv2,select * from Win32_ComputerSystemProduct,IdentifyingNumber) This number is generally not what is entered when calling up support, they prefer the DTMF friendly Express Service Code that is a numerical version of the Service Tag (easier to type on number pad). I've found a couple of links that describe the service tag as a base-36 number [A-Z][0-9] that you just convert to decimal. http://creativyst.com/Doc/Articles/HT/Dell/DellNumb.htm https://serverfault.com/questions/589774/how-to-convert-a-dell-service-tag-to-an-express-service-code What is the best way to do this in NetXMS? Do I create a DCI that takes the same WMI query and uses a transformation script to convert the number?  Is this possible in NXSL with base36 conversion to decimal? Or if NXSL can't handle arbitrary bases do I have to use an external Python/nxshell script to do the conversion and call that from a DCI? My goal is to get it represented as a DCI to display on the object details tab and in DCI summary tables. Thanks for any suggestions.

Hello Tatjana, team, I can confirm that "Remove this template automatically when node no longer passes through filer" option is selected. Thanks for pointing my mistake out. I will check if this is the issue here and will update. Best regards, Adrian

Thanks for quick response, great.