The names of IPspaces to which the partner interfaces are assigned must be the same on both storage systems.
For example, in a cluster pair of StorageSystem A and StorageSystem B, if IPspaceA is created on StorageSystem A, an IPspaceA must also exist on StorageSystem B.
The partner interfaces on both partners must be assigned to the same-name IPspaces on their respective storage systems.
For example, in a cluster pair of StorageSystem A and StorageSystem B, interface e4 of StorageSystem B is the takeover interface of interface e0 of StorageSystem A, and vice versa. If interface e0 belongs to IPspaceA on StorageSystem A, interface e4 must belong to IPspaceA on StorageSystem B.
In an asymmetric cluster setup, vFiler unit-IPspace configuration on one cluster partner is different from the other; for example, each partner might have a different number of vFiler units configured in a specific IPspace, or one partner might have no vFiler units.
A "standby" cluster configuration is an example of an asymmetric cluster setup in which one of the hosts is connected to minimal storage of its own. This host takes over its partner's storage and vFiler units if the partner fails. In such a configuration, the standby host might not have enough storage to support the number of vFiler units that the primary host has. To specify the partner interface when setting up such a cluster configuration, you can use the interface name of the partner instead of the IP address.
For example, two storage systems, StorageSystem1 and StorageSystem2, are configured as shown in the following table.
To specify partner interfaces on Storage System1, complete the following step.
To specify partner interfaces on Storage System2, complete the following steps.
| 1 | |
| 2 | |
| 3 |
Create a host-partner relationship on Storage System2 in the following way: ifconfig e0 1.1.1.2 netmask 255.255.255.0 partner e0 |
Copyright © 1994-2005, Network Appliance, Inc. All rights
reserved.
Part No. 210-01078-B0
File: ipspace4.htm
Last updated: 08-Dec-2005 13:31:50