The following sections provide sizing guidance for zCenter instances in the public cloud.
Recommended Instance Sizing
zCenter Virtual Appliances
CPU and Memory
Consult the following table for the minimum recommended CPU and memory for an on-premises zCenter virtual appliance.
|
Part Number |
Max Endpoints |
Min Recommended CPU |
Min Recommended Memory (GB) |
|
ZVA-100 |
100 |
2 |
4 |
|
ZVA-500 |
500 |
4 |
4 |
|
ZVA-1K |
1,000 |
8 |
8 |
|
ZVA-5K |
5,000 |
8 |
16 |
|
ZVA-10K |
10,000 |
16 |
32 |
|
ZVA-20K |
20,000 |
24 |
64 |
Storage and Networking
The minimum storage requirement for a zCenter instance is 80GB, however, larger storage volumes are recommended to provide storage for logs. The zCenter is not sensitive to IOPS, and either SSD or magnetic storage are acceptable.
zCenter data connectivity requirements are not critical, as the control channel to each endpoint uses minimal bandwidth for presence detection/heartbeat and log collection.
Sizing for HA instances
HA instances should match the specs of the primary zCenter instance, to help ensure continued operation under load during a failover event.
ZNS Virtual Appliances
CPU and Memory
Consult the following table for the minimum recommended CPU and memory for an on-premises ZNS virtual appliance.
|
Part Number |
Max Throughput |
Min Recommended CPU |
Min Recommended Memory (GB) |
|
vZNS-2G |
1G in / |
4 |
4 |
|
vZNS-10G |
5G in / |
8 |
8 |
Storage and Networking
The minimum storage requirement for a ZNS instance is 80GB. The ZNS is not sensitive to IOPS, and either SSD or magnetic storage are acceptable.
The ZNS is used to bridge overlay connections across different network domains, and good network performance is critical for achieving the expected application performance. Multiple ZNS nodes may be clustered together to achieve arbitrarily large throughput.
Comments
0 comments
Article is closed for comments.