NetXMS Support Forum

I have made some changes in reading LLDP information in upcoming release 4.4.1. FIrst of all there were few bugs left in reading LLDP-V2 MIB. Also, now server will use both LLDP-MIB and LLDP-V2-MIB if supported by device, and LLDP-MIB takes precedence. This should solve discovery issues.

Best regards,
Victor

Another option is to call functions by explicitly specifying script name. For example, if you have script

MIKROTIK::Update and function doUpdate within it, instead of doing
import MIKROTIK::Update;

doUpdate();

you can do

MIKROTIK::Update::doUpdate();

But wildcard import could be useful anyway, I agree on that.

First you have to setup notification channels - see this part of documentation: https://netxms.org/documentation/adminguide/event-processing.html#notification-channels
When notification channels are set, you can create actions for sending notifications.
Then you can add one or more rules to event processing policy that will trigger those notification actions.

Best regards,
Victor

New UI client accepts the following command line options:

-auto do auto-login
-server=<address> set server host name or address
-login=<login_name> set login name
-password=<password> set password
-ignore-protocol-version ignore communication protocol version mismatch
-dashboard=<name> open full-screen dashboard with given name after login
-kiosk-mode start in kiosk mode (only valid if -dashboard is provided, will not open main window)

Example:
java -jar nxmc-4.4.0-standalone.jar -auto -server=127.0.0.1 -login=admin -password=admin1

Best regards,
Victor

We plan to improve pinboard functionality. Saving view state definitely will be implemented. We didn't thought about rearranging items in pinboard, but I think it can be implemented as well.

Best regards,
Victor

Version 4.4 requires Java 17. Not our decision, unfortunately Eclipse RAP has switched to Java 17 in latest version.

Best regards,
Victor

NetXMS version 4.4 is finally officially released! It took some time and there were few unfortunate issues in the process, but finally we are here!

Changes since previous release:

-  "Trusted devices" in two-factor authentication
-  Scrollable dashboards
-  Native Modbus TCP support
-  Arguments can be passed to script called via script macro
-  Indirect function calls in NXSL
-  Interface table in agents
-  Linux agent can report interface aliases
-  Improved dashboard elements "Pie Chart" and "Gauge"
-  New macro {node-name} in DCI performance view configuration
-  Added Query table columns for SNMP Table DCI
-  Spanning Tree port state for interfaces collected at status poll
-  System event for STP port state change
-  Improved configuration import

Fixed issues:

-  NX-457 (Support for multiple tile providers)
-  NX-696 (Condition status reset to UNKNOWN on change)
-  NX-875 (More info on per-node basis on polls for that node)
-  NX-935 (Scrollbar in Dashboards)
-  NX-1014 (Correct names of "Remove" menu items to "Remove from node" or "Remove from template")
-  NX-1232 (Tool for simplified SNMP tables configuration)
-  NX-1598 (Rename column "submap_id" in table "object_properties")
-  NX-1613 (Object state icon not shown in Template -> Remove)
-  NX-2067 (Add a hotkey to save policies. Ctrl+S)
-  NX-2244 (Have ability in the UI to jump to specific DCI from check)
-  NX-2294 (Add server setting to prefer IPv4 address when resolving node hostname)
-  NX-2295 (Use System.ActiveUserSessions agent list to display "User sessions" in management client)
-  NX-2317 (Add parameters to threshold activation events with additional information on triggered threshold)
-  NX-2357 (Create events for invalid object identifiers in EPP rules)
-  NX-2364 (Add option to request 2FA authorization less frequently)
-  NX-2370 (Use libedit for shell-style tools)
-  NX-2372 (Show DCI comments in Data Collection / Last Values view)
-  NX-2373 (Make DCI comments available in alarms generated from threshold violation events)
-  NX-2384 (Store and display event message in active threshold)
-  NX-2391 (Not possible to set correct zone for cluster)
-  NX-2392 (ARP table view for nodes)
-  NX-2397 (Cluster that is in another zone still belongs to the zone with Zone UIN=0)
-  NX-2420 (Add explicit option for log parser to follow symlinks)
-  NX-2424 (Add information about user login failure (2FA issue, etc) to audit log)

Best regards,
Victor

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