Distributed Architecture Configuration
- Last Updated: May 1, 2026
- 1 minute read
- Flowmon Products
- Flowmon Anomaly Detection System
- Documentation
To successfully configure the distributed architecture, you must have at least one Master node and one Slave node (see the Distributed architecture page). You can enable the ADS distributed architecture on any existing installation. When the existing standalone ADS is turned into a Master node, processing of the database is disabled. When it is turned into a Slave node, the web user interface is disabled. Events and configuration are still kept in storage on the Slave node, but they are not used. This allows you to change the mode of ADS without needing to reinstall it.
After changing the mode of ADS, the allocated quota must be checked. The quota for Master can be configured in Flowmon Configuration Center → Quotas Manager. The quota for Slave in the Flowmon distributed architecture is available on Master (TPM) in Flowmon Configuration Center → Distributed Architecture → Source Group → Open FCC → Quotas Manager for all Slave units in the Source Group.
You can enable the distributed architecture through the wizard or manually. There is no GUI. Access to the Flowmon device terminal is necessary.
Ensure that you have configured the distributed architecture for the Flowmon OS (in the Flowmon Configuration Center) before configuring distributed architecture for the ADS module. Otherwise, the distributed architecture for the Flowmon ADS module will not work correctly. Details about the configuration of a distributed architecture for Flowmon OS can be found in the Set up Distributed Architecture section of the Flowmon User Guide.