Establish Cluster Peering

 

Goal

This workflow will automate the establishment of a peer relationship between two Clustered ONTAP storage systems. Cluster peering allows two clusters to exchange data and the ability to initiate / request remote operations.  This step is a mandatory pre-requisite for SnapMirror data to flow between two clusters.  This workflow includes:

·         Creation of an intercluster Logical Interface (LIF) on each of the ports specified in the input for both the clusters. Provide at least one or two (recommended) port names on each node of each cluster to create the intercluster LIFs.

·         Naming the LIFs incrementally using the user inputs for Prefix, and the IP Addresses are also configured incrementally using the starting IP Address provided as user input.

 

Cluster to peer Input parameters:

 

 

 

1)       Cluster to be peered (required): The source Clustered ONTAP storage system where you would like the peering relationship established. This is a tabular list showing Name of the cluster, Primary address, Node count and Node Names.

 

 

 

 

2)       Broadcast Domain Name: The name of the broadcast domain from which ports should be selected for intercluster LIF creation. This is a tabular list showing the Broadcast Domain and Broadcast MTU. This option is applicable only for clustered Data ONTAP 8.3.0 and later.

3)       List of Node and Port Names (required): Multi select table that lists all the Node-Port combinations related to the selected Cluster. You need to select at least one Node-Port combination per Node in the cluster. Best Practice is to select 2 Node-Port combinations per Node in the cluster. Intercluster LIFs will be on the selected ports.

 

 

NOTE: Ports provided can be either intercluster ports or data ports. Use of intercluster ports can be used to ensure that intercluster traffic is segregated from the main data traffic. (UI will not differentiate between intercluster ports and data ports).

 

4)       InterCluster Interface Name Prefix (required): Prefix for the names of logical interfaces to be created on the cluster that is being peered. Each logical interface will have <prefix>_<n> where 'n' is the running number starting from 1.

5)       Starting IP Address for Logical Interfaces (required): Starting IP Address for Logical Interfaces. Each logical interface will be configured with an IP Address whose range starts from this given IP Address. Each subsequent interface’s IP will be incremented by 1.
Example: If <prefix>_1’s IP is 10.72.233.40 (Starting range), <prefix>_2’s IP will be 10.72.233.41 and so on.

6)       Netmask (required): Netmask for the IP address that is being configured on the logical interface.

7)       Netmask Length: Netmask length for the IP address that is being configured on the logical interface. You must use netmask length only for IPv6 addresses.

8)       Default Gateway (required): Default gateway for the intercluster logical interfaces.

 

 Peer Cluster Input parameters:

 

 

1)       Peer Cluster to be peered (required): The destination Clustered ONTAP storage system where you would like the peering relationship established. This would be a tabular list showing Name of the cluster, Primary address, Node count and Node Names.

 

 

2)       Broadcast Domain Name: The name of the broadcast domain from which ports should be selected for intercluster LIF creation. This is a tabular list showing the Broadcast Domain and Broadcast MTU. This option is applicable only for clustered Data ONTAP 8.3.0 and later.

3)       List of Node and Port Names (required): Multi select table that lists all the Node-Port combinations related to the selected Cluster. You need to select at least one Node-Port combination per Node in the cluster. Best Practice is to select 2 Node-Port combinations per Node in the cluster. Intercluster LIFs will be on the selected ports.

 

 

NOTE: Ports provided can be either intercluster ports or data ports. Use of intercluster ports can be used to ensure that intercluster traffic is segregated from the main data traffic. (UI will not differentiate between intercluster ports and data ports).

 

4)       InterCluster Interface Name Prefix (required): Prefix for the names of logical interfaces to be created on the cluster that is being peered. Each logical interface will have <prefix>_<n> where 'n' is the running number starting from 1.

5)       Starting IP Address for Logical Interfaces (required): Starting IP Address for Logical Interfaces. Each logical interface will be configured with an IP Address whose range starts from this given IP Address. Each subsequent interface’s IP will be incremented by 1. Example: If <prefix>_1’s IP is 10.72.233.40 (Starting range), <prefix>_2’s IP will be 10.72.233.41 and so on.

6)       Netmask (required): Netmask for the IP address that is being configured on the logical interface.

7)       Netmask Length: Netmask length for the IP address that is being configured on the logical interface. You must use netmask length only for IPv6 addresses.

8)       Default Gateway (required): Default gateway for the intercluster logical interfaces.

 

Result

The workflow will result in establishing a peering relationship between the two Cluster-Mode clusters.