Home > Storage > PowerStore > Data Protection > Dell PowerStore: Metro Volume > Supported configurations
Metro Volume connectivity requirements may vary depending on intended and actual use. For example, requirements for using Metro Volume to migrate a workload of powered off virtual machines is going to be significantly different than migrating virtual machines that are powered on and highly active.
A native PowerStore Metro Volume can be configured on all PowerStore T models running PowerStoreOS 3.0 or later in a vSphere Metro Storage Cluster (vMSC) configuration. A vMSC can provide a vSphere stretched cluster architecture. For the host configuration PowerStore supports non-uniform host access which uses only local path, and Uniform host access which provides extra cross connectivity to the remote PowerStore cluster.
We recommend using dedicated VLANs or fabrics to isolate IP-based storage traffic from other types of general-purpose LAN traffic, especially when spanning data centers. While this recommendation is not a requirement for Metro Volume, it is a general best practice for IP-based storage.
Besides the existing requirements for PowerStore replication, the following restrictions and requirements apply for Metro Volume:
Note: The PowerStore TCP-based replication protocol uses TCP ports in the range of 13333-13337 depending on the network latency configuration of the remote system. Ensure firewall rules between PowerStore clusters with Metro Volumes allow these ports to pass traffic.
Note: SCSI-3 persistent reservations, vSphere Raw Device Mappings (RDMs), and shared VMFS VMDK virtual disks are not supported with Metro Volume.