135/netdisco
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

add documentation note on running multiple backend pollers

Browse Source
This commit is contained in:
Oliver Gorwits
2017-06-13 07:47:00 +01:00
parent 1a21df29e3
commit 4092d79718
2 changed files with 14 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
Changes
View File

@@ -14,6 +14,7 @@
* renamed netdisco-daemon to netdisco-backend (and *-fg too) * renamed netdisco-daemon to netdisco-backend (and *-fg too)
* topology import script runs discover for each device (M. Bauer) * topology import script runs discover for each device (M. Bauer)
* avoid lock/defer of jobs deined by *_no ACL settings * avoid lock/defer of jobs deined by *_no ACL settings
* add documentation note on running multiple backend pollers
[BUG FIXES] [BUG FIXES]

13
lib/App/Netdisco/Manual/Deployment.pod
View File

@@ -31,6 +31,19 @@ the database service):
# TYPE DATABASE USER ADDRESS METHOD # TYPE DATABASE USER ADDRESS METHOD
host all all 127.0.0.1/32 md5 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 =head1 Connect to PostgreSQL database on non-standard port
The standard port for PostgreSQL is 5432. To connect on a different port you The standard port for PostgreSQL is 5432. To connect on a different port you