Faddom supports the following options for capturing network traffic:
- VMWare environment - See details here: Setting up network traffic collection in VMware
- Physical servers | Netflow
Configured in the router or the switch and directed to a Faddom Sensor.
- Verify a Faddom sensor is installed and configured.
- Configure the router or the switch to send Netflow data to the Faddom sensor.
- Physical servers | sFlow
Install the Host sFlow agent on any server to collect utilization information and network traffic. For Windows Servers the Faddom-created sFlow Generator is required. For full details, please see Capturing network traffic using agents
- Verify a Faddom sensor is installed and configured.
- Configure the collector address for the Host sFlow agent to the Faddom sensor.
See also Recommended sFlow settings.
- Physical servers | Port mirroring/tap
Connecting the Faddom Sensors to mirror ports on network switches or to TAP devices.
- Prepare a server for the Faddom Sensor – either Windows or Linux, can be physical or virtual.
- Direct the mirrored traffic to the Faddom Sensor.
- Firewall configuration: Faddom Server should connect to the Faddom Sensors – TCP port 9545 (by default).
- Define the sensor in the Faddom GUI.
- Physical servers |local mode
Installing Sensors on specific servers (physical or virtual). The installation is simple and does not require restarting the server.
- Install a sensor on the relevant servers – from which traffic should be captured.
- Firewall configuration (where applicable): Faddom Server should connect to the Faddom Sensors – TCP port 9545 (by default).
- Define the sensors in the Faddom GUI.
- Hyper-V | sFlow
Use the Faddom extension to the Hyper-V switch, which exports network traffic statistics from Hyper-V hypervisor in sFlow format.
Follow the steps in Hyper-V sFlow Configuration. - Hyper-V | port mirroring
Connect the Faddom sensors to mirror ports on network switches. - Cloud environments
Create permissions for Faddom to access the cloud environment and enable flow logs
Mapping an AWS Subscription Using Faddom
Mapping a Microsoft Azure subscription using Faddom
For non-heterogeneous environments, use multiple options. Faddom will combine the data in the system.
Comments