DR CONFIG REPLICATION FAILED Reason: Onboard key management is already configured
- Views:
- 695
- Visibility:
- Public
- Votes:
- 1
- Category:
- metrocluster
- Specialty:
- metrocluster
- Last Updated:
- 11/26/2021, 8:11:03 AM
Applies to
- MetroCluster
- Config Replication Service
- ONTAP 9
Issue
An autosupport is triggered for DR CONFIG REPLICATION FAILED and an error message similar to the below is observed in METROCLUSTER-VSERVER.XML:
Cluster : ClusterA
Vserver : SVM1
Partner Vserver : SVM1-mc
Configuration State : syncing
Stream Status : processing-task
Failed Row : Table Name: volume, Operation: get, Fields: SVM1-mc volume aggr <volume details> Table Name: volume_object_repl_attrs, Operation: get, Fields: - Enabled false - - -
Failed Reason : Apply failed for Object: volume Method: baseline. Reason: Onboard key management is already configured. To sync any nodes with onboard key management configuration, run the "security key-manager onboard sync" command. Provide the cluster-wide passphrase initially configured for the cluster
Last apply fail time : 3/29/2020 12:25:41