DR CONFIG REPLICATION FAILED caused by stale LIF configuration on destination
Applies to
Issue
- Receiving (DR CONFIG REPLICATION FAILED) ERROR messages
- Review of event logs found root cause of duplicate IPs:
Fri Feb 03 21:48:56 -0600 [netapp1-01: mgwd: vsdr.net.IPInDiffVserver:error]: Cannot create LIF LIF1 with IP address 10.192.168.24 in Vserver SVM2-mc because another LIF with the same IP exists in another Vserver.
Fri Feb 03 21:49:42 -0600 [netapp1-01: crs: callhome.dr.apply.failed:error]: Call home for DR CONFIG REPLICATION FAILED
- LIF associated with the message is a stale entry on the destination
-
Destination cluster unable to create LIF:
Vserver: SVM2-mc
LIF: LIF1
IP: 10.192.168.24When looking at the network interface information we see the destination
cluster has an existing LIF in different vserver:Vserver: SVM1-mc
LIF: LIF1
IP: 10.192.168.24While on the source cluster has the network interface information
correlating with the EMS alert:Vserver: SVM2
LIF: LIF1
IP: 10.192.168.24
-
- LIF1 created on source under SVM1 and properly synced to destination SVM1-mc
- Deleted LIF1 on source SVM1 and created same LIF1 on SVM2 on source
- Destination never deleted LIF1 on SVM1 causing the duplicate IP messages
- Metrocluster vserver show degraded
- Metrocluster check LIF degraded