Skip to main content
NetApp Knowledge Base

What is use case of IPSPACE in Clustered Data ONTAP if the IPs and subnets are not overlapping?

  1. Last updated
  2. Save as PDF
Views:
509
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • Cluster Data ONTAP 8.3 and later
  • ONTAP 9 and later

Answer

  • There is no use case of IPSPACE in clustered Data ONTAP or in ONTAP 9 if the IPs and subnets are not overlapping.
  • Virtual segregation of network or infrastructure can be achieved by using multiple SVMs in same default IPSPACE instead of using custom IPSPACE if they don't have overlapping IP addresses.

Additional Information

  • Beginning in NetApp clustered Data ONTAP 8.3, users have the ability to create unique IPspaces (or they might choose to use only the default IPspace). 
  • The IPspace feature enables a single storage cluster to be accessed by clients from more than one disconnected network, even if those networks have overlapping IP addresses. 
  • The IPspace object is not new to Data ONTAP and clustered Data ONTAP, there are similarities and differences with IPspaces in clustered Data ONTAP 8.3. 
  • One significant difference to keep in mind with IPspaces in clustered Data ONTAP 8.3 versus Data ONTAP operating in 7-Mode is that in 7-Mode, each Virtual Interface shared a routing table. 
  • But with clustered Data ONTAP 8.3, each SVM maintains its own routing table:

clipboard_e24e6df29b8e4681aa20cd78ad1a493c2.png

 

  • In the networking world, IPspaces are equivalent to Virtual Routing and Forwarding, a technology that allows multiple instances of a routing table to coexist on the same piece of networking infrastructure.
  • Two hosts in two different IPspaces can have the same IP address and not conflict with each other.
  • This feature is useful if, for example, different entities are being collapsed onto the same infrastructure. 
  • The transition is made simpler if you do not have to ask the host-side administrators or developers to change IP addresses or host-name references.
  • For more details, please read theTR-4182 Page 8-9.

 

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.