Universal Poller - Architecture

savell

A couple of questions regarding the version 9 universal poller if someone doesn't mind.

I've added a few thousand custom pollers (mainly the ciscoEnvMonSupplyState table to monitor the power supply status for our dual power supply devices). I expected that the element counts would increase on each of our polling engines - but they didn't.

So, I'm assuming another task is doing these polls - and they are not included in the element count (is this correct?)

If another task is doing the custom polls - are they also spread around our separate polling engines (i.e. does the custom polling occur on the same poller that manages each node?).

Is there also any stats available regarding the polling completion for the custom poller (it doesn't appear in the Poller Status View).

Dave.

 

FormerMember

So, I'm assuming another task is doing these polls - and they are not included in the element count (is this correct?)

 

You are correct, device pollers are not counted in your element count.  Only nodes, interfaces, and volumes are used for NPM licensing.

 

If another task is doing the custom polls - are they also spread around our separate polling engines (i.e. does the custom polling occur on the same poller that manages each node?).

 

Just like the standard poller, the Universal Device Poller uses polling engines.  If some of your nodes are assigned to engine 3, then device polling will happen from engine 3 for those nodes.

 

Is there also any stats available regarding the polling completion for the custom poller (it doesn't appear in the Poller Status View).

 

With the Universal Device Poller, there really isn't a concept of polling completion.  Pollers all run at their scheduled time.  They don't run one after the other like they have in previous versions.  There is some work done to "stagger" the starting time when lots of items are added at once, but after that, they are all polling at the node(or interface) polling frequency.