Skip to main content
NetApp Knowledge Base

MetroCluster vserver changes not replicated

Views:
209
Visibility:
Public
Votes:
1
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

Applies to

  • MetroCluster
  • ONTAP 9
  • MetroCluster vserver changes not replicated between clusters

Issue

In this example a vserver has been deleted on cluster02 but this change is not replicated to cluster01 and the DR vserver is not deleted. The vserver is still visible in the output of metrocluster vserver show on cluster01 and Configuration State is unhealthy.

cluster01
Cluster Name         Vserver            Partner                     Configuration State        
cluster01            Vserver001         Vserver001-mc               healthy            
cluster01            cluster01          cluster02                   healthy            
cluster02            cluster02          cluster01                   healthy
cluster02            Vserver002         Vserver002-mc               unhealthy

cluster02
Cluster Name        Vserver            Partner                     Configuration State
cluster01           Vserver001         Vserver001-mc               healthy
cluster01           cluster01          cluster02                   healthy
cluster02           cluster02          cluster01                   healthy

The following errors will be present in MGWD logs

server=mgwd: RPC: Timed out; netid=tcp fd=695 TO=60.0s TT=60.000s O=23576b I=0b CN=31985/17 VSID=-1 192.168.12.13:11104RPC: Timed out; netid=tcp fd=675 TO=60.0s TT=60.000s O=2912b I=0b CN=25923/3 VSID=-1 192.168.12.10:11104
server=mgwd: RPC: Timed out; netid=tcp fd=695 TO=60.0s TT=60.000s O=23576b I=0b CN=31985/17 VSID=-1 192.168.12.13:11104RPC: Timed out; netid=tcp fd=695 TO=60.0s TT=60.000s O=23576b I=0b CN=31985/17 VSID=-1 192.168.12.20:11104

In this example the 192.168.12.X IP addresses are the intercluster lifs and port 11104 is used by the Config Replication Service (CRS)

 

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.