NetXMS Support Forum

Just to clarify - you mean you have created VPN or VLAN interface on Mikrotik device, and it is not visible in "Interfaces" view?
One note on newly added interfaces - they will appear in NetXMS after next configuration poll. You can manually force configuration poll by selecting Poll -> Configuration from node menu.
If new interface did not appear after configuration poll, please provide more specific details on interface type and how it is configured in Mikrotik so we could reproduce the issue.

It's either something is still missing in the configuration, or there is firewall or connectivity issue.
Can you share screenshot of your network discovery configuration?
Also, note that discovered nodes will appear in "Network" perspective with default configuration. To make them appear in "Infrastructure" perspective you have to create containers with auto-bind filters.

Just published 6.0.3 - it should have the fix.

Today we have published patch release 3 for version 6.0. Changes since previous release:

- Added wireless controller bridge for Aruba Instant controllers (PR #257)
- Improved interactive SSH mode support
- Improved web API
- Windows agent renames in-use files during upload if they cannot be replaced
- Fixed incorrect handling of empty tool call list in LLM response
- Fixed bug in database schema upgrade on Microsoft SQL Server
- Fixed issues:
   - NX-2369 (Option to add number of items in a container)
   - NX-2867 (Disable "Create database and database user before initialization" if SQLite selected in Windows installer)
   - NX-2922 (New agent actions: enable / disable ExternalMetricProvider)

I've found the issue. When no tool calls needed, your model returns tool_calls as empty array, but server code only checks for missing or null tool_calls. Just fixed that, upcoming patch release should work as expected.

Quote from: johnnyva on February 23, 2026, 11:42:37 PMHey Victor will the change in idata/tdata timestamp to millisecond impact the REST API or NXSL dci values? i.e. will we see millisecond timestamp there as well or will we only see change in db?

New REST API (webapi module) - it is using ISO 8601 format for timestamps which allows milliseconds (although 5.x did not set millisecond part), any decent ISO 8601 parser should handle milliseconds correctly.
Old REST API (Java app) - should be unaffected.
NXSL - all timestamps for collected data are now in milliseconds.

Best regards,
Victor

I notice that it also missing prompt files. They are here: https://github.com/netxms/netxms/tree/master/src/server/aitools/prompts

Yes, that's a bug in Windows installer. We plan to publish patch release 6.0.3 today or tomorrow, it will have skill files included.
In the meantime, you can try to place them into correct folder manually. All skill files can be downloaded from here: https://github.com/netxms/netxms/tree/master/src/server/aitools/skills

We just published patch release 2 for version 6.0. Changes since previous patch release:

- Added wireless controller bridge for UniFi controllers (PR #255)
- Small fixes in background conversion of collected data
- Improved AI assistant guardrails
- Added internal metrics for monitoring AI providers usage
- Added TLS support in web API using monitored reproxy process
Fixed issues:
  - NX-1658 (Drag and Drop confirmation prompt)
  - NX-2495 (Do not treat disk I/O error as file rotation in log file monitoring)
  - NX-2900 (Business Service check script editor should have hint)
  - NX-2907 (ssh.nsm can not be loaded on Windows)
  - NX-2913 (Cluster DCI is not populated to nodes under cluster)
  - NX-2919 (Push DCI from agent log parsing may come in wrong order)
  - NX-2925 (Proxy selector should show only relevant objects)

Show your netxmsd.conf please.

Can you show virtual and physical memory consumption for netxmsd process specifically?

Just published version 6.0.1 that should address database upgrade issue. Now it does not convert data immediately, but do this in background while server is running, in chunks by 24 hors, so you should gradually get your collected data back, starting from most recent.

So, we just published patch release 1 for version 6.0. It mostly addresses critical issues with database upgrade. Full change log is following:
-   Improved database upgrade procedure (no long data conversion during upgrade)
-   Agent environment can be set from server using custom attributes
-   Fixed object names not resolved on "Dashboards and Maps" property page (showing object IDs instead of names)
-   Fixed missing action list loading in Event Processing Policy editor
-   Fixed business service uptime calculation for business services containing other business services
-   Fixed database upgrade procedure failure on Microsoft SQL Server
-   Added support for Anthropic API for AI agent
-   Implemented changes proposed in PR #155 (IP address wipe on DNS resolution failure and DNS resolution conflict detection)

Quote from: batnator on February 09, 2026, 05:36:05 AMThank you for the new release. Is it possible to again provide a statically linked binary of the agent for Linux x86_64 as a download (like nxagent-5.2.8-linux-x86_64-static.tar.gz)?

I think yes, we will bring those back in a few days. Can you explain a use case for those? I'd think that nowadays agents mostly deployed from deb or rpm packages.

I'm looking into it. We expect to have patch release 6.0.1 with improved DB upgrade on Monday.