In AVS, HCX setup and planning,

Hi Lakshmi Narasimha Raju Atmakuri,
Thank you for reaching out to us on Microsoft Q&A forum.

Configuring Service Mesh for AVS HCX

To address your concerns, I'll outline the key considerations for designing Service Meshes for your on-premises environment with 3 vCenters, each with 2-3 clusters, and different management and vMotion network segments.

Key Factors:

1. Network segmentation: Create separate Service Meshes for each cluster to maintain network isolation.
2. vCenter and cluster boundaries: Consider creating separate Service Meshes for each vCenter or a single Service Mesh that spans across multiple vCenters.
3. Scalability and manageability: Balance the number of Service Meshes with manageability and scalability requirements.

Deciding Factors:

1. Network complexity: Create separate Service Meshes for complex network topologies.
2. Scalability requirements: Create multiple Service Meshes for large or rapidly growing environments.
3. Resource utilization: Consider resource utilization for each Service Mesh.

Site Pairs: The number of site pairs depends on the number of Service Meshes and connections required between them.

Recommendation: Create separate Service Meshes for each cluster to maintain network isolation and simplify the design. Alternatively, create a single Service Mesh that spans across multiple vCenters, but carefully plan and consider network topology and scalability requirements.

If you are still facing any issue, please let us know in the comments. We are glad to help you.

If the information is helpful, please Accept Answer so that it would be helpful to community members.