You must configure the MetroCluster IP (MCCIP) interfaces that are used for replication of each node's storage and nonvolatile cache. You then establish the connections using the MCCIP interfaces. This creates iSCSI connections for storage replication.
You must create two interfaces for each node. The interfaces must be associated with the VLANs defined in the MetroCluster RCF file.
You must create all MetroCluster IP interface 'A' ports in the same VLAN and all MetroCluster IP interface 'B' ports in the other VLAN.
The following platform models use VLANs.
AFF platforms | FAS platforms |
---|---|
|
|
Node | Interface | IP address | Subnet |
---|---|---|---|
node_A_1 | MetroCluster IP interface 1 | 10.1.1.1 | 10.1.1/24 |
MetroCluster IP interface 2 | 10.1.2.1 | 10.1.2/24 | |
node_A_2 | MetroCluster IP interface 1 | 10.1.1.2 | 10.1.1/24 |
MetroCluster IP interface 2 | 10.1.2.2 | 10.1.2/24 | |
node_B_1 | MetroCluster IP interface 1 | 10.1.1.3 | 10.1.1/24 |
MetroCluster IP interface 2 | 10.1.2.3 | 10.1.2/24 | |
node_B_2 | MetroCluster IP interface 1 | 10.1.1.4 | 10.1.1/24 |
MetroCluster IP interface 2 | 10.1.2.4 | 10.1.2/24 |
The physical ports used by the MetroCluster IP interfaces depends on the platform model, as shown in the following table.
Platform model | MetroCluster IP port | VLAN ID | |
---|---|---|---|
AFF A800 | e0b | Not used | |
e1b | |||
AFF A700 and FAS9000 | e5a | ||
e5b | |||
AFF A320 | e0g | ||
e0h | |||
AFF A300 and FAS8200 | e1a | ||
e1b | |||
AFF A220 and FAS2750 | e0a | 10 | On these systems, these physical ports are also used as cluster interfaces. |
e0b | 20 | ||
AFF A250 and FAS500f | e0c | 10 | |
e0d | 20 |
The port usage in the following examples is for an AFF A700 or a FAS9000 system.