Faddom Help Center

Server Installation - Pre-Installation

Faddom Components

Server

The Faddom server is responsible for getting traffic summaries from the sensors and discovering the application maps. It hosts the web services and communicates with all other components. 

 

The server uses an Apache Tomcat Server and a PostgreSQL database.

The Faddom Server includes a web UI including the views and administrative capabilities required to work with Faddom.

Proxy

A proxy server can optionally be installed to allow Faddom to map a remote environment. This allows the Faddom server to be deployed in a separate environment than the one it is mapping (i.e. installing the Faddom server in the public cloud and a proxy server in a separate data center).

Sensor

The Faddom Sensor is used to capture data about TCP and UDP activity between computers across the network. It can use either full network capture or statistical capture (NetFlow/sFlow based). 

Faddom Server connects to the sensor periodically to get a summary of the traffic that was captured by the sensor.

 

Deployment Options

Faddom supports multiple deployment options that can fit every environment. 

You can quickly start with Faddom in a VMWare environment.

Explore the various deployment options in the deployment guide.

Installation Prerequisites

Software Prerequisites

OS (operating system):

  • Windows: 2012 and above (physical/virtual)
  • Linux (Faddom virtual appliance - CentOS 7)

Hardware:

 

Component

Requirements

CPU

Memory

Disk

Faddom Server

Minimum

Dual CPU/Dual-core CPU

4GB RAM

10GB free disk space

Recommended

8 CPUs/cores

8GB RAM

40GB free disk space

Faddom Proxy

Minimum

Single CPU/Single-core CPU

2GB RAM

1GB free disk space

Recommended

Dual CPU/Dual-core CPU

2GB RAM

1GB free disk space

Faddom Sensor on VMWare ESX

Minimum

Single CPU/Single-core CPU

1GB RAM

50MB free disk space

Recommended

Dual CPU/Dual-core CPU

2GB RAM

1GB free disk space

Faddom Sensor with port mirroring/tap

Minimum

Dual CPU/Dual-core CPU

2GB RAM

50MB free disk space

Faddom Sensor local mode

Minimum

Single CPU/Single-core CPU

1GB RAM

50MB free disk space


Network Prerequisites

Based on deployment type:

  • NetFlow/sFlow mode
    NetFlow should be configured either at the switch/router level or on the VMware vSwitch. The NetFlow traffic should be directed to the IP address of the Faddom Server/Sensor; any port can be used (all incoming traffic is captured).
    Supported NetFlow versions: 5, 6, 7, 9, IpFix.

    Note: For NetFlow-only deployments, use a single server setup without a separate sensor. A separate sensor is supported.
    It is also possible to configure multiple NetFlow statistics outputs from separate networks to the Faddom Server/Sensor host.

  • ESX mode
    The Faddom Sensor Virtual Appliance should be deployed to each ESX Server and connected to a port group configured with promiscuous mode.

Was this article helpful?
0 out of 0 found this helpful

Comments