Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

remote polling engine - hse setup

we're planning to add an additional polling engine to our existing npm. the pe would be placed in our remote pop in asia.

also we want to add redundancy to our system by setting up a hse at the main site.

question...is it a problem to have a polling engine connected to the main npm/sql server via wan about 300ms away?

and can the hse backup both engines? or is it better to have to a seperate hse on both sites (is this covered by one hse-license)

thx

klaus

Find more posts tagged with

additional_poller

Accepted answers

expereo

Got a reply from SW via Mail.

SQL over WAN not supported

All comments

Yann

Hi,

The following link should answer some of your questions:

A HSE can cover all the polling engines of an Orion instance (1 DB + X Polling Engines).

As detailed in the thread I linked, 2 Orion instances would provide better performances and stability.

If required an EOC can be installed to facilitate the administration/monitoring.

See attached example of an EOC deployment.

HTH,

Yann

eoc-diagram.jpg

expereo

Hi, thanks for the tip, but this setup would mean to have a full NPM and DB deployed on the remote site and centralized monitoring with EOC...this would go over the budget.

I'd rather have a setup with a central NPM/DB and remote polling engines backuped by a single HSE at the central site. the problems that i expect is the latency between the remote PE and the central DB (~300ms) and the increased latency in the graphs when the HSE takes over the polling from the remote PE.

So is it a problem to have the PE 300ms away from the central NPM/DB and is there a way to configure a latency "handicap" on the central HSE for the nodes of the remote PE in order to have the graphs not showing increased latencies when polled from HSE.

Thanks,

Cheers

Klaus

expereo

Got a reply from SW via Mail.

SQL over WAN not supported