bug fixed. thank you

Check the tiny triangle next to Refresh button in the top of Mib explorer view. It hides the menu which enables the filter.

Hi Victor, I was a little busy last week. Here's what debug lvl 6 shows: 2020.03.30 02:48:51.256 *D* [poll.conf          ] Primary IP address 1xx.xxx.xxx.21 of node server08.domain.de [279] found on interface Microsoft Network Adapter Multiplexor Driver of node ilo-server08.domain.de [106297] 2020.03.30 02:48:51.256 *D* [poll.conf          ] Node server08.domain.de [279] is a duplicate of node ilo-server08.domain.de [106297] 2020.03.30 02:48:51.256 *D* [poll.conf          ] Removing node ilo-server08.domain.de [106297] as duplicate 2020.03.30 02:48:51.256 *D* [                  ] Deleting object 106297 [ilo-server08.domain.de] The problem is appearing at all of our ILOs after we decided to monitor their network. The servers are in a different network than their ILOs. The ILOs get found and then get deleted. e.g.: server08.domain.de has primary IP 192.111.222.21 an ILO-server08.domain.de has IP 192.111.100.8. Best regards Sebastian

Hello, i tried to import AOS-8.5-MIB.txt copy of file AOS-8.5-MIB.txt to /usr/share/netxms/mibs run command: # nxmibc -d /usr/share/netxms/mibs -o /usr/share/netxms/mibs/netxms.mib at the end there is no error but in MIB Explorer I cannot find any xirrus entry under enterprise OID .1.3.6.1.4.1.21013. Thank you for helping Rainer AOS-8.5-MIB.txt

Hey! I have recently used NetXMS and noticed that my template settings are being reset. I found this solution, but I did not find the ImportConfigurationOnStartup option. I found the ImportConfigurationonStartup option in the server settings, changed to Never and the problem persists. I did so that I duplicated some settings, e.g. CPU load, and deleted the default entry. Unfortunately, after about 24 hours, the deleted entry re-appeared, which means I now have two CPU load charts. I use the latest stable version, available on the website. Please help.

The Alarm looks like this: [image: Alarm-Fehlermeldungen.png] Most of the time every thing looks good and fine: [image: Last-Values-ok.png] The Values change to ERROR like this: [image: Last-Values-changed-to-error.png] It goes up and down all the time. --> The device (Lenovo host) definitely supports the OID --> In my opinion it can be due to the following:   - the device is currently unreachable but NetXMS hasn't worked that out yet   - the device is having a temporary issue dealing with the request Is there a possibility if there is a temporary problem with the communication, that NetXMS will wait until the communication is stabable? Or that NetXMS tests the result for 3 or 5 times (polling(???) and take the only one which will work fine. I hope anyone could help me. Thank you so much Rainer

Thank you.  I would suggest this information is added to the dialog box when you setup new Tools.  Thanks again for your help.  It does work as expected when I run nxmc!

You also could just enable SSL in tomcat like described here https://tomcat.apache.org/tomcat-7.0-doc/ssl-howto.html.

I'm a stupid newbie. I've tested the output from  executeSSHCommand with println and it cannot write an array. This works fine: ret = $node->executeSSHCommand("/opt/test/test.sh"); println ArrayToString(ret, "\n");  // prints all lines println ret[0];  // prints first line only

3.1.241 is displayed. This pointed me towards the culprit: /var/cache/tomcat9 had the old cached information, which I now purged manually, and everything works now. Never had this kind of issue when upgrading previously. Thank you.

Hello Wanted to check if that is expected behavior or bug. Node has most dcis from snmp and for ping there is ICMP.ResponseTime.Last. What happens when node is offline, snmp shows << Error >> but ping keeps still logging results every poll and displaying last value. Should it also show error when ping is not working ? Also node status remains critical not down. "use icmp as status" is checked

Is there a way to speed up deletion of objects? syncer.cpp appears to be deleting objects one at a time. In this particular case, we're removing many individual interfaces prior to deletion of the parent node. The time to delete each interface is approximately 1 second, and then the next interface is queued for deletion. Is there no way to batch the deletions so they happen faster?

Hi, make sure that other UPS software is not running when you try to monitor it via agent - otherwise COM port could be in use and agent may not be able to use it. Best regards, Victor

Bump Any update to this? Specifically for 'node down' as I still can't find a way to do that outside of the built in 'node-down' event I've managed to get alerts based on custom attributes working for other things such as SNR or Ethernet speed I.e. in the case of ethernet speed, I want alerts on any core/distribution equipment in our network running at 100mbit as 99% of the time that will indicate a wire has gone bad. However that other 1% are ones I don't care about, edge networks with no more than i.e. 20mbit/s of bandwidth. Or something we inherited from a company acquisition. So it doesn't matter, and I want to suppress the alerts So I just create my DCI's as I would. I set up thresholds like so... DCI - Ethernet Speed (reported in megabits/sec) Thresholds script  if ($1 < GetCustomAttribute($node, "Target_EthSpeed")) return true  activation event: slack alert (with relevant details)  repeat every 86400 seconds script  if ($1 >= GetCustomAttribute($node, "Target_EthSpeed")) return true;  activation event: sys_threshold_rearmed  repeat every 86400 seconds last polled value  <1000  activation event: send slack alert (with relevant details)  repeat every 86400 seconds If the custom attribute of 'Target_EthSpeed' exists, the first 2 are checked, and one of them will always trigger. The second one means it will never check the third one. So I can add Target_EthSpeed of 100 to a node If the custom attribute doesn't exist, it ignores those first 2 conditions entirely and will use the third, in which case if its less than 1000mbit/s it will still trigger an alert If there is a cleaner and more appropriate method i'm all ears. Either way I still need 'node down' alerts setup. As far as I can tell there is no DCI for 'node down' only 'node status' which isn't appropriate as the status code is shared with other events

Ah that does it.  Thank you!

print $node->productCode; should work. What version are you using?

Tried this out, produces new Errors and no Data where shown after this Change, so I think this original error is some kind of cosmetic problem

Thanks again, Filipp. That's quite interesting; I'm seeing an average of 10x more objects per node than in your examples. This could be due to device types, of course. I will see if I can determine relative counts for different types of objects.

As of v. 3.2. there's a bug on that matter. The thing is that when a node is discovered, an appropriate subned in created in "Entire network", having netmask of first found node. So it first found node had incorrect configuration (or if that node nad no netxms agent or snmp - in this case we can't get subnet from node and use /24) then subnet is created incorrectly (and this is not fixed due to the mentioned bug). It's not possible to edit netmask of a subnet, the way to fix this situation is: check if configuration of nodes is correct make sure your nodes are present in a container in "Infrastructure services". Otherwise nodes will get deleted on the next step along with DCI history. delete the subned from Entire Network it should recreate again after some time with correct mask

Those lines won't have switch name, only "FDB" prefix.