NetXMS Support Forum

In new REST API (the one loaded as server module) you can do POST on endpoint /v1/objects/{object-id}/set-managed where {object-id} is ID of interface object and content is JSON
{
   "managed":false
}

For old REST API (the one implemented as Java web app) request body will be the same but URL will look like /objects/{object-id}/set-managed

Best regards,
Victor

Agent configuration filter does not provide access to node object - because it is just a request from certain IP and not necessarily matches already known node (although probably it will be good idea to implement such lookup). However, you can implement such lookup yourself, for example (I assume version 5.x):
node = FindNodeByIPAddress($1);
return node?.name?.startsWith('db');
This script will return true if requested IP address corresponds to existing node and name of that node starts with "db".

Best regards,
Victor

For version 5.x script GetContainerName could look like this:

for(p : $object.parents)
  if (classof(p) == "Container")
      return p.name;
return "";


Hello everyone!

NetXMS Talks webinar is back — this Thursday.
We're going live on April 24 at 16:30 Riga time (EEST / UTC+03:00) — don't miss it!
This time we'll cover new things in NetXMS 5.2:
- New features in NXSL language;
- Built in Interface traffic template;
- Fan-out diver for ClickHouse.

Join us live or send your questions to [email protected] if you can't be there in person. There will be a recording of the webinar on our YouTube channel shortly after.

Link for joining live streaming: https://events.teams.microsoft.com/event/2b069dca-252d-42b4-9e9e-b9b493940c1c@c9cf5896-fa72-44b6-8d57-8742ad2b4e6e?fbclid=IwY2xjawJ1lLpleHRuA2FlbQIxMABicmlkETBPelVQa2VsQkg3MjdHTWFOAR7zE865VVIEvsyNIUJGucfc83Q36SkYrJ0h1a8FZoeSmUE-elLSbQpc4oOjag_aem_6B8f8DSOr9D8iRl2KPiVKQ

We just published first patch release for version 5.2. It addresses few important issues found in 5.2.0. Full change log is following:

- NXSL function PostEvent accepts any event source object
- Added option to set in maintenance all objects under Wireless Domain
- InfluxDB and Clickhouse drivers can be configured to use custom attributes of DCI's template
- Fixed bug in driver for Cambium CnPilot devices
- Fixed database connection leak during package deployment
- Fixed issues:
   - NX-2600 (Threshold for missing table instances never deactivated)
   - NX-2723 (Add Web API endpoint for object maintenance)
   - NX-2729 (Display hints for hook scripts in script library)
   - NX-2734 (When exporting event processing policy rule, automatically add referenced actions)
   - NX-2735 (Cannot delete user from object access control list)
   - NX-2740 (Modbus DCI becomes unsupported when proxy is unreachable)

Hi,

could you please provide SNMP walk output for 1.3.6.1.4.1.2636.3.40.1.5.1.5.1 and 1.3.6.1.4.1.2636.3.40.1.5.1.7.1 for this switch?

Best regards,
Victor

We just published NetXMS version 5.2.0. Changes since previous version:

- User-defined tags on data collection items
- Network maps can be shown in object's context in a same way as dashboards
- Improved package deployment
- NXSL math functions Min, Max, Average, MeanAbsoluteDeviation, and StandardDeviation accepts variadic arguments
- New NXSL function Math::Sum
- New NXSL array method indexOf
- Simplified loops over numeric ranges in NXSL using class \"Range\"
- Unicode escape sequences in NXSL string literals
- Script entry point can be given for script DCI
- Dot can be used as script entry point separator instead of slash
- Fan-out diver for ClickHouse
- Fixed direction and arrow size for Network Map links
- Reworked Network Map link label location calculation for multi link connection
- Configurable values for RADIUS authentication request attributes Service-Type and NAS-Identifier
- SM-CLP protocol support reworked and switched to SSH as a transport
- Fixed incorrect data and occasional server crashes in network discovery filter script
- Fixed issues:
   - NX-74 (New node options - "expected capabilities")
   - NX-1301 (Automatic traffic DCI linking to interface)
   - NX-2654 (Add agent running config object tool via db migration script)
   - NX-1302 ("Traffic" overlay for maps)
   - NX-2568 (Add case-insensitive versions of threshold operations "like" and "not like")
   - NX-2624 (Review SMCLP data source and switch it to SSH)
   - NX-2662 (Show map in tab on object)
   - NX-2667 (Context dashboard should be able to pick DCIs from child objects by specific DCI tag)
   - NX-2668 (Change all server configuration variables related to polling intervals to be modifiable without server restart)
   - NX-2680 (Add NXSL function Math::Sum)
   - NX-2681 (Add array method "indexOf")
   - NX-2686 (Put DCI to ERROR state if it's transformation script has compilation error)
   - NX-2689 (Add event ID (if available) to notification log)
   - NX-2694 (Add "front side only" property to rack objects)
   - NX-2695 (Fit rack image into the view both vertically and horizontally)
   - NX-2703 (Support Unicode escape sequences in NXSL string literals)
   - NX-2707 (Add method "createSensor" to container object classes in NXSL)
   - NX-2716 (Agent metric that reports server's access level to that agent)
   - NX-2721 (Add $ipAddress variable of class InetAddress in Hook::AcceptNewNode script)
   - NX-2725 (NetXMS does not fallback to secondary proxy nodes)
   - NX-2728 (Update interface configuration when a node with an agent is rebooted)
   - NX-2732 (Server attempts TCP ping for nodes behind proxy)

можно попробовать после падения дать такие команды в gdb:

frame 4
print m_name
print m_id

должен напечатать имя и ID ноды

Похоже что там какое-то устройство, которое дает ответ на SNMP запрос, но при этом там не все OIDы. Я добавил дополнительную проверку на наличие всех полей в ответе (коммиты 301b0d140f в 5.2 и f06eead655 в 5.1), в следующем релизе будет.

We just published unplanned patch release 5 for version 5.1. It fixes few critical issues discovered since patch release 4, and intended for those who is not ready to upgrade straight to 5.2.0 (which should be published tomorrow). Full change list since version 5.1.4:

- VNC detection during configuration poll can be disabled
- System access rights included into user ACL report
- Fixed bugs in NXSL script conversion to V5 format
- Fixed file handle leak in SSH subagent
- Fixed bug in configuration export
- Fixed issues:
  - NX-2712 (Scripted thresholds triggers activation event repeatedly)
  - NX-2714 (Status of interface not propagated to circuit)
  - NX-2726 (Web API call causes server crash)

We just published patch release 4 for version 5.1. Changes since previous patch release:

- Agent uses Windows Installer API instead of launching msiexec.exe for installing .msi and .msp packages
- New Windows agent metric System.IsRestartPending
- Improved server performance when launching multiple external actions
- MIB Explorer added to "Tools" perspective
- Fixed incorrect parsing of 32 bit agent installer names when adding package to package manager
- Changed IPv4 address parser - now it only accepts canonical form (4 decimal numbers separated by dots)
- Correct handling of network mask /31 on peer-to-peer interfaces
- Node sub objects like Interface will not be shown on Infrastructure perspective if they do not have parent shown in the same tree
- Added dBm and rpm DCI units to no multipliers list
- Fixed tab priority for multiple built in views
- Fixed problem when newly added DCI were not shown on Network Map (links, DCI containers)
- Fixed broken autobind during node configuration poll
- Fixed issues:
    - NX-2645 (Remember perspective splitter position)
    - NX-2684 (Remove hardcoded license id from the nxlicmgr)
    - NX-2690 (Migration from Timescale to regular Postgres fails on win\_event\_log table)
    - NX-2696 (View options in Data Collection does not show actual state of Use Multipliers checkbox)
    - NX-2699 (Show value of os.name in nxmc's About dialog)
    - NX-2701 (Automatic DB unlock fails because GetLocalIpAddr() may return different address)
    - NX-2705 (NXSL split string with trim option)
    - NX-2711 (scheduled_tasks column is out of range for type integer)

There is flaw in subnet object creation logic - server ignores /32 on interfaces, but not /31. I just fixed that, now /31 on peer-to-peer links are handled correctly. Fix will be included into upcoming patch release.

Best regards,
Victor

Implemented in upcoming 5.2. Both are configurable via server configuration parameters RADIUS.NASIdentifier and RADIUS.ServiceType.

Hi!

From stack trace it looks like netxmsd run out of memory. Can you please show chart of memory consumption by netxmsd?

Best regards,
Victor

Hello!

Is it possible to show (or post to me via PM) exact output of "failed record" message?

Best regards,
Victor