Configuring a Data Aggregator
If you have firewalls between your data sensors and the data processor (DP), you must open ports on each firewall to allow the sensors to reach the DP. Instead, you can install a data aggregator to collect TCP traffic from the sensors and send it to the DP. Then you only have to open ports between the aggregator and the DP. The aggregator acts as a proxy to forward traffic from other sensors to the DP.
You must open ports on the firewall to allow the:
- Aggregator to reach the DP and other sensors
- DP to communicate with the aggregator
- Sensors to communicate with the internet and the aggregator
The aggregator is a single point of failure for your sensors. We strongly recommend that you install and configure a secondary aggregator.
When you install the aggregator, the DP automatically discovers it, as with any sensor:
-
Modular Sensors with the Aggregator feature enabled appear in the System | Collection | Sensors | Sensor list.
If you have a sensor that cannot connect to the DP, use the set aggregator
command to add up to two aggregators to the sensor.
Configuring the Aggregator
Configuring an aggregator deployed using a Modular Sensor consists of the following steps, each of which is described in detail below the summary:
-
Create a Modular Sensor profile for the aggregator in the System | Collection | Sensor Profiles tab. Ensure that the Aggregator feature is enabled in the Modular Sensor profile.
-
Assign the Modular Sensor profile to the sensor to be used as an aggregator.
Creating a Modular Sensor Profile with the Aggregator Feature Enabled
-
Click System | Collection | Sensor Profiles. The Sensor Profile Configuration page appears, with the Sensor Profiles tab displayed by default.
-
Click Create and select Add Modular Sensor Profile. The ADD SENSOR PROFILE screen appears.
- Enter the Profile Name. We recommend that you establish a naming convention so you can easily understand the intent of each profile by looking at the name. This field can only contain alphanumeric characters, underscores, spaces, and dashes.
-
Choose at least one Receiver. Each sensor profile must have at least one receiver, which is the destination of the data it collects. You can add one receiver of each type: packet and JSON.
See the Receiver configuration page for more information on creating and maintaining receivers.
-
Customize the settings for the profile. Since we will use this profile to configure modular sensors as aggregators, we must make sure the Aggregator feature is enabled, as in the figure below:
Refer to Configuring Modular Sensor Profiles for details on the different Modular Sensor feature available in a profile.
- Click Submit. The profile is active immediately.
Assigning a Modular Sensor Profile to a Sensor
To assign a Modular Sensor profile to a sensor:
-
Navigate to the System | Collection | Sensors page.
-
Click sensor's icon to edit its settings. The Edit Sensor Parameters dialog box appears.
-
Use the Sensor Profile dropdown to assign the Modular Sensor profile with the Aggregator feature enabled that you configured in the previous procedure.
-
Click Submit. The profile is immediately assigned to that aggregator.
Configuring Sensors to Use an Aggregator
To configure a sensor to use an aggregator:
-
Click on System | Collection | Sensors. The Sensors page appears.
-
Click to edit a sensor. The Edit Sensor Parameters screen appears.
-
Choose a Primary Aggregator from the drop-down.
-
Choose a Secondary Aggregator from the drop-down.
-
Click Submit. The sensor immediately starts sending traffic to the primary aggregator.
The Primary/Secondary Aggregator options do not appear for Linux server sensors in the 5.0.4 release. However, you can still configure them to use an aggregator with the set/show aggregator
commands from the sensor CLI.
When you finish configuring all of the sensors, you can remove the associated open ports from your firewall.