Hardware Requirements

vSZ-D supports auto scaling, which means the number of CPU cores can be expanded without needing a software update. Ruckus has tested 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 Release Notes or the vSZ Getting Started Guide.
The following table lists the minimum hardware requirements recommended for running an instance of vSZ-D.
Table 1. vSZ-D hardware requirements
Hardware Component Requirement
Hypervisor support required by Management Interface VMWare ESXi 6.7 and later OR KVM (CentOS 7.4 64bit)
Processor Intel Xeon E55xx and above. Recent Intel E5-2xxx chips are recommended
CPU cores
  • Minimum 3 to 6 cores per instance dedicated for data plane processing.
  • DirectIO 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 that support Intel DPDK requiredby Data Interface
  • Intel NICs igb, ixgbe, i40en
  • I350
  • 82599, 82599EB, 82599ES, X520, X710, XL710

Important Notes About Hardware Requirements

  • If you change the number of CPU cores, you must reboot vSZ-D for the changes to take effect.
  • The first core is always shared between Linux and NPE. 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 as long as the NIC is supported by the hypervisor.
  • The data interface needs to be Intel DPDK based.