How to identify and validate the vSZ resource requirements?

[remya_murugesh]

vSZ requires enough hardware resources to sustain the service. vSZ cannot support deployment in low performance hypervisor.

During the time of deployment or upgrade it is always a good practice to reconfirm and validate the resource requirements of vSZ and validate the system performance:

Use the SZ CLI in debug-tools > system > system performance. The command will run system benchmark on CPU and IO for vSZ.

Note: Disks IO is most important in vSZ cluster. Disk IO is the slowest subsystem in a server, which means that write-heavy clusters can easily saturate their disks, which in turn become the bottleneck of the cluster.

The vSZ resource requirements for the deployment will vary from the VM deployment type  - Essentials or High Scale and the Virtual Platform – Cloud or on-premises

In case of a cluster with multiple nodes, every node is expected to have the same SKU or resource allocation, and it is not recommended to run multiple vSZs on the same VM hardware for high end deployment.

Any resource modification would need to power off the SZ instance prior to the change and then power on the same to take effect

The required resources for a type of deployment can be verified from:

1.        Virtual SmartZone Getting Started Guide – Section: Virtual SmartZone Minimum Requirements (https://docs.commscope.com/bundle/vsz-gettingstartedguide/page/GUID-217EBB12-8C20-48A6-A1F0-411FBC03...)
2.        Upgrade Guide – Section: Virtual SmartZone Minimum Requirements on the respective version

Cluster Scaling based on Number of APs and Switches:

Resource Requirements for on-Premise Deployment (based on SZ version 6.1.x):

Resource Requirements for Cloud Platform:

Generic Notes:

Increase the vSZ total memory 2~4 GB when running on special or extreme deploy environment when vSZ raise a memory exceed (90%) alarm. For example:

• Deploy 4-node vSZ cluster on Nutanix with full 30K AP capacity.
• One vSZ node down in 4-node vSZ cluster to long term sustain 30K AP in 3 alive vSZ nodes.
• The solution should be recovered the fail vSZ node as soon as possible. But if user need run 3 nodes with 30K AP in long term sustain, it need to increase the vSZ memory to run.
• All APs with full statistic reports (AVC, HCCD, UE, ...) to SZ on full load stress condition.

Required Disk Type

• AWS: General Purpose SSD (gp2)
• GCE: SSD
• Azure: Standard-SSD

If deployed hardware CPU computing performance is not good as recommended in 100 AP resource level, the 2 cores CPU setting cannot be supported. Upgrade to 4 cores instead of 2 cores in this case.

If deployed hardware CPU computing performance is not good as recommended Hypervisor (like Hyper-V) in 4-CPU setting to support 1000K AP, upgrade to 6 cores instead of 4 cores in this case.

The 6000 AP resource profile level could support to 4 nodes cluster. The total supported AP number will be up to 18,000 APs in a 4 node vSZ cluster.

One or more resources can be higher than the specified requirements. For example, if the instance requires 24Gb RAM, assigning 32Gb RAM is supported.