NetXMS Support Forum

Hi,

after updating NetXMS to the latest version, I get a lot of alarms because of unsupported DCIs (see attachment 1).
I had this once in the past and was able to fix this by setting the "ImportConfigurationOnStartup" setting to always. This time it doesn't help.
Any suggestions?

Best regards

Stefan

Hello.

These metrics are provided by the netxmsd itself, and they are from the template System/NetXMS Server/Thread pools.
Template is applied based on the $node->isLocalManagement flag, which is always set by the monitoring server.

So the only possible cause for this I can imagine is that this node was server's node for some time, then server was started on different node (e.g. high availability setup with active/passive nodes).
Template is removed on the configuration poll, so it will remain active for a while - hence the alarms (which should be automatically terminated, if I recall correctly).

Check following:

1) is this node your active netxms server?
2) does it have isLocalManagement flag set? (right click on the node -> Execute server script -> "println($node->isLocalManagement);")
3) what happens with these metrics if you force configuration poll on this node?

Hi Alex,
thanks for Your reply.

Here are my answers:
1) It is the active server (we only have one)
2) I think no. The command returns false. Please see the attache screenshot.
3) I did the poll today, let's see if the alarms come back tomorrow

Some additional info that I think might help.
- After terminating the alarms they come back the next day.
- In addition to the update, the NetXMS installation was moved to a new server.

Best regards

Stefan

Hi,

the alarms are back, so the Cofiguration Poll had no effect. So I think it's the "isLocalManagement flag".
If I understand You right, is has to be true if this is the active NetXMS server. How can I set it to true?.

Regards

Stefan

Any idea? Do You need more informations?

Best regards

Stefan

Hi,

isLocalManagement flag is set automatically. I suggest to find node that currently holds management server flag using object query or NXSL script, delete it, then set server configuration parameter RoamingServer to true and change primary IP address on node that should be local management server to 127.0.0.1. That way management node will be fixed.

Best regards,
Victor