Note: This section is relevant only in situations for sharing vSAN datastore resources over the network. This section can be skipped if this is not in your plans.
With an HCI Mesh topology, the local vSAN datastore on a VxRail cluster can be shared with other VxRail clusters. This storage sharing model is applicable only in a multi-cluster environment where the VxRail clusters are configured under a common data center object on a common vCenter instance.
With a vSAN HCI Mesh network in place, VxRail cluster that leverage a local vSAN datastore for primary storage can also leverage the capacity on a remote vSAN datastore for application workload. If dynamic clusters will be part of the vSAN HCI mesh network, they can mount a remote vSAN datastore on a cluster with free vSAN storage capacity and use that as their primary storage resource.
Figure 29. Storage resource sharing between VxRail clusters with vSAN HCI mesh
If your plans include sharing storage resources between clusters in a vSAN HCI mesh, prepare your data center to meet the following prerequisites:
- A vCenter instance at a version that supports VxRail version 7.0.100 or later.
- A vSAN Enterprise license for each VxRail cluster that will participate in a vSAN HCI mesh topology.
Figure 30. Storage resource sharing between a cluster with a local vSAN datastore and dynamic clusters
If you share vSAN resources of a cluster with one or more VxRail dynamic clusters, you must adhere to the following pre-requisites:
- A vCenter instance at a version that supports VxRail version 7.0.240 or later.
- A vSAN Enterprise license is only required for the VxRail cluster that is sharing its vSAN storage resources. This license is not needed on a dynamic cluster.
Figure 31. Enable vSAN network connectivity between clusters
To enable vSAN HCI mesh, the data center must have a network topology that can enable connectivity of the vSAN networks on the two participating VxRail clusters.
- Two Ethernet ports on each node in the cluster will be configured to support vSAN network traffic.
- A common VLAN can be assigned to this vSAN network on each cluster so they can connect over a Layer 2 network. If the VxRail clusters are deployed against different top-of-rack switches, the VLAN must be configured to stretch between the switch instances.
- If the VxRail clusters are deployed against different top-of-rack switches, or if the common VLAN cannot be stretched between the switch instances, connectivity can be enabled using Layer 3 routing services. If this option is selected, be sure to assign routable IP addresses to the vSAN network on each participating VxRail cluster.