NetXMS Support Forum

You are welcome to visit us on stand E164 from June 26 to June 29.

Best regards,
Victor

I suppose that you have option "process all thresholds" turned on. If this is the case then for all values in first four thresholds last threshold will also be activated. Then you will have two active thresholds, and when UPS goes back online, both will be deactivated, generating two UPS_ONLINE events. There are few possible fixes:
1. Do not use "process all thresholds" - it should work as expected without that option.
2. Use more complex condition for last threshold - exclude all explicitly checked values.
3. Use different deactivation event for last threshold.

Best regards,
Victor

I suppose UPS_ONLINE event is threshold based? If yes, can you show configuration of relevant thresholds?

Am I understand correctly that this problem is on all Cisco switches? What SNMP version you are using? If you are using version 3, make sure that you have allowed access to vlan-* contexts. Command should be similar to this:

snmp-server group GroupName V3 priv context vlan- match prefix
Best regards,
Victor

Finally it will be in 4.4 (to be released in June). Development is mostly done.

Best regards,
Victor

Hi,

configuration looks correct. We will test this and check if something is broken with the timers.

Best regards,
Victor

Hi,

definitely, should be available soon.

Best regards,
Victor

One possibility that I see is out of order execution of hook scripts which is theoretically possible. Server schedules execution of hook script in background thread pool, passing copy of alarm in its current state to the script. It is possible that due to database problems thread pool was full with tasks waiting on database, so earlier script execution task was waiting on free thread, next task was scheduled in the meantime, and then both were started in parallel, possibly in wrong order.
I will think about it, but probably we have to serialize executions of alarm state change hooks.

Best regards,
Victor

According to log server got two timeouts - at 09:57:18 and 09:58:23 (status=2 means timeout). Next ping was successful again. Do you think there was a possibility of network issues at that time that could cause loss of ICMP packets? Also, if you change poll count to 3 or 4, will it fix the situation?

Best regards,
Victor

Hi,

I suppose you mean Windows version, because on Linux platforms NetXMS uses whatever OpenSSL version is installed as system package. Current version shipped with OpenSSL 3.0.7, we will switch to 3.0.9 in next release (should be in June).

Best regards,
Victor

You should be able to do that with object tools. Create tool that will call a script, define necessary input fields, and when user will run the tool he will be asked for additional input. This input will be available in a script.
You can even create context dashboard and add those tools as action buttons.

Best regards,
Victor

This is normal behavior - for some reasons PDH reports temporary objects that cannot actually be accessed. You can safely ignore those errors.

Best regards,
Victor

Yes, we have that "sponsor" button on github

Best regards,
Victor

Sorry for delay, just get back to issues that piled up.
Looks like switch returns FDB information, so problem is within server. Can you set debug level 6 for tag "topology.fdb", run topology poll on switch node, and show me server log?

Best regards,
Victor

Currently it is not possible to inject topology information from hook script, but I see how that could be beneficial. Another option which I consider for some time already is to extend driver concept beyond SNMP, to allow SSH commands and possibly other protocols. This may help with reading VLAN information on Mikrotik switches for example, and probably lot of other cases with devices that have marginal SNMP support.
Added note to myself to think about it for one of next releases

Best regards,
Victor