Virtual machine from OVF properties: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
== Solution == | == Solution == | ||
=== nGenius Flow Collector Virtual Appliance | === nGenius Flow Collector Virtual Appliance === | ||
{| border="1" cellpadding="1" cellspacing="1" style="width: 500px" | {| border="1" cellpadding="1" cellspacing="1" style="width: 500px" | ||
| Line 25: | Line 25: | ||
|- | |- | ||
| Hard Disk 2 | | Hard Disk 2 | ||
| * | | (*) | ||
|- | |- | ||
| Network adapter 1 | | Network adapter 1 | ||
| Line 31: | Line 31: | ||
|} | |} | ||
The size of this hard disk depends on the number of flows per second received form all flow exporting devices and the number of days you want detailed session data to remain available. | (*) The size of this hard disk depends on the number of flows per second received form all flow exporting devices and the number of days you want detailed session data to remain available. | ||
Use this table for guidance: | Use this table for guidance: | ||
| Line 70: | Line 70: | ||
| | ||
=== vSTREAM | === vSTREAM === | ||
{| border="1" cellpadding="1" cellspacing="1" style="width: 500px" | {| border="1" cellpadding="1" cellspacing="1" style="width: 500px" | ||
| Line 78: | Line 78: | ||
|- | |- | ||
| CPU | | CPU | ||
| 2 | | 2 (#) | ||
|- | |- | ||
| Memory | | Memory | ||
| | | 4 GB (#) | ||
|- | |- | ||
| Hard Disk 1 | | Hard Disk 1 | ||
| Line 87: | Line 87: | ||
|- | |- | ||
| Hard Disk 2 | | Hard Disk 2 | ||
| | | ($) | ||
|- | |- | ||
| Network adapter 1 | | Network adapter 1 | ||
| Line 93: | Line 93: | ||
|} | |} | ||
(#) We deploy vSTREAM with two interfaces for monitor. | |||
The size of the second hard disk that will serve as data store, is configurable during ovf deployment. | ($) The size of the second hard disk that will serve as data store, is configurable during ovf deployment. | ||
The size of this hard disk depends on the expected traffic volume and how long you want packets to be available; it should not be less than 100GB. | The size of this hard disk depends on the expected traffic volume and how long you want packets to be available; it should not be less than 100GB. | ||
Revision as of 09:10, 2 November 2019
Introduction
InfiniStream virtual appliances are build from OVF.
These are the properties of the vitual machines immediately after deployment.
Solution
nGenius Flow Collector Virtual Appliance
| Virtual Hardware | Size |
|---|---|
| CPU | 8 |
| Memory | 8 GB |
| Hard Disk 1 | 50 GB (Thick Provisioned) |
| Hard Disk 2 | (*) |
| Network adapter 1 | E1000 |
(*) The size of this hard disk depends on the number of flows per second received form all flow exporting devices and the number of days you want detailed session data to remain available.
Use this table for guidance:
| Flow per second (f/s) | Retention | Hard Disk 2 Size |
|---|---|---|
| 5k | 7 d | 200 GB |
| 20k | 7 d | 800 GB |
| 50k | 7 d | 2 TB |
| 5k | 14 d | 400 GB |
| 20k | 14 d | 1600 GB |
| 50k | 14 d | 4 TB |
The second hard disk shall be Thick Provisioned.
vSTREAM
| Virtual Hardware | Size |
|---|---|
| CPU | 2 (#) |
| Memory | 4 GB (#) |
| Hard Disk 1 | 32 GB (Thick Provisioned) |
| Hard Disk 2 | ($) |
| Network adapter 1 | VMXNET3 |
(#) We deploy vSTREAM with two interfaces for monitor.
($) The size of the second hard disk that will serve as data store, is configurable during ovf deployment.
The size of this hard disk depends on the expected traffic volume and how long you want packets to be available; it should not be less than 100GB.