Networking and LIF creation guidelines for MetroCluster configurations

You should be aware of how LIFs are created and replicated within the MetroCluster configuration, and you must also know about the requirement for consistency so you can make proper decisions when configuring your network .

IPspace configuration

IPspace names must match between the two sites.

IPspace objects must be manually replicated to the partner cluster. Any SVMs created and assigned to an IPspace before the IPspace is replicated will not be replicated to the partner cluster.

IPv6 configuration

If IPv6 is configured on one site, it must be configured on the other site.

LIF creation

You can confirm the successful creation of a LIF in a MetroCluster configuration by running the metrocluster check lif show. If there are issues, you can use the metrocluster check lif repair-placement command.

Duplicate LIFs

You should not create duplicate LIFs (multiple LIFs with the same IP address) within the same IPspace.

Intercluster LIFs

intercluster LIFs are limited to the default IPspace, owned by the admin SVM.

Replication of LIFs to the partner cluster

When you create a LIF on a cluster in a MetroCluster configuration, that LIF is replicated on the partner cluster. The system must meet the following conditions to place the replicated LIF on the partner cluster:

DR partner availability
The system attempts to place the replicated LIF on the DR partner of the node on which it was created.
Connectivity
- For IP or iSCSI LIFs, the system places them on a reachable subnet.
- For FCP LIFs, the system attempts to place them on a reachable FC fabric.
Port attributes
The system attempts to place the LIF on a port with the desired VLAN, adapter type, and speed attributes.

An EMS message is displayed if the LIF replication fails.

You can also check the failure by using the metrocluster check lif show command. Failures can be corrected by running the metrocluster check lif repair-placement command for any LIF that fails to find a correct port. You should resolve any LIF failures as soon as possible to ensure LIF operation in the event of a MetroCluster switchover operation.

Note: Even if the source Storage Virtual Machine (SVM) is down, LIF placement may proceed normally if there is a LIF belonging to a different SVM in a port with the same ipspace and network in the destination.

Placement of replicated LIFs when the DR partner node is down

When a LIF is created on a node whose DR partner has been taken over, the replicated LIF is placed on the DR auxiliary partner node. After a subsequent giveback, the LIFs are not automatically moved to the DR partner. This could lead to LIFs being concentrated on a single node in the partner cluster. In the event of a MetroCluster switchover operation, subsequent attempts to map LUNs belonging to the SVM will fail.

You should run the metrocluster check lif show after a takeover or giveback to ensure correct LIF placement. If errors exist, you can run the metrocluster check lif repair-placement command.