System requirements depend primarily on the number of IP flows that will be received and processed by the system. The bigger the network traffic volume, the higher the number of IP flows. This reflects strongly on IP flow processing speed and Raw Data file size. The former rises the CPU speed requirement and the latter rises the amount of HDD space needed to store Raw Data.
In addition to this, HDD space requirement rises with the number of Traffic Patterns and subnets you create and with the amount of Raw Data files you decide to store on your system. The number of Traffic Patterns you create also affects the IP flow processing speed.
Hardware Requirements
:NetFlow Analyzer Server
| Package (max fps) | Usual Load (avg fps, avg nodes) | CPU | RAM | HDD Space |
|---|
| Free (5 fps) | 2 fps, 10 nodes | Singe-core 1.6GHz processor |
2GB5 20 GB |
| Express (50 fps) | 20 fps, 50 nodes | Singe-core |
16GHz 4GB10 SME | Small & Medium (500 fps) | 200 fps, 100 nodes | Singe-core |
16GHz 4GB5)Modern dual core processor, each core at least 1.6GHz| , 500 nodes | Dual-core 2.0GHz processor | 16GB |
100 | 500 GB - SAS or SSD in RAID 0 or similar setup with striping |
| Large Enterprise ( |
10)| , 1,500 nodes | Octa-core 2.0GHz processor | 32GB | 5 TB |
Modern quad core processor, each core at least 1.6GHz | 16GB | 200 GB | - SAS or SSD in RAID 0 or similar setup with striping |
The recommended server requirements assume default configuration for NetVizura NetFlow Analyzer. Significantly increasing the number of flows processed (above 10.000 fps on average), and monitoring nodes can increase CPU and memory requirements. Significantly increasing the number of flows and flow archive storing time will increase flow archive size and require more HDD space and/or additional external storage.
Assumptions: 10.000 fps, 1.000 counters, 30 days of Raw Data and 365 days of database history stored.
General assumptions: 30 days of Archive and 365 days of Database history stored.
| Info |
|---|
| Info |
|---|
- These are recommended server requirements based on the Usual Load (during business hours) given in the table above. Average flows processed and monitoring counters impact all parameters (CPU, RAM and HDD). Archive and Database storing time also impacts HDD space and may require additional external storage.
|
- NetVizura comes with built-in database which will be installed on the NetVizura server. You can use a different server for your database to achieve better performance but note that NetVizura only supports PostgreSQL version 9.2 or higher6+.
- NetFlow Analyzer Raw Data files are stored on the NetVizura server. You can store them in some other storage, but keep in mind that it can have a considerable impact on the performance due to large files being transferred across your network between the NetVizura server and Raw data files storage.
|
EventLog Analyzer Server
| Package (max exporters) | Usual Load (max mps, alarms) | CPU | RAM | HDD Space |
|---|
| Free (3 exporters) | 500 mps, 2 alarms | Singe-core 1.6 GHz | 2GB | 1.2 TB - SAS or SSD in RAID 0 or similar set-up with striping |
| Small & Medium (20 exporters) | 5k mps, 5 alarms | Quad-Core 3.0 GHz | 4GB | 12 TB - SAS or SSD in RAID 0 or similar setup with striping |
| Enterprise (100 exporters) | 30k mps, 10 alarms | Octa-Core 3.6 GHz | 16GB | 120 TB - SAS or SSD in RAID 0 or similar setup with striping |
| Premium (100+ exporters) | Contact us |
General assumptions: 30 days of Database history stored.
| Info |
|---|
These are recommended server requirements based on the Usual Load (during business hours) given in the table above. Maximum messages processed and applied alarms impact all parameters (CPU, RAM and HDD). Database storing time also impacts HDD space and may require additional external storage. |
MIB Browser Server
| Package | CPU | RAM | HDD Space |
|---|
| Minimum | Singe-core 1.6GHz processor | 2GB | 500 MB |
General assumptions: lifetime Database history stored.