Faddom

Faddom supports the following options for capturing network traffic:

VMWare environment - See details here: <a href="https://support.faddom.com/en/articles/9059438-how-to-enable-traffic-collection-in-vmware">Setting up network traffic collection in VMware</a> ​

Nutanix AHV - IPFIX needs to be provided. For full details and the prerequisites see <a href="https://support.faddom.com/en/articles/9428869-how-to-discover-nutanix-ahv">How to Discover Nutanix AHV</a> ​

Physical servers | Netflow Configured in the router or the switch and directed to a Faddom Sensor

1. Verify a Faddom sensor is installed and configured.
2. 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 <a href="https://support.faddom.com/en/articles/9428889-capturing-network-traffic-using-agents">Capturing network traffic using agents</a>

1. Verify a Faddom sensor is installed and configured.
2. Configure the collector address for the Host sFlow agent to the Faddom sensor. ​ See also <a href="https://support.faddom.com/en/articles/9428894-recommended-sflow-settings">Recommended sFlow settings</a>. ​ ​

Physical servers | Port mirroring/tap Connecting the Faddom Sensors to mirror ports on network switches or to TAP devices.

1. Prepare a server for the Faddom Sensor – either Windows or Linux, can be physical or virtual.
2. Direct the mirrored traffic to the Faddom Sensor.
3. Firewall configuration: Faddom Server should connect to the Faddom Sensors – TCP port 9545 (by default).
4. 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. ​ ​

1. Install a sensor on the relevant servers – from which traffic should be captured.
2. Firewall configuration (where applicable): Faddom Server should connect to the Faddom Sensors – TCP port 9545 (by default).
3. 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 <a href="https://support.faddom.com/en/articles/9428893-hyper-v-sflow-configuration">Hyper-V sFlow Configuration</a>. ​ ​

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 ​<a href="https://support.faddom.com/en/articles/9428871-mapping-an-aws-subscription-using-faddom">Mapping an AWS Subscription Using Faddom</a> ​<a href="https://support.faddom.com/en/articles/9059442-mapping-a-microsoft-azure-subscription-using-faddom">Mapping a Microsoft Azure subscription using Faddom</a>

1. VMWare environment - See details here: <a href="https://support.faddom.com/en/articles/9059438-how-to-enable-traffic-collection-in-vmware">Setting up network traffic collection in VMware</a> ​
2. Nutanix AHV - IPFIX needs to be provided. For full details and the prerequisites see <a href="https://support.faddom.com/en/articles/9428869-how-to-discover-nutanix-ahv">How to Discover Nutanix AHV</a> ​
3. Physical servers | Netflow Configured in the router or the switch and directed to a Faddom Sensor
 1. Verify a Faddom sensor is installed and configured.
 2. Configure the router or the switch to send Netflow data to the Faddom sensor. ​
4. 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 <a href="https://support.faddom.com/en/articles/9428889-capturing-network-traffic-using-agents">Capturing network traffic using agents</a>
 1. Verify a Faddom sensor is installed and configured.
 2. Configure the collector address for the Host sFlow agent to the Faddom sensor. ​ See also <a href="https://support.faddom.com/en/articles/9428894-recommended-sflow-settings">Recommended sFlow settings</a>. ​ ​
5. Physical servers | Port mirroring/tap Connecting the Faddom Sensors to mirror ports on network switches or to TAP devices. 
 1. Prepare a server for the Faddom Sensor – either Windows or Linux, can be physical or virtual.
 2. Direct the mirrored traffic to the Faddom Sensor.
 3. Firewall configuration: Faddom Server should connect to the Faddom Sensors – TCP port 9545 (by default).
 4. Define the sensor in the Faddom GUI. 
6. Physical servers |local mode Installing Sensors on specific servers (physical or virtual). The installation is simple and does not require restarting the server. ​ ​
 
 1. Install a sensor on the relevant servers – from which traffic should be captured.
 2. Firewall configuration (where applicable): Faddom Server should connect to the Faddom Sensors – TCP port 9545 (by default).
 3. Define the sensors in the Faddom GUI. ​ ​
7. 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 <a href="https://support.faddom.com/en/articles/9428893-hyper-v-sflow-configuration">Hyper-V sFlow Configuration</a>. ​ ​
8. Hyper-V | port mirroring Connect the Faddom sensors to mirror ports on network switches. ​ ​
9. Cloud environments ​Create permissions for Faddom to access the cloud environment and enable flow logs ​<a href="https://support.faddom.com/en/articles/9428871-mapping-an-aws-subscription-using-faddom">Mapping an AWS Subscription Using Faddom</a> ​<a href="https://support.faddom.com/en/articles/9059442-mapping-a-microsoft-azure-subscription-using-faddom">Mapping a Microsoft Azure subscription using Faddom</a>

For non-heterogeneous environments, use multiple options. Faddom will combine the data in the system.