Hardware Requirements

vSZ-D supports auto scaling, which means the number of CPU cores can be expanded without needing a software update. RUCKUS recommends from three to six CPU core allocations for the vSZ-D.

Note: The minimum memory and CPU requirements for vSZ have changed in this release. You may need to upgrade your infrastructure before upgrading. Please read carefully. This is the minimum requirement recommended. Refer to the RUCKUS SmartZone Release Notes or the RUCKUS Virtual SmartZone Getting Started Guide.
The following table lists the minimum hardware requirements recommended for running an instance of vSZ-D.

vSZ-D Hardware Requirements

Hardware Component Requirement
Hypervisor support required by Management Interface VMWare ESXi 6.7 and later, or KVM CentOS 7.9 (64 bit)
Processor Intel Xeon E55xx series or the newer E5-2xxx series (recommended).
CPU cores
  • Minimum 3 to 6 cores per instance dedicated for data plane processing.
  • Direct I/O mode for best data plane performance.
    Note: Actual throughput numbers will vary depending on infrastructure and traffic type.
  • vSwitch mode for flexibility
Memory Minimum 6 GB memory per instance
Disk space 10GB per instance
Ethernet interfaces 2
NICs
  • Use Intel DPDK‑capable adapters for the data interface.
  • Supported Intel NIC families/models: I350; 82599/82599EB/82599ES; X520; X710; XL710.
Note: Supported drivers for the supported NICs:
  • Linux/KVM: igb, ixgbe, i40e/i40evf
  • VMware ESXi: igb, ixgbe, i40en

Important Notes About Hardware Requirements

  • If you change the number of CPU cores, you must reboot vSZ-D for the changes to take effect.
  • Linux and Network Processing Engine (NPE) share the first core. Other cores are dedicated to NPE.
  • vSZ-D requires two interfaces and these interfaces must be deployed on different subnets.
  • The management interface of the vSZ-D can be any model if the hypervisor supports the NIC.
  • The data interface needs to be Intel Data Plane Development Kit (DPDK)-based.