Replicator

Replicator#

After a Replicator license is registered, the Replicator web interface page becomes available and allows users to monitor activity, manage replication parameters (profiles, policies, collectors, etc.), and enable Auto Replicate.

Note

See the Replicator online documentation for further details about Replicator’s core functions and other deployment options.

On this page:

Overview

Overview
Exporters
Exporters
Profiles
Profiles
Collectors
Collectors
Auto Replicate
Auto Replicate
High availability
High-availability replication

Overview#

The Overview view is a dashboard summarizing statistics related to Replicator’s functions.

Real-Time Statistics#

The Real-time Statistics gadgets contain visualizations for the following statistics:

  • Total number of exporters in profiles

  • Total number of collectors in profiles

  • Total number of unique collector-exporter pairs across all profiles

  • Current number of profiles configured

  • Average packet rate (in and out)

  • Average bit rate (in and out)

  • Packet rates over time (in and out)

  • Bit rates over time (in and out)

  • Total bits received and sent

  • Total number of packets received and sent

Hovering over the packet or bit rate timeline will display details for a specific point in time.

Topology#

The Topology gadget shows the flow of packets from exporters to their destination collectors.

Filters#

When a filter is defined from the Filters menu in any of the Replicator UI views, the filter is applied to all views, including the Overview.

The information that can be displayed in the Overview will reflect the type of filter applied:

  • If a profile filter is applied, only outbound/replicated traffic for the selected profile will be displayed. This is because inbound traffic vitals are not associated with a profile (i.e., inbound traffic can apply to no profiles, a single profile, or multiple profiles).

  • If a Replicator instance filter is applied, only inbound and outbound traffic details for that instance will be displayed.

Exporters#

The Exporters view displays all exporters currently sending packets/flows to the Replicator instance.

The list/table includes the following details for each exporter:

  • IP address

  • Port number

  • Current status of the exporter

  • Replicator instance associated with the exporter

  • Timestamp when the exporter was last confirmed as available

  • Total number of profiles associated with the exporter

  • Total number of collectors associated with the exporter

  • Timestamp when the exporter was last modified

Clicking the IP address in the main list/table opens the summary/details view for the exporter. Managing profiles and collectors associated with the exporter can also be done here.

Additional exporter actions#

In the main list/table, the three-dot menu also includes shortcuts to view names, profiles, and collectors associated with the exporter.

Clicking Add To Profiles from the three-dot menu opens a secondary tray where you can select one or more profiles to add the exporter to.

Advanced filters#

Clicking the Filters button opens a tray where one or more filters can be manually configured.

The following filtering options are available:

  • Replicator

  • Profile Name

  • Exporter

  • Exporter Port

  • Collector

  • Collector Port

To apply a filter, expand the filter option/section, and select the criteria to use. Multiple filters and criteria can be applied at the same time to further refine results.

Filter operators#

  • Equal: Returns results that exactly match the specified value

  • Like: Returns results that contain the specified search term

  • Not Like: Excludes results that contain the specified search term

An All Active option is also available, allowing filtering across all currently active values for the selected category.

Profiles#

The Profiles view can be used to create, edit, and manage replication profile configurations.

The list/table shows the following details for all profiles currently saved on the Replicator instance:

  • Profile name

  • Replicator instance the profile was created on

  • Number of policies added to the profile

  • Number of exporters included in the profile

  • Number of collectors assigned to the profile

  • Username of the user who created the profile

  • Date and time the profile was last modified

Creating a new profile#

  1. Click the + button.

  2. In the Add Replicator Profile tray, enter a name for the profile.

  3. Select a profile type (see below) from the Type dropdown.

  4. Select the Replicator instance to associate the profile with.

  5. Add a description for the profile, and then select whether to enable or disable the profile.

  6. Click Save.

Once created, new profiles will be added to the main Profiles list/table and can be further configured at a later time.

Profile types#

New profiles can be created as one of the following types to match its intended use case:

Auto Replicate

Type

Function

Usage

Auto Replicate Seed

Contains exporter policies for an Auto Replicate configuration (functions as the autoreplication ingress point)

Enables Auto Replicate and defines the source exporters for packets to be autoreplicated (multiple seed profiles can be active at the same time)

Auto Replicate Collector

Defines a destination/collector for autoreplication (functions as an autoreplication egress point)

Associate with a seed profile to add the collector to the Auto Replicate configuration
On-prem

Type

Function

Usage

IPv4 Spoofing

Rewrites IPv4 packet headers to show the source exporter (instead of the Replicator instance) as their origin

Preserves the original source IP address for important exporters (will not work in cloud deployments)

IPv6 Spoofing

Rewrites IPv6 packet headers to show the source exporter (instead of the Replicator instance) as their origin

Preserves the original source IP address for important exporters (will not work in cloud deployments)

Note

IPv4 spoofing profiles replicate IPv6 datagrams, but IPv6 spoofing profiles do not replicate IPv4 datagrams.

Cloud

Type

Function

Usage

Plixer Exporter Spoofing

Embeds source exporter details in the payload data

Allows Plixer collectors to read a packet’s origin address from the payload data (used in cloud environments where spoofing is not allowed and only with Plixer collectors)

No Spoof v4

Forwards unmodified IPv4 packets to collectors with the Replicator instance as the source address

Used mainly in cloud environments when no spoofing is allowed and source exporter details are already embedded in the payload data

No Spoof v6

Forwards unmodified IPv6 packets to collectors with the Replicator instance as the source address

Used mainly in cloud environments when no spoofing is allowed and source exporter details are already embedded in the payload data
Specialized

Type

Function

Usage

IPv4 HA Dual Exporters

Rewrites IPv4 packet headers from multiple source exporters to show a specified IP address and port as their origin

Used with multiple GPS data sources for controlling autonomous trucks

Deleting profiles#

Profiles can be deleted by ticking one or more profiles in the main list/table, and then clicking Delete via the Bulk Actions button.

Editing a profile#

Clicking the profile name or selecting Edit from the three-dot menu in the main list/table opens the profile settings tray where the following can be modified:

  • Name

  • Type

  • Replicator

  • Description

  • Enable/disable the profile

  • Policies added to the profile

  • Exporters added to the profile

  • Collectors assigned to the profile

Adding Replicator policies to a profile#

View instructions

  1. Select Add Replicator Policy from the three-dot menu in the list/table.

  2. Enter the subnet/CIDR for the exporters to be defined by the policy.

  3. Select whether to include or exclude the specified subnet/CIDR for the policy.

  4. Click Save.

Assigning collectors to a profile#

Select Add Collectors from the three-dot menu in the list/table, and then in the Add Collectors tray, select the collector to assign to the profile.

Note

Only collectors associated with the Replicator instance that the profile is assigned to are displayed.

Additional profile actions#

In the main view, the three-dot menu for profiles also includes shortcuts to view policies and collectors assigned to a profile.

Filtering options#

Clicking the Filters button opens a tray where one or more filters can be manually configured.

The following filtering options are available:

  • Replicator

  • Profile Name

  • Exporter

  • Exporter Port

  • Collector

  • Collector Port

To apply a filter, expand the filter option/section, and select the criteria to use. Multiple filters and criteria can be applied at the same time to further refine results.

Filter operators

  • Equal: Returns results that exactly match the specified value.

  • Like: Returns results that contain the specified search term.

  • Not Like: Excludes results that contain the specified search term.

An All Active option is also available, allowing filtering across all currently active values for the selected category.

Collectors#

The Collectors view can be used to view all collectors that are currently assigned to at least one profile.

The list/table includes the following details for each collector:

  • IP address

  • Port number

  • Current status of the collector

  • Replicator instance associated with the collector

  • Timestamp when the collector was last confirmed as available

  • Total number of profiles associated with the collector

  • Total number of exporters associated with the collector

Adding a Replicator collector#

To add a Replicator collector, click the + button, and then enter the following details in the Add Replicator Collector tray:

  • Collector IP address

  • Port to use on the collector

  • Replicator instance to associate with the collector

  • [Optional] Description for the collector

Once saved, the collector will be added to the main Collectors list/table. The collector configuration can be further configured or modified at a later time.

Changed in version 19.7.2: Replication to internal/Plixer collectors (including autoreplication) is now supported with any Plixer One license type.

External collectors (as well as additional Replicator instances) can be enabled with a Replicator license key. Contact Plixer Technical Support for more information.

Editing a collector#

Clicking the collector IP address or selecting Edit from the three-dot menu in the main list/table opens the collector settings tray where the following can be modified:

  • IP address

  • Port number

  • Description

  • Profiles associated with the collector

  • Exporters associated with the collector

Adding a collector to profile/s#

Select Add To Profiles from the three-dot menu in the main list/table, and then in the Add To Profiles tray, select one or more profiles to add the collector to.

Additional collector actions#

In the main view, the three-dot menu also includes shortcuts to view profiles and exporters associated with the collector.

Advanced filters#

Clicking the Filters button opens a tray where one or more filters can be manually configured.

The following filtering options are available:

  • Replicator

  • Profile Name

  • Collector

  • Collector Port

  • Exporter

  • Exporter Port

To apply a filter, expand the filter option/section, and select the criteria to use. Multiple filters and criteria can be applied at the same time to further refine results.

Filter operators#

  • Equal: Returns results that exactly match the specified value

  • Like: Returns results that contain the specified search term

  • Not Like: Excludes results that contain the specified search term

An All Active option is also available, allowing filtering across all currently active values for the selected category.

Auto Replicate#

Auto Replicate is an additional Replicator integration for Scrutinizer/Plixer One deployments that allows flow streams to all be sent to a single Replicator instance. These streams will then be automatically distributed across specified collectors in the same distributed cluster based on their available capacity.

Rebalancing process#

Auto Replicate uses two Replicator profile types to define exporters and collectors for autoreplication:

  • Seed profile: Contains inclusion and exclusion policies to define a pool of source exporters to be managed through Auto Replicate

  • Collector profile: Contains collector details, including maximum exporter count and flow rate, and must be associated with the seed profile to add destination collectors for an Auto Replicate cluster (one profile per collector)

Rebalancing action sequence#

Once the necessary profiles have been set up, enabling the seed profile will start the following rebalancing sequence:

  1. All exporters that are currently sending flow data but not assigned to a collector are identified.

  2. The unassigned exporters are assigned, prioritizing collectors with the most available capacity (exporter count and flow rate).

  3. Collectors are checked, and exporters are reassigned from any collectors that have exceeded their capacity limits (exporter count or flow rate).

  4. Actions are reported in the Alarm Monitor using the following policies:

    • Auto Replicate ran: Triggered whenever the Auto Replicate sequence is automatically or manually run

    • Auto Replicate exporter added: Triggered when a new exporter is discovered or when an exporter is assigned to a collector

    • Auto Replicate exporter removed: Triggered when an exporter is unassigned from a collector

    • Auto Replicate error: All configured collector limits reached (requires collector reconfiguration or additional collectors)

By default, the full sequence is automatically re-run every 24 hours, and a check to assign new and unassigned exporters is run every hour. The sequence can also be manually run from the web interface or via API.

Additional logic#

  • No additional exporters will be assigned to a collector that has reached its configured exporter count or flow rate limit. If either limit is exceeded, exporters will be reassigned from the collector when the load distribution sequence is next run (either automatically or manually).

  • Auto Replicate uses a weighted scoring system (see below) to assess collector utilization to optimize exporter assignments. Any unassigned exporter is always assigned to the collector with the lowest resulting composite score.

  • When reassigning exporters from an overloaded collector, the exporter that was most recently added is unassigned first (LIFO).

  • If an exporter is offline/inactive for 15 minutes (can be changed by editing active_exporter_minutes in /home/plixer/scrutinizer/files/conf/rebalance.yaml), it will be unassigned from its current collector.

Composite Utilization Score#

A collector’s Composite Utilization Score is the weighted sum of its current exporter count and flow rate utilization values (e.g., current exporters / max exporters).

By default, the system favors exporter count (70%) over flow rate (30%), but this weighting can be tuned by changing the exporter_count_weight value in /home/plixer/scrutinizer/files/conf/rebalance.yaml to one of the following:

Value

Behavior

1.0

Exporter count only; exporters are distributed as evenly as possible regardless of flow rate differences

0.7

Strongly favors even exporter distribution while still considering flow rates (Default)

0.5

Exporter count and flow rate are considered equally

0.3

Strongly favors even flow rate distribution while still considering exporter counts

0.0

Flow rate only; flow rates are kept as even as possible regardless of exporter distribution

Setup and configuration#

Auto Replicate is enabled by creating a collector profile for each destination collector and associating them with a seed profile with the necessary exporter inclusion/exclusion policies.

Profiles must be created on the local Replicator instance on a Scrutinizer primary reporter or a headless deployment registered with the primary reporter. Destination collectors for autoreplication must be registered with the same primary reporter, which will have access to all collector configurations and current loads.

Note

Multiple seed profiles can be created to enable autoreplication for separate collector groups. All seed profiles are automatically discovered and processed when rebalancing and assigning exporters.

Creating a collector profile#

To create a new collector profile:

View instructions

  1. Navigate to Replicator > Collectors, and then click the + icon to create a new collector profile.

  2. In the Add Replicator Profile tray, enter a name for the profile.

  3. Select Auto Replicate Collector as the profile type, and then select the Replicator instance to create the profile on.

  4. Enter the collector’s IP address and port number to use.

  5. Enter an exporter count limit and a flow rate limit for the collector.

  6. [OPTIONAL] Add a description for the collector/profile.

  7. Click Save.

Repeat the above steps to create a collector profile for each destination collector, and then proceed to create the seed profile.

Creating a seed profile

To create a new seed profile:

View instructions

  1. Navigate to Replicator > Profiles, and then click the + icon to create a new profile.

  2. In the Add Replicator Profile tray, enter a name for the profile.

  3. Select Auto Replicate Seed as the profile type in the dropdown, and then select the Replicator instance to create the profile on.

  4. [OPTIONAL] Add a description for the collector/profile.

  5. Click Save, and then return to the main Profiles view.

  6. Click on the newly created profile to open the configuration tray.

  7. Create inclusion and exclusion policies to define source exporters for autoreplication.

  8. Select the collector profiles of all destination collectors to associate with the seed profile (only collector profiles not currently associated with a seed profile can be selected).

  9. Click Save.

Once the seed profile has been configured, enabling it will start Auto Replicate and immediately run the load distribution sequence.

Manual configuration#

Autoreplication parameters can be manually configured by editing the following values in /home/plixer/scrutinizer/files/conf/rebalance.yaml:

Option

Type

Default

Description

api_port

int

8082

API server port

api_enabled

bool

true

Enable/disable the API server

rebalance_interval

int

1440 (24 hours)

Interval between full rebalances (in minutes)

add_exporter_interval

int

60 (1 hour)

Interval between adding unassigned exporters only (in minutes)

active_exporter_minutes

int

15

Exporter inactivity timeout (in minutes)

exporter_count_weight

float

0.7

Exporter count weighting in the Composite Utilization Score

log_level

string

info

Sets the logging level (debug, info, warn, error)

log_directory

string

/home/plixer/scrutinizer/files/logs

Specify the directory to save log files to

api_log_file

string

autoreplicate.log

Specify the name of the API log file

level_tolerance

float

0.05

Composite Utilization Score tolerance for the CLI -level runmode (0.0–1.0); collectors within this score range are considered balanced

assumed_exporter_rate

float

200

Fallback flow rate for exporters without observed metrics (auto-updated to the median observed rate after -level/-levelall is run)

generate_text_reports

bool

false

Enable/disable daily text summary report generation

text_report_directory

string

/home/plixer/scrutinizer/files/logs

Specify the directory to save text summary reports

Note

A different configuration file can be used by running:

/home/plixer/scrutinizer/bin/rebalance -config /PATH/TO/CUSTOM_CONFIG_FILENAME.yaml

Activity logging#

Auto Replicate uses Zerolog for structured, JSON-based logging and supports multiple logging levels for ease of monitoring and troubleshooting.

CLI mode#

When rebalance is run from the CLI, the logging level (via stderr) defaults to warn (see below).

To change the terminal logging level use the following runmodes:

info level:

/home/plixer/scrutinizer/bin/rebalance -verbose

debug level:

/home/plixer/scrutinizer/bin/rebalance -debug <-minutes [TIME_WINDOW_IN_MINUTES]>

API daemon mode#

When rebalance is running in API daemon mode, logs are saved to /home/plixer/scrutinizer/files/logs/rebalance.log.

Logging levels#

The logfile logging level for Auto Replicate activity can be modified by changing log_level in /home/plixer/scrutinizer/files/conf/rebalance.yaml to one of the following:

  • debug: Per-item details (individual policy changes, capacity calculations, function entry/exit), profile loading, exporter metrics

  • info: Process lifecycle (start/stop), per-collector capacity status, rebalance summaries, decision outcomes, policy update totals, manually managed exporters

  • warn: Only actionable events requiring attention (overloaded collectors, unassignable exporters, collectors without Auto Replicate profiles)

  • error: Only critical errors preventing operation

CLI operations#

Rebalancing operations can be manually initiated from the CLI by running:

/home/plixer/scrutinizer/bin/rebalance

CLI mode options:#

When running rebalance via CLI, the following additional options are available:

  • -debug: Enable debug-level logging

  • -verbose: Enable info-level logging

  • -minutes: Lookback window for exporter rate analysis in minutes (default: 2880 = 48 hours)

  • -seed-profile-id: Specify a seed profile ID to rebalance, -level, or -levelall (0 = all seed profiles)

  • -level: Reassign most recently assigned exporters from over-target collectors to under-target collectors (gentle redistribution)

  • -level-tolerance: Specify a score tolerance for -level mode (0.0–1.0, default: 0.05 = 5%); only collectors outside this tolerance band are considered over-/under-target

  • -levelall: Delete all policies automatically created by Auto Replicate and reassign all exporters by descending rate (full reset)

  • -help: Show help message

Note

  • The default -level-tolerance value can be set by changing level_tolerance in /home/plixer/scrutinizer/files/conf/rebalance.yaml.

  • After -level is run, assumed exporter flow rates are updated to the median observed rate and saved to /home/plixer/scrutinizer/files/conf/rebalance.yaml.

  • -level and -levelall will not run if any Auto Replicate policies were recently modified (cooldown timer is the same as the exporter inactivity timeout).

API daemon mode options:#

To run rebalance as an API daemon server (with scheduling), run the following:

/home/plixer/scrutinizer/bin/rebalance -daemon

In API daemon mode, the following additional options are available:

  • -api-port: Set the API server port (default: 8082)

  • -api-enabled: Enable API server (default: true)

  • -log-level: Set the logging level to debug, info, warn, error (default: info)

  • -config: Set the configuration file path (default: /home/plixer/scrutinizer/files/conf/rebalance.yaml)

  • -rebalance-interval: Set the interval between full rebalances in minutes (default: 1440)

  • -add-exporter-interval: Set the interval between adding unassigned exporters only in minutes (default: 60)

  • -active-exporter-minutes: Set the exporter inactivity timeout in minutes (default: 15)

  • -exporter-count-weight: Set the exporter count weighting in the Composite Utilization Score (default: 0.7)

  • -generate-text-reports: Enable daily summary text report generation (default: false)

  • -text-report-directory: Specify the directory for text summary reports (default: /home/plixer/scrutinizer/files/logs)

Note

The above settings can also be configured in rebalance.yaml or another specified configuration file.

API endpoints#

When Auto Replicate is running as an API daemon server, the following endpoints are available:

Note

API access requires an API authentication token.

  • GET /health - Get service health status (no authentication required)

  • GET /api/v1/status - Get service status and statistics

  • GET /api/v1/operations - List all operations (active and completed)

  • GET /api/v1/operations/{operation_id} - Get operation details for the specified operation_id

  • POST /api/v1/rebalance/trigger - Trigger a rebalance operation

  • GET /api/v1/rebalance/status/{operation_id} - Get operation status and progress for the specified operation_id

  • GET /api/v1/rebalance/history - Get rebalance operation history

  • GET /api/v1/profiles - List all seed profiles

  • GET /api/v1/profiles/{profile_id}/status - Get detailed profile status for the specified profile_id

API call examples#

View examples

Trigger rebalance for all seed profiles:

curl -X POST http://localhost:8082/api/v1/rebalance/trigger \
  -H "Content-Type: application/json" \
  -d '{"minutes": 2880}' \
  --cookie "sessionid=your_session_id"

Trigger rebalance for a specific profile:

curl -X POST http://localhost:8082/api/v1/rebalance/trigger \
  -H "Content-Type: application/json" \
  -d '{"seed_profile_id": 1, "minutes": 1440}' \
  --cookie "sessionid=your_session_id"

Check operation status:

curl http://localhost:8082/api/v1/rebalance/status/rebalance-20250814-093500-1 \
  --cookie "sessionid=your_session_id"

Get service status:

curl http://localhost:8082/api/v1/status \
  --cookie "sessionid=your_session_id"

Get rebalance history:

curl http://localhost:8082/api/v1/rebalance/history?limit=10 \
  --cookie "sessionid=your_session_id"

High-availability replication#

A Replicator instance can be paired with a secondary instance to create a high-availability pair that ensures uninterrupted flow data replication. Configuration data is synced between the primary and secondary instances for seamless failover.

Note

Any unpaired headless Replicator instance without saved profiles can be set as a secondary instance in an HA pair.

In distributed Scrutinizer clusters, the secondary reporter or any remote collector can be used as a secondary Replicator instance by enabling the Replicator service.

Multi-network mode#

When the primary and secondary Replicator instances are on different subnets (where a virtual IP address cannot be used), the flow data to be replicated must be sent to both Replicator instances.

After a high availability pair is set up in this mode, the primary instance continuously sends UDP heartbeat packets to the secondary instance (1 packet per second). If the secondary fails to receive two consecutive heartbeat packets, it immediately starts replication. Once a heartbeat packet is received from the primary instance again, the secondary syncs any configuration updates, stops replication, and reverts to the standby state.

Note

Multi-network mode is the default high-availability configuration. If the primary and secondary Replicator instances are on the same network, enabling virtual IP/single-network mode is recommended.

Enabling multi-network HA on a Replicator#

To create a multi-network HA pair, follow these steps:

View instructions

  1. Go to Admin > Resources > Replicators, and then click on the name of the Replicator instance to use as the primary.

  2. In the Replicator configuration tray, toggle the High Availability switch to On (will not be displayed if no secondary instances are available).

  3. Select the Replicator instance to use as the secondary in the Secondary IP dropdown.

  4. Click Save to create the HA pair.

After the multi-network HA pair has been saved, configure all exporters to send flow data to both the primary and secondary instances.

Virtual IP mode#

When the primary and secondary Replicator instances are on the same network, they can receive flow data packets via a shared virtual IP address.

After a high-availability pair is set up in this mode, the availability of the primary and secondary instances is monitored using the Virtual Router Redundancy Protocol (VRRP). If the primary Replicator instance becomes unavailable, the specified virtual IP address is immediately reassigned to the secondary instance, which then starts replication (handover typically takes ~1 second). Once the primary becomes available again, it takes possession of the virtual IP address and starts replication after a user-defined delay (see instructions below).

Enabling virtual IP HA on a Replicator#

View instructions

  1. Go to Admin > Resources > Replicators, and then click on the name of the Replicator instance to use as the primary.

  2. In the Replicator configuration tray, toggle the High Availability switch to On.

  3. Select the Replicator instance to use as the secondary in the Secondary IP dropdown.

  4. Enable Virtual IP, and then enter the following details in the provided fields:

    • Virtual IP address: IP address to be shared between the primary and secondary instances

    • Virtual router ID: Virtual router ID to assign to the HA pair (must be unique to the pair to avoid conflicts with other software devices using VRRP)

    • Failover delay: Length of time that the primary instance must be online again before it takes over the virtual IP and replication (to avoid flapping)

    Note

    The failover delay is meant to allow all services on primary instance to fully restart after a reboot/outage. A delay of at least 2 minutes is recommended (default: 5 minutes).

  5. Click Save to create the HA pair.

After the VIP HA pair has been saved, configure all exporters to send flow data to the virtual IP address specified.

Reverting HA pairings#

To revert paired Replicator instances back to separate instances, toggle off High Availability for the primary instance.

This will unpair the instances and allow them to be used as regular Replicator instances again. The primary instance will retain all profiles, collectors, and other settings previously applied, and the secondary instance will be reverted to its unused, post-deployment state.

High-availability exporter pairs#

Replicator can automatically manage flow data streams from a specified pair of redundant IPv4 exporters using the IPv4 Dual HA Exporters profile type.

After a profile of this type is created, it must be configured as follows:

View instructions

  1. Select the Replicator instance to use.

  2. [Optional] Add a description for the profile.

  3. Enter the spoofed IP address to use for replicated streams.

  4. [Optional] Enter the spoofed port to use for replicated streams.

  5. Create exactly two /32 policies (one for each HA exporter).

  6. Select the preferred/primary source.

  7. Set the amount of time to wait for the preferred source.

  8. Add collectors to the profile (or define new collectors, if necessary).

After the profile has been configured and enabled, flow data from the preferred source will be replicated and forwarded to the specified collector(s). If the preferred source becomes inactive for the specified wait time, replication will start for the stream from the other exporter/policy defined in the profile. The same spoofed IP address and port will be used regardless of the active source.