I've found a few other posts with similar issues, however none of the solutions found seem to work. I've noticed this issue since NPM 10.7 and it doesn't seem to be any better in 11.0.1.
If some time in the past someone has discovered a bunch of devices without turning on a poller, lets say Topology 3 since that is what I'm working with at the moment, and later you decide you want to turn Topology Layer 3 on. You go into Manage Pollers, select the Layer 3 Poller and hit assign. You find your layer 3 network gear and it says Not a Match. So you think, hmm, that doesn't seem right. You click on one, go to List Resources of that device, and lo and behold, the Layer 3 check box is available for that device. It was a match, but for some reason Device Studio (Manage Pollers) doesn't think it is. This is no big deal if you only have a couple items you want to turn Layer 3 polling on for, but if you have dozens or more then not having the Manage Pollers resource work as expected is a real bummer, since bulk editing is what I need to be able to do here.
The above scenario was just for layer 3 topology, but I have found this issue to ubiquitous across all of the pollers in Manage Pollers. Once Orion incorrectly determines its Not a Match (I don't know how or when it determined that either) it doesn't seem to ever want to check again. I can see a grayed out option to "Enable/Disable scanning on new nodes", but I'm not entirely sure what that does. It doesn't seem to matter because its always grayed out no matter what I do or what I select. It seems like I found a Knowledgebase article a while back that recognized that button being grayed out as a bug and it offered a work around, however I can't find that article right now. Also, I remember trying the workaround and not having any success with it.
See below screenshots for an example.
Is this false "Not a Match" just a known bug and there is nothing I can do about it, or is there something I've been missing in dozens of different customers' Orion environments and somebody can finally enlighten me as to what I've been doing wrong this entire time? As it stands now, the only solution I have is to either List Resources on each and every item I need to add a poller to, or delete all of the nodes and add them back in through a discovery, since running a discovery on nodes already in the database seems to not want to add the pollers in either?
Thanks!
P.S. Here is an example of the grayed out button:
Here is the "Routing" poller exhibiting the behaviour I mentioned in my post above:
Notice it says Not a Match here?
Now I do a List Resources on that exact node, and lo and behold! Routing is available:
I selected "Routing" in the List Resources of that node, then bo back to Manage Pollers and refresh the screen and what do you know, it was actually an Exact match all along:
