<![CDATA[Rediscovering my discovery]]>I had discovery running a few days ago:

[17-Nov-2015 07:38:13.433] [DEBUG] AcceptNewNode(172.26.1.3): auto filter, flags=0003
[17-Nov-2015 07:38:13.482] [DEBUG] AcceptNewNode(172.26.1.3): auto filter - bResult=0
[17-Nov-2015 07:38:13.482] [DEBUG] NodePoller: processing node 172.26.1.4/32 in zone 0
[17-Nov-2015 07:38:13.482] [DEBUG] AcceptNewNode(172.26.1.4): auto filter, flags=0003
[17-Nov-2015 07:38:13.532] [DEBUG] AcceptNewNode(172.26.1.4): auto filter - bResult=0
[17-Nov-2015 07:38:13.532] [DEBUG] NodePoller: processing node 172.26.1.5/32 in zone 0
[17-Nov-2015 07:38:13.532] [DEBUG] AcceptNewNode(172.26.1.5): auto filter, flags=0003
[17-Nov-2015 07:38:13.582] [DEBUG] AcceptNewNode(172.26.1.5): auto filter - bResult=0
...
[17-Nov-2015 07:53:20.632] [DEBUG] Finished active discovery check on range 172.26.1.1 - 172.26.1.255

What does flags=0003 and bResult=0 mean? I have Network Discovery configured for Active and Passive and 172.26.1.0/24 is in the Active Discovery Targets, but the above three nodes haven't been added. Also, 172.26.1.0/24 is in zone 11 not zone 0.

Since then I have restarted the netxmsd service and I haven't seen any more active discovery messages. Can I force an active discovery? In the Server Configuration, ActiveNetworkDiscovery = 1 which I assume means 'on'.

]]>https://forum.netxms.org/topic/4122/rediscovering-my-discoveryRSS for NodeFri, 13 Nov 2026 20:07:07 GMTFri, 20 Nov 2015 18:23:06 GMT60<![CDATA[Reply to Rediscovering my discovery on Thu, 16 Jun 2016 20:56:55 GMT]]>Has been a while since I looked at this [still no "active discovery check" lines in 2.7M lines of log files] so I will upgrade to newer version before troubleshooting further.

]]>https://forum.netxms.org/post/20174https://forum.netxms.org/post/20174Thu, 16 Jun 2016 20:56:55 GMT<![CDATA[Reply to Rediscovering my discovery on Mon, 30 Nov 2015 20:27:17 GMT]]>Filter not matched means host rejected. Could you please share a screenshot of network discovery configuration screen?

Best regards,
Victor

]]>https://forum.netxms.org/post/18464https://forum.netxms.org/post/18464Mon, 30 Nov 2015 20:27:17 GMT<![CDATA[Reply to Rediscovering my discovery on Wed, 25 Nov 2015 22:42:56 GMT]]>Filter not matched means the host is accepted, not rejected?

I will re-order the communities in the SNMP settings and....well, I was going to say try again but it seems you just leave it and it does recovery by itself. I know SNMP works on all these devices because I am already monitoring them with SNMP from the same server with Zabbix.

]]>https://forum.netxms.org/post/18436https://forum.netxms.org/post/18436Wed, 25 Nov 2015 22:42:56 GMT<![CDATA[Reply to Rediscovering my discovery on Tue, 24 Nov 2015 18:59:52 GMT]]>172.26.1.3/32 is within 172.26.1.0/24, but likely do not respond to SNMP or do not have netXMS agent.

Best regards,
Victor

]]>https://forum.netxms.org/post/18424https://forum.netxms.org/post/18424Tue, 24 Nov 2015 18:59:52 GMT<![CDATA[Reply to Rediscovering my discovery on Fri, 20 Nov 2015 22:34:48 GMT]]>OK, I don't get it. Why wouldn't 172.26.1.3/32 match a filter of 172.26.1.0/24? Is it because the  the subnet doesn't match the zone?

All the agents have a community string of 'public' which is on my list of strings in the SNMP Credentials.

]]>https://forum.netxms.org/post/18382https://forum.netxms.org/post/18382Fri, 20 Nov 2015 22:34:48 GMT<![CDATA[Reply to Rediscovering my discovery on Fri, 20 Nov 2015 20:30:50 GMT]]>flags==3 is DFF_ALLOW_AGENT + DFF_ALLOW_SNMP – automatically generated filter, which will accept any node with agent or with active snmp.
bResult==0 means "false", this filter was no matched (0 - false, anything else - true).

]]>https://forum.netxms.org/post/18374https://forum.netxms.org/post/18374Fri, 20 Nov 2015 20:30:50 GMT