adding an additional poller soon

Question

Experienced users,

I tried to psot this message earlier, but never saw it come through, so I apologize if this is a duplicate post.

I will be adding a secondary poller on my network soon. I will not use this post to go into the rationale behind the decision, but I do need a little advice.

What best practices approach should I use to determine how to load balance the network between the two pollers? I should add that we have NetFlow, wireless and will likely add APM soon. As I recall, all the modules must be installed on the primary poller (right?), so how does that effect my load balancing approach?

Anyone want to detail how they approached this issue?

mark_wiggans · Answer

All Orion modules have to be on the Primary poller.

freemen · Answer

Thanks for the reply. So, do I understand correctly that all Orion add-in modules must be installed on the PRIMARY poller, or could I install NetFlow on the primary and wireless on the secondary as an example?

rajivbahl · Answer

I am running NPM SLX 9.0 with additional poller. Since both of my servers are identical in hardware and are located in same building i have distributed my nodes almost equally on each poller. 300 on each.

If you are planning to put your pollers in a distant locations than linking them to their closest node would be a good idea.

If you have additional load of Netflow and APM on your primary poller that releasing some server CPU resource from polling by shifting additional load to new poller will be a good idea.

Netflow is a more I/O intensive so it has to be closer to your database server.

And don't forget to fine tune your pollers with polls per second tunning options to get the best out of it and your Database server on RAID 1+0.

Thats how it worked for me hope it helps your deployment too.