NetXMS Support Forum

You can create scheduled task that will run NXSL script on any top level object ("entire network" or "infrastructure services"). In that script you can do something like this:

for(a : $object->alarms)
{
   a->terminate();
}

Alternatively you can use FindObejct(2) to refer to "infrastructure services" instead of $object - then you can run script in any context.

You can add additional logic to terminate only old alarms, etc.

Best regards,
Victor

Can you show full agent config?

Hi all!

NetXMS team is participating in FOSDEM 2024. You can catch us there today or tomorrow, or visit my talk on topology discovery in room UB5.230 at 12:10 today.

Best regards,
Victor

We just published patch release 1 for version 4.5. Changes since 4.5.0:

-  Driver for Edgecore enterprise switches
-  Driver for HPE Aruba Networking switches and wireless controllers
-  Chart height in performance view automatically adjusted to accomodate large legend
-  New NXSL class "MacAddress"
-  Attribute "state" of NXSL class "AccessPoint" renamed to "apState" (to avoid conflict with attribute "state" from parent class)
-  Context object views can be hidden
-  Configurable timeout for client session first packet
-  Improved VLAN handling by generic driver
-  Updated Eltex driver
-  Fix missing object synchronization for ad-hock maps (drill down)
-  Fixed server crash when interface list cannot be read from SNMP device and option to ignore interfaces in NOT PRESENT state is on
-  Fixed bug in EPP rule copying
-  Fixed line numbering bug in desktop UI script editor
- Fixed issues:
   -  NX-2491 (Add alarm category attribute to NXSL alarm class)
   -  NX-2493 (Activation / Deactivation event not shown in threshold editor)

Finally get to check this - works fine for me (using API token). Maybe the problem was in using password instead of API token.

I changed /rest/auth/1/session to /rest/api/2/myself for checking connection for the future though, as former URL supposed to be removed in the future.

Best regards,
Victor

I think that I found what could have caused server crash. Fix will be included in patch release 4.5.1.

Best regards,
Victor

Hi,

I've updated Nexus driver to recognize this model. Change will be included into next patch release.

Best regards,
Victor

NetXMS version 4.5.0 is just published. It is intermediate release on a way to version 5.0, and it includes improvements and fixes that are too big to be considered for patch release but important enough to be published before 5.0 is ready.

Full change list since version 4.4.5:

- XPath can be used for querying XML-based web services
- New NXSL operation "?." (safe dereference)
- New method "join" in NXSL arrays
- Server-side custom attributes (not visible by clients)
- Additional argument in NXSL method createSNMPTransport to control if it should fail when node is marked as unreachable via SNMP
- Updated drivers for Eltex and TP-Link switches
- Added agent metric Agent.LocalDatabase.FileSize
- Fixed internal metrics PollTime.\*
- Fixed issues:
   - NX-1409 (Implement separate access right for editing object comments)
   - NX-2275 (Option for ignoring interfaces in NOT PRESENT state)
   - NX-2412 (Separate access right for editing agent configuration file)
   - NX-2440 (Wildcard imports in NXSL)
   - NX-2485 (XPath support in web service queries)
   - NX-2487 (Any changes to object from UI or via Java API wipe out responsible users list)

Could you please explain where you configuring it and what exception are you getting? I have little experience with Tomcat, but I can check if I can adapt packages to it if I'll be able to setup test environment.

Best regards,
Victor

I have found the problem with classpath setting in JMX plugin. Try to replace jmx.jar on your system with this version: https://cloud.radensolutions.com/s/WDCCtmPKHXGZwyo.
If you installed agent on Linux from packages it will be inside /usr/lib/netxms/java.

Best regards,
Victor

Wildcard import implemented in current development branch and will be included in release 5.0 (and 4.5 if it will be publicly released).

Best regards,
Victor

NetXMS version 4.4.5 is just released. It fixes two critical issues: server crash on polling TP-Link devices (bug that was introduced in 4.4.4), and severe performance degradation when monitoring multiple (thousands) SNMP devices via single proxy.

Full change log since previous patch release:

-  Improved SNMP proxy performance under heavy load
-  Added limit on number of nested NXSL VMs (to prevent accidential infinite loop of script execution)
-  Fixed server crash on polling TP-Link switches
-  Fixed bug in dashboard element "status indicator"
-  Fixed bug in status map view
-  Fixed bug in database manager check function
-  Fixed "Failed to register resource" error in web UI
-  Fixed database import/migration to TimescaleDB
-  Java components switched to logback 1.3.13 (fixes CVE-2023-6378)
Fixed issues:
-  NX-2465 (List of saved queries in Tools->Find Object is not updated when query list is altered in Configuration)
-  NX-2479 (Misleading error messages when loading properties for root objects)

Should be as simple as running
nxdbmgr.exe init
from command line. It may ask additional information and will show result in console.

Best regards,
Victor

Rewriting Grafana plugin is in our pipeline, I hope we can make it in January or February.

Best regards,
Victor

We made a fix recently (in 4.4.x) for stalled client sessions from web API - that may fix this issue too.

Best regards,
Victor