vTPS can be deployed with the following:
- VMWare ESXi
- Kernel-Based Virtual Machine (KVM)
General Requirements: To deploy a vTPS in any software environment, the following system specifications are required:
- Memory (RAM) - 8 GB
- Cores - vTPS supports configurations of either two cores (meets general performance requirements) or three cores (for enhanced performance; upgrading to three cores after installation requires a shutdown, configuration change, and reboot)
- Disk space - 16.2 GB
Note: Both thin and thick provisioning are supported, but for optimum performance, use thick provisioning.
- CPU—Host CPU must support the SSSE3 instruction set. Tested CPU configurations:
- Intel Xeon CPU E5-2697v2
- Intel Xeon CPU E5-2690
- Intel Xeon CPU E5-2683v3
- Intel Xeon CPU X5670
- Intel Xeon CPU X5650
VMware ESXi requirements
The vTPS supports the following system and software environment for a VMware ESXi deployment:
- Hypervisor version - ESXi version 5.5 (Update-1) or 6.0
- Networking requirements - three vNICs - one for management and two for data. Both vSwitches and distributed vSwitches (dvSwitches) are supported. The two data vNICs must be configured in promiscuous mode. Ensure that any Forged Transmits and MAC Address Changes are set to ACCEPT in order for network packets to get forwarded.
Kernel-Based Virtual Machine (KVM) requirements
Software environments - Ensure you have the following minimum requirements:
Note: vTPS installation has been verified with RHEL version 7.1 KVM hosts. A three-core configuration requires the following minimum software package versions:
- libvirt version 1.1.0
- Quick Emulator (QEMU) version 1.5.3
- virt-install version 1.1.0
Networking requirements - Three bridge interfaces, one for management and two for data.
Console access – The default and recommended console is a graphical UI, such as virt-manager, virtviewer, vncviewer, or other VNC client.
Note: The vTPS supports only one console type. After you initially select the console type, you cannot change it later.
OpenStack HEAT template requirements
A HEAT template can be used to describe the vTPS infrastructure.
Note: The instructions in this section describe a GUI deployment of a TippingPoint vTPS that uses the OpenStack Liberty release. If you use a different release or customization of OpenStack components, you might see small variations in the procedure.
vTPS emulation requirements
The OpenStack HEAT template requires the following emulation configuration:
- Processor emulator – ssse3 enabled
- Disk driver – ide
- Support for virtio on all three interfaces (management port and two data ports)
vTPS functional requirements
The OpenStack HEAT template requires the following functional configuration:
- Hypervisor – kvm
- Virtual processors – 2 or 3
- RAM – 8GB
- Disk image – 1 (system disk required, 16GB total size)
- Configuration drive – optional