A typical application of an IPspace is when a Storage Service Provider (SSP) needs to connect customers of companies A and B to a storage system on the SSP's premises.
The SSP creates two vFiler units on the physical storage system—one per customer—and provides a dedicated network path from one vFiler unit to A’s network and one from the other vFiler unit to B’s network.
This deployment should work if both companies use non-private IP address ranges. However, the following illustration shows both companies using the same private address ranges:
Both companies use the private IP address subnet 10.0.0.0, causing the following problems:
To overcome these problems, two IPspaces are defined on the storage system—one per vFiler unit. Because a distinct routing table is maintained for each IPspace and no cross-IPspace traffic is routed, the data for each company is securely routed to its respective network even if the two vFiler units are configured in the 10.0.0.0 address space, as shown in the following illustration:
Additionally, the IP addresses referred to by the various configuration files, such as the /etc/hosts file, the /etc/hosts.equiv file, and the /etc/rc file, are relative to that IPspace. Therefore, the IPspaces allow the SSP to configure the same IP address for the configuration and authentication data for both vFiler units, without conflict.