Product Documentation

System Requirements and Provisioning

Oct 18, 2013

CloudBridge VPX runs on XenServer 5.5 or later, VMware vSphere ESX/ESXi 4.1 or later, Hyper-V under 64-bit Windows Server 2008 R2 SP1, and Amazon AWS. CloudBridge VPX supports four configurations, from 2 to 8 GB of RAM and 100 to 500 GB of disk space. The intermediate, 4 GB RAM/250 GB disk configuration is similar to the Repeater 8500 series appliance.

Supported Configurations
The following tables list all supported CloudBridge VM configurations. (Amazon AWS configurations are preselected and are somewhat different.)
Type vCPUs RAM Disk Maximum WAN Speed Maximum Accelerated Connections Maximum CloudBridge Plug-ins
2 GB production config. 2 2 GB 100 GB 2 mbps 1,000 50
4 GB production config. 2 4 GB 250 GB 10 mbps 10,000 250
4 GB production config.* 2 4 GB 250 GB 45 mbps 15,000 400
8 GB production config. 4 8 GB 500 GB 45 mbps 25,000 500
* With 45mbps license
Other configurations (not for production networks)
Type vCPUs RAM Disk Maximum WAN Speed Maximum Accelerated Connections Maximum CloudBridge Plug-ins
VPX Express 2 1 GB 60 GB 512 kbps 10 5
Min. evaluation config. 2 1 GB 60 GB 2 mbps 1,000 5
Minimum Resource Requirements
A CloudBridge VPX virtual machine has the following minimum hardware requirements for a production environment
  • 2 GB RAM
  • 100 GB disk (local disks provide the best performance)
  • 2 virtual NICs (Ethernet ports), except for Amazon AWS, which requires only one virtual NIC
  • 2 virtual CPUs
  • A modern CPU (Intel Nehalem or newer or AMD Family 10h or newer, both of which were introduced in 2008). Older CPUs may run at reduced performance due to the use of emulated x86 TSC (timestamp counter) functionality. If clock states higher than C1 are not used and SpeedStep/PowerNow modes are disabled in the BIOS of older processors, TSC emulation will not be used and the system will run at normal speed.
The server hosting CloudBridge VPX must have RAM, CPU, and disk resources greater than those required by the VPX VM. (VPX does not support VMware hardware over-commit.) Obviously, the server must have enough resources to run the hypervisor as well as the virtual appliance. However, having as many physical Ethernet ports as virtual ones is not mandatory if one of a CloudBridge VPX VM's Ethernet ports is connected to another virtual machine on the same server. Possible Ethernet options include:
  • Mapping the CloudBridge VPX VM's two virtual ports to two physical ports, rendering its operation equivalent to that of a stand-alone CloudBridge.
  • Mapping one of CloudBridge VPX VM's virtual ports to a physical port, and the other to a virtual network containing one or more virtual machines on the same server, thus creating an accelerated server.
  • Mapping each of CloudBridge VPX VM's virtual ports to a virtual network, thus chaining the CloudBridge VPX VM between two sets of VMs on the same server.

The following figure shows a CloudBridge VPX VM in a one-arm deployment for traffic that terminates on another virtual machine on the same server. Only one physical port is required in this case, but both virtual ports are used.

Figure 1. Ethernet (Network) Port Assignments, One-Arm Operation

Maximum Usable Resources
Following are the maximum amount of resources that a single CloudBridge VPX virtual machine can use effectively
  • 4 virtual CPUs
  • 8 GB RAM
  • 500 GB disk
  • 4 virtual NICs
Server resources not allocated to CloudBridge VPX VMs are available to other VMs on the same server, but be careful to avoid overcommitting resources.
Disk and RAM

As the amounts of RAM and disk space are increased, the additional resources are allocated primarily to the compression subsystem. Increased memory also allows more connections and acceleration partners to be supported.

The CloudBridge compression system makes heavy demands on the disk subsystem. In general, local disk storage outperforms network disk storage and reduces resource contention on both the LAN and the network disk.

The relationship between disk or memory resources and link speed is indirect. Memory and disk sizes have no effect on the speed at which packets are sent over the link (bps). Providing more memory and disk space improves compression performance by increasing the amount of compression history that can be used for pattern matching.

Virtual NICs

Except for Amazon AWS, two virtual network interfaces are required. They are bridged and used for both acceleration and the browser based user interface. These interfaces must be attached to different virtual networks. Note that, for one-arm operation, the second interface can be a stub, attached only to a CloudBridge VPX VM.

A third virtual network interface provides an independent interface to the CloudBridge VPX VM, which is the equivalent to the Primary port on a physical appliance. It can be used for the browser based interface, but not for acceleration.

Other Virtual Machines
  • Server resources beyond those allocated to CloudBridge VPX are available for other virtual machines on the same server.
  • Resource usage by other VMs affects CloudBridge VPX performance, and vice versa. Acceleration makes intensive use of CPU, memory, disk, and network.
Virtual network routing can be used to connect other VMs on the server to CloudBridge VPX VMs, but the simplest method of connecting such VMs is to attach them to the server's LAN-side Ethernet port. WAN-bound packets then pass through the CloudBridge VPX VM's bridge and are accelerated automatically, whether they originate inside or outside the server hosting VPX.
Figure 2. An Inline Deployment that Accelerates External Traffic and Traffic from Local VMs