Preferably you should use not $node->isPrinter or !$node->isPrinter although your form will work too, because isPrinter will contain boolean value TRUE or FALSE, and if it is false then isPrinter != TRUE will produce expected result. Best regards, Victor

Thanks to Victor's help, all this required was some tuning on the NetXMS server.  Turning on parallel processing and increasing the Discovery.BaseSize from 1 to 8 seems to have helped immensely.  The root cause seems to be the large number of subnets we had on our Default zone.  It couldn't keep up with the discovery process for subsequent zones. I am now having an issue with discovery filters.  We want to only add devices that have SNMP enabled or the Agent installed.  However, when we turn these filters on in 3.7.116, nothing gets added.  If I restrict it to active scan only on a single test IP, and then turn off all filters, the device with agent gets added as expected. If I check debug logs on the proxy agent, it does ping the device but never seems to try to connect via SNMP or Agent. What it looks like is that if the filter is set to SNMP or Agent only, it only attempts a ping scan and since it hasn't seen it so far as an SNMP or Agent device, it doesn't bother scanning (a Catch 22). -Zeb

Hi, Thank you for helping. The problem was, that i use 1 node for HP iLO which has 8 Network Interfaces, one of the Network interfaces has the same IP Address of the ESXi VMWare Host which is installed on this Server. So the IP-Adress is a duplicate and the new Node was deleted. I changed the Server Property to: NetworkDiscovery.MergeDuplicateNodes = 0 Now I think it works! Thank you so much for helping! Bye Woody

It is not possible to configure server to use only SNMP sysName for resolving node name. However, you can synchronize node name with SNMP sysName by adding the following code to configuration poll hook script: if (($node != null) && $node->isSNMP && ($node->name != $node->snmpSysName)) { $node->rename($node->snmpSysName); } It will update node name according to SNMP sysName on each configuration poll. Best regards, Victor

Hey, there. When I upgraded to NetXMS server 3.7 from NetXMS 3.6 the computer screen sent the following message: Setting up netxms-agent:amd64 (3.7.116-1) ... Setting up netxms-server:amd64 (3.7.116-1) ... NetXMS Database Manager Version 3.7.116 Build 3.7-116-g133064d484 (UNICODE) Upgrading database... Database is locked If you want to upgrade netXMS server succesfully, please type: nxdbmgr unlock Then nxdbmgr upgrade Finally sudo systemctl start netxmsd P.S. It works well with Desktop Managment tool 3.6 so far. My best wishes Jose

Calling for the instance as a variable in the action is what I was missing. That did the trick, thanks!

Nexus devices are monitored yes.

Hi, I see that database writer queue is quite high (5721598 in log file you've sent). Try to monitor it for some time (you can use internal DCIs on server node or debug console command "show queues"). If it is constantly growing it may indicate database performance issue and can cause excessive memory consumption (because more and more data kept in memory). Best regards, Victor

The filtering script would completely suppress additional alerts though, correct? I still want to see every matched string because they will contain unique information, but if two of them occur in the same log file back-to-back, I'd like it grouped into a single email. I will have to do testing with the DCI checking log file modification time and see if that works for me.

You can set expected states of interfaces to "IGNORE". This could be done automatically from HOOK::ConfigurationPoll - it's a script that is launched on each configuration poll. interfaces = GetNodeInterfaces($node); foreach(i : interfaces) { SetInterfaceExpectedState(i, "IGNORE"); } Obviously you need to add some filters - you can check if node has agent ($node->isAgent), etc.

Hi Filipp, @filipp-sudanov said in failed to start netxms-server.service: try deleting libraries that were installed by older version, these are libnx* libnetxms* files in /usr/local/lib/netxms and /usr/local/lib then make & make install again This worked perfectly, thank you!

Netxms updates on linux are available, only support for jessie was dropped, that's why it's stuck on 2.2. Currently supported are Debian 9 (Stretch) and 10 (Buster) so you might need to upgrade the OS. Upgrade of NetXMS most probably will happen automatically, but it's strongly recommended to do it first in testing environment and have DB backup/snapshot prior to upgrading.

MIB files only provide a more convenient way to work in MIB explorer. SNMP driver is selected from a number of drivers present in the system. List of drivers is available in docs: https://www.netxms.org/documentation/adminguide/snmp.html?highlight=snmp driver These drivers provide special handling for some devices that are not handled well by generic driver.

Hi! as discussed in another thread, under linux logger utility could be helpful to generate syslog messages A matched syslog line generates an event, so we have to do the logic in Event Processing Policy (EPP). There you have filtering script - if it's not empty, event will be processed further only if that script returns true. You can just take current time in that script and check it: now = localtime(); return (now->hour >= 8); I am not exactly sure how to use the repeatCount in syslog processing, but anyway reaction to syslog only happens when a new syslog message is received. Here we need something in another place that would be executed regularly, event if there will be no syslog messages from a given node. A possible approach could be: when you receive backup successful message, store current unixtime in custom attribute of the node. You can do this in filter script in EPP: $node->setCustomAttribute("lastBackupTime", time()); create a DCI with origin "Internal" and parameter "Dummy". in transformation script add the following: return time() - $node->getCustomAttribute("lastBackupTime"); as the result this DCI will have time in seconds since last backup. add threshold so that an event will be generated when time since last backup is too big.

That makes sense! You don't actually have to have the agent installed, but it does need to be a node in NetXMS.  You should be able to use SNMP and not strictly have to install the agent.  However, the agent does give you a lot more control over the node.

Hi Victor, the systemd setting was the problem. Thank you.

Hi, there is open change request for that: https://track.radensolutions.com/issue/NX-1826. Hopefully will fix it soon. Best regards, Victor

Hi, latest agent versions do store syslog records and SNMP traps in local database (since version 3.4). Best regards, Victor

Hi Victor, thank you for the confirmation that it is an error and for the workaround.

Thanks Alex,  It has been chugging along nicely for years and I'm sure there is more old stuff in there that I have long forgotten about. Regards, David