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

Addional polling enginer Question

hi,

we currenlty have a NPM setup, which is self contained doing npm,sql,ncm and so on

we are setting up a large DMZ environment, and was thinking of putting a polling engine inside which can then poll and collect stats to all devices in the DMZ,

am i right in thinking this will collect stat's, poll devices for up/down like my current setup and then show up this info on the currently orion maps?

does that make sense?

Find more posts tagged with

Accepted answers

All comments

njoylif

you are correct. you would need to allow that poller to talk to the main NPM server and SQL (same server right?). All the info the additional poller collects goes in the DB and the web site polls the DB for its info.

mdriskell

An alternative (unless you need the additional polling engine due to the size of the network) would be to allow your NPM server to get through the firewall to the DMZ to poll the nodes.

To put a polling engine in the DMZ you will have to open a hole in the firewall anyway to allow the additional engine to send information back to your network.

I assume you are wanting to put the engine in your DMZ due to a security policy...if you have to open a hole in your DMZ it is a much safer practice to allow your local network to talk to your DMZ than to allow your DMZ to talk to your local network.

Just my two cents