quote:Originally posted by Network_GuruIn this situation, the remote polling engine has its own SQL server. Customers then will remotely roll-up the data they need via queries to the remote SQL server.
quote:When you say "Customers then will remotely roll-up the data"
quote:Originally posted by Network_GuruDepends on the bandwidth & latency of your WAN link.Generally it is not a good idea:
Well it appears I am in this exact situation now.The DB will be separated from the secondary poller via an OC12 WAN link with 40ms latency.
Does anyone have any experience with this?What is the performance like ?Any issues with the DB or other services timing out?
Our secondary poller is across a WAN link and before we upgraded our WAN we had a latency of 40 - 50ms and didn't have a single problem with any timeouts.
It will also depend on how frequently your polling and gathering stats.
Jon
Hi Jon,
Ever since moving the DB to another site with the Primary polling engine/web server, my secondary polling engine has 1 - 2 hour gaps in any SNMP collected data.ICMP stats are fine & are collected & written to the DB every 5 minutes.Of course Solarwinds Tier 3 support was no help & used the standard disclaimer - "we do not support remote polling engines separated from the DB".
I'm sure there is a problem with the install, or perhaps something else I have missed.Documentation on setting up a secondary polling engine is sparse, to say the least...
Any words of advice would be greatly appreciated.