Table of ContentsView in Frames

Creating the cluster peer relationship

You create the cluster peer relationship using a set of intercluster logical interfaces to make information about one cluster available to the other cluster for use in cluster peering applications.

Before you begin

About this task

If you created intercluster LIFs in a nondefault IPspace, you need to designate the IPspace when you create the cluster peer.

Steps

  1. Create the cluster peer relationship on each cluster by using the cluster peer create command.
    The passphrase that you use is not displayed as you type it.
    If you created a nondefault IPspace to designate intercluster connectivity, you use the ipspace parameter to select that IPspace.
    Example
    In the following example, cluster01 is peered with a remote cluster named cluster02. Cluster01 is a two-node cluster that has one intercluster LIF per node. The IP addresses of the intercluster LIFs created in cluster01 are 192.168.2.201 and 192.168.2.202. Similarly, cluster02 is a two-node cluster that has one intercluster LIF per node. The IP addresses of the intercluster LIFs created in cluster02 are 192.168.2.203 and 192.168.2.204. These IP addresses are used to create the cluster peer relationship.
    cluster01::> cluster peer create -peer-addrs 192.168.2.203,192.168.2.204
    Please type the passphrase: 
    Please type the passphrase again:
    cluster02::> cluster peer create -peer-addrs 192.168.2.201,192.168.2.202
    Please type the passphrase: 
    Please type the passphrase again:

    If DNS is configured to resolve host names for the intercluster IP addresses, you can use host names in the –peer-addrs option. It is not likely that intercluster IP addresses frequently change; however, using host names allows intercluster IP addresses to change without having to modify the cluster peer relationship.

    Example
    In the following example, an IPspace called IP01A was created on cluster01 for intercluster connectivity. The IP addresses used in the previous example are used in this example to create the cluster peer relationship.
    cluster01::> cluster peer create -peer-addrs 192.168.2.203,192.168.2.204
    -ipspace IP01A
    Please type the passphrase: 
    Please type the passphrase again:
    cluster02::> cluster peer create -peer-addrs 192.168.2.201,192.168.2.202
    Please type the passphrase: 
    Please type the passphrase again:
  2. Display the cluster peer relationship by using the cluster peer show command with the -instance parameter.
    Displaying the cluster peer relationship verifies that the relationship was established successfully.
    Example
    cluster01::> cluster peer show –instance
    Peer Cluster Name: cluster02
    Remote Intercluster Addresses: 192.168.2.203,192.168.2.204
    Availability: Available
    Remote Cluster Name: cluster02
    Active IP Addresses: 192.168.2.203,192.168.2.204
    Cluster Serial Number: 1-80-000013
  3. Preview the health of the nodes in the peer cluster by using the cluster peer health show command.
    Previewing the health checks the connectivity and status of the nodes on the peer cluster.
    Example
    cluster01::> cluster peer health show
    Node       cluster-Name                Node-Name
                 Ping-Status               RDB-Health Cluster-Health  Avail…
    ---------- --------------------------- ---------  --------------- --------
    cluster01-01
               cluster02                   cluster02-01
                 Data: interface_reachable
                 ICMP: interface_reachable true       true            true
                                           cluster02-02
                 Data: interface_reachable
                 ICMP: interface_reachable true       true            true
    cluster01-02
               cluster02                   cluster02-01
                 Data: interface_reachable
                 ICMP: interface_reachable true       true            true
                                           cluster02-02
                 Data: interface_reachable
                 ICMP: interface_reachable true       true            true