System Requirements
NetFlow processing tends to consume a lot of system resources due to a huge number of data that's received, stored and visualized by the collector. In large networks, special precautions should be made to get optimal flow processing performance. A dedicated flow processing server may be required in some cases.
Several factors can impact system requirements of NetFlow server. The first factor is flow rate (number of flows per second) that's received by an Iotellect. It depends to the number of sensors, network traffic volume, and sensor-side flow exporting settings. The second factor is Iotellect Server-side flow processing setup: aggregation intervals, discarded traffic percentages, DNS name resolution settings, etc.
When planning your Iotellect Network Manager installation for flow processing, keep in mind that actual requirements are determined by your network configuration and by the volume and uniqueness of NetFlow data that is received. Actual resource usage can vary greatly depending on these factors.
The below table helps to find system configuration for a dedicated flow processing server. If flow processing is combined with regular network monitoring, system requirements should be also combined with normal Iotellect Server system requirements. Note, that NetFlow processing especially fastidious about HDD space and I/O performance.
Flow Rate per Second | CPU | CPU Cores | RAM | Disk Space | Comments |
Up to 100 | 3 GHz | 2 | 4 GB | 500 GB | |
100 to 1000 | 3 GHz | 4 | 8 GB | 1 Tb | |
1000 to 10000 | 2 * 3 GHz | 8 | 16 GB | 2 Tb | 10K or 15K RPM SAS drives in RAID 0 or 10 configuration are highly recommended |
Above 10000 | 2 * 3 GHz | 16 | 32 GB | 4 Tb | 15K RPM SAS drives in RAID 0 or 10 configuration are highly recommended |
If you have additional questions or experience performance problems, please contact Iotellect to get advice from our system engineers.
Was this page helpful?