Virtual SmartZone Required Resources

Before upgrading vSZ to this release, verify that the virtual machine on which vSZ is installed has sufficient resources to handle the number of APs and wireless clients that you plan to manage. See the tables below for the required virtual machine system resources.

The values for vCPU, RAM, and Disk Size are linked together and cannot be changed individually. When changing one of these parameters, all three values need to match exactly with an existing Resource Level. Taking vSZ-H Resource Level 5 as an example: when adjusting the number of vCPU from 4 to 6, the amount of RAM needs to be adjusted to 22GB and the Disk Size needs to be adjusted to 300GB, thereby matching all the values of Resource Level 6.

Warning:

These vSZ required resources may change from release to release. Before upgrading vSZ, always check the required resource tables for the release to which you are upgrading.

Note:

When initially building up the network it can use a higher Resource Level than needed for the number of APs first deployed, if all the three parameters (vCPU, RAM and Disk Size) match exactly with that higher Resource Level.

Attention:

It is recommended that there should be only one concurrent CLI connection per cluster when configuring vSZ.

In the following tables the high scale resources are broken into two tables for easy readability. These tables are based on the AP Count Range.

Table 1. vSZ High Scale required resources

AP Count Range

Max Clients

Nodes per Cluster

AP Count per Node (without switch)

AP/Switch Capacity Ratio

Switch Per Node(without AP)

From

To

Max

Max

10,001

30,000

300,000

4

10,000

8 : 1

1,250

20,000

200,000

3

8 : 1

1,250

5,001

10,000

100,000

1-2

10,000

8 : 1

1,250

2,501

5,000

50,000

1-2

5,000

8 : 1

625

1,001

2,500

50,000

1-2

2,500

8 : 1

312

501

1,000

20,000

1-2

1,000

5 : 1

200

101

500

10,000

1-2

500

5 : 1

100

1

100

2,000

1-2

100

5 : 1

20

Table 2. vSZ High Scale required resources

AP Count Range

vCPU

RAM

Disk Size

Preserved Events

Concurrent CLI Connection

Resource Level

From

To

Logic Processor [1][2] [3]

GB [3]

GB

Max

Max (per node not per cluster)

10,001

30,000

24

48

600

3 M

4

8

20,000

5,001

10,000

24

48

600

3 M

4

7

2,501

5,000

12

28

300

2 M

2

6.5

1,001

2,500

6

22

300

1.5 M

2

6

501

1,000

4

18

100

600 K

2

5

101

500

4

16

100

300 K

2

4

1

100

2

13

100

60 K

2

3

In the following tables the essential scale resources are broken into two tables for easy readability. These tables are based on the AP Count Range.

Table 3. vSZ Essentials required resources

AP Count Range

Maximum Clients

Nodes per Cluster

AP Count per Node

AP/Switch Capacity Ratio

Switch Per Node (without AP)

From

To

Max

Max

1025

3,000

60,000

4

1,024

5 : 1

200

2,000

40,000

3

5 : 1

200

501

1,024

25,000

1-2

1,024

5 : 1

200

101

500

10,000

1-2

500

5 : 1

100

1

100

2,000

1-2

100

5 : 1

20

Table 4. vSZ Essentials required resources

AP Count Range

vCPU

RAM

Disk Size

Preserved Events

Concurrent CLI Connection

Resource Level

From

To

Logic Processor [1][2][3]

GB [3]

GB

Max

Max (per node not per cluster)

1025

3,000

8

18

250

10 K

2

3

2,000

501

1,024

8

18

250

10 K

2

2

101

500

4

16

100

5 K

2

1.5

1

100

2

13

100

1 K

2

1

Note:

Logic Processor 1 vCPU requirement is based on Intel Xeon CPU E5- 2630v2 @2.60 GHz.

Logic Processor 2 Azure with low CPU throughput unsupported. The vSZ with the lowest resource plan (2 core CPU, 13 GB memory) can NOT be supported due to the low CPU throughput on Azure.

Logic Processor 3 vSZ-H and vSZ-E have different report interval. For example, AP sends the status to vSZ-E every 90 seconds but to vSZ-H it is sent every 180 seconds, which means that vSZ-E need more CPU in scaling environment based on the resource level.