Flowlink Requirements
This topic details the prerequisites and hardware capacity requirements for configuring and using Flowlink.
Prerequisites
Make sure you possess and/or have configured the following:
CentOS or RHEL server
Root privileges to the server
Flowlink RPM downloaded from the Illumio Support site
PCE with Service Account API Key and Secret
Important
You must have the Org User role to configure Flowlink.
CPU, Memory, and Storage Requirements
To use Flowlink, your hardware must meet the capacity requirements detailed in this section.
Machine Type | Cores/Clock Speed1 | RAM per Node2 | Storage Device Size3 and IOPS4 |
|---|---|---|---|
Flowlink 2500 workloads |
| 8 GB |
|
Footnotes:
1 CPUs:
The recommended number of cores is based only on physical cores from allocated CPUs, irrespective of hyper-threading or virtual cores. For example, in AWS one vCPU is only a single hyper-thread running on a physical core, which is half a core. 16 physical cores equates to 32 vCPUs in AWS.
Full reservations for vCPU. No overcommit.
2 Full reservations for vRAM. No overcommit.
3 Additional disk notes:
Storage requirements for network traffic data can increase rapidly as the amount of network traffic increases. Allocating a separate, large storage device for traffic data can accommodate these rapid changes without potentially interrupting the service.
Network File Systems (NFS) is not supported.
4 Input/output operations per second (IOPS) are based on 8K random write operations. IOPS specified for an average of 300 flow summaries (80% unique src_ip, dest_ip, dest_port, proto) per workload every 10 minutes. Different traffic profiles might require higher IOPS.
Flowlink Storage Partitioning
Storage Device | Partition mount point | Size to Allocate | Notes |
|---|---|---|---|
Device 1, Partition A |
| 20 GB | Logrotate must be configured to limit the disk consumption of Flow & System Logs. |