NetXMS Support Forum

When I status poll an unmanaged node, I get a "Node is Connected" but node status remains unmanaged - however - what I am looking for is if the node is now in a state that I can manage it again. The Status poll does not tell me that - at all.

I went low tech and simply added a tool called ping - local command - ping %n - and I use that as my status poller instead. I have a second one which pings from NetXMS server which I use alternatively, depending on where I think the issue might be.

Next thing is to add is a snmpget of the sysdesc to the tools so I can see if I get SNMP responses as again, Status polling does not trigger polling if it thinks node is unreachable.

Unmanaged is for nodes that really are unmanaged. They are not polled for anything and don't change status.
Unreachable nodes do run status polls, that's how they change back to being reachable. If yours don't, that'd be a bug that needs to be investigated/reported.
However, unreachable nodes will not run configuration or instance discovery polls until status polls show that a node is reachable again.
How many status polls need to be successful for a node to be considered reachable as well as the time between status polls can be configured.

Perhaps I just seem to find unusual situations.

Transitioning from three other NMS's to NetXMs meant adding devices by IP - and then working on those that did not discover.

I am fine that unmanaged means no automatic retry or discovery - that is consistent with unmanaged, but manually running status or configuration poll, I would expect that it would do the polling as requested, and then, if the node was contactable, to ask if I would want it managed again.

End result - I now have snmpget and ping as object tools that achieve the equivalent - tell me if the node is manageable again - and I act on that.

This came about when I was trying to get SNMP to work through to an EC2 instance. ICMP was not working, Node had been added, but polling just would not seem to work, no matter what settings along the way we changed. It was only when the comment was made - no snmp traffic requests for over 30 minutes - that  I realized that NetXMS is making up its own mind about whether it would actually do what was requested, based on the connectivity status and discovered status.

Like all NMS tools, each one has its peculiarities and with NetXMS, this is one of them.

I added the Ping and SNMPGET to Node Tools so these show up on the Object Details page and are quicker to execute that right click ==> poll == status