A customer asks what is the correct way to configure an ONTAP system for multi-tenancy. The customer wants to serve data and also protect data using
SnapMirror from tenant A using network A and from tenant B using network B.
In this scenario, which statement is correct?
To configure an ONTAP system for multi-tenancy and ensure tenant A and tenant B can serve and protect data using their respective networks, the customer must set up two different IPspaces. IPspaces allow for the isolation of network traffic, administration, and IP address spaces, ensuring that no cross-traffic occurs between the tenants, thus providing a proper multi-tenant environment.
An IPspace defines a distinct IP address space (which is a subnet) of which SVMs and Broadcast Domains (of which consist of network ports - such as ifgroups or physical ports) reside. An IPspace is a logical container that consists of Storage VMs and ( Broadcast Domains) } • Ports and IP addresses that are defined for an IPspace are applicable only within that IPspace. • A Distinct routing table is maintained for each SVM within an IPspace. Therefore, no cross SVM traffic or no cross IP traffic routing occurs within the IPspace The primary use case for this feature (which is IPspaces and each SVM having its own routing table maintained) is the Storage service provider that needs to connect customers to Company A and Company B to the SAME storage systems on the storage service providers premises.
• An IPspace is a logical container that consists of Storage VMs and ( Broadcast Domains - (containing network ports - of either Ifgroups or physical ports ) ) that is used to create administratively separate network domains. • An IPspace defines a distinct IP address space (subnet) that contains storage VMs (or storage virtual machines or SVMs) ○ IPspaces are similar to VLANs for network traffic but for storage virtual machines.
https://docs.netapp.com/us-en/ontap/peering/ipspaces-isolate-replication-traffic-concept.html