Server Hardware Recommendations

Last updated
Save as PDF

This article provides the hardware recommendations for the vBond orchestrator server, vEdge Cloud router server, Manage Network Management System (NMS) server, and vSmart controller server.

vBond Orchestrator Server Recommendations

The resources required to run the vBond orchestrator on the VMware vSphere ESXi or the Kernel-based Virtual Machine (KVM) server vary depending on the number of devices you deploy in the overlay network. See Table 1. Note that the OS volume must be on a solid-state drive (SSD).

Table 1: vBond Orchestrator Server Recommendations

Devices	vCPUs	RAM	OS Volume	Bandwidth	vNICs
1-50	2	4 GB	10 GB	1 Mbps	2 (one for tunnel interface, one for management)
51-250	2	4 GB	10 GB	2 Mbps	2 (one for tunnel interface, one for management)
251-1000	2	4 GB	10 GB	5 Mbps	2 (one for tunnel interface, one for management)
1001 or more	4	8 GB	10 GB	10 Mbps	2 (one for tunnel interface, one for management)

vEdge Cloud Router Server Recommendations

Table 2 lists the resources required to run the vEdge Cloud router on the ESXi or KVM server.

**Table 2: vEdge Cloud Router Server Recommendations**
Specification	Description
Software image format	AMI OVA QCOW2 VDX
Recommended host operating system	Red Hat Enterprise Linux 7.0 Ubuntu 14.04/16.04 LTS
Supported hypervisors	Amazon Machine Image (AMI) on Amazon Web Services (AWS) Azure Hyper V Kernel-based Virtual Machine (KVM) VMWare ESXi 5.5 and ESXi6.0
Server specifications	Intel Sandy Bridge, 2.0-GHz clock frequency Intel ATOM Rangely, 2.0-GHz clock frequency WAN interface—Gigabit Ethernet NICs CPU—Minimum of 2 virtual CPUs (vCPUs) RAM—2 GB Disk space—10 GB. The vEdge Cloud VM instance itself requires 1 GB. The recommendation of 10 GB is made to account for the hypervisor and any other modules that might require a small amount memory. Bandwidth—Up to 2 Gbps Network interfaces—Minimum of 3: one for tunnel interface, one for management, one for LAN. Maximum of 8 vNICs per VM. Use VMXNET3 NICs only.
Bandwidth and CPU	500 Mbps—Minimum of 2 vCPUs 1 Gbps—Minimum of 4 vCPUs 2 Gbps—Minimum of 8 vCPUs

vManage NMS Server Recommendations

The resources required to run the vManage NMS on the ESXi or KVM server vary depending on the number of devices you deploy in the overlay network. See Table 3. Note that the OS and database volumes must be on a solid-state drive (SSD).

If your overlay network has a small number devices, but if they generate large amounts of DPI or cflowd data, it is recommended that you use the server recommendations given for 251-1000 devices or for 1001 or more devices.

Table 3: vManage NMS Server Recommendations

Devices	vCPUs	RAM	OS Volume	Database Volume	Bandwidth	vNICs
1-250	16	32 GB	20 GB	500 GB, 1500 IOPS	25 Mbps	3 (one for tunnel interface, one for management, one for the vManage cluster message bus)
251-1000	32	64 GB	20 GB	1 TB, 3072 IOPS	100 Mbps	3 (one for tunnel interface, one for management, one for the vManage cluster message bus)
1001 or more	32	64 GB	20 GB	1 TB, 3072 IOPS	150 Mbps	3 (one for tunnel interface, one for management, one for the vManage cluster message bus)

vSmart Controller Server Recommendations

The resources required to run the vSmart controller on the ESXi or KVM server vary depending on the number of devices you deploy in the overlay network. See Table 4. Note that the OS volume must be on a solid-state drive (SSD).

Table 4: vSmart Controller Server Recommendations

Devices	vCPUs	RAM	OS Volume	Bandwidth	vNICs
1-50	2	4 GB	16 GB	2 Mbps	2 (one for tunnel interface, one for management)
51-250	4	8 GB	16 GB	5 Mbps	2 (one for tunnel interface, one for management)
251-1000	4	16 GB	16 GB	7 Mbps	2 (one for tunnel interface, one for management)
1001 or more	8	16 GB	16 GB	10 Mbps	2 (one for tunnel interface, one for management)

Additional Information

Configuring OMP/Firewall Ports for Viptela Deployments
Create vBond VM Instance on ESXi
Create vBond VM Instance on KVM
Create vEdge Cloud Router VM Instance on AWS
Create vEdge Cloud VM Instance on ESXi
Create vEdge Cloud VM Instance on KVM
Create vManage VM Instance on ESXi
Create vManage VM Instance on KVM
Create vSmart VM Instance on ESXi
Create vSmart VM Instance on KVM