Virtual machine from OVF properties: Difference between revisions
No edit summary |
No edit summary |
||
| (23 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
== Introduction == | == Introduction == | ||
InfiniStream virtual appliances are build from OVF. | |||
These are the properties of the vitual machines immediately after deployment. | |||
== Solution == | == Solution == | ||
=== Flow | === nGenius Flow Collector Virtual Appliance === | ||
{| | {| border="1" cellpadding="1" cellspacing="1" style="width: 500px" | ||
|- | |- | ||
! scope="col" | Virtual Hardware | ! scope="col" | Virtual Hardware | ||
| Line 17: | Line 19: | ||
|- | |- | ||
| Memory | | Memory | ||
| | | 8 GB | ||
|- | |- | ||
| Hard Disk 1 | | Hard Disk 1 | ||
| | | 50 GB (Thick Provisioned) | ||
|- | |- | ||
| Hard Disk 2 | | Hard Disk 2 | ||
| | | (*) | ||
|- | |- | ||
| Network adapter 1 | | Network adapter 1 | ||
| E1000 | | 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: | |||
{| border="1" cellpadding="1" cellspacing="1" style="width: 500px" | |||
|- | |||
! scope="col" | Flow per second (f/s) | |||
! scope="col" | Retention | |||
! scope="col" | 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 (standalone) === | |||
This is vSTREAM, a virtual machine dedicated for network monitoring. Read this article on [[vSTREAM_Embedded_resource_usage|resources used by vSTREAM Agent]]. | |||
{| border="1" cellpadding="1" cellspacing="1" style="width: 500px" | |||
|- | |||
! scope="col" | Virtual Hardware | |||
! scope="col" | 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 monitoring. | |||
($) 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. | |||
Latest revision as of 09:19, 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 (standalone)
This is vSTREAM, a virtual machine dedicated for network monitoring. Read this article on resources used by vSTREAM Agent.
| 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 monitoring.
($) 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.