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

Distributed Polling Engines

Anyone know if SW will be offering DPE's in versions other than SLX? We have some "smaller" sites where there are 100-200 elements and it's not very cost effective to buy an SLX poller for those sites.

Find more posts tagged with

Accepted answers

All comments

mreitz

quote:Originally posted by ceclark

Anyone know if SW will be offering DPE's in versions other than SLX? We have some "smaller" sites where there are 100-200 elements and it's not very cost effective to buy an SLX poller for those sites.

Do you really need a polling engine just for those small sites? We have multiple polling engines, all at the same data center, polling lots of small sites.

Malcolm

ceclark

Yes because there are two firewalls in between the two sites.

skaczkowski

Opened up the needed ports between the networks/firewalls..

It's what SNMP, ICMP? Shouldn't be too big of deal..

-Steve

jonchill

We've currently got two pollers for the major sites and those pollers also pole several smaller sites all we've done is put explicit rules on the firewall and routers for the devices we want to monitor.

HTH

Jon

IT Infrastructure Manager
Pilgrim Hospital
UK

ceclark

skaczkowski-

If I need to monitor a dozen servers behind the firewall it is! I would have to create a translation for each. That's too many holes in the firewall.

jonchill-

The big problem is we want to monitor customer sites. Your idea is great for regional sites, but we're trying to something SW isn't made to do (I think).

iunderwo

If you want to monitor a bunch of remotes for customer sites, your best bet is to establish a VPN between each customer site and your main operations center.

You can do a lot of fancy things with a good NAT router. For example, you can run NAT on the VPN router at the site, and route a small block of IPs unique to your internal organization over the VPN. The router then NATs those unique IPs to whatever it needs internally.

There's no cheap and easy way to achieve what you're looking for ... but doing this with a router is much more flexible than putting a poller at each remote location.

// Ian Underwood - Network Engineering
// Boston Stock Exchange

ceclark

SW agrees with the VPN tunnel, but there are a couple of major issues. If the tunnel goes down, it looks like the entire customer site is down. Security (can be mitigated, but at a cost). A think a better design is to have a remote poller. The poller can collect for that site and then send a roll-up back to our central site (via a server to server vpn). Less holes in the firewall, local polling and alerting will be true (ie the VPN tunnel going down issue). SW doesn't make anything like this yet, but hopefully they will in the near future.