Skip to main content
NetApp Knowledge Base

vserver peer deletion failed

  1. Last updated
  2. Save as PDF
Views:
501
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
dp
Last Updated:

Applies to

ONTAP 9

Issue

Vserver peering deletion failed with the below error.
 

::> vserver peer delete -vserver XXXX -peer-vserver XXXXX
Info: [Job 1935] 'vserver peer delete' job queued

::*> job show 1935
                            Owning
Job ID Name                 Vserver    Node           State
------ -------------------- ---------- -------------- ----------
1935   'vserver peer delete' XXXXX XXXXX Failure
       Description: Deleting a Vserver peer relationship between XXXXX and XXXXX

::*> job show 1935 -inst

                      Job ID: 1935
              Owning Vserver: XXXXX
                        Name: 'vserver peer delete'
                 Description: Deleting a Vserver peer relationship between XXXXX and XXXXX
                    Priority: Medium
                        Node: XXXXX
                    Affinity: Cluster
                    Schedule: @now
                  Queue Time: 08/29 10:54:04
                  Start Time: 08/29 10:54:04
                    End Time: 08/29 10:54:04
              Drop-dead Time: -
                  Restarted?: false
                       State: Failure
                 Status Code: 1263375
           Completion String: Failed to communicate with peer cluster. Reason: (Failed to contact peer cluster with name "XXXXX" at addresses: X.X.X.X, X.X.X.X. No operational intercluster LIFs of the IPv4 address family are available on this node.). Intercluster logical interfaces (LIFs) on both the clusters must be up. Use the "network interface show" command to display logical interface information. Cluster peering relationship must be healthy. Use the "cluster peer health show -bypass-cache true" command to display cluster peering health. If the remote cluster is not available, use "-force" to perform local processing only. The remote cluster will need to be configured manually.
                    Job Type: vserver peer delete
                Job Category: vserver peer
                        UUID: XXXX-465a-11ee-a757-XXXX
          Execution Progress: Complete: Failed to communicate with peer cluster. Reason: (Failed to contact peer cluster with name "XXXXX" at addresses: X.X.X.X, X.X.X.X. No operational intercluster LIFs of the IPv4 address family are available on this node.). Intercluster logical interfaces (LIFs) on both the clusters must be up. Use the "network interface show" command to display logical interface information. Cluster peering relationship must be healthy. Use the "cluster peer health show -bypass-cache true" command to display cluster peering health. If the remote cluster is not available, use "-force" to perform local processing only. The remote cluster will need to be configured manually. [1263375]
                   User Name: XXXXX
                     Process: mgwd
  Restart Is or Was Delayed?: false
Restart Is Delayed by Module: -


 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.