NetXMS Support Forum

The software is split into several packages, to avoid pulling dependencies for things that are not needed. MySQL subagent should be in netxms-agent-mysql package, and you also might need netxms-dbdrv-mysql.

Должно быть в самом последнем релизе

By NET-SNMP you mean that these devices are computers and net-snmp package is used to provide snmp daemon? Or netxms snmp driver is GENERIC?
Can you provide screenshot of Overwiew page for such device? What are these devices, what producer, what models?

One more question for clarification - in node properties -> Communication in Primary host name field you have IP address or hostname?

Looks like documentation is not clear on this - this metric is collected from NetXMS agent. 

Origin should be set to "NetXMS Agent". 
This DCI should either be on the node where an agent is running, or node with agent should be specified in "Source node override" field. 
Agent that is used should have netsvc subagent enabled.

1. On what exactly version of NetXMS this is happening? 
2. Whare are the capabilites of such node (visible on the Overview page)
3. Do you have network discovery enabled? Can you show screenshot of network discovery configuration?
4. Does NetXMS obtain mac addresses for these nodes (visible in Interfaces tab of node)
5. Do these machines have static IP or they get IP address via dhcp?
6. In configuration->Server configuration what are the values of the following parameters:

Objects.Nodes.ResolveDNSToIPOnStatusPoll
Objects.Nodes.ResolveDNSToIPOnStatusPoll.Interval
Objects.Nodes.ResolveNames
Objects.Nodes.SyncNamesWithDNS

Ability to bind subnets to containers is a rarely used thing and was forgotten when features were moved to the new client. I'll get back when I have some information from developers on this.

It's kinda a rare case to use color zones with values exactly on the edge of zones. The logic seems to be, with your settings, that:
left red is from 0.0 till 1.0 (including it)
left yellow is from 1.0 (excluding) till 2.0 (including)
but on the right it's opposite and red stars from 3.0 (including) and till the end of the dial, which is again 3.0

Just use 3.01 for right yellow and red zones

Quote from: BigBlue on June 17, 2024, 12:44:21 PMHi,

When will version 5.0 be available for RHEL-compatible distributions ?

thanks a lot

Yes, there's a delay preparing the release

Yes, definitely a bug

Node for the management server should get automatically created when server is started. This node would have special attribute set, you can check it by running NXSL script:

println($node.isLocalManagement);

Based on the presence attribute out of the box templates would be applied.

The templates can be found here: https://github.com/netxms/netxms/tree/master/contrib/templates
Specifically these two files:

netxms_agent.xml
netxms_server.xml

This feature was added, will be included in next patch release

Do you use desktop client? Old or new?
What is ping time from client to the server?

This was fixed, fix will be in next patch release (should be out within a week or so).
Pls report, if you find similar issue with other things besides graphs.

I mean that coordinates set in map properties correspond to what's in the upper left corner of the map. So e.g. if I take latitude 51°30'N and longitude 0, I'll have London in the corner of my map.