Yes, we are running one remote poller across a WAN to the DB server.
Here are our specs:
So how many elements do you have on that remote poller? What's the latency between it and the DB server? What are your settings for polls, statistic collection, etc?
Sorry for the questions....just seeing how different your set up is to mine. Thanks.BB
I'd be interested in how you have this working as well.I've tuned my polls per seconds below the recommended values & my polling completion percentage has increased from 98.6% to 99.1% for the remote poller.I now have it running across a lightly loaded OC12 WAN link (622mbps) to the DB with 36ms latency.However I still only record SNMP data every 1-2 hours in the CPU, Mem & Utilization graphs.
Thanks for any assistance.
apparently the "head geek" is going to do a webinar on this subject. see the top page thwack.com to register.
FYI
I'd be interested in how you have this working as well.I've tuned my polls per seconds below the recommended values & my polling completion percentage has increased from 98.6% to 99.1% for the remote poller.I now have it running across a lightly loaded OC12 WAN link (622mbps) to the DB with 36ms latency.However I still only record SNMP data every 1-2 hours in the CPU, Mem & Utilization graphs.Thanks for any assistance.
NG...you say you tuned BELOW the recommended value? Was that the one provided by the polls per sec program? I'm getting ~96% completion rate on my 2 remote pollers (ones across the WAN). BB
Bryan,
I did some testing with the polls per second tuning.What I found was when I increased the polls/sec above the recommended values (I even tried doubling it at on point) the % completion rate was significantly reduced. By tuning the polls below the recommended value the completion rate increased, but it still does not poll the SNMP MIBs every 5 minutes as it should (according to the packet capture I did on the remote polling server).I'm really not sure what the % completion is actually measuring & what significance this has overall.