NetXMS Support Forum

Hi Andrea,

It's not in the Admin Guide yet (I've opened a ticket to add it). For now the documentation is the README next to the extension itself: https://github.com/netxms/netxms/blob/stable-6.2/src/agent/extensions/vcenter/README.md

It's not a subagent - it's a Python agent extension (6.2.0 and later) built on pyvmomi. The agent starts the script and keeps it running, and the script polls vCenter (or a standalone ESXi) once a minute. Setup in short:

• Install pyvmomi on the agent host: pip install pyvmomi
• Add the extension block to nxagentd.conf and restart the agent:
  
  Code Select Expand
  *extensions/vcenter
Mode = spawn
Command = /usr/bin/python3 /usr/share/netxms/extensions/vcenter/nxagent-vcenter.py   # adjust to where your package installed it
Environment = VC_HOST=vcenter.example.com
Environment = [email protected]
Environment = VC_PASSWORD=secret

• Import the template vmware_vcenter_esxi.json and apply it to the node where that agent runs. It creates DCIs for every VM, host and datastore, with thresholds and alarms. It's in share/netxms/templates on Linux server installs, and also on GitHub: https://github.com/netxms/netxms/blob/stable-6.2/contrib/templates/vmware_vcenter_esxi.json

Hi, i saw on release notes that from the latest versions it is possible to monitor VMware via the vCenter SDK, but I cannot find any documentation on it.

thank you

Andrea

Hi,

Yes, Module = mcp enables it, and you'll want Module = aitools as well - most of the tools the MCP server exposes come from that module.

The module has no settings of its own. It adds the endpoint to the server's built-in HTTP listener, so port and address are set in the [WEBAPI] section of netxmsd.conf:

Module = mcp
Module = aitools

[WEBAPI]
Address = any    # default is loopback only
Port = 8000      # default

The endpoint path is fixed: http://<server>:8000/mcp (streamable HTTP transport). No separate web service is needed - the listener is part of netxmsd and enabled by default. Module = webapi only adds the REST API endpoints, MCP doesn't depend on it.

Clients authenticate with an "Authorization: Bearer <token>" header. Issue a persistent token in the user's properties, and give that user the "Use AI assistant" system right, otherwise requests get 403.

You're right that this isn't documented, ticket: https://github.com/netxms/netxms-doc/issues/87

Hi,

This is a bug in the server, not your configuration: https://github.com/netxms/netxms/issues/3682

Here's what's actually happening: when the node leaves maintenance mode, the server re-generates threshold events for every threshold whose state changed during maintenance. That's where your two "task running" events at 04:00 came from. Those events can be processed while the node is still flagged as in maintenance, and then they get correlated to the "maintenance enter" event, which is why they reference 8766568. By default, EPP rules ignore correlated events, so the rule that should terminate the alarm never sees them. It's a timing race, which is why it only happens sometimes.

Workaround until it's fixed: enable Accept correlated events on the EPP rule that terminates the alarm on OS_PROCESS_OK. As a side effect, the alarm will also be terminated when the task recovers while the node is still in maintenance, which is probably what you want anyway. If the same rule also creates the alarm, split it into two rules and set the flag only on the terminating one. Otherwise alarms will be created during maintenance too.

Hi,

Confirmed, this is a bug in the 6.2 management client, not in the server or your setup. Since 6.2.0 the Auto-link action sends an empty node list to the server, so it reports success and creates nothing. Layer 2 maps are not affected because their links are built by the server from topology data. Fix is tracked in https://github.com/netxms/netxms/issues/3681 and will be in the next 6.2 release.

Until then, "Link objects" still works, but it links two objects at a time and doesn't bind the link to interfaces.

Great! Thanks Alex.

it's fixed already: https://github.com/netxms/netxms/issues/3674

It seems that in some versions of Linux (Debian 13 tested by me, but others too...) /var/run/utmp is no longer available.

Some further context I found: https://lists.debian.org/debian-devel/2025/04/msg00014.html

The changelog mentions a new MCP server. I assume the module is enabled by setting `Module=mcp` in the configuration file. How do I set the port number and endpoint name? Is it necessary to enable the NetXMS web service on the server for the MCP server to work?
I couldn't find any information on this topic in the documentation, except for the AI tools.

Hopefully some more information will be helpful in resolving the issue. 
All of this is from the About NetXMS Management Client section.
The first block is from the old 6.0.5 version, the second one from the new 6.2.5 version.

Version 6.0.5

Connected to 172.20.20.20 (172.20.20.20) as admin
Server version: 6.0.5 (build 6.0-596-gda553d00de)
Java version: 17.0.19
JVM: OpenJDK 64-Bit Server VM 17.0.19+10
Operating system: Linux (7.1.5-76070105-generic)

Version 6.2.5

Connected to 172.20.20.20 (172.20.20.20) as admin
Server version: 6.2.5 (build 6.2-832-g5c3117069c)
Java version: 17.0.20.1
JVM: OpenJDK 64-Bit Server VM 17.0.20.1+1
Operating system: Linux (7.1.5-76070105-generic)