From 4092d797186e26f88d2a5a49ef6a13e9255fb3ef Mon Sep 17 00:00:00 2001
From: Oliver Gorwits <oliver@cpan.org>
Date: Tue, 13 Jun 2017 07:47:00 +0100
Subject: [PATCH] add documentation note on running multiple backend pollers

---
 Changes                                |  1 +
 lib/App/Netdisco/Manual/Deployment.pod | 13 +++++++++++++
 2 files changed, 14 insertions(+)

diff --git a/Changes b/Changes
index b5dc5268..8c4b73f0 100644
--- a/Changes
+++ b/Changes
@@ -14,6 +14,7 @@
   * renamed netdisco-daemon to netdisco-backend (and *-fg too)
   * topology import script runs discover for each device (M. Bauer)
   * avoid lock/defer of jobs deined by *_no ACL settings
+  * add documentation note on running multiple backend pollers
 
   [BUG FIXES]
 
diff --git a/lib/App/Netdisco/Manual/Deployment.pod b/lib/App/Netdisco/Manual/Deployment.pod
index bb2b01f9..ef383c12 100644
--- a/lib/App/Netdisco/Manual/Deployment.pod
+++ b/lib/App/Netdisco/Manual/Deployment.pod
@@ -31,6 +31,19 @@ the database service):
  # TYPE  DATABASE  USER  ADDRESS       METHOD
  host    all       all   127.0.0.1/32  md5
 
+=head1 Run multiple poller daemons
+
+A common scenario is that the network is split into security domains (or
+zones) and one Netdisco poller daemon cannot see all devices.
+
+You can run multiple pollers, as long as they all connect back to the same
+PostgreSQL database. Use the C<discover_only>, C<macsuck_only>, C<arpnip_only>
+configuration settings (or their C<*_no> variants) to control which devices
+are "seen" by each poller. You can also include only the necessary minimum
+SNMP community/authentication settings in each poller's configuration.
+
+Of course you will also need to start the web server somewhere, as well.
+
 =head1 Connect to PostgreSQL database on non-standard port
 
 The standard port for PostgreSQL is 5432. To connect on a different port you