provisioning node with NodeCategorySettingPolicy policy in foreign source does not work if node has no SNMP available

after a restart of OpenNMS, nodes without SNMP access added to the specified surveillance categories in Foreign Source Policies.
The disadvantage is, that latency thresholding etc. based on surveillance categorys not work properly until OpenNMS is restarted.

Just to clarify what you say is going on: if you have a category defined for a foreign source and synchronize the provisioning group, then the nodes that support SNMP are added to the category immediately, but nodes that do not support SNMP will not be added to the category until the system is restarted. Is this the behavior you are seeing?

yes, this is correct.
This is exactly the behavior I have seen.

But you must surely disable SNMP access to node by setting a different community as public.
Why OpenNMS make SNMP queries when provisioning, although this was not configured
(no SNMP Service on Node, no SNMP in Foreign Source, no SNMP Asset Adapter),
but i can see SNMP Node Informations on node page!?

Created an attachment (id=1114)
provisiond.log for Bug4001 - 2 node scans

there are 2 node scans. first node does not support snmp and therefor does not get assigned to 'Test' Category.
Second Node does support SNMP and DefaultPluginRegistry loads NodeCategorySettingPolicy.

any news about this issue?
NodeCategorySettingPolicy is completely useless if node does not support SNMP.
Why there is a dependency on SNMP support?

I've struggled on the same issue in 1.8.5

I can confirm for 1.8.7 - and nodes don't even get added to the categories when I restart OpenNMS. I agree to Martin that this makes everything that is based on surveillance categories useless if you you use provisioning and NodeCategorySettingPolicy.

Commercial support ticket #3859 references and confirms this bug.

Added a fix to master, but it needs some work yet. Hope to finish in a few days.

Did a follow-up commit to master which hopefully will take care of this issue. I'll kick the tires some more on a production network next week before adding the changes to the 1.8 branch.

FYI, I've merged these changes back to 1.8, they applied cleanly.

Sorry for the Cloning.. I'm copying the comments here. Please reopen this if you think its convenient.

Using 1.8.11 on Ubuntu

This is the Foreign source being used:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<foreign-source date-stamp="2011-04-14T11:31:18.776-03:00" name="IFX-sansSNMP" xmlns="http://xmlns.opennms.org/xsd/config/foreign-source">
<scan-interval>1d</scan-interval>
<detectors>
<detector class="org.opennms.netmgt.provision.detector.icmp.IcmpDetector" name="ICMP"/>
<detector class="org.opennms.netmgt.provision.detector.icmp.IcmpDetector" name="StrafePing"/>
</detectors>
<policies>
<policy class="org.opennms.netmgt.provision.persist.policies.NodeCategorySettingPolicy" name="Set Routers">
<parameter value="Routers" key="category"/>
<parameter value="ANY_PARAMETER" key="matchBehavior"/>
</policy>
<policy class="org.opennms.netmgt.provision.persist.policies.NodeCategorySettingPolicy" name="Set Produccion">
<parameter value="Production" key="category"/>
<parameter value="ANY_PARAMETER" key="matchBehavior"/>
</policy>
<policy class="org.opennms.netmgt.provision.persist.policies.NodeCategorySettingPolicy" name="Set IFX">
<parameter value="IFX" key="category"/>
<parameter value="ANY_PARAMETER" key="matchBehavior"/>
</policy>
</policies>
</foreign-source>

When adding a node via the "Add node" link, selecting this foreign source, and adding no other data, the node gets added, SNMP service is added anyway (because of #NMS-3489). StrafePing gets added OK.
Categories don't get added, even after a openms restart.

Excerpt from provisiond debug:

2011-04-14 12:15:27,400 INFO [scanExecutor-5] NodeScan: Aborting Scan of node 95 for the following reason: Aborting node scan : Agent timedout while scanning the system table
2011-04-14 12:15:27,418 DEBUG [scanExecutor-5] DefaultPluginRegistry: Found bean org.opennms.netmgt.provision.persist.policies.NodeCategorySettingPolicy@329a1ba9 with name org.opennms.netmgt.provision.persist.policies.NodeCategorySettingPolicy of type interface org.opennms.netmgt.provision.NodePolicy
2011-04-14 12:15:27,420 DEBUG [scanExecutor-5] DefaultPluginRegistry: Found bean org.opennms.netmgt.provision.persist.policies.NodeCategorySettingPolicy@238e0e33 with name org.opennms.netmgt.provision.persist.policies.NodeCategorySettingPolicy of type interface org.opennms.netmgt.provision.NodePolicy
2011-04-14 12:15:27,422 DEBUG [scanExecutor-5] DefaultPluginRegistry: Found bean org.opennms.netmgt.provision.persist.policies.NodeCategorySettingPolicy@3b422fa8 with name org.opennms.netmgt.provision.persist.policies.NodeCategorySettingPolicy of type interface org.opennms.netmgt.provision.NodePolicy
2011-04-14 12:15:27,432 DEBUG [scanExecutor-5] NodeInfoScan: collectNodeInfo: checking 3 node policies for restoration of categories
2011-04-14 12:15:27,432 DEBUG [scanExecutor-5] NodeCategorySettingPolicy: No Match Found: [OnmsNode@58dab1be id = 95, label = 'TEST-borrar'] for org.opennms.netmgt.provision.persist.policies.NodeCategorySettingPolicy@329a1ba9
2011-04-14 12:15:27,432 DEBUG [scanExecutor-5] NodeCategorySettingPolicy: No Match Found: [OnmsNode@58dab1be id = 95, label = 'TEST-borrar'] for org.opennms.netmgt.provision.persist.policies.NodeCategorySettingPolicy@238e0e33
2011-04-14 12:15:27,432 DEBUG [scanExecutor-5] NodeCategorySettingPolicy: No Match Found: [OnmsNode@58dab1be id = 95, label = 'TEST-borrar'] for org.opennms.netmgt.provision.persist.policies.NodeCategorySettingPolicy@3b422fa8
2011-04-14 12:15:27,433 DEBUG [scanExecutor-4] NodeInfoScan: doPersistNodeInfo: Restoring 0 categories to DB
2011-04-14 12:15:27,444 DEBUG [pool-1-thread-1] NodeScan: Finished scanning node (IFX-sansSNMP/1302793003440)

Thanks!

info added in comment. Still having same problem on 1.8.11

Tomás,

I found another minor problem when SNMP is provisioned on a node that has no SNMP. I believe I committed the fix to master and the 1.8 branch today. Try the 1.8.12 snapshot tommorow if you can. Of course it would be better to not have SNMP hard-coded as a provisioned service. I'm looking at possible ways to make that an option.

Hi Bill,
I wasn´t able to test it yet.
Anyway, as this is a production system, and no testbench available , will stick to releases. I´ll try 1.8.12 as soon as I found some time for it.
Y saw you solved the "snmp added anyway in #NMS-4615 Will it make in 1.8.12? or 1.8.13?

Cheers!

Hi,

seems to be resolved and works in 1.8.12.
But Bug #NMS-4658 still exist and make Surveillance Categories unusable