LIF interface of SVM is inconsistent between MetroCluster sites
Applies to
- MetroCluster
- SnapMirror
- SnapVault
Issue
- AutoSupport report "HA Group Notification (DR CONFIG REPLICATION FAILED) ERROR"
- MetroCluster check lif report warning:
Discovery of LIF with address 172.xx.xx.xx failed from destination cluster Ensure that the destination cluster has ports that have connectivity to the LIF on the source cluster."
- MetroCluser vserver stuck at "syncing" state with warning:
Table Name: snapmirror, Operation: get, Fields: OA05:OAxxx_O2S - OAFILE05 OAxxx_O2S XDP - 0 0d708367-852a-11ed-8d9e-d039ea17e9f8 3221226050 1073742402 SWxxxx01:OAxxx_O2S - SWxxxx01 OAxxx_O2S XDP none SWxxxx01-mc 1min - OAFILE05_O2S - unlimited - - - Idle - - - - - - - - - - - - - 2cf2111d-852d-11ed-8d9e-d039ea17e9f8 47c03a46-7ab6-11ed-8d9e-d039ea17e9f8 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Extended_data_protection - - - - - - - - - - - 3221226040 1073742392 2d0292c0-5210-11ec-adf7-d039ea17e9f8 - - - - - - - - false - - - - - - - - - -
- The problematic SnapMirror policy has
transfer schedule
andthrottle
defined on the policy. - But some policies can be replicated to the DR site even if the policy has
transfer schedule
andthrottle
defined on the policy. - The KB article MetroCluster Vservers can be out of sync because of SnapMirror\SnapVault Policy errors can not be used to fix the issue because the existing policy can not be modified