Skip to main content

Verifying cluster peer relationship and SVM peer relationship

Before you set up a volume for data protection by using SnapVault technology, you must verify that the source cluster and destination cluster are peered and are communicating with each other through the peer relationship. You must also verify that the source SVM and destination SVM are peered and are communicating with each other through the peer relationship.

About this task

You must perform this task from the source cluster.
  1. Verify that the cluster peer relationship was created: cluster peer show -instance

    Example

    Cluster1::> cluster peer show -instance

    Peer Cluster Name: cluster02
    Remote Intercluster Addresses: 192.140.112.101, 192.140.112.102
    Availability of the Remote Cluster: Available
    Remote Cluster Name: cluster2
    Active IP Addresses: 192.140.112.101, 192.140.112.102
    Cluster Serial Number: 1-80-123456
    Address Family of Relationship: ipv4
    Authentication Status Administrative: no-authentication
    Authentication Status Operational: absent
    Last Update Time: 02/05 21:05:41
    IPspace for the Relationship: Default

  2. You can also view the status of the SVM peer relationship and the applications running on the peer relationship.
    • View the details of the SVM peer relationship: vserver peer show

      Example

      cluster1::> vserver peer show

      Peer Peer
      Vserver Vserver State
      ----------- ----------- ------------
      vs1.example0.com vs3.example0.com peered
      1 entries were displayed.

    • View the applications running on the SVM peer relationship: vserver peer show-all

      Example

      cluster1::> vserver peer show-all

      Peer Peer Peering
      Vserver Vserver State Peer Cluster Applications
      ----------- ----------- -------- ----------- ----------
      vs1.example0.com vs3.example0.com peered cluster02 snapmirror