Additional Polling Engines

We typically don't recommend deploying a polling engine across the WAN due to latency issues.  If this is not an issue you can purchase an additional poller, which is in essence a headless Orion install and talks back to the central DB across the WAN.

Another option is to put a smaller Orion install on that site with it's own DB and then use EOC to roll up together that remote site and your central site into a single dashboard

do we need an extra license for this remote poller.

We currently have some 100 elements left to monitor or do we have to buy an extra license for the remote poller.

Yes if you need another poller, that is something you will need to purchase, see here for more info

The only additional polling engine I can buy is the SLX, so that will cost me 13000 dollar to monitor an extra 20 elements ?????

If you need to install a poller on another site, then yes.  We are looking at providing more flexability going forward, but this is what we have today.  You could also deploy an SL100 at that site and use EOC to roll them up together into a single console, but you would need SQL at that site as well.

If you need to install a poller on another site, then yes.  We are looking at providing more flexability going forward, but this is what we have today.  You could also deploy an SL100 at that site and use EOC to roll them up together into a single console, but you would need SQL at that site as well.

Brandon

We have also considered an additional poller as a solution to off-site monitoring for remote locations.  What exactly are the speed and latency requirements for the polling engine's communication to the database?