Can I extend an already created cluster?
Yes, extending a cluster is supported up to 10 nodes.
What happens if a non-primary platform VM becomes unavailable?
Internal services have limited resiliency to non-primary node failures. In general, due to a node failure NI loses compute power.
What kind of load balancing is supported?
Mapping of proxy to platform is fixed. Once data from any Proxy VM reaches any Platform VM, its processing is load-balanced internally among all the Platform VMs.
Will creating a platform cluster increase bandwidth consumption?
The proxy or collector VMs continue to talk only to primary or platform VM. The bandwidth requirement for platform VM clustering communication is minimal. Therefore there is no significant increase in bandwidth consumption.
What is the frequency of data transmission between proxy VM to platform VM?
The proxy VM sends the deduplicated or compressed data continuously to the platform VM.
Does any optimization of data take place in the proxy VM?
Various deduplications, compressions, reduction, or batching steps happen in the proxy VM. When the connection between the platform VM and the proxy VM is down, the proxy VM stores data locally (depending on the disk space) and sends it whenever the connection is restored.
Is there any optimization done for network bandwidth?
Yes, various deduplication/compressions/reduction/batching steps happen on the proxy VM.
Is clustering possible on the proxy servers?
No. Clustering is not possible on the proxy servers.
How does vCenter send traffic to the proxy server?
vCenters do not send traffic to the proxy server. The proxy servers actually connect to their designated vCenter to fetch the information.
When deploying a cluster , how does vCenter send traffic to the various proxy servers?
Actually proxies get connected to vCenter to fetch the information. Respective proxy will connect to designated vCenter & fetch the information. There is no clustering available on proxy